Chris Oliver

Permissions are probably good. You also want to check if it is owned by deploy and not root or someone else. ls -la will show you which user and group the files/folders are owned by. You can then use chown to modify that if you need to.

You may need to check and make sure the app directories are (recursively) all set to be owned by the deploy user. That's a somewhat common cause for that error.

That's no fun. Do you still have the error to share?

Send a copy of your config to me at chris@gorails.com and I'll see if I can help!

The first one. It's saying it can't ssh into domain.com as the deploy user. When you ssh in manually with ssh deploy@domain.com that should connect without asking you for a password. That works correctly?

forward_agent is mainly just used when it checks out your code from Github or the like. It will use the key you deploy with to talk to github instead of a key on the server.

Don't specify the keys option there. Your local key in ~/.ssh/id_rsa will be tried against the server's /home/deploy/authorized_keys file. Capistrano won't allow password authentication, so you must make sure you ran the ssh-copy-id to add your pub key to the server deploy user's authorized_keys file.

You could probably do something like this in your controller:

@posts = Post.paginate(page: params[:page])
redirect_to root_path if @posts.empty?

Yeah, when it says authentication failed, it means it couldn't connect over SSH. You'll need to tweak your deploy config to make sure it matches your SSH configuration.

Absolutely! I'll probably plan on covering this in a screencast or a separate tutorial.

Oh hey, good find. I'll be sure to update that soon.

I'm covering Pundit next, but CanCan is by far the leader with 4 million downloads. CanCanCan is the community maintained version of cancan so it is still always up-to-date. I'm going to do a few authorization approaches in a row so we can compare them side by side and you can determine which works the best for you.

The package names have probably changed a bit. You may want to switch to the 13.04 version as it probably has some more similar package versions.

That's interesting. Do you get any errors in the console that show the browser having trouble loading the icon font by chance?

Yes! I forgot to mention that. Thanks for sharing. :)

Great post Nick. That will be useful for anyone running into trouble with rvm. I'll be sure to point people that direction if they have issues. :)

Depends on what you want to do, but generally Passenger is quite good on all fronts. You can read some more about some performance testing but no matter what, it isn't going to be definitive that one is always better than another. https://blog.engineyard.com...

That would be a problem with your nginx config. The IP address doesn't matter, it's okay to serve up on that instead of a domain. You may have changed the config and not restarted nginx or you did and it was invalid and nginx didn't actually load it. Double check that and the /var/log/nginx/error.log file to see if you have anything wrong there.

Thanks David! :)

Plenty of cases, but most of those revolve around building out a very custom onboarding flow. Most of the time (including OAuth) is handled well enough with Devise.