aboutsummaryrefslogtreecommitdiffstats
path: root/railties/lib/rails/application.rb
Commit message (Collapse)AuthorAgeFilesLines
* Allowing multiple rails applications in the same ruby instance.wangjohn2013-06-301-7/+78
| | | | | This change provides the ability to create a new application with a configuration which can be specified.
* Removing a repetitive comment and removing a deprecation warning.wangjohn2013-06-171-24/+7
| | | | | | | The comment on the +env_config+ method is repetitive, likely to get outdated, and provides no useful information which cannot be gleamed from the code. I'm therefore removing it. I'm also refactoring the check for the presence of a secret_token in the configuration.
* Revert "Merge pull request #10961 from wangjohn/changing_rails_env_config"Santiago Pastorino2013-06-171-7/+24
| | | | | | This reverts commit 7098d6c9ab28931acc9562a00037567609f9e529, reversing changes made to 9ec2e2ee91568af24e09760a6de2890b89c33f56. This make some tests fail /cc @wangjohn
* Merge pull request #10968 from wangjohn/refactoring_rails_application_classSantiago Pastorino2013-06-171-95/+8
|\ | | | | Creating a class to build the default middleware stack.
| * Creating a class to build the default middleware stack.wangjohn2013-06-161-95/+8
| | | | | | | | | | | | | | A lot of logic for building the default middleware stack is currently kept in Application class, but this can be encapsulated and made more modular by being moved to its own class. Also refactored a couple of the helper methods.
* | Removing a repetitive comment and refactoring the Application class inwangjohn2013-06-161-24/+7
|/ | | | | | | | | Railties. The comment on the +env_config+ method is repetitive, likely to get outdated, and provides no useful information which cannot be gleamed from the code. I'm therefore removing it. I'm also refactoring the check for the presence of a secret_token in the configuration.
* `initialize_on_precompile` is not used anymore.Terence Lee2013-06-131-3/+1
|
* Fix generating route from engine to other enginePiotr Sarnacki2013-05-031-0/+1
| | | | | | | | | | | | A regression was introduced in 5b3bb6, generating route from within an engine to an another engine resulted in prefixing a path with the SCRIPT_NAME value. The regression was caused by the fact that SCRIPT_NAME should be appended only if it's the SCRIPT_NAME for the application, not if it's SCRIPT_NAME from the current engine. closes #10409
* Remove comments about removing LegacyKeyGenerator in 4.1Trevor Turk2013-04-031-1/+0
|
* Rename DummyKeyGenerator -> LegacyKeyGeneratorTrevor Turk2013-04-021-2/+2
|
* Allow transparent upgrading of legacy signed cookies to encrypted cookies; ↵Trevor Turk2013-03-281-6/+7
| | | | Automatically configure cookie-based sessions to use the best cookie jar given the app's config
* Introduce UpgradeLegacySignedCookieJar to transparently upgrade existing ↵Trevor Turk2013-03-241-0/+1
| | | | signed cookies generated by Rails 3 to avoid invalidating them when upgrading to Rails 4
* Initialize @app_env_config now that the var name has changedCarlos Antonio da Silva2013-03-191-1/+1
| | | | Check 862389c9537dbb6f65fd26c4325e07607ed437b5 for more background.
* Use @app_env_config instead of @env_configJosé Valim2013-03-181-1/+1
| | | | Check pull request #9789 for more information.
* Renumbering the comments in the application boot process.wangjohn2013-03-091-4/+4
|
* Bring config.allow_concurrency backJosé Valim2013-03-031-18/+40
| | | | | Since the Rack::Lock still exists in development, let's provide a way to disable it explicitly.
* 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.
generated by cgit v1.2.3 (git 2.25.1) at 2024-07-03 13:33:21 +0000