|Project Name||Stars||Downloads||Repos Using This||Packages Using This||Most Recent Commit||Total Releases||Latest Release||Open Issues||License||Language|
|Rails Dev Box||2,046||4 months ago||11||mit||Shell|
|A virtual machine for Ruby on Rails core development|
|Ruby Benchmark Suite||159||10 years ago||1||other||C|
|A set of Ruby benchmarks for testing Ruby implementations.|
|Rails Starter Box||137||9 years ago||3||Puppet|
|Base Vagrant box for development of Rails apps|
|Madscience||72||8 years ago||1||mit||Ruby|
|Deploy your Rails app with a full dedicated server in an hour! The source for Ruby Mad Science and Rails Deploy In An Hour|
|Minotauro_vagrant_rails||65||6 years ago||mit|
|:taurus: Base Vagrant box for development of Ruby on Rails apps|
|SUSE Hack Week tools and data|
|Rails Development Environment||50||6 years ago||mit||Shell|
|Development environment for Ruby on Rails based on Vagrant, VirtualBox and Ubuntu 16.04 LTS (Xenial Xerus).|
|Chef Rails Dev Box||50||10 years ago||Ruby|
|Yet another rails-dev-box|
|Vagrant Rails Project Box||32||9 years ago||Ruby|
|A rails dev box for Vagrant, built using Chef & Librarian|
Please note this VM is not designed for Rails application development, only Rails core development.
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.
vagrant plugin install vagrant-vbguest.
Building the virtual machine is this easy:
host $ git clone https://github.com/rails/rails-dev-box.git host $ cd rails-dev-box host $ vagrant up
After the installation has finished, you can access the virtual machine with
host $ vagrant ssh Welcome to Ubuntu 22.10 (GNU/Linux 5.19.0-21-generic x86_64) ... [email protected]:~$
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
By default, the VM launches with 2 GB of RAM and 2 CPUs.
These can be overridden by setting the environment variables
RAILS_DEV_BOX_CPUS, respectively. Settings on VM creation don't matter, the environment variables are checked each time the VM boots.
RAILS_DEV_BOX_RAM has to be expressed in megabytes, so configure 4096 if you want the VM to have 4 GB of RAM.
SQLite3, MySQL, and Postgres
Databases and users needed to run the Active Record test suite
System dependencies for
An ExecJS runtime
The recommended workflow is
edit in the host computer and
test within the virtual machine.
Just clone your Rails fork into the rails-dev-box directory on the host computer:
host $ ls bootstrap.sh MIT-LICENSE README.md Vagrantfile host $ git clone [email protected]:<your username>/rails.git
Vagrant mounts that directory as /vagrant within the virtual machine:
[email protected]:~$ ls /vagrant bootstrap.sh MIT-LICENSE rails README.md Vagrantfile
Install gem dependencies in there:
[email protected]:~$ cd /vagrant/rails [email protected]:/vagrant/rails$ bundle
We are ready to go to edit in the host, and test in the virtual machine.
Please have a look at the Contributing to Ruby on Rails guide for tips on how to run test suites, how to generate an application that uses your local checkout of Rails, etc.
This workflow is convenient because in the host computer you normally have your editor of choice fine-tuned, Git configured, and SSH keys in place.
When done just log out with
^D and suspend the virtual machine
host $ vagrant suspend
then, resume to hack again
host $ vagrant resume
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
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 an 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
host $ vagrant up
Please check the Vagrant documentation on NFS synced folders for more information.
vagrant up, it's possible to get this error message:
The box 'ubuntu/yakkety64' could not be found or could not be accessed in the remote catalog. If this is a private box on HashiCorp's Atlas, please verify you're logged in via vagrant login. Also, please double-check the name. The expanded URL and error message are shown below: URL: ["https://atlas.hashicorp.com/ubuntu/yakkety64"] Error:
And a known work-around (https://github.com/Varying-Vagrant-Vagrants/VVV/issues/354) can be:
sudo rm /opt/vagrant/embedded/bin/curl
Released under the MIT License, Copyright (c) 2012–ω Xavier Noria.