GitLab

- uses enviornment vars
- loads script that you can source when `vagrant ssh`'d in

- this was included in the original version of Go before cas
was fully utilised
- I'm not sure it even works and has been sitting around for a long time
- will slightly speed up builds

- figured out how to test urls woo

- thanks ubuntu

- django_manage still runs the server with python2, working on it
- can confirm manually running the server with python3 works

- need to hack around a bit before cleaning up

- cannot force 3.6 development with apt afaik

- whoops

- upping our style game

- vs. having it exist already then it asking you to remove it

- including a test that always passes and ensuring you can run it

- whoops

- upping our style game

- vs. having it exist already then it asking you to remove it

- including a test that always passes and ensuring you can run it

- "have you ever asked your bitch for more bitches"?

This reverts commit 83b26899

This reverts commit 78a3a58a

- the DB gets confused if you want to change models but the old migrations are still there
- getting problems solved by nuking everything -- the :dhaynes: way!
- now in master

- sometimes despite being listed in installed_apps, go models
will not be migrated, this ensures that

Whew, that was quite a lot. Where do I start?

To utilize Vagrant, you first need to install virtualbox and vagrant
itself. After those are installed, simply do "vagrant up" from the
project's root directory. That's it! It will install and set everything
up for you. Once the playbook has completed provisioning, simply go to
localhost:8000 in your browser. This directory is shared with the
virtual machine, so all changes made here will be reflected live!

Give it a shot!