Today, I was replacing RailsCron and BackgrounDRb with generated Daemons, and I happened to investigate how Rails sets up it’s logger. For the longest time, I knew it was possible to change the options, but I just never investigated how to do it. I thought I’d share my findings so others won’t be in the dark as I was.

Actually doing the replacement is very easy:


1 do |config|
2 config.logger = + "/../log/#{RAILS_ENV}.log")
3 end

That’s it. Have fun. Stop reading… Unless you want more details.

This is essentially what Rails does, except now you have complete control over how the Logger is instantiated.

Some options you might want to investigate:

1 # Keep at most 2 2 megabytes log files
2 config.logger = + "/../log/#{RAILS_ENV}.log", 2, 210241024)
4 # Create a new log file each day
5 config.logger = + "/../log/#{RAILS_ENV}.log", "daily")

If you are running a script which loads the Rails environment manually, you can also do this:


1 #!/usr/bin/env ruby
3 # You might want to change this
4 raise "No RAILS_ENV defined" if ENV["RAILS_ENV"].to_s.empty?
6 require "logger"
8 RAILS_DEFAULT_LOGGER = + "/../../log/futures_runner.rb.log", 3, 210241024)
9 require File.dirname(FILE) + "/../../config/environment"
11 # Other code as appropriate

The Rails::Initializer is smart enough to use either the RAILS_DEFAULT_LOGGER or the one defined in the configuration block. For the gory details, please read Rails::Initializer#initialize_logger


Your Host

A picture of me

I am François Beausoleil, a Ruby on Rails and Scala developer. During the day, I work on Seevibes, a platform to measure social interactions related to TV shows. At night, I am interested many things. Read my biography.

Top Tags

Books I read and recommend


Projects I work on

Projects I worked on