Sorry, meant to add an example of the output:
/usr/lib/ruby/gems/1.8/gems/rspec-1.1.11/lib/spec/runner/options.rb:229:in
`files_to_load?:
File or directory not found: RAILS_ENV=production
(RuntimeError)
from /usr/lib/ruby/gems/1.8/gems/rspec-1.1.11/lib/spec/runner/options.rb:221:in
`each?
from
Radiant provides two tasks to set the environment: production and
development. So you can run the rake task like so:
rake production db:check:config
Sean
Paul Ingles wrote:
Sorry, meant to add an example of the output:
Thanks Sean,
Changing it to execute that way still leaves it outputting
(in /home/rails/myapp/releases/20090109135907)
Checking database mysql configuration...
/usr/lib/ruby/gems/1.8/gems/rspec-1.1.11/lib/spec/runner/options.rb:
229:in `files_to_load':
File or directory not found: production
Can you run it with --trace?
Sean
Paul Ingles wrote:
Thanks Sean,
Changing it to execute that way still leaves it outputting
(in /home/rails/myapp/releases/20090109135907)
Checking database mysql configuration...
/usr/lib/ruby/gems/1.8/gems/rspec-1.1.11/lib/spec/runner/options.rb:229:in
Hi Sean,
Sorry- looks like that was incorrect. I don't get the RSpec errors
now, but it still fails to deploy. Here's the new output:
* executing sh -c 'cd /home/rails/myapp/releases/20090109173841;
rake production db:check:config --trace'
servers: [my.vm.brightbox.net]
