aboutsummaryrefslogtreecommitdiffstats
path: root/railties/CHANGELOG.md
Commit message (Collapse)AuthorAgeFilesLines
* Fix rails restart issue with PumaPrathamesh Sonpatki2016-03-301-0/+5
| | | | | | | | | | | | | | | - We need to pass the restart command to Puma so that it will use it while restarting the server. - Also made sure that all the options passed by user while starting the server are used in the generated restart command so that they will be used while restarting the server. - Besides that we need to remove the server.pid file for the previous running server because otherwise Rack complains about it's presence. - We don't care if the server.pid file does not exist. We only want to delete it if it exists. - This also requires some changes on Puma side which are being tracked here - https://github.com/puma/puma/pull/936. - Fixes #23910.
* guides, sync railties and AP changelogs with 5.0 release notes.Yves Senn2016-03-221-1/+3
| | | | | | | | | | [ci skip] This updates the 5.0 release notes guide to reflect changes that happened after beta1 has been released. I'll sync the other changelogs later today but I'll push this batch to prevent against cumbersome merge conflicts.
* Fix CHANGELOG spacing [ci skip]Jeremy Daer2016-03-021-2/+2
|
* generate config/spring.rb in new applications [closes #18874]Xavier Noria2016-02-291-0/+5
|
* The tasks in the rails task namespace is deprecated in favor of app namespace.Ryo Hashimoto2016-02-261-0/+5
| | | | (e.g. `rails:update` and `rails:template` tasks is renamed to `app:update` and `app:template`.)
* Add CHANGELOG entryPrathamesh Sonpatki2016-02-251-0/+4
|
* Preparing for 5.0.0.beta3 releaseeileencodes2016-02-241-0/+2
| | | | Adds changelog headers for beta3 release
* Add CHANGELOG for https://github.com/rails/rails/pull/23734 [ci skip]Prathamesh Sonpatki2016-02-241-0/+5
|
* AppGenerator: Replace 'rake' with 'rails_command'claudiob2016-02-201-0/+5
| | | | | | | | | | | Since Rails 5.0 is switching the Rails command line from 'rake …' to 'rails …', it makes sense to also replace the `rake` method in the Rails templates API. Based on feedback from @matthewd and @kaspth, I chose to replace `rake` with `rails_command`, which is less confusing than the alternatives `rails` or `command` or `rails_run` and is not Thor-reserved word like `task`.
* modify to `error` also abort when specify fail fast optionyuuji.yaginuma2016-02-171-0/+4
|
* adds --skip-listen to the application generator [closes #23590]Xavier Noria2016-02-171-0/+4
|
* include spring-watcher-listen in the Gemfile of new applicationsXavier Noria2016-02-101-0/+5
|
* enables the evented monitor in new applicationsXavier Noria2016-02-101-0/+5
|
* move CHANGELOG entry to the appropriate position [ci skip]yuuji.yaginuma2016-02-051-2/+2
| | | | | Dummy apple icon files has been added after the 5.0.0.beta2 release. ref: #23455
* Add dummy apple icon filesAlexey Zabelin2016-02-031-0/+4
| | | | | | | | Previously Safari would try to load these files when you visit localhost:3000. That created two exceptions in the log. It also caused the exception notifier to send them out. In response to #23427
* Add some Action Cable CHANGELOG entriesRafael Mendonça França2016-02-011-3/+1
| | | | | | And improve changelongs. [ci skip]
* Preparing for Rails 5.0.0.beta2Sean Griffin2016-02-011-0/+5
|
* Implemented pull request changes.Ryan Manuel2016-01-291-7/+5
|
* Update doc with appropriate issue and pull request versionsRyan Manuel2016-01-281-1/+1
|
* Add an after_bundle callback in Rails plugin templatesRyan Manuel2016-01-281-0/+7
|
* remove unnecessary `ENV[]` from `log:clear` example [ci skip]yuuji.yaginuma2016-01-161-1/+1
|
* bring back `TEST` env for `rake test`.Yves Senn2016-01-121-0/+4
| | | | | | | Closes #23027. This does not restore complete backwards compatibility. It simply passes the contets of the `TEST` env to the new runner.
* rake log:clear task updated refs[#22544]Pramod2016-01-091-0/+10
| | | | | | | | - Avoided truncating all files if no ENV['LOGS'] specified - Updated task to accept LOGS=all for truncating all files from log/ i.e. log/*log - If no LOGS specified will truncates standard environment log files i.e. 'development,test,production' - CHANGELOG & guide update added - bin/setup test cases fixed
* release notes, extract notable changes from Railties CHANGELOG.Yves Senn2015-12-221-4/+4
| | | | [ci skip]
* [ci skip] No more no changes entries in the CHANGELOGs (cases left in #22718)Akshay Vishnoi2015-12-221-3/+0
|
* Fixes using `add_source` with a block after using `gem` in a custom railsWill Fisher2015-12-211-0/+4
| | | | generator template.
* Add CHANGELOG headers for Rails 5.0.0.beta1eileencodes2015-12-181-0/+5
|
* README.rdoc -> README.md for newly generated pluginsyuuji.yaginuma2015-12-171-0/+4
| | | | I think Markdown is nowadays a better default.
* let config.file_watcher be the way to enable the evented file watcherXavier Noria2015-12-131-5/+5
| | | | | | | | | | | Before this commit, the sole presence of the Listen constant enabled the evented file watcher (unless listen resorted to the polling backend). This way, applications may depend on listen for other stuff independently of this feature. Also, allows teams with mixed setups to decide at boot time whether the evented watcher should be enabled for each particular instance.
* Update Changelog with the added response_format option in AD::DebugExceptionsJorge Bejar2015-12-091-0/+9
|
* Fix #22232: rake test tasks exit status codeArkadiusz Fal2015-12-071-0/+7
| | | | | | | The exit status code was not set when tests were fired with `rake`. Now, it is being set and it matches behavior of running tests via `rails` command (`rails test`), so no matter if `rake test` or `rails test` command is used the exit code will be set.
* Add Rails command infrastructure and encapsulate development cachingChuck Callebs2015-12-041-0/+7
|
* allow use of minitest-rails gem with test runnerChris Kottom2015-11-301-0/+6
|
* add `bin/test` script to rails pluginyuuji.yaginuma2015-11-281-0/+6
|
* Make the `static_index` config part of the `config.public_server` configYuki Nishijima2015-11-161-0/+5
| | | | Also call it `public_server.index_name` so it'll make more sense.
* registers these changes in the CHANGELOGsXavier Noria2015-11-111-0/+5
|
* Move `static_cache_contorl` deprecation changelog entry to Railties.Kasper Timm Hansen2015-11-041-0/+22
| | | | | | | The configuration for `config.static_cache_control`, and its replacement `config.public_file_server.headers` are implemented in Railties. People would configure this in environment files, which is Railties domain too.
* Add enabled flag to the public file server.Kasper Timm Hansen2015-11-031-0/+19
| | | | | | | | As discussed in https://github.com/rails/rails/pull/19135#issuecomment-153385986. Replaces `serve_static_files` to unify the static options under the `public_file_server` wing. Deprecates `serve_static_files` accessors, but make them use the newer config internally.
* Route generator should be idempotent - closes #22082Thiago Pinto2015-10-311-0/+4
|
* rails/application: allow passing an env to config_forSimon Eskildsen2015-10-301-0/+4
|
* Allow rake:stats to account for rake tasksKevin Deisz2015-10-191-0/+4
|
* Update the URL when changing mailer preview formatsJames Kerr2015-10-061-0/+6
| | | | | | Added javascript to update the URL on mailer previews with the currently selected email format. Reloading the page now keeps you on your selected format rather than going back to the default html version.
* Revert "removing Rack::Runtime from the default stack."Aaron Patterson2015-10-031-3/+0
| | | | | | | | | | | | | | | | | | This reverts commit 37423e4ff883ad5584bab983aceb4b2b759a1fd8. Jeremy is right that we shouldn't remove this. The fact is that many engines are depending on this middleware to be in the default stack. This ties our hands and forces us to keep the middleware in the stack so that engines will work. To be extremely clear, I think this is another smell of "the rack stack" that we have in place. When manipulating middleware, we should have meaningful names for places in the req / res lifecycle **not** have engines depend on a particular constant be in a particular place in the stack. This is a weakness of the API that we have to figure out a way to address before removing the constant. As far as timing attacks are concerned, we can reduce the granularity such that it isn't useful information for hackers, but is still useful for developers.
* removing Rack::Runtime from the default stack.Aaron Patterson2015-10-021-0/+3
| | | | | | | | | | | | The runtime header is a potential target for timing attacks since it returns the amount of time spent on the server (eliminating network speed). Total time is also not accurate for streaming responses. The middleware can be added back via: ```ruby config.middleware.ues ::Rack::Runtime ```
* Refactor AS::Callbacks halt config and fix the documentationRoque Pinel2015-10-011-3/+4
| | | | | | | | | Move from `AS::Callbacks::CallbackChain.halt_and_display_warning_on_return_false` to `AS::Callbacks.halt_and_display_warning_on_return_false` base on [this discussion](https://github.com/rails/rails/pull/21218#discussion_r39354580) Fix the documentation broken by 0a120a818d413c64ff9867125f0b03788fc306f8
* Add fail fast to test runner.Kasper Timm Hansen2015-09-291-0/+32
| | | | | Passing `--fail-fast` to the test runner will now abort the test run on the first failure. The run continues on any unexpected errors.
* Add inline failure reporting to test runner.Kasper Timm Hansen2015-09-281-0/+30
| | | | | | | | | Any failures or errors will be reported inline during the run by default. Skipped tests will be reported if run in verbose mode. Any result is output with failure messages and a rerun snippet for that test. Rerun snippets won't be output after a run, unless `--defer-output` is passed.
* Fix displaying mailer previews on non local requests.Wojciech Wnętrzak2015-09-171-0/+5
| | | | | When config `action_mailer.show_previews` is set, previews are displayed regardless of local request check.
* Use the PORT environment variable for rails serverDavid Cornu2015-08-181-0/+4
|
* Plugins are generated with the version 0.1.0Daniel Morris2015-08-161-0/+5
| | | | | | The semantic versioning specification uses MAJOR.MINOR.PATCH – it would make more sense to set the version to 0.1.0 for initial development since a patch release cannot be created before a minor feature release.
generated by cgit v1.2.3 (git 2.25.1) at 2024-11-03 02:12:37 +0000