aboutsummaryrefslogtreecommitdiffstats
path: root/railties/lib/rails/application.rb
Commit message (Collapse)AuthorAgeFilesLines
...
* Engine sets routes as default rack endpoint if no endpoint was givenPiotr Sarnacki2010-09-031-4/+0
|
* Delegate non existing class methods to instance for EnginePiotr Sarnacki2010-09-031-5/+0
|
* Improve best_standards_support to use only IE=Edge in development modewycats2010-08-091-1/+1
|
* Add a header that tells Internet Explorer (all versions) to use the best ↵wycats2010-07-271-0/+1
| | | | | | available standards support. This ensures that IE doesn't go into quirks mode because it has been blacklisted by too many users pressing the incompatible button. It also tells IE to use the ChromeFrame renderer, if the user has installed the plugin. This guarantees that the best available standards support will be used on the client.
* Add console hook to force ActiveRecord::Base to be loaded when console ↵José Valim2010-07-181-0/+13
| | | | starts avoiding reference loops.
* reload_routes! was still referencing old Rails::Application.José Valim2010-07-021-6/+5
|
* Avoid calls to Rails::Application since this is not the official API.José Valim2010-07-011-8/+4
| | | | Your application should *always* reference your application const (as Blog::Application) and Rails.application should be used just internally.
* A few changes were done in this commit:José Valim2010-06-281-6/+1
| | | | | | * Added :autoload to engines path API and redefine usage to be in sync with 6f83a5036d8a9c3f8ed7; * Do not autoload code in *lib* for applications (now you need to explicitly require them). This makes an application behave closer to an engine (code in lib is still autoloaded for plugins); * Always autoload code in app/ for engines and plugins. This makes engines behave closer to an application and should allow us to get rid of the unloadable hack required when controllers inside engines inherit from ApplicationController;
* Move Collection responsibility from application to initializableJeremy Kemper2010-06-241-1/+1
|
* Speed up boot by tsorting as infrequently as possibleJeremy Kemper2010-06-241-1/+1
|
* renames load_(once_)paths to autoload_(once_)paths in dependencies and configXavier Noria2010-06-241-2/+2
|
* Alias app to build_middleware_stack for clarity.José Valim2010-06-211-0/+1
|
* Use the new ActiveSupport::FileUpdateChecker instead of RoutesReloader.José Valim2010-06-201-3/+10
|
* Improve documentation for add_lib_to_load_paths!José Valim2010-06-201-3/+16
|
* Add lib to load paths when application is inherited to be able to load lib ↵José Valim2010-06-021-0/+11
| | | | code during configuration.
* Remove the laziness from the middleware stack.José Valim2010-05-291-1/+27
|
* Removing Metal from Rails 3. wycats2010-05-291-6/+4
| | | | | | | | | | | | | | | | | | | | If you have existing Metals, you have a few options: * if your metal behaves like a middleware, add it to the middleware stack via config.middleware.use. You can use methods on the middleware stack to control exactly where it should go * if it behaves like a Rack endpoint, you can link to it in the router. This will result in more optimal routing time, and allows you to remove code in your endpoint that matches specific URLs in favor of the more powerful handling in the router itself. For the future, you can use ActionController::Metal to get a very fast controller with the ability to opt-in to specific controller features without paying the penalty of the full controller stack. Since Rails 3 is closer to Rack, the Metal abstraction is no longer needed.
* Expose remaining hooks to minimize the need for a Railtie based on feedback ↵José Valim2010-05-161-1/+0
| | | | from plugin developers.
* Reorganized initializers a bit to enable better hooks for common cases ↵wycats2010-05-151-4/+6
| | | | | | | | | | | | | | | without the need for Railtie. Specifically, the following hooks were added: * before_configuration: this hook is run immediately after the Application class comes into existence, but before the user has added any configuration. This is the appropriate place to set configuration for your plugin * before_initialize: This is run after all of the user's configuration has completed, but before any initializers have begun (in other words, it runs right after config/environments/{development,production,test}.rb) * after_initialize: This is run after all of the initializers have run. It is an appropriate place for forking in a preforking setup Each of these hooks may be used via ActiveSupport.on_load(name) { }. In all these cases, the context inside the block will be the Application object. This means that for simple cases, you can use these hooks without needing to create a Railtie.
* The rake task :environment now loads config/environment.rb instead of ↵José Valim2010-04-291-2/+2
| | | | initializing the application on its own. This fixes [#4492 state:resolved] and also avoids the application being initialized twice in some rake tasks.
* Ensure application rake tasks and generators are loaded after the ones ↵José Valim2010-04-261-2/+2
| | | | specified in railties/engines/rails. [#4471 state:resolved]
* Rename config.cookie_secret to config.secret_token and pass it as ↵José Valim2010-04-051-2/+9
| | | | configuration in request.env. This is another step forward removing global configuration.
* Merge branch 'master' into docrailswycats2010-03-261-1/+2
|\
| * Move application configuration to the application configuration object, ↵José Valim2010-03-261-0/+2
| | | | | | | | remove railtie_name and engine_name and allow to set the configuration object.
| * Move railties/builtin into libJoshua Peek2010-03-201-1/+0
| |
* | Merge remote branch 'mainstream/master'Pratik Naik2010-03-121-6/+5
|\| | | | | | | | | | | | | Conflicts: activerecord/lib/active_record/base.rb railties/lib/rails/configuration.rb railties/lib/rails/log_subscriber.rb
| * Aliasing class_eval makes JRuby ornery.wycats2010-03-071-1/+4
| |
| * Don't rely on Rails.application global state in ConfigCarlhuda2010-03-031-4/+0
| |
| * Get Railties tests passingCarlhuda2010-02-251-1/+1
| |
| * Use ActionDispatch::Routing everywhereMartin Schürrer2010-02-211-1/+1
| |
| * TypoMartin Schürrer2010-02-211-1/+1
| |
* | Add docs for Railtie, Engine, Plugin and Application.José Valim2010-02-021-0/+37
|/
* Add more tests to some key points in Railties.José Valim2010-01-281-0/+4
| | | | Signed-off-by: Carl Lerche <carllerche@mac.com>
* Refactor MetalLoader and RoutesReloader to rely less on class configuration.José Valim2010-01-281-2/+6
| | | | Signed-off-by: Carl Lerche <carllerche@mac.com>
* Move Rails::Rack::Metal to Rails::Application::Metal and just add cascade if ↵José Valim2010-01-261-0/+1
| | | | any metal was declared.
* Add tests for explicit engines.José Valim2010-01-261-4/+1
|
* Ensure calling a method in Rails::Application does not instantiate a void ↵José Valim2010-01-261-3/+3
| | | | application.
* Ensure all initializers are collections.José Valim2010-01-261-2/+2
|
* Plugins need to load before app initializersJoshua Peek2010-01-251-1/+1
|
* Add Rails::Application pointer to the default app to add symmetry to ↵Joshua Peek2010-01-241-1/+5
| | | | Foo::Application
* Ensure environment config has higher priority than application ones.José Valim2010-01-241-2/+0
|
* Ensure helpers work from configured path.José Valim2010-01-241-2/+0
|
* Solve some pendencies.José Valim2010-01-241-3/+2
|
* Move configuration to subfolders.José Valim2010-01-231-1/+6
|
* Create configurable modules and ensure that they are added only on direct ↵José Valim2010-01-231-28/+30
| | | | children.
* Plugin is now an Engine.José Valim2010-01-231-1/+0
|
* First steps into making Plugin < Engine.José Valim2010-01-231-0/+5
|
* Extract Railtie load from application.José Valim2010-01-231-29/+30
|
* Break application.rb file in smaller chunks.José Valim2010-01-231-102/+2
|
* Extract routes reloading responsibilities from application and load them ↵José Valim2010-01-231-46/+21
| | | | just upon a request.