Chris Oliver

It's on the server in the /etc/nginx folder. You can type nano /etc/nginx/nginx.conf or use vim instead to edit it through your SSH connection.

I'm not sure if you can do that with the typical json. The database recipe should let you do that, but you'll likely need to write some calls to it instead of defining json. https://github.com/opscode-...

I really like ZSH because of all the cool shortcuts you get if you set up various plugins. There are ones for bundler that alias be to bundle exec for you along with a bunch of other common ones. Take a look at this for the plugins you can get with oh-my-zsh which is a common zsh distribution.

My dotfiles are over at http://github.com/excid3/dotfiles

I've been meaning to build some install scripts for it, but just haven't had the time. I'm using iTerm2 because it adds a lot of benefits over the default Terminal on OSX. It's super configurable with splitting windows and other useful features. http://iterm2.com/features.html

My theme you see in iTerm is a mixture of the excid3 zsh theme inside my dotfiles and the iTerm colors file. The iTerm colors will set them to be monokai colors in the terminal and then the zsh prompt sets up the descriptive prompt. I wanted it to be more like a sentence description rather than a jumble of various details like most prompts are. I'm pretty happy with it so far.

YADR is awesome and I like that it even contains vim plugins. I'm using Janus for my Vim configuration so at some point I'll give YADR a try and see how it goes. I've been pretty happy with Janus + zsh though so I'm not in a huge hurry to switch. ;)

Ancestry is a great solution to the problem. To do this manually, you may want to instead change the update action in your controller to:

• Load the old record into a variable
• Create a new record
• Then update the old record to link to the new one as a child of it

This way your newest record will always be the most recent and each post can belongs_to it's parent post. In effect, you're just setting old record with a new parent each time you update it.

Yep! :) Glad you got it working!

If you used rbenv and have installed the Rails gem, make sure to run

rbenv rehash

This will make the "rails" executable visible to your terminal by putting a stub in your PATH.

Thanks for the tips Dave! :)

Hey everyone!

Today I am releasing the GoRails forum. This is the place you can turn when you need advice for how to design a feature or refactor your code. I'll be answering questions here and discussing Rails topics as well as hopefully turning some of these questions into screencasts.

This forum is custom built so if you run into any issues let me know. I'm going to be using this as an example for some screencasts so you can see how I built it as well.

It's a Monokai theme for ZSH. You can download it here https://github.com/excid3/d...

That looks correct, but you'll always want to check the sub folders too. You may also want to try changing the user to deploy in the nginx config.

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.