Skip to content

Commit

Permalink
Call rails server with bundle exec [skip ci]
Browse files Browse the repository at this point in the history
  • Loading branch information
axilleas committed Dec 1, 2014
1 parent dfc1c92 commit 8b5eb36
Show file tree
Hide file tree
Showing 2 changed files with 10 additions and 10 deletions.
14 changes: 7 additions & 7 deletions CONTRIBUTING.md
Expand Up @@ -26,16 +26,16 @@ Once you have the dependencies installed, go to the project directory via consol

$ vagrant up

The first time you run _vagrant_, the process will take several minutes, as it will download the base box and run all the tasks necessary to setup the VM server.
The first time you run _vagrant_, the process will take several minutes, as it will download the base box and run all the tasks necessary to setup the VM server.
Once the process is completed, you need to log in, by running:

$ vagrant ssh

There's no need to provide login or password. Now go to the project directory inside the VM in order to run the rails server:

$ cd /vagrant
$ rails s
$ bundle exec rails s

This will initialize the development Rails server.
Now you can go to your regular browser, in the Host machine (your main OS) and access the application through the address `http://192.168.12.34:3000`.

Expand All @@ -44,12 +44,12 @@ Any changes that you make to the app files will be reflected inside the VM serve
When you want to pause or finish working, you can run:

$ vagrant suspend

And the VM will be suspended. Whenever you want to get back to it, the state will be saved, you just need to run:

$ vagrant resume

To get the VM running again, in the state you left it. Remember that if you turn off the VM or if you restart your main OS, you will need to run `vagrant up` again, but this time
it will be much faster because the VM is already provisioned.

For more instructions on how to use Vagrant, have a look at their official documentation: [https://docs.vagrantup.com/v2/getting-started/](https://docs.vagrantup.com/v2/getting-started/).
For more instructions on how to use Vagrant, have a look at their official documentation: [https://docs.vagrantup.com/v2/getting-started/](https://docs.vagrantup.com/v2/getting-started/).
6 changes: 3 additions & 3 deletions Readme.md
Expand Up @@ -98,7 +98,7 @@ The included Vagrant setup uses Ansible as provisioner. First, you'll need to in
* [Vagrant](https://www.vagrantup.com/downloads.html)
* [VirtualBox](https://www.virtualbox.org/wiki/Downloads)
* [Ansible](http://docs.ansible.com/intro_installation.html)

_Windows Users: Ansible does not support Windows as controller machine, but there's a little hack in the Vagrantfile that will allow you to run the provision using a local
SSH connection Guest-Guest. Just install Vagrant and VirtualBox, and you should be able to get it running._

Expand All @@ -111,11 +111,11 @@ is finished, log in to run the rails dev server:

$ vagrant ssh
$ cd /vagrant
$ rails s
$ bundle exec rails s

Then you should be able to access the application through your regular browser at http://192.168.12.34:3000.

Simply edit the files in the project directory using your favorite editor on your host machine and the changes will be automatically reflected in the `/vagrant` directory inside the guest virtual machine and so you can see the changes on your browser.
Simply edit the files in the project directory using your favorite editor on your host machine and the changes will be automatically reflected in the `/vagrant` directory inside the guest virtual machine and so you can see the changes on your browser.

### Tests

Expand Down

0 comments on commit 8b5eb36

Please sign in to comment.