aboutsummaryrefslogtreecommitdiffstats
path: root/railties/lib/rails/application/bootstrap.rb
Commit message (Collapse)AuthorAgeFilesLines
* Move AS set configs to AS RaitieSantiago Pastorino2012-05-121-11/+1
|
* Update railties/lib/rails/application/bootstrap.rbEgor Homakov2012-05-111-1/+11
|
* 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-121-3/+3
| | | | production so that PID and timestamp are logged. fixes #5388
* Make log autoflushing configurableFelix Bünemann2012-02-231-1/+1
|
* always flush all logs. fixes #4277Aaron Patterson2012-02-071-1/+1
|
* Deprecate RAILS_CACHE constant.kennyj2012-01-181-4/+4
|
* do not rewrite log during application bootstrapSergey Nartimov2012-01-031-1/+1
|
* * BufferedLogger is deprecated. Use ActiveSupport::Logger, or the loggerAaron Patterson2011-12-191-4/+4
| | | | from Ruby stdlib.
* Improve docs for Rails::Application and add routes_reloader_hook and ↵José Valim2011-12-121-7/+0
| | | | app_reloader_hooks.
* * ActiveSupport::BufferedLogger#silence is deprecated. If you want to squelchAaron Patterson2011-12-091-3/+11
| | | | | | | | | | | | | | | | | | | | | | | logs for a certain block, change the log level for that block. * ActiveSupport::BufferedLogger#open_log is deprecated. This method should not have been public in the first place. * ActiveSupport::BufferedLogger's behavior of automatically creating the directory for your log file is deprecated. Please make sure to create the directory for your log file before instantiating. * ActiveSupport::BufferedLogger#auto_flushing is deprecated. Either set the sync level on the underlying file handle like this: f = File.open('foo.log', 'w') f.sync = true ActiveSupport::BufferedLogger.new f Or tune your filesystem. The FS cache is now what controls flushing. * ActiveSupport::BufferedLogger#flush is deprecated. Set sync on your filehandle, or tune your filesystem.
* Added X-Request-Id tracking and TaggedLogging to easily log that and other ↵David Heinemeier Hansson2011-10-191-2/+2
| | | | production concerns
* `rake assets:precompile` loads the application but does not initialize it.José Valim2011-09-241-8/+8
| | | | | | | | | | | | | To the app developer, this means configuration add in config/initializers/* will not be executed. Plugins developers need to special case their initializers that are meant to be run in the assets group by adding :group => :assets. Conflicts: railties/CHANGELOG railties/test/application/assets_test.rb
* dealing with some -w warnings on startupAaron Patterson2011-08-241-1/+1
|
* ADdd missing requires (thanks to @arunagw)José Valim2011-05-071-1/+1
|
* Always flush logger at exitJason Rudolph2011-05-061-0/+1
| | | | | | | | | | | | | | Prior to this change, running code via script/runner would demonstrate different logging behavior than running the same code via a rake task. In production mode the script/runner approach would always flush the logger, but the rake-based approach would not automatically flush the logger. This discrepancy violates the principle of least surprise, and it could lead to the loss of important production logging data. This change removes special-case code in the "runner" command, and replaces it with a general solution to ensure that the logger gets flushed at exit. This solution works for "runner", "console", "server", rake tasks, and any other process that loads the Rails environment.
* Use AD::Reloader.to_cleanup for reloading [#2873 state:resolved]John Firebaugh2010-12-201-5/+3
| | | | Signed-off-by: José Valim <jose.valim@gmail.com>
* Provide a cleaner syntax for paths configuration that does not rely on ↵José Valim2010-10-061-1/+1
| | | | method_missing.
* Allow Engines loading its own environment file from config/environmentsPiotr Sarnacki2010-09-031-5/+2
|
* Clear DescendantsTracker on each request.José Valim2010-06-191-0/+2
|
* Remove the laziness from the middleware stack.José Valim2010-05-291-1/+1
|
* Reorganized initializers a bit to enable better hooks for common cases ↵wycats2010-05-151-4/+4
| | | | | | | | | | | | | | | 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-1/+2
| | | | initializing the application on its own. This fixes [#4492 state:resolved] and also avoids the application being initialized twice in some rake tasks.
* Moved initializers for ActionMailer and ActionController into their own railtiesCarlhuda2010-03-021-14/+2
|
* Rename Rails::Subscriber to Rails::LogSubscriberPrem Sichanugrist2010-02-161-4/+4
|
* Ensure all initializers are collections.José Valim2010-01-261-21/+21
|
* As first step setup the load path and lazy compare middlewares.José Valim2010-01-251-0/+4
|
* Ensure environment config has higher priority than application ones.José Valim2010-01-241-0/+4
|
* Break application.rb file in smaller chunks.José Valim2010-01-231-0/+77
generated by cgit v1.2.3 (git 2.25.1) at 2024-10-31 09:37:31 +0000