Skip to content
This repository

Dec 05, 2012

  1. Fabrizio Regini

    Adding filter capability to ActionController logs

    freegenie authored

Nov 16, 2012

  1. Santiago Pastorino

    Add UpgradeSignatureToEncryptionCookieStore

    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
    spastorino authored

Nov 03, 2012

  1. Santiago Pastorino

    Rename secret_token_key to secret_key_base

    spastorino authored
  2. Santiago Pastorino

    Cache generated keys per KeyGenerator instance using salt + key_size

    spastorino authored
  3. Santiago Pastorino

    Allow users to change the default salt if they want, shouldn't be nec…

    spastorino authored
  4. Santiago Pastorino

    Use derived keys everywhere, http_authentication was missing it

    spastorino authored
  5. Santiago Pastorino

    Warn config.derive_keys will be true by default in 4.1

    spastorino authored
  6. Santiago Pastorino

    Sign cookies using key deriver

    spastorino authored

Oct 18, 2012

  1. Rafael Mendonça França

    Don't use action_controller.perform_caching to enable rack-rack.

    Setting the action_dispatch.rack_cache options to true or a hash should
    be the way to enable it.
    rafaelfranca authored

Oct 14, 2012

  1. Robin Dupret

    Use Ruby 1.9 Hash syntax in railties

    robin850 authored

Oct 13, 2012

  1. Jeremy Kemper

    Remove the queue container. Premature consolidation. Set up and maint…

    …ain queues in the classes that use them instead.
    jeremy authored

Oct 05, 2012

  1. Guillermo Iguaran

    config.action_dispatch.rack_cache should set explicitly to enable Rac…

    guilleiguaran authored

Oct 02, 2012

  1. Michael Koziarski

    Merge pull request #6952 from NZKoz/key_generator

    Add ActiveSupport::KeyGenerator as a simple wrapper around PBKDF2
    NZKoz authored
  2. Guillermo Iguaran

    Use Rack::Cache middleware only if is in Gemfile

    guilleiguaran authored

Oct 01, 2012

  1. Michael Koziarski

    Provide access to the application's KeyGenerator

    Available both as an env entry for rack and an instance method on Rails::Application for other uses
    NZKoz authored

Sep 15, 2012

  1. David Czarnecki

    Clarify the documentation on the Rails::Application#call method

    czarneckid authored

Sep 14, 2012

  1. Santiago Pastorino

    Move queue classes to ActiveSupport

    spastorino authored

Aug 23, 2012

  1. Rafael Mendonça França

    Update the ducumentation about the before_eager_load callback [ci skip]

    rafaelfranca authored

Aug 21, 2012

  1. José Valim

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

    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

    Remove allow_concurrency as a flag

    The flag was mainly used to add a Rack::Lock middleware to
    the stack, but the only scenario the lock is desired is in
    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`
    josevalim authored
  3. 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
    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

Aug 01, 2012

  1. Justin Mazzi

    Restoring documentation for env_config per #7070

    jmazzi authored

Jul 23, 2012

  1. Santiago Pastorino

    Remove ActionDispatch::Head middleware in favor of Rack::Head

    Closes #7110 there's more work to do on rack-cache issue 69
    spastorino authored

Jul 19, 2012

  1. Aaron Patterson

    adding Rails::Queueing::Container

    This allows us to do:
    In your configuration:
    Rails.queue[:image_queue] =
    Rails.queue[:mail_queue]  =
    In your app code:
    Both jobs pushed to the same default queue
    tenderlove authored

Jul 07, 2012

  1. Mattt Thompson

    move route_inspector to actionpack

    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.
    mattt authored schneems committed

Jun 29, 2012

  1. José Valim

    Remove unused responsibilities and add a few load definitions to engines

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

    Remove unnecessary Railties structure now that plugins are gone

    josevalim authored

May 29, 2012

  1. Toshinori Kajihara

    Add support runner hook.

    kennyj authored

May 27, 2012

  1. Piotr Sarnacki

    Fix railties_order when application object is passed

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

May 23, 2012

  1. Aaron Patterson

    use File.join to decrease dependencies on Pathname

    tenderlove authored

May 22, 2012

  1. Aaron Patterson

    initialize instance variables

    tenderlove 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. Carlos Antonio da Silva

    Define only writer method for queue, as reader is declared

    Remove deprecation warning of method redefined.

Apr 27, 2012

  1. Aaron Patterson

    add a factory method for queue construction so that apps can have mul…

    …tiple queues
    tenderlove authored
  2. Yehuda Katz

    Initial queue implementation

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