Chris Oliver

I think this comes from your Capfile not being configured appropriately. Double check that step and make sure you've got all the correct require statements.

Did you install Vagrant from the rubygem before? I linked to the installer and make sure you remove the Vagrant gem.

Glad you found it!

You can check the nginx log then for errors and you should find something there. Could be syntax errors for example.

Looks like you're trying to install with an RVM version of Ruby. https://github.com/Homebrew...

Your deploy was successful. The failures are supposed to happen.

Make sure you point nginx to /home/deploy/sample_app/current/ and restart it.

The Ruby openssl extension was not compiled. Missing the OpenSSL lib?

Did you install the OpenSSL lib with apt-get?

It's inside your rails app; a file in the config directory.

If you used rbenv, make sure you run rbenv rehash after installing the Rails gem. That makes the gem's executables available to use. It currently isn't available, so Ubuntu is suggesting a different installation method.

Yep! For error logs, check out this file for your production logs: /home/deploy/MYAPP/current/log/production.log

Well, it's saying that you should update your config/secrets.yml to include a section for production. You can either set it up in the file and commit it, or you can remove it from git and set it up to link the file on deploy just like your database.yml

Try

passenger_ruby /usr/local/rvm/wrappers/ruby-2.1.2/ruby

but replace that version of Ruby with the one you installed in case it is different.

Dang! :\ To be fair, Heroku's simplicity is pretty darn impressive and I don't blame you.

If you ever do need to get your site running on a VPS, shoot me an email and we can do a short one-on-one gig and I can probably get you squared away.

I guess, just double check that you've got it in the right format then. Can't think of anything else that would be wrong. You're pretty close now!

Thanks for sharing Maxime! I've also written a post on this about without having to setup a new controller. https://gorails.com/blog/ra...

Here's an example: https://github.com/excid3/a...

Interesting, that all looks correct to me.

Looks like you've already got a database.yml in your repo. Either remove the symlink on deploy and add your credentials to that file, or remove the file from git so that it can symlink on deploy.

That's okay because it is just cloning the repository. It looks like the symlink is crashing possibly because /home/deploy/gymsight/shared/config/database.yml doesn't exist. Have you double checked that file exists?

When you rake db:create in development it also tries to create the test database. Make sure you also have the proper username and password for the test environment. This is telling you it can't connect.