| Commit message (Collapse) | Author | Age | Files | Lines |
|
|
|
|
|
|
|
|
| |
This reverts commit 41381c19d1f3920ee9540aff0d35209cb43fb057.
Reason: This doesn't quite fit the flow where it's added. Let's add this
someplace else if it's explicitly required.
[ci skip]
|
| |
|
|
|
|
| |
These tips were documenting an inconsistency issue https://github.com/rails/rails/issues/8621. That issue is resolved by https://github.com/rails/rails/issues/8622.
|
| |
|
|\ |
|
| | |
|
| |
| |
| |
| |
| |
| |
| |
| |
| | |
The current section on controller specific assets does not really explain how the default application.css and application.js files
generated by rails will work with controller specific assets and is a bit ambiguous. We should remind users that they will be included
into their application by default but that they have the option to include them only where needed if they want and how this works with
precompiling assets.
[ci_skip]
|
| |
| |
| |
| |
| | |
Somehow this got lost in my PRs before. I'm going to re-check all the
guides to make sure this didn't happen again elsewhere.
|
|/ |
|
|\
| |
| |
| |
| |
| | |
Conflicts:
actionpack/lib/action_view/helpers/form_helper.rb
railties/lib/rails/info_controller.rb
|
| | |
|
| | |
|
| |
| |
| |
| |
| |
| |
| |
| | |
https://github.com/lifo/docrails/commit/55a2820cc6d33e96b8d1b64b38b033913058dce4
messes up
https://github.com/lifo/docrails/commit/cfd324b4b68469ba3188e4b7ba8586e59b239693
Hopefully there is other stuff lost in translation...
|
| |
| |
| |
| | |
application.
|
| | |
|
| |
| |
| |
| |
| |
| |
| | |
Don't use:
* Time.time_with_datetime_fallback
* Time.utc_time
* Time.local_time
|
| |
| |
| | |
It's no longer necessary to delete public/index.html for the root route to take effect.
|
| | |
|
| | |
|
| | |
|
| | |
|
| |
| |
| |
| |
| |
| | |
I was slightly overzealous when removing this before.
Identified here: https://github.com/rails/rails/commit/ed78770b1a13788a5d3fcae484f34654de580bd5\#commitcomment-2281181
|
| | |
|
| | |
|
| |
| |
| |
| |
| |
| | |
Since mass assignment doesn't exist anymore, we don't need to discuss it.
I checked with @fxn last night before making this change.
|
|\ \
| | |
| | |
| | |
| | |
| | |
| | | |
rmcastil/add_migration_example_to_each_association_type
Add migration examples to Association Basics
[ci skip]
|
| | | |
|
| | | |
|
|\ \ \
| | | |
| | | | |
Use Rails to Render Default Index Page
|
| | | |
| | | |
| | | |
| | | |
| | | |
| | | |
| | | |
| | | |
| | | |
| | | |
| | | |
| | | |
| | | |
| | | |
| | | | |
This is an alternative implementation to #7771 thanks to the advice of @spastorino
Rails is a dynamic framework that serves a static index.html by default. One of my first questions ever on IRC was solved by simply deleting my public/index.html file. This file is a source of confusion when starting as it over-rides any set "root" in the routes yet it itself is not listed in the routes. By making the page dynamic by default we can eliminate this confusion.
This PR moves the static index page to an internal controller/route/view similar to `rails/info`. When someone starts a rails server, if no root is defined, this route will take over and the "dynamic" index page from rails/welcome_controller will be rendered. These routes are only added in development. If a developer defines a root in their routes, it automatically takes precedence over this route and will be rendered, with no deleting of files required.
In addition to removing this source of confusion for new devs, we can now use Rails view helpers to build and render this page. While not the primary intent, the added value of "dogfooding" should not be under-estimated.
The prior PR #7771 had push-back since it introduced developer facing files. This PR solves all of the same problems, but does not have any new developer facing files (it actually removes one).
cc/ @wsouto, @dickeyxxx, @tyre, @ryanb, @josevalim, @maxim, @subdigital, @steveklabnik
ATP Railties and Actionpack.
|
|/ / /
| | |
| | |
| | |
| | |
| | |
| | | |
This can be done using the class attribute cache_timestamp_format
Conflicts:
railties/guides/source/configuring.textile
|
| | | |
|
|\ \ \
| | | |
| | | |
| | | |
| | | | |
Include command to create mysql user
[ci skip]
|
| | | |
| | | |
| | | |
| | | |
| | | | |
The guide mentions that the 'rails' user is needed, but doesn't
explicitly include the command to do so.
|
|\ \ \ \
| | | | |
| | | | | |
Kindle ebook generation with working section navigation
|
| | | | | |
|
| |_|_|/
|/| | | |
|
|\ \ \ \ |
|
| | | | | |
|
| | | | |
| | | | |
| | | | |
| | | | |
| | | | |
| | | | |
| | | | |
| | | | | |
This reverts commit 83cb6fbd13f3c5ea3106b9a57964b1a6fb243682.
Reason: very trivial
[ci skip]
|
| | | | | |
|
| | | | | |
|
| | | | |
| | | | |
| | | | |
| | | | |
| | | | | |
Mailers are always async now, and we already discuss
queueing lower down in the guide.
|
| | | | |
| | | | |
| | | | |
| | | | |
| | | | |
| | | | |
| | | | |
| | | | | |
There's no reason for guides to reference old behaviors. They should
be current as of the versions of Rails that they ship with, and including
older information just clutters thing.
I discussed this change with @fxn and he agrees.
|
| | | | | |
|
| | | | | |
|
| | | | | |
|
| | | | | |
|
| | | | | |
|
| | | | | |
|