Chris Oliver

Does sudo apt-get update work? It's saying something is wrong with that.

Take a look at this: http://stackoverflow.com/qu...

What did you set for your repo_url?

That's what Bundler is for. Your version of Rails is application specific, so you let Bundler manage it with your app's Gemfile.

If you have multiple versions of ruby, you'll want to set the default (or use rbenv/rvm to switch). For me, I have 1.8.7, 1.9.3, 2.0, and 2.1 installed on my machine. I set 2.1.2 as the default, but certain applications switch back to 1.9 and 1.8.7 for me.

I'd guess you just haven't set the default to 2.1.2 yet and that's what is missing.

If you've already downloaded all the gems and ruby versions, you can work offline but if you need to install anything new, you'll need an internet connection.

Great! Let me know if there's anything I can make more clear for that part.

Should be as simple as adding in the ".com" to the host thing in your production.rb that you added earlier I believe.

Yeah you'll need to run redis-server in production if you use sidekiq.

You can add config.action_mailer.default_url_options = { host: 'yourdomain.com' } to your config/production.rb file. Just change "yourdomain.com" to the domain or IP address you are using.

Well it says: Missing host to link to! Please provide the :host parameter, set default_url_options[:host], or set :only_path to true

So you need to set that in your different environment.rb files. Probably forgot to add that in your production.rb

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.