aboutsummaryrefslogtreecommitdiffstats
path: root/railties/lib/rails/application.rb
Commit message (Collapse)AuthorAgeFilesLines
* Remove BestStandardsSupport middlewareGuillermo Iguaran2013-01-291-4/+0
|
* Adding Back Rails::Engine::Railties#enginesTim Raymond2013-01-031-5/+1
| | | | | Removing it breaks functionality with gems such as Thinking Sphinx. This restores it with a deprecation warning. Closes #8551
* Improve secret_token deprecation messageSantiago Pastorino2012-12-301-3/+4
|
* remove duplication from Rails::Application docsHrvoje Šimić2012-12-241-2/+0
|
* Move background jobs to the 'jobs' branch until fully baked. Not shipping ↵Jeremy Kemper2012-12-211-8/+1
| | | | with Rails 4.0.
* Adding filter capability to ActionController logsFabrizio Regini2012-12-051-0/+2
|
* Add UpgradeSignatureToEncryptionCookieStoreSantiago Pastorino2012-11-161-0/+2
| | | | | | This allows easy upgrading from the old signed Cookie Store <= 3.2 or the deprecated one in 4.0 (the ones that doesn't use key derivation) to the new one that signs using key derivation
* Rename secret_token_key to secret_key_baseSantiago Pastorino2012-11-031-6/+6
|
* Cache generated keys per KeyGenerator instance using salt + key_sizeSantiago Pastorino2012-11-031-5/+8
|
* Allow users to change the default salt if they want, shouldn't be necessarySantiago Pastorino2012-11-031-7/+15
|
* Use derived keys everywhere, http_authentication was missing itSantiago Pastorino2012-11-031-2/+3
|
* Warn config.derive_keys will be true by default in 4.1Santiago Pastorino2012-11-031-9/+17
|
* Sign cookies using key deriverSantiago Pastorino2012-11-031-1/+8
|
* Don't use action_controller.perform_caching to enable rack-rack.Rafael Mendonça França2012-10-181-1/+1
| | | | | Setting the action_dispatch.rack_cache options to true or a hash should be the way to enable it.
* Use Ruby 1.9 Hash syntax in railtiesRobin Dupret2012-10-141-5/+5
|
* Remove the queue container. Premature consolidation. Set up and maintain ↵Jeremy Kemper2012-10-121-5/+1
| | | | queues in the classes that use them instead.
* config.action_dispatch.rack_cache should set explicitly to enable Rack::CacheGuillermo Iguaran2012-10-041-0/+9
|
* Merge pull request #6952 from NZKoz/key_generatorMichael Koziarski2012-10-021-1/+10
|\ | | | | Add ActiveSupport::KeyGenerator as a simple wrapper around PBKDF2
| * Provide access to the application's KeyGeneratorMichael Koziarski2012-10-011-1/+10
| | | | | | | | Available both as an env entry for rack and an instance method on Rails::Application for other uses
* | Use Rack::Cache middleware only if is in GemfileGuillermo Iguaran2012-10-011-0/+6
|/
* Clarify the documentation on the Rails::Application#call methodDavid Czarnecki2012-09-151-2/+2
|
* Move queue classes to ActiveSupportSantiago Pastorino2012-09-141-1/+2
|
* Update the ducumentation about the before_eager_load callback [ci skip]Rafael Mendonça França2012-08-221-1/+1
|
* Get rid of config.preload_frameworks in favor of config.eager_load_namespacesJosé Valim2012-08-211-7/+0
| | | | | | | 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-2/+2
| | | | | | | | | | | | | | | | 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-211-1/+9
| | | | | | | | | | | | | | | | | 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.
* Restoring documentation for env_config per #7070Justin Mazzi2012-08-011-0/+11
|
* Remove ActionDispatch::Head middleware in favor of Rack::HeadSantiago Pastorino2012-07-231-1/+1
| | | | Closes #7110 there's more work to do on rack-cache issue 69
* adding Rails::Queueing::ContainerAaron Patterson2012-07-191-1/+1
| | | | | | | | | | | | | | | This allows us to do: In your configuration: Rails.queue[:image_queue] = SomeQueue.new Rails.queue[:mail_queue] = SomeQueue.new In your app code: Rails.queue[:mail_queue].push MailJob.new Both jobs pushed to the same default queue Rails.queue.push DefaultJob.new Rails.queue[:default].push DefaultJob.new
* move route_inspector to actionpack@schneems and @mattt2012-07-071-2/+2
| | | | this is so we can show route output in the development when we get a routing error. Railties can use features of ActionDispatch, but ActionDispatch should not depend on Railties.
* Remove unused responsibilities and add a few load definitions to enginesJosé Valim2012-06-291-67/+63
| | | | | | | | Since plugins were removed, we can clean up a few methods in engines. We also use this opportunity to move `load_console`, `load_tasks` and `load_runner` to Rails::Engine. This means that, if someone wants to improve script/rails for engines to support console or runner commands, part of the work is already done.
* Remove unnecessary Railties structure now that plugins are goneJosé Valim2012-06-291-59/+68
|
* Add support runner hook.kennyj2012-05-291-0/+11
|
* Fix railties_order when application object is passedPiotr Sarnacki2012-05-271-1/+1
| | | | | | | | | | | | | | | railites_order method, introduced in 40b19e0, had a bug that was causing loading application instance twice in initializers if railties_order already included application instance. So for example railties_order = [Foo::Engine, :main_app, Bar::Engine] would result in such railties array: [MyApp::Application, Foo::Engine, MyAppApplication, Bar::Engine] In order to fix it, we need to check for existence of application in both railties_order and railties arrays.
* use File.join to decrease dependencies on PathnameAaron Patterson2012-05-231-1/+1
|
* initialize instance variablesAaron Patterson2012-05-221-2/+6
|
* Allow configuring a different queue consumerCarlos Antonio da Silva2012-05-041-1/+1
| | | | | | 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.
* Define only writer method for queue, as reader is declaredCarlos Antonio da Silva2012-04-281-1/+2
| | | | Remove deprecation warning of method redefined.
* add a factory method for queue construction so that apps can have multiple ↵Aaron Patterson2012-04-271-1/+5
| | | | queues
* Initial queue implementationYehuda Katz2012-04-261-1/+5
|
* Remove not needed requiresSantiago Pastorino2012-03-311-1/+0
|
* Rails.initialized? can be called at any time without raising an exception ↵Franck Verrot2012-03-281-0/+4
| | | | | | | | | | [Closes #2507] Changes: * `Rails.initialized=` has been removed * `Rails.initialized?` and `Rails.application.initialized?` are now * delegating to `MyApp::Application.initialized?`
* Rack::SSL -> ActionDispatch::SSLRafael Mendonça França2012-03-171-2/+1
|
* Remove remaining http_only? calls.José Valim2012-03-141-4/+4
|
* Change api_only to http_onlyCarlos Antonio da Silva2012-03-101-4/+4
| | | | [Carlos Antonio da Silva & Santiago Pastorino]
* Add config.middleware.api_only!Carlos Antonio da Silva and Santiago Pastorino2012-03-051-4/+4
|
* Handle files from ActionDispatch::Static with Rack::Sendfile (fixes #5225)Piotr Sarnacki2012-03-031-4/+4
| | | | | | | | This makes rails behave properly when you serve static assets and you have X-Sendfile headers enabled. Nevertheless in most cases you should not rely on that and serve static assets with a webserver like Apache or Nginx (as you already have it in place anyway if you use X-Sendfile)
* Reverted build_original_fullpath method, as per discussion at ↵Nathan Broadbent2012-01-281-1/+9
| | | | https://github.com/rails/rails/pull/4470/files#r393461
* Refactored watchable_args and build_original_fullpath methods in ↵Nathan Broadbent2012-01-151-13/+2
| | | | railties/lib/rails/application.rb
* config.force_ssl should mark the session as secure.José Valim2012-01-131-0/+3
|
generated by cgit v1.2.3 (git 2.25.1) at 2024-11-03 00:27:24 +0000