Difficulty executing installation instructions
cboettig opened this issue · comments
Thanks for providing what looks like a very promising open source alternative to disqus.
Unfortunately I've been unable to run your install directions as provided. I'm not experienced with rails apps, so my apologies if this is elementary. First couple steps are fine, but upon running
bundle exec rake db:schema:load RAILS_ENV=production
I hit the error and traceback shown below. Any hints as to what I've done wrong here? Many thanks for your advice.
Could not load sequel gem, so WordPress import will not work.
rake aborted!
No such file or directory - /home/cboettig/Documents/code/thirdparty/juvia/config/application.yml
/home/cboettig/Documents/code/thirdparty/juvia/lib/app_config.rb:76:in `block in <class:Railtie>'
/home/cboettig/Documents/code/thirdparty/juvia/help/ruby/1.9.1/gems/railties-3.1.10/lib/rails/initializable.rb:30:in `instance_exec'
/home/cboettig/Documents/code/thirdparty/juvia/help/ruby/1.9.1/gems/railties-3.1.10/lib/rails/initializable.rb:30:in `run'
/home/cboettig/Documents/code/thirdparty/juvia/help/ruby/1.9.1/gems/railties-3.1.10/lib/rails/initializable.rb:55:in `block in run_initializers'
/home/cboettig/Documents/code/thirdparty/juvia/help/ruby/1.9.1/gems/railties-3.1.10/lib/rails/initializable.rb:54:in `each'
/home/cboettig/Documents/code/thirdparty/juvia/help/ruby/1.9.1/gems/railties-3.1.10/lib/rails/initializable.rb:54:in `run_initializers'
/home/cboettig/Documents/code/thirdparty/juvia/help/ruby/1.9.1/gems/railties-3.1.10/lib/rails/application.rb:96:in `initialize!'
/home/cboettig/Documents/code/thirdparty/juvia/help/ruby/1.9.1/gems/railties-3.1.10/lib/rails/railtie/configurable.rb:30:in `method_missing'
/home/cboettig/Documents/code/thirdparty/juvia/config/environment.rb:5:in `<top (required)>'
/home/cboettig/Documents/code/thirdparty/juvia/help/ruby/1.9.1/gems/activesupport-3.1.10/lib/active_support/dependencies.rb:240:in `require'
/home/cboettig/Documents/code/thirdparty/juvia/help/ruby/1.9.1/gems/activesupport-3.1.10/lib/active_support/dependencies.rb:240:in `block in require'
/home/cboettig/Documents/code/thirdparty/juvia/help/ruby/1.9.1/gems/activesupport-3.1.10/lib/active_support/dependencies.rb:223:in `block in load_dependency'
/home/cboettig/Documents/code/thirdparty/juvia/help/ruby/1.9.1/gems/activesupport-3.1.10/lib/active_support/dependencies.rb:640:in `new_constants_in'
/home/cboettig/Documents/code/thirdparty/juvia/help/ruby/1.9.1/gems/activesupport-3.1.10/lib/active_support/dependencies.rb:223:in `load_dependency'
/home/cboettig/Documents/code/thirdparty/juvia/help/ruby/1.9.1/gems/activesupport-3.1.10/lib/active_support/dependencies.rb:240:in `require'
/home/cboettig/Documents/code/thirdparty/juvia/help/ruby/1.9.1/gems/railties-3.1.10/lib/rails/application.rb:83:in `require_environment!'
/home/cboettig/Documents/code/thirdparty/juvia/help/ruby/1.9.1/gems/railties-3.1.10/lib/rails/application.rb:203:in `block (2 levels) in initialize_tasks'
Hey @cboettig. You'll want to copy over the config/application.yml.example file like this:
cp config/application.yml.example config/application.yml
Change the configuration in application.yml for your needs and save it. Then run the command again.
thanks, I'm an idiot. Just to clarify, I should be running all this on a server, rather than running it locally and then copying over the files? And I would copy the entire directory into the domain where I have Passenger set up to deploy? thanks much.
Yes you should be running the installation instructions on the server that you want to deploy to. bundle install
installs dependency libraries on the local machine. rake db:migrate
creates/updates database tables. Naturally those commands mutate state outside of the Juvia directory so copying the Juvia directory over to the server is not sufficient.
The current installation instructions are not quite short and kind of assume that the user is familiar with Rails. I believe it would be a good idea to elaborate more on the commands for users who are not familiar with Rails.
I've opened issue #43 which advocates the creation of Debian packages for ease of installation, so I'm closing this issue.