Skip to content
This repository was archived by the owner on Oct 7, 2023. It is now read-only.

Recommended development workflow

Timothy Bueno edited this page Aug 25, 2013 · 4 revisions

Set up the developer environment described in the wiki.

You will have at least two main terminal windows open. One will allow you to interact with the Ubuntu virtual machine provided by the vagrant program. The other will allow you to interact with git on your local machine for committing changes. You may wish to have a third terminal session to interact with the Ubuntu virtual machine.

Make sure you are currently working in the develop branch in your local machines terminal:

  • $ git status

The Ubuntu virtual machine can be started like so:

  1. $ vagrant up
  2. $ vagrant ssh
  3. $ workon longboxed
  4. $ cd /vagrant

You can then edit your code on your local machine as normal. The /vagrant directory in the virtual machine is linked to your project directory!

Try running the program!

  • $ python wsgi.py

Work on specific features and bug fixes by branching off of the develop branch into a branch called feature/cool_new_feature. More information can be found on the recommended branching workflow here:

Version control best practices

Two specifics to remember:

  1. Never commit to the master branch directly or without confirming with the team
  2. Always merge completed feature branches back into the develop branch for inclusion in the next release.

When you are finished working for the day:

  1. Exit the SSH session
  2. $ vagrant halt

Clone this wiki locally