aboutsummaryrefslogtreecommitdiffstats
path: root/guides/source/upgrading_ruby_on_rails.md
Commit message (Collapse)AuthorAgeFilesLines
* Preserve existing attachment assignment behavior for upgraded appsGeorge Claghorn2019-07-201-0/+48
| | | | | | | | | Assigning to a collection of attachments appends rather than replacing, as in 5.2. Existing 5.2 apps that rely on this behavior will no longer break when they're upgraded to 6.0. For apps generated on 6.0 or newer, assigning replaces the existing attachments in the collection. #attach should be used to add new attachments to the collection without removing existing ones. I expect that we'll deprecate the old behavior in 6.1. Closes #36374.
* let the upgrading guide point to the autoloading guide for STIs [skip ci]Xavier Noria2019-07-131-14/+1
|
* simplifies Zeitwerk compat instructions in upgrading guide [skip ci]Xavier Noria2019-07-121-35/+5
|
* ports edits to the upgrading guide [skip ci]Xavier Noria2019-07-121-0/+23
|
* adds two sections to the upgrading notes for autoloading [skip ci]Xavier Noria2019-06-301-0/+16
|
* Reword the ActionDispatch::Response#content_type change [ci skip]Sharang Dashputre2019-06-021-4/+4
|
* Change `ActionDispatch::Response#content_type` returning Content-Type header ↵yuuji.yaginuma2019-06-011-0/+22
| | | | | | | | | | | | | | | | | | | | | | | | | | as it is Since #35709, `Response#conten_type` returns only MIME type correctly. It is a documented behavior that this method only returns MIME type, so this change seems appropriate. https://github.com/rails/rails/blob/39de7fac0507070e3c5f8b33fbad6fced84d97ed/actionpack/lib/action_dispatch/http/response.rb#L245-L249 But unfortunately, some users expect this method to return all Content-Type that does not contain charset. This seems to be breaking changes. We can change this behavior with the deprecate cycle. But, in that case, a method needs that include Content-Type with additional parameters. And that method name is probably the `content_type` seems to properly. So I changed the new behavior to more appropriate `media_type` method. And `Response#content_type` changed (as the method name) to return Content-Type header as it is. Fixes #35709. [Rafael Mendonça França & Yuuji Yaginuma ]
* shortens a comment [ci skip]Xavier Noria2019-05-141-1/+1
| | | | To avoid word wrap in the rendered guide.
* Merge pull request #36245 from vishaltelangre/patch-4Vipul A M2019-05-121-3/+4
|\ | | | | [ci skip] Clarity about embed metadata in signed and encrypted cookie
| * [ci skip] Clarity about embed metadata in signed and encrypted cookieVishal Telangre2019-05-121-3/+4
| |
* | upgrading docs: one file => one constant [ci skip]Xavier Noria2019-05-121-0/+29
|/
* Merge pull request #36241 from ↵Xavier Noria2019-05-111-1/+1
|\ | | | | | | | | vishaltelangre/fix-confusing-sentence-in-upgrade-guide [ci skip] Fix confusing sentence in upgrade guide
| * [ci skip] Fix confusing sentence in upgrade guideVishal Telangre2019-05-111-1/+1
| |
* | Corrected the sentence in upgrade guideshekhar-patil2019-05-111-1/+1
|/
* fixes configuration examples [ci skip]Xavier Noria2019-05-091-3/+3
|
* documents restriction for explicit namespaces [ci skip]Xavier Noria2019-05-081-0/+34
|
* documents how to use the classic autoloader in Rails 6 [ci skip]Xavier Noria2019-05-081-0/+11
|
* documents autoloading in the upgrading guide [ci skip]Xavier Noria2019-05-081-0/+172
|
* [ci skip] Get npm just the way they like itKasper Timm Hansen2019-04-251-1/+1
|
* [ci skip] Documentation pass of upgrading guide.Kasper Timm Hansen2019-04-251-14/+14
|
* Update links and code examples in the guides to use HTTPS where the host ↵Nathaniel Suchy2019-03-061-1/+1
| | | | supports it.
* Document the ActionCable JS changes in the upgrade guide & release notesRichard Macklin2019-01-141-0/+36
|
* Require Ruby 2.5 for Rails 6.Kasper Timm Hansen2018-12-191-1/+1
| | | | | | | | | | Generally followed the pattern for https://github.com/rails/rails/pull/32034 * Removes needless CI configs for 2.4 * Targets 2.5 in rubocop * Updates existing CHANGELOG entries for fewer merge conflicts * Removes Hash#slice extension as that's inlined on Ruby 2.5. * Removes the need for send on define_method in MethodCallAssertions.
* Fix typo in per-form CSRF token docs [ci skip]Randy Antler2018-12-071-1/+1
|
* Fix spellings for 'unmarshall(ing/ed)' & 'marshall(ing/ed)'Sharang Dashputre2018-10-021-1/+1
|
* Add info about purpose in cookies to "Upgrading Ruby on Rails" guide [ci skip]bogdanvlviv2018-08-301-0/+11
| | | | | | Context https://github.com/rails/rails/pull/33605#discussion_r210354278 Related to #32937, #33605
* Add "Ruby on Rails 6.0 Release Notes" guide [ci skip]bogdanvlviv2018-08-291-1/+3
| | | | | | | | | This commit adds a skeleton of "Ruby on Rails 6.0 Release Notes". It isn't a good time to add changelogs' entries to this guide since we can redo/revert some things till the final release 6.0. It would be better to do it close to the release. But we already can add mentions about major features that have been added to 6.0. I added mention about "Parallel Testing".
* Fixed file name [ci skip]Claas Zurawski2018-08-221-1/+1
|
* Added explanation about new_framework_defaults.rb file [ci skip]Claas Zurawski2018-08-221-0/+7
|
* Update Rails 3.2 to 4.0 upgrade guide to include a mention and tip for ↵thetizzo2018-08-031-0/+11
| | | | handling the addition of configurable default HTTP headers. [ci skip]
* Merge pull request #33229 from ↵Matthew Draper2018-07-251-7/+9
|\ | | | | | | | | albertoalmagro/albertoalmagro/prefer-rails-command-over-bin-rails Prefer rails command over bin/rails
| * Substitute references to task for commandAlberto Almagro2018-07-061-3/+3
| | | | | | | | This commit substitutes references to rails/rake task for rails command
| * Recommend use of rails over bin/railsAlberto Almagro2018-07-061-4/+6
| | | | | | | | | | | | | | | | | | As discussed in #33203 rails command already looks for, and runs, bin/rails if it is present. We were mixing recommendations within guides and USAGE guidelines, in some files we recommended using rails, in others bin/rails and in some cases we even had both options mixed together.
* | Rails guides are now served over httpsPaul McMahon2018-07-241-2/+2
|/ | | | | http links will be redirected to the https version, but still better to just directly link to the https version.
* Use https with weblog URIYoshiyuki Hirano2018-05-021-1/+1
|
* Deprecate controller level force_sslDerek Prior2018-03-301-0/+11
| | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | Today there are two common ways for Rails developers to force their applications to communicate over HTTPS: * `config.force_ssl` is a setting in environment configurations that enables the `ActionDispatch::SSL` middleware. With this middleware enabled, all HTTP communication to your application will be redirected to HTTPS. The middleware also takes care of other best practices by setting HSTS headers, upgrading all cookies to secure only, etc. * The `force_ssl` controller method redirects HTTP requests to certain controllers to HTTPS. As a consultant, I've seen many applications with misconfigured HTTPS setups due to developers adding `force_ssl` to `ApplicationController` and not enabling `config.force_ssl`. With this configuration, many application requests can be served over HTTP such as assets, requests that hit mounted engines, etc. In addition, because cookies are not upgraded to secure only in this configuration and HSTS headers are not set, it's possible for cookies that are meant to be secure to be sent over HTTP. The confusion between these two methods of forcing HTTPS is compounded by the fact that they share an identical name. This makes finding documentation on the "right" method confusing. HTTPS throughout is quickly becomming table stakes for all web sites. Sites are expected to operate over HTTPS for all communication, sensitive or otherwise. Let's encourage use of the broader-reaching `ActionDispatch::SSL` middleware and elminate this source of user confusion. If, for some reason, applications need to expose certain endpoints over HTTP they can do so by properly configuring `config.ssl_options`.
* Update "Upgrading from Rails 5.1 to Rails 5.2" [ci skip]bogdanvlviv2018-03-141-0/+10
| | | | | | | | | | | Add section "Expiry in signed or encrypted cookie is now embedded in the cookies values" to `master` since it should always be in the guides, not only for version 5.2. Add info about `config.action_dispatch.use_authenticated_cookie_encryption` to the "Configuring Rails Applications" guide. It was committed straight to `5-2-stable` since we don't need this functionality in 6.0. Related to b25fcbc074ea688765af62a163698d5449221a8c.
* Fix note marks [ci skip]Yauheni Dakuka2018-03-121-1/+1
|
* Rails 6 requires Ruby 2.4.1+Jeremy Daer2018-02-171-1/+1
| | | | | | Skipping over 2.4.0 to sidestep the `"symbol_from_string".to_sym.dup` bug. References #32028
* Rails 6 requires Ruby 2.3+Jeremy Daer2018-02-171-0/+1
|
* Merge pull request #31577 from prathamesh-sonpatki/upgrade-guide-bootsnapEileen M. Uchitelle2018-01-181-0/+11
|\ | | | | Added a note about bootsnap in the Rails 5.2 upgrade guide [ci skip]
| * Added a note about bootsnap in the Rails 5.2 upgrade guide [ci skip]Prathamesh Sonpatki2017-12-271-0/+11
| |
* | Fix some broken links in guidesDorian Marié2018-01-111-1/+1
| |
* | Fix "the the " [ci skip]Ryuta Kamizono2018-01-101-1/+1
|/
* Merge pull request #30474 from yhirano55/make_it_same_title_in_index_and_pageEileen M. Uchitelle2017-12-131-2/+2
|\ | | | | Make it same title in index and page [ci skip]
| * Make it same title in index and page [ci skip]Yoshiyuki Hirano2017-08-311-2/+2
| |
* | Cosmetic changes [ci skip]Yauheni Dakuka2017-11-301-13/+13
| |
* | Cosmetic fixes [ci skip]Yauheni Dakuka2017-10-061-3/+3
|/
* Use https instead of http in guide [ci skip]Yoshiyuki Hirano2017-08-231-2/+2
|
* Add note about JSON/JSONB serialization changesJon Moss2017-08-171-0/+9
| | | | | | | | | | | | | | | | | | | | | | | | | | | The initial commit (efaa6e4f79d457c2cdd08cbc56d63bc972a6993c) that changed this behavior was intended to be a minor change, but ended up becoming a large-ish breaking change within Active Record. This is because instead of only JSON encoding `Hash`es or `Array`s in `#serialize`, we now encode all values passed in. This is an issue if you're passing in a `String`, that has already been transformed from a `Hash` to a `String`, since your data is now being double encoded. Unfortunately, the change was included in one of the v5.0.0 beta releases, and it is too late to revert without huge ripple effects. Thus, all we can do is update the documentation (via this commit), and add some test coverage (coming soon in a PR) for the new behavior. Please note that in the documentation I talk about deserialization, not about serialization, where the actual change occurred. This is because you won't notice any changes in serialized data until you try and deserialize it. Also to make the change itself (confusing until you read through everything multiple times) easier to understand. Related #27788, #25594, #26101, #24234, #28292, #28285, #28285, and probably others. [ci skip]
generated by cgit v1.2.3 (git 2.25.1) at 2024-11-16 07:56:40 +0000