Skip to content
Commits on Oct 18, 2012
  1. @rafaelfranca

    Require ActionController::Railtie in the default middleware stack.

    rafaelfranca committed Oct 18, 2012
    This will make possible to do a frameworkless initialization since the
    the default middleware stack is self contained.
Commits on Jul 16, 2012
  1. @jmazzi
Commits on May 27, 2012
  1. @drogus

    Fix railties_order when application object is passed

    drogus committed May 27, 2012
    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.
Commits on Jan 13, 2012
  1. @josevalim
Commits on Jan 10, 2012
  1. @drogus


    drogus committed Dec 20, 2011
    This behaves similarly to REQUEST_URI, but
    we need to implement it on our own because
    REQUEST_URI is not reliable.
    Note that since PATH_INFO does not contain
    information about trailing question mark,
    this is not 100% accurate, for example
    `/foo?` will result in `/foo` in ORIGINAL_FULLPATH
Commits on Dec 16, 2011
  1. @josevalim
  2. @josevalim
Commits on Dec 15, 2011
  1. @josevalim
Commits on Dec 13, 2011
  1. @josevalim
  2. @josevalim
  3. @josevalim

    Add config.file_watcher so developers can provide their own watchers …

    josevalim committed Dec 13, 2011
    …(for instance, hooking on fsevents).
  4. @josevalim

    Revert "Provide a unique point for running initializers."

    josevalim committed Dec 13, 2011
    This reverts commit c2e3ce8.
Commits on Dec 12, 2011
  1. @josevalim

    Speed up development by only reloading classes if dependencies files …

    josevalim committed Dec 12, 2011
    This can be turned off by setting `config.reload_classes_only_on_change` to false.
    Extensions like Active Record should add their respective files like db/schema.rb and db/structure.sql to `config.watchable_files` if they want their changes to affect classes reloading.
    Thanks to and Pastorino for the inspiration. <3
  2. @josevalim
  3. @josevalim
  4. @josevalim
Commits on Dec 1, 2011
  1. @josevalim
Commits on Nov 28, 2011
  1. @lest

    put backtrace_cleaner to env

    lest committed Nov 28, 2011
Commits on Nov 25, 2011
  1. @lest
Commits on Nov 23, 2011
  1. @drogus
  2. @josevalim

    Rely on a public contract between railties instead of accessing railt…

    josevalim committed Nov 23, 2011
    …ie methods directly.
Commits on Nov 22, 2011
  1. @lest
Commits on Nov 9, 2011
  1. @amatsuda
  2. @amatsuda

    Modulize Rails console methods so that other console libraries such a…

    amatsuda committed Nov 9, 2011
    …s Pry can include these methods
Commits on Oct 19, 2011
  1. @josevalim
  2. @dhh

    Added X-Request-Id tracking and TaggedLogging to easily log that and …

    dhh committed Oct 19, 2011
    …other production concerns
Commits on Oct 2, 2011
  1. @josevalim
Commits on Sep 27, 2011
  1. @jsl
Commits on Sep 24, 2011
  1. @josevalim

    `rake assets:precompile` loads the application but does not initializ…

    josevalim committed Sep 24, 2011
    …e it.
    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.
Commits on Aug 24, 2011
  1. @tenderlove
Commits on Aug 13, 2011
  1. @spastorino @fxn
Commits on Jul 23, 2011
  1. @fxn
Commits on Jul 12, 2011
  1. @mjankowski
Commits on Jul 11, 2011
  1. @franckverrot
Commits on Jun 16, 2011
  1. @jhtwong

    Cherry-picking patch for #1460

    jhtwong committed Jun 16, 2011
    from 3-1-stable to master
    [3.1.0.rc1] Plugins inside engines not eager-loaded properly and their
    rake tasks ignored
    Working with the new support for plugins inside engines in Rails 3.1,
    I found that certain things that work for regular plugins don't work
    for these new nested plugins. In particular, these methods in
    Rails::Engine don't seem to understand that an engine could have
    nested plugins:
    A solution which worked out for me is to move the calls to
    railties.all { ... } from the overriding methods in Rails::Application
    into Rails::Engine.
Something went wrong with that request. Please try again.