| Commit message (Collapse) | Author | Age | Files | Lines |
|---|
| ... | |
| |
|
|
| |
Signed-off-by: José Valim <jose.valim@gmail.com>
|
| | |
|
| |
|
|
| |
ActionDispatch::Static in initializers
|
| |
|
|
| |
db/migrate paths
|
| | |
|
| |
|
|
| |
Application::Configurable in favor of unified Railtie::Configurable
|
| | |
|
| |
|
|
| |
method between Engine and Application
|
| | |
|
| | |
|
| | |
|
| |
|
|
|
|
| |
This was causing engines/gems to eager load everything in lib. Another fix is comming soon.
This reverts commit 02a5842cd09bd75de4c2fdb6b474c6c0ff163ebf.
|
| | |
|
| |
|
|
|
|
| |
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.
|
| |
|
|
|
|
| |
* 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;
|
| | |
|
| |
|
|
|
|
|
| |
This patch is not consistent since it leaves similar
directories in load_paths, needs more thought.
This reverts commit b5fe014fdcc285f3bcb8779c4f7cfbc5a820856f.
|
| |
|
|
|
|
|
|
|
|
|
| |
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 )
|
| |
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| |
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.
|
| | |
|
| | |
|
| |
|
|
| |
configuration in request.env. This is another step forward removing global configuration.
|
| |
|
|
| |
deep nesting works in controllers.
|
| |
|
|
| |
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.
|
| | |
|
| |
|
|
| |
lookup.
|
| |
|
|
| |
Signed-off-by: Carl Lerche <carllerche@mac.com>
|
| |
|
|
| |
paths, load active_support/railtie since we need it and ensure default logger is set before config.
|
| | |
|
| | |
|
| | |
|
| | |
|
|
|
children.
|
