Ignore ./rails

[simonjefford]

This allows users to have a clone in their rails-dev-box checkout that will automatically appear in their /vagrant folder. That way they can edit files "locally" and test the changes on the vagrant box.

[fxn]

This PR comes in the right time. I am pondering changing the "What's next section" to suggest cloning the fork in the home of the box as you do, since git and SSH keys and preferred editor are all set in the host normally. Is it working well for you?

Nevertheless, what is the point of ignoring the "rails" directory? People are not going yo modify the virtual machine itself right?

[simonjefford]

I guess it's just an OCD thing, my command prompt no longer shows a dirty working folder if "rails" is ignored :-) Also, slightly more seriously, I guess if you are going to contribute a change to rails-dev-box itself this would prevent accidentally adding rails as a submodule.

Agree it's probably of marginal benefit though...

(Either way, adding something to the README to suggest doing this is probably a good idea)

[fxn]

On a second thought, that may helpful to me myself also to check how editing from /vagrant works... in then. Thanks!