aboutsummaryrefslogtreecommitdiffstats
path: root/railties/lib/rails/engine
Commit message (Collapse)AuthorAgeFilesLines
...
* Get rid of static_paths method and instead configure paths for ↵Piotr Sarnacki2010-09-031-0/+4
| | | | ActionDispatch::Static in initializers
* Added Rails.application.config.paths.db.migrate to remove hardcoded ↵Piotr Sarnacki2010-09-031-0/+2
| | | | db/migrate paths
* Added ability to set asset_path for enginesPiotr Sarnacki2010-09-031-1/+1
|
* Move singleton pattern to Railtie and remove Engine::Configurable and ↵Piotr Sarnacki2010-09-031-31/+0
| | | | Application::Configurable in favor of unified Railtie::Configurable
* Allow Engines loading its own environment file from config/environmentsPiotr Sarnacki2010-09-031-0/+1
|
* Removed ActionDispatch::Static, but left empty MiddlewareStack to unify app ↵Piotr Sarnacki2010-09-032-7/+1
| | | | method between Engine and Application
* Engine can now serve files with ActionDispatch::StaticPiotr Sarnacki2010-09-031-2/+3
|
* Engine can now load its own pluginsPiotr Sarnacki2010-09-032-1/+26
|
* Made Engine valid rack app with its own middleware stackPiotr Sarnacki2010-09-032-1/+14
|
* Revert "Put lib back on the autoload path"José Valim2010-08-041-1/+1
| | | | | | This was causing engines/gems to eager load everything in lib. Another fix is comming soon. This reverts commit 02a5842cd09bd75de4c2fdb6b474c6c0ff163ebf.
* Put lib back on the autoload pathwycats2010-08-031-1/+1
|
* Add a header that tells Internet Explorer (all versions) to use the best ↵wycats2010-07-271-1/+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.
* A few changes were done in this commit:José Valim2010-06-281-2/+2
| | | | | | * 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;
* renames load_(once_)paths to autoload_(once_)paths in dependencies and configXavier Noria2010-06-241-5/+5
|
* Revert "files in the lib directory are no longer autoloaded"Xavier Noria2010-06-211-5/+1
| | | | | | | This patch is not consistent since it leaves similar directories in load_paths, needs more thought. This reverts commit b5fe014fdcc285f3bcb8779c4f7cfbc5a820856f.
* files in the lib directory are no longer autoloadedXavier Noria2010-06-211-1/+5
| | | | | | | | | | | Conceptually, the lib directory is closer 3rd party libraries than to the application itself. Thus, Rails adds it to Ruby's load path ($LOAD_PATH, $:) but it is no longer included in dependencies' load paths. To enable autoloading back put this in your config/application.rb config.load_paths += %W( #{config.root}/lib )
* Removing Metal from Rails 3. wycats2010-05-291-1/+0
| | | | | | | | | | | | | | | | | | | | 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.
* Fix a typo in load_once_paths [#4357 state:resolved] (ht: Kim Altintop)José Valim2010-04-101-1/+1
|
* Remove app/views from the load paths [#4226 state:resolved]José Valim2010-04-051-1/+1
|
* Rename config.cookie_secret to config.secret_token and pass it as ↵José Valim2010-04-051-1/+0
| | | | configuration in request.env. This is another step forward removing global configuration.
* Add mailers to paths in case someone wants to access it directly and ensures ↵José Valim2010-03-061-2/+3
| | | | deep nesting works in controllers.
* Deprecated ActionController::Base.session_options= and ↵Carlhuda2010-03-041-0/+1
| | | | ActionController::Base.session_store= in favor of a config.session_store method (which takes params) and a config.cookie_secret variable, which is used in various secret scenarios. The old AC::Base options will continue to work with deprecation warnings.
* Start refactoring the method of configuring ActionViewCarlhuda2010-03-031-0/+3
|
* Add config.generators.templates to provide alternative paths for template ↵José Valim2010-02-061-0/+1
| | | | lookup.
* Add reloadable specific for engines and move environment to application paths.José Valim2010-01-281-1/+0
| | | | Signed-off-by: Carl Lerche <carllerche@mac.com>
* Add active_model/railtie back to generated boot.rb, add models back to ↵José Valim2010-01-251-0/+1
| | | | paths, load active_support/railtie since we need it and ensure default logger is set before config.
* Ensure metals and initializers in plugins are loaded.José Valim2010-01-241-1/+1
|
* Add tests for plugin sanity check.José Valim2010-01-241-1/+2
|
* Ensure helpers work from configured path.José Valim2010-01-241-0/+1
|
* Move configuration to subfolders.José Valim2010-01-232-1/+49
|
* Create configurable modules and ensure that they are added only on direct ↵José Valim2010-01-231-0/+24
children.