Activity
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.
Thanks for sharing Nick!
Awesome stuff. Thanks for sharing Daniel.
Hey Steve, this setup is primarily for development. On a production AMI on AWS you probably want to run a server like Passenger so that it can serve up the app on port 80. This tutorial might be more what you're looking for https://gorails.com/deploy/...
If you're wanting to do development on AWS though, you probably just need to open up port 3000 in your security group because I can bet the firewall is blocking it.
The Gemfile is in the top folder in your Rails application.
Awesome! glad you got that figured out and thanks for sharing. I'll be sure to note this for the future.
Sometimes people keep database.yml in their repository but then your production password is saved in your code repo so a lot of people choose not to do it that way.
Let me know if I can help out with any of the other issues!
Hey Daniel,
You'll need to manually create a database.yml file on your server. It's trying to link it but it hasn't been created yet. So you can ssh in and edit that file
nano /home/deploy/my_actual_app_name/shared/config/database.yml
and put in your database config for the server database that you just setup.
Good find! Thanks for sharing this.
Good to hear but sorry you had to rebuild! There's a link to the about page in the footer that has my email address on it if you need to get ahold of me in the future.
Dang. Well, one good practice is to always disable password authentication with SSH. http://askubuntu.com/questi...
I'll probably add this step into the tutorial tomorrow because that's no fun at all.
Hmm, looks like it's similar issue. One last suggestion from my server that I have running apache instead of Nginx (but still uses Passenger) is to use this for passenger_ruby:
passenger_ruby /usr/local/rvm/wrappers/ruby-2.1.2/ruby
It's possible the wrapper helps it load the proper version. This is one of the problems with rvm in the sense that it integrates almost too much with your environment causing it to be a headache to set up at times.
My bad. I misread. You're using rvm so that wouldn't help anyways. Try:
passenger_ruby /usr/local/bin/passenger_ruby;
Try changing it to passenger_ruby /home/deploy/.rbenv/shims/ruby; and restarting nginx to see what happens. I think pointing directly to that version of Ruby should work, but I've also always just pointed it to the shim.
Double check that you set your nginx passenger_ruby to point to RVM or Rbenv properly and that you set the global ruby version to 2.1.2.
Ouch! Did you have a short password?
You want to run sudo nano /etc/nginx/nginx.conf instead (not the /opt one).
You can see the file as your deploy user but you can't actually save changes. That's why you need sudo so that you can save your changes.
I think because that's not a command you run in your terminal but you need to add that to the file named Gemfile instead.