aboutsummaryrefslogtreecommitdiffstats
path: root/railties/lib/rails/application
Commit message (Collapse)AuthorAgeFilesLines
...
* Remove highly uncommon `config.assets.manifest` option for moving the ↵Guillermo Iguaran2012-09-191-1/+0
| | | | | | manifest path. This option is now unsupported in sprockets-rails.
* Date.beginning_of_week thread local and beginning_of_week application config ↵gregolsen2012-09-181-1/+2
| | | | option added (default is Monday)
* Fix build for Queue.Arun Agrawal2012-09-171-1/+1
|
* Move queue classes to ActiveSupportSantiago Pastorino2012-09-142-4/+5
|
* Action Mailer async flag is true by default using a Synchronous implSantiago Pastorino2012-09-111-1/+1
|
* Raise more helpful error message on missing gemPrem Sichanugrist2012-08-241-0/+7
| | | | | | Tell people to install `activerecord-session_store` gem when it's not installed instead ofraising `NameError` on missing `ActionDispatch::Session::ActiveRecordStore`.
* Extract ActiveRecord::SessionStore from RailsPrem Sichanugrist2012-08-241-2/+0
| | | | | This functionality will be available from gem `active_record-session_store` instead.
* Fix failure on middleware/exceptions_testJosé Valim2012-08-231-1/+1
| | | | | | | The reason the test was failing was because when the test invokes `app.config`, the app is loaded and, as `eager_load` is set to true, it disables the dependency loading mechanism, so controllers that are later defined are not loaded.
* Deprecate config.threadsafe!José Valim2012-08-211-4/+3
|
* Get rid of config.preload_frameworks in favor of config.eager_load_namespacesJosé Valim2012-08-213-11/+3
| | | | | | | The new option allows any Ruby namespace to be registered and set up for eager load. We are effectively exposing the structure existing in Rails since v3.0 for all developers in order to make their applications thread-safe and CoW friendly.
* Remove allow_concurrency as a flagJosé Valim2012-08-211-3/+1
| | | | | | | | | | | | | | | | The flag was mainly used to add a Rack::Lock middleware to the stack, but the only scenario the lock is desired is in development. If you are deploying on a not-threaded server, the Rack::Lock does not provide any benefit since you don't have concurrent accesses. On the other hand, if you are on a threaded server, you don't want the lock, since it defeats the purpose of using a threaded server. If there is someone out there, running on a thread server and does want a lock, it can be added to your environment as easy as: `use Rack::Lock`
* Allow users to choose when to eager_load the application or not.José Valim2012-08-213-6/+19
| | | | | | | | | | | | | | | | | Previously, the eager load behavior was mostly coupled to config.cache_classes, however this was suboptimal since in some environments a developer may want to cache classes but not necessarily load them all on boot (for example, test env). This pull request also promotes the use of config.eager_load set to true by default in production. In the majority of the cases, this is the behavior you want since it will copy most of your app into memory on boot (which was also the previous behavior). Finally, this fix a long standing Rails bug where it was impossible to access a model in a rake task when Rails was set as thread safe.
* removes usage of Object#in? from the code base (the method remains defined ↵Xavier Noria2012-08-061-1/+1
| | | | | | | | | | | | | | | | | | | by Active Support) Selecting which key extensions to include in active_support/rails made apparent the systematic usage of Object#in? in the code base. After some discussion in https://github.com/rails/rails/commit/5ea6b0df9a36d033f21b52049426257a4637028d we decided to remove it and use plain Ruby, which seems enough for this particular idiom. In this commit the refactor has been made case by case. Sometimes include? is the natural alternative, others a simple || is the way you actually spell the condition in your head, others a case statement seems more appropriate. I have chosen the one I liked the most in each case.
* The use_schema_cache_dump configuration moved to ActiveRecord.kennyj2012-08-021-2/+1
|
* Remove RoutesInspector from railties, since it was moved to APCarlos Antonio da Silva2012-07-081-121/+0
| | | | | Changes introduced in 7404cda9f61e41d52ce244d60abbf598684a96c4. Fix railties build.
* Revert "Allow loading external route files from the router"José Valim2012-06-291-9/+4
| | | | | | | | | | | | | | This reverts commit 6acebb38bc0637bc05c19d87f8767f16ce79189b. Usage of this feature did not reveal any improvement in existing apps. Conflicts: actionpack/lib/action_dispatch/routing/mapper.rb guides/source/routing.textile railties/lib/rails/engine.rb railties/lib/rails/paths.rb railties/test/paths_test.rb
* Remove unnecessary Railties structure now that plugins are goneJosé Valim2012-06-291-13/+0
|
* Rename RouteInspect to RoutesInspector for consistencyJosé Valim2012-06-291-1/+1
|
* /rails/info/routes path shows routing informationschneems2012-05-242-1/+3
| | | | Will show similar contents to the output of `$ rake routes` in the browser in development. This speeds the time required to generate routes, since the application is already initialized.
* Improve `rake routes` output for redirects - closes #6369.Andrew White2012-05-191-1/+1
|
* Fix inspecting route redirections, closes #6369Łukasz Strzałkowski2012-05-181-2/+2
| | | | | | | | | | | | This commit fixes route inspection in `rake routes` Before: foo /foo(.:format) :controller#:action" After: foo /foo(.:format) Redirect (301)
* Move AS set configs to AS RaitieSantiago Pastorino2012-05-121-11/+1
|
* Update railties/lib/rails/application/bootstrap.rbEgor Homakov2012-05-111-1/+11
|
* Allow configuring a different queue consumerCarlos Antonio da Silva2012-05-042-5/+7
| | | | | | Also make sure to not use default queue consumer with custom queue implementation. It is up to the new queue implementation to start / shutdown the consumer.
* Refactor RoutesReloader a bit to avoid creating extra hash objectsCarlos Antonio da Silva2012-04-281-3/+2
|
* Use Rails::Queueing::Queue instead of Queue so people can build their own ↵José Valim2012-04-282-2/+2
| | | | consumers around stdlib's Queue
* Initial queue implementationYehuda Katz2012-04-262-1/+9
|
* Routes reloader knows how to reload external filesYehuda Katz2012-04-251-4/+10
|
* Remove default match without specified methodJose and Yehuda2012-04-241-1/+1
| | | | | | | | | | | | | | | | In the current router DSL, using the +match+ DSL method will match all verbs for the path to the specified endpoint. In the vast majority of cases, people are currently using +match+ when they actually mean +get+. This introduces security implications. This commit disallows calling +match+ without an HTTP verb constraint by default. To explicitly match all verbs, this commit also adds a :via => :all option to +match+. Closes #5964
* use File.binread to pull in the schema cacheAaron Patterson2012-04-031-1/+1
|
* use AS::Logger so we are consistentAaron Patterson2012-03-121-1/+1
|
* allow people to specify custom formatters, use the default formatter in ↵Aaron Patterson2012-03-122-4/+5
| | | | production so that PID and timestamp are logged. fixes #5388
* Merge pull request #5162 from kennyj/schema_cache_dumpAaron Patterson2012-03-071-1/+2
|\ | | | | [Proposal] Schema cache dump
| * Load db/schema_cache.dump duaring boot time.kennyj2012-03-011-1/+2
| |
* | remove usages of AS::OrderedHashVishnu Atrai2012-03-031-1/+1
|/
* uses PATCH for the forms of persisted records, and routes PATCH and PUT to ↵Xavier Noria2012-02-241-2/+1
| | | | the update action of resources
* Always default to flushing enabledFelix Bünemann2012-02-231-1/+1
|
* Make log autoflushing configurableFelix Bünemann2012-02-232-2/+3
|
* Add config.default_method_for_update to support PATCHDavid Lee2012-02-221-1/+2
| | | | | | | | | | | | | | | | PATCH is the correct HTML verb to map to the #update action. The semantics for PATCH allows for partial updates, whereas PUT requires a complete replacement. Changes: * adds config.default_method_for_update you can set to :patch * optionally use PATCH instead of PUT in resource routes and forms * adds the #patch verb to routes to detect PATCH requests * adds #patch? to Request * changes documentation and comments to indicate support for PATCH This change maintains complete backwards compatibility by keeping :put as the default for config.default_method_for_update.
* Allow to set custom console type with Rails.application.config.console=Piotr Sarnacki2012-02-161-1/+1
| | | | | | | | | | | | | This patch adds ability to set custom console if you want to use something other than IRB. Previously the hack that people used was: silence_warnings do require 'pry' IRB = Pry end which is not the best way to customize things.
* remove unnecessary require core_ext/string/encodingSergey Nartimov2012-02-141-1/+0
|
* always flush all logs. fixes #4277Aaron Patterson2012-02-071-1/+1
|
* Remove redundant instance_variables (@colorize_logging)kennyj2012-01-271-2/+1
|
* Fix `$rails_rake_task` global variable warning without replacing the value ↵Jonathan Viney2012-01-221-2/+1
| | | | | of $rails_rake_task if it is already set. Fixes #4591.
* Silent Sprockets logger when config.assets.logger is set to falseGuillermo Iguaran2012-01-171-0/+1
|
* Deprecate RAILS_CACHE constant.kennyj2012-01-181-4/+4
|
* Don't hardcode assets route skipped in route inspectorGuillermo Iguaran2012-01-141-1/+1
|
* changing self.attribute to @atrribute to follow one kind of value assignment ↵prasath2012-01-121-4/+4
| | | | through out the file
* We should finalize the routes as soon as possible and not wait for the ↵José Valim2012-01-061-1/+1
| | | | controller to be loaded.
* do not rewrite log during application bootstrapSergey Nartimov2012-01-031-1/+1
|