This project automates the setup of a development environment for working on Ruby on Rails itself. Use this virtual machine to work on a pull request with everything ready to hack and run the test suites.

• VirtualBox

• Vagrant

Building the virtual machine is this easy:

host $ git clone https://github.com/41studio/rails-dev-box.git host $ cd rails-dev-box host $ vagrant up 

That's it.

After the installation has finished, you can access the virtual machine with

host $ vagrant ssh Welcome to Ubuntu 14.04.2 LTS (GNU/Linux 3.13.0-55-generic x86_64) ... vagrant@rails-dev-box:~$ 

Port 3000 in the host computer is forwarded to port 3000 in the virtual machine. Thus, applications running in the virtual machine can be accessed via localhost:3000 in the host computer. Be sure the web server is bound to the IP 0.0.0.0, instead of 127.0.0.1, so it can access all interfaces:

bin/rails server -b 0.0.0.0 

• Development tools

• Git

• Ruby 2.2

• Bundler

• Rails

• SQLite3, MySQL, and Postgres

• Databases and users needed to run the Active Record test suite

• System dependencies for nokogiri, sqlite3, mysql, mysql2, and pg

• Memcached

• Redis

• Elasticsearch

• Image Magick

• An ExecJS runtime

When you connect to vagrant, all development tool above will availabe to use. You can access the host folder with change to /vagrant directory or based your setting on file bootstrap.sh.

When done just log out with ^D and suspend the virtual machine

host $ vagrant suspend 

then, resume to hack again

host $ vagrant resume 

Run

host $ vagrant halt 

to shutdown the virtual machine, and

host $ vagrant up 

to boot it again.

You can find out the state of a virtual machine anytime by invoking

host $ vagrant status 

Finally, to completely wipe the virtual machine from the disk destroying all its contents:

host $ vagrant destroy # DANGER: all is gone 

Please check the Vagrant documentation for more information on Vagrant.

The default mechanism for sharing folders is convenient and works out the box in all Vagrant versions, but there are a couple of alternatives that are more performant.

Vagrant 1.5 implements a sharing mechanism based on rsync that dramatically improves read/write because files are actually stored in the guest. Just throw

config.vm.synced_folder '.', '/vagrant', type: 'rsync' 

to the Vagrantfile and either rsync manually with

vagrant rsync 

or run

vagrant rsync-auto 

for automatic syncs. See the post linked above for details.

If you're using Mac OS X or Linux you can increase the speed of Rails test suites with Vagrant's NFS synced folders.

With a NFS server installed (already installed on Mac OS X), add the following to the Vagrantfile:

config.vm.synced_folder '.', '/vagrant', type: 'nfs' config.vm.network 'private_network', ip: '192.168.50.4' # ensure this is available 

Then

host $ vagrant up 

Please check the Vagrant documentation on NFS synced folders for more information.

Error - Peer authentication failed for user "postgres" 

When you got this error when create or migrate database command, you need modify your pg_hba.conf file. Please change method of postgres user from "peer" to "trust"

Released under the MIT License, Copyright (c) 2012–ω Xavier Noria.