3. Install Ruby 1.9.3. We recommend RVM: https://rvm.io/
4. Open a terminal
5. Clone the project: `git@github.com:discourse/core.git`
6. Enter the project directory: `cd core`
7. Install vagrant: `gem install vagrant`
### Using Vagrant
When you're ready to start working, boot the VM:
```
vagrant up
```
It should prompt you for your admin password. This is so it can mount your local files inside the VM for an easy workflow.
(The first time you do this, it will take a while as it downloads the VM image and installs it. Go grab a coffee.)
Once the machine has booted up, you can shell into it by typing:
```
vagrant ssh
```
### Keeping your VM up to date
Now you're in a virtual machine is almost ready to start developing. It's a good idea to perform the following instructions
*every time* you pull from master to ensure your environment is still up to date.
```
bundle install
bundle exec rake db:migrate
bundle exec rake db:seed_fu
```
### Starting Rails
Once your VM is up to date, you can start a rails instance using the following command:
```
bundle exec rails server
```
In a few seconds, rails will start server pages. To access them, open a web browser to http://localhost:4000 - if it all worked you should see discourse! Congratulations, you are ready to start working!
You can now edit files on your local file system, using your favorite text editor or IDE. When you reload your web browser, it should have the latest changed.
### Guard + Rspec
If you're actively working on Discourse, we recommend that you run Guard. It'll automatically run our unit tests over and over, and includes support
for live CSS reloading.
To use it, follow all the above steps. Once rails is running, open a new terminal window or tab, and then do this:
```
vagrant ssh
bundle exec guard -p
```
Wait a minute while it runs all our unit tests. Once it has completed, live reloading should start working. Simply save a file locally, wait a couple of seconds and you'll see it change in your browser. No reloading of pages should be necessary for the most part, although if something doesn't update you should refresh to confirm.
### Shutting down the VM
When you're done working on Discourse, you can shut down Vagrant like so:
