Saturday, October 1, 2011
On Fri, Sep 30, 2011 at 6:54 PM, Walter Lee Davis <waltd@wdstudio.com> wrote:
-- If you're using Rails 2.x, then this should work, although you might want to try quoting the word production in this syntax. If you're using Rails 3.x, then RAILS_ENV is deprecated or removed, depending on 3.0 vs 3.1. The new syntax is Rails.env, I
On Sep 30, 2011, at 12:35 PM, Andre Flory wrote:
> I have somewhat of a complex issue involving several different programs
> including redmine, MySQL, Ruby, Ruby on Rails etc.
>
> I am following the redmine instructions here:
> http://www.redmine.org/projects/redmine/wiki/RedmineInstall
>
> I am on step 5. where I am suppose to type "RAILS_ENV=production rake
> db:migrate"
>
> When I type this in the command prompt and hit enter I get an error:
> "RAILS_ENV" is not a command blah blah.
>
> So I reorder it to: rake db:migrate RAILS_ENV=production
believe.
I am not sure that is correct.
In rails 3.1.1.rc1 I am still able to use the RAILS_ENV=production in a bash shell
and it behaves as I would expect (same as 2.3 AFAICS)
peterv@ASUS:~/f$ RAILS_ENV=production
peterv@ASUS:~/f$ RAILS_ENV=production rake environment
peterv@ASUS:~/f$ RAILS_ENV=production rails c
Loading production environment (Rails 3.1.1.rc1)
001:0> quit
This is on Ubuntu 10.04 (but I presume this works generally in bash).
Peter
You received this message because you are subscribed to the Google Groups "Ruby on Rails: Talk" group.
To post to this group, send email to rubyonrails-talk@googlegroups.com.
To unsubscribe from this group, send email to rubyonrails-talk+unsubscribe@googlegroups.com.
For more options, visit this group at http://groups.google.com/group/rubyonrails-talk?hl=en.
Subscribe to:
Post Comments (Atom)
No comments:
Post a Comment