Chris Oliver

You add them in. Put them under the development section.

It is inside your Rails app, inside the config directory. See this: https://www.evernote.com/sh...

You can just open that file in your favorite text editor and set the username and password keys inside it. I'd recommend using Sublime Text or something similar to do that.

That's a good question. I would imagine you could set a system proxy on your OS and your network traffic would flow through there. Hopefully that would take care of routing all the downloads through there without having to configure a proxy inside the Vagrant guest machine too.

Ouch, that's kind of nasty. I hope they get that fixed soon. Thanks for sharing the link!

So when you ran brew install those directories were empty? That's odd.

It's best to make the changes, commit them, and deploy again. Now that you have everything working, the site will just seamlessly update when you deploy.

If you just want to tweak one of the config files in shared that isn't part of the Rails app (like database.yml) you can edit this file manually and them touch tmp/restart.txt

You'll need to make sure you delete the default server block for Nginx, add your Rails one, and then run "sudo service nginx restart" to load all those new configs.

Make sure that you type in the quotes by hand. It looks like the first quotes are an HTML formatted one but not the normal one.

Thanks! I'll be sure to update that.

Sounds like you had internet connectivity problems. Try running it again and see if it works next time?

Make sure you run it inside of a rails app directory otherwise it will just display usage info.

Minitest is used for development so you should not see this in production. Are you sure you used RAILS_ENV=production everywhere?

That will work just fine.

Haven't seen that before. Does this help? http://stackoverflow.com/qu...

No problem!

Correct, you'll want to do both of those after creating.

You can deploy as many times as you need safely. It will keep copies in the releases folder. When it is successful, it will symlink it to the current folder that we just talked about.

Ah okay, so either cd into one of the releases folders (capistrano may have removed failed deploys so there may not be any) and run the rake db:create or open up the mysql command line and create the database manually instead.

Great! :) Are you in the app's current directory?

Well you can do Author.books.available because that's just querying Book.where(author_id: X).available. But obviously this is for the more complex joining tables case, so at least you're working with the models like you normally would. Not the best, but it saves you from duplication.