RAILS_ENV=production script/about fails
Added by Sean Whitney about 16 years ago
I posted 7 days ago about a svn issue I'm am having and I didn't receive any response. Maybe I try this again in smaller chunks
I have redmine set up on a openvz ubuntu 8.04 image using a development release from last week (sorry I can't find the release version) following the howto's for mongrel_clusters, and the simple authentication.
Right now I get this output
RAILS_ENV=production script/about
/var/lib/gems/1.8/gems/activesupport-2.1.0/lib/active_support/dependencies.rb:275:in `load_missing_constant': uninitialized constant Rails::Info (NameError)
from /var/lib/gems/1.8/gems/activesupport-2.1.0/lib/active_support/dependencies.rb:467:in `const_missing'
from /var/lib/gems/1.8/gems/rails-2.1.0/lib/commands/about.rb:2
from /usr/lib/ruby/1.8/rubygems/custom_require.rb:27:in `gem_original_require'
from /usr/lib/ruby/1.8/rubygems/custom_require.rb:27:in `require'
from script/about:3
If I run
script/about
About your application's environment
Ruby version 1.8.6 (i486-linux)
RubyGems version 1.1.1
Rails version 2.1.0
Active Record version 2.1.0
Action Pack version 2.1.0
Active Resource version 2.1.0
Action Mailer version 2.1.0
Active Support version 2.1.0
Application root /var/www/rails_apps/redmine
Environment development
Database adapter mysql
Database schema version 0
Any ideas?
Thanks,
Sean
Replies (3)
RE: RAILS_ENV=production script/about fails - Added by Thomas Löber about 16 years ago
I think the command has to be:
script/about RAILS_ENV=production
RE: RAILS_ENV=production script/about fails - Added by Sean Whitney about 16 years ago
No I don't think so,
RAILS_ENV-production script/about, sets the RAILS_ENV environment variable to production and then executes the script with this value. I'm not sure what setting the variable after the command has executed will do.
I tried your command anyway...
and in the return
Environment development
So it didn't do anything interesting.
Sean
RE: RAILS_ENV=production script/about fails - Added by Thomas Löber about 16 years ago
You're right. The command I proposed doesn't work either.
But I just found this Rails ticket. So this seems to be a bug in Rails.