Skip to content
This repository

Feb 19, 2013

  1. Andrew White

    Don't unhook autoloading in production

    Whilst autoloading is known to be not threadsafe, leaving it in place
    is a softer solution than failing hard when an application is deployed.
    
    Many older applications will have paths added to `autoload_paths` and
    ideally these should be eagerly loaded to be threadsafe. However one
    of these paths is quite often lib which could lead to unintended
    consequences due to the 'junk drawer' nature of this directory.
    
    Developers should refrain from adding paths to `autoload_paths` or
    `eager_load_paths` and use custom folders inside app for code that
    needs to be eagerly loaded and use `require` or `require_dependency`
    to explicitly load code from other locations.
    pixeltrix authored

Dec 22, 2012

  1. Jeremy Kemper

    Move background jobs to the 'jobs' branch until fully baked. Not ship…

    …ping with Rails 4.0.
    jeremy authored

Dec 11, 2012

  1. Richard Schneeman

    Use Rails to Render Default Index Page

    This is an alternative implementation to #7771 thanks to the advice of @spastorino
    
    Rails is a dynamic framework that serves a static index.html by default. One of my first questions ever on IRC was solved by simply deleting my public/index.html file. This file is a source of confusion when starting as it over-rides any set "root" in the routes yet it itself is not listed in the routes. By making the page dynamic by default we can eliminate this confusion.
    
    This PR moves the static index page to an internal controller/route/view similar to `rails/info`. When someone starts a rails server, if no root is defined, this route will take over and the "dynamic" index page from rails/welcome_controller will be rendered. These routes are only added in development. If a developer defines a root in their routes, it automatically takes precedence over this route and will be rendered, with no deleting of files required. 
    
    In addition to removing this source of confusion for new devs, we can now use Rails view helpers to build and render this page. While not the primary intent, the added value of "dogfooding" should not be under-estimated.
    
    The prior PR #7771 had push-back since it introduced developer facing files. This PR solves all of the same problems, but does not have any new developer facing files (it actually removes one). 
    
    cc/ @wsouto, @dickeyxxx, @tyre, @ryanb, @josevalim, @maxim, @subdigital, @steveklabnik
    
    ATP Railties and Actionpack.
    schneems authored

Oct 26, 2012

  1. Jeremy Kemper

    Job consumer logs to Rails.logger by default

    jeremy authored

Oct 14, 2012

  1. Robin Dupret

    Use Ruby 1.9 Hash syntax in railties

    robin850 authored

Oct 13, 2012

  1. Jeremy Kemper

    Test that a Rails.queue consumer is automatically started in production

    jeremy authored
  2. Jeremy Kemper

    Backpedal from class-oriented config.queue. Set an actual queue insta…

    …nce.
    jeremy authored

Sep 17, 2012

  1. Arun Agrawal

    Fix build for Queue.

    arunagw authored

Sep 14, 2012

  1. Santiago Pastorino

    Move queue classes to ActiveSupport

    spastorino authored

Aug 23, 2012

  1. José Valim

    Fix failure on middleware/exceptions_test

    The reason the test was failing was because when the test
    invokes `app.config`, the app is loaded and, as `eager_load`
    is set to true, it disables the dependency loading mechanism,
    so controllers that are later defined are not loaded.
    josevalim authored

Aug 21, 2012

  1. José Valim

    Get rid of config.preload_frameworks in favor of config.eager_load_na…

    …mespaces
    
    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.
    josevalim authored
  2. José Valim

    Allow users to choose when to eager_load the application or not.

    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.
    josevalim authored

May 24, 2012

  1. Richard Schneeman

    /rails/info/routes path shows routing information

    Will show similar contents to the output of `$ rake routes` in the browser in development. This speeds the time required to generate routes, since the application is already initialized.
    schneems authored

May 04, 2012

  1. Carlos Antonio da Silva

    Allow configuring a different queue consumer

    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.

Apr 28, 2012

  1. José Valim

    Use Rails::Queueing::Queue instead of Queue so people can build their…

    … own consumers around stdlib's Queue
    josevalim authored

Apr 27, 2012

  1. Yehuda Katz

    Initial queue implementation

    wycats authored

Apr 25, 2012

  1. Yehuda Katz

    Remove default match without specified method

    In the current router DSL, using the +match+ DSL
    method will match all verbs for the path to the
    specified endpoint.
    
    In the vast majority of cases, people are
    currently using +match+ when they actually mean
    +get+. This introduces security implications.
    
    This commit disallows calling +match+ without
    an HTTP verb constraint by default. To explicitly
    match all verbs, this commit also adds a
    :via => :all option to +match+.
    
    Closes #5964
    wycats authored

Jan 21, 2012

  1. Jonathan Viney

    Fix `$rails_rake_task` global variable warning without replacing the …

    …value of $rails_rake_task if it is already set.
    
    Fixes #4591.
    jviney authored

Dec 15, 2011

  1. José Valim

    Clean up the cache before the request in case we are running in the r…

    …eload_classes_only_on_change schema.
    josevalim authored

Dec 13, 2011

  1. José Valim

    FileUpdateChecker should be able to handle deleted files.

    josevalim authored
  2. José Valim

    Clean up FileUpdateChecker API.

    josevalim authored
  3. José Valim

    Move hooks back to initializers (we need an API that allows hooks to …

    …be replaced).
    josevalim authored
  4. José Valim

    Revert "Provide a unique point for running initializers."

    This reverts commit c2e3ce8.
    
    Conflicts:
    
    	railties/lib/rails/application/configuration.rb
    	railties/lib/rails/application/finisher.rb
    	railties/lib/rails/engine.rb
    josevalim authored

Dec 12, 2011

  1. José Valim

    Speed up development by only reloading classes if dependencies files …

    …changed.
    
    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 https://github.com/paneq/active_reload and Pastorino for the inspiration. <3
    josevalim authored
  2. José Valim

    Give hooks the flexibility to choose the type of callback.

    josevalim authored
  3. José Valim

    Provide a unique point for running initializers.

    josevalim authored
  4. José Valim

    Improve docs for Rails::Application and add routes_reloader_hook and …

    …app_reloader_hooks.
    josevalim authored

Nov 28, 2011

  1. Arun Agrawal

    global variable `$rails_rake_task' not initialized Warning removed

    arunagw authored

Apr 25, 2011

  1. Piotr Sarnacki

    Explicitly define main_app proxy

    drogus authored

Apr 17, 2011

  1. José Valim

    Move app initializers to sprockets railtie.

    josevalim authored

Apr 15, 2011

  1. José Valim

    Booya, sprockets now works from Engines.

    josevalim authored

Apr 13, 2011

  1. Joshua Peek

    Index sprockets environment if perform caching is enabled

    josh authored

Mar 31, 2011

  1. Joshua Peek

    Unify sprockets config options

    josh authored

Mar 30, 2011

  1. Joshua Peek

    Rename option to config.asset_pipeline

    josh authored
  2. Joshua Peek

    Move sprockets initializers back to application

    josh authored
Something went wrong with that request. Please try again.