Having gotten Vagrant working generally to host a development environment on Windows, I have two main objectives left:
- Run a Rails server locally in my Vagrant vm so that I can do rails dev on Windows.
- Push a vagrantfile onto AWS so that I can “deploy” a rails server from Windows.
In pursuit of goal 1, I spent quite a bit of time looking at different posts that claimed to set up a rails environment on Virtual box in different ways. I learned that there’s a reasonable amount of variability in what people call a rails stack. Some of the posts depended on Chef, which is fine, but it’s not the tool I’m trying to use right now. Other posts depended on setting up a bare VM and SSHing into it and running a million little commands to get rails running properly, but that seems contrary to what I think Vagrant is for. I want to get all my Vagrantfiles and bootstrap.sh
‘s right, and then just vagrant up
. I don’t want to spend all day babysitting some VM that has weird locality errors when you install Postgresql. Continue reading “Ruby on Rails on Vagrant”