Activity
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.
Hmm, that's odd. It shouldn't be trying to remove the file. Can you send over some more of your logs in a github gist?
Oh! That's an interesting one. It has happened to me before but that definitely is an obscure one. I'm glad you got it figured out!
Awesome!! :)
One thing is to check and make sure your config points to the right directory. It definitely has happened to me before, but it is almost always a case of either reading the wrong config or the config pointing to the wrong folder.
One thing (and I updated the line) is that it should be perform -t production_backup to match the name of the backup that you created earlier.
That should be it I imagine.
Sometimes having failed commands is good. It occasionally checks to see if it needs to create a directory like this one so it fails because it already exists which is totally okay.
I've had times where I went through everything and I couldn't find it so I ended up deleting all the files and starting from scratch so I know the feeling well. ;-)
Make sure the file is saved, but that's all you should need to do. You can try doing a project wide search in your text editor to find "example.com". That should point you to it.
Check your config/deploy/production.rb file to make sure it doesn't have example.com in it. I would guess that's where it is coming from. Swap that with your domain or IP and you should be good.
When you use mysql from the command line, you must specify your user and tell it you will type in a password:
mysql -u root -p
It should be the root user by default. Test it with this command and then put those credentials in your database.yml under production.
I don't mind at all Jakub. Let me know if there's anything I can help with.