#206 Improve Rails.env - Ruby on Rails

Type	To find
responsible:me	tickets assigned to you
tagged:"@high"	tickets tagged @high
milestone:next	tickets in the upcoming milestone
state:invalid	tickets with the state invalid
created:"last week"	tickets created last week
sort:number, importance, updated	tickets sorted by #, importance or updated
Combine keywords for powerful searching.
Use advanced searching »

This project is archived and is in readonly mode.

#206 ✓resolved

Improve Rails.env

Reported by Markús | May 16th, 2008 @ 09:13 AM | in 2.1.1

In this commit http://github.com/rails/rails/co..., you (Pratik), insert a serie of shortcuts for RAILS_* constants.

Well, I like this change, but I think it can be improved to make something like this:

Rails.env # => "production"
Rails.env.production? # => true
Rails.env.development? # => false

This can be achieved adding a few lines to the Rails.env method:

  def self.env
    env = RAILS_ENV
    def env.production? # Or method_missing
      self == "production"
    end
    def env.development?
      self == "development"
    end
    def env.test?
      self == "test"
    end
  end
  env # returns the RAILS_ENV string
end

May be a "method_missing" could ba a better solution, but this is only an example.

Comments and changes to this ticket

DHH May 31st, 2008 @ 09:35 PM
- State changed from “new” to “incomplete”
We'd definitely have to make a solution that would be general purpose enough to deal with all possible environments. Many people add their own environments, like benchmarking or staging. Please reopen if you come up with a implementation to do that.
You flagged this item as spam.
Luke Redpath June 24th, 2008 @ 02:56 PM
I believe this ticket has been resolved as of this changeset.
Jeremy Kemper June 24th, 2008 @ 05:23 PM
- Milestone set to “2.1.1”
- State changed from “incomplete” to “resolved”