Provisioning

Install http://www.vagrantup.com/ and install Ansible (brew install ansible on OS X, sudo apt-get install ansible on Debian based machines). If you are using Windows you still need to check this directory out, but you will not be able to use Vagrant/ansible. You should instead create a VirtualBox VM with Ubuntu 12.04, install ansible, and run provisioning/local.sh instead.

Run git clone http://github.com/ayaigame/ayai-deploy.git and change into that directory.

Run vagrant up. This will download and setup a basic Ubuntu 12.04 LTS virtual machine. It will then attempt to provision. This will fail the first time halfway through. Run vagrant provision to restart the process, which should succeed this time.

This process will take some time as it is setting up a server suitable for Ayai as well as some general backend trickery to make development easier.

It will also attempt to compile the Ayai backend as the last step. This may take a long time and if you wish to see it's process, I would Ctrl-C out of the provisioning and manually build it myself (this will happen naturally following the next steps).

After this, run vagrant ssh. You are now ssh'ed into the Vagrant virtual machine. cd /vagrant/ to see a directory that is synchronized with the directory you checked out into.

Firstly, run sudo service nginx restart. For some reason, ansible believes nginx to have been restarted when it hasn't yet (possibly due to a non-standard Websocket friendly version being used).

Secondly, cd into (inside either /vagrant/ or wherever you checked out ayai-deploy to) ayai-frontend. Edit the file js/ayai/Ayai.js on the Connection line, to now point to ws://192.168.100.10/ws. Save this file.

Finally, cd into (inside of /vagrant/, not on your own machine) ayai-backend. Run sbt run. If you cancelled the compile process earlier, it will attempt to compile here. After several messages you will eventually see Running SockoServer. This means that the database, generated worlds, and every remaining step has been completed.

Navigate in your browser (on your local machine, not inside of vagrant) to 192.168.100.10/debug.html. If all goes well, you should now have a copy of Ayai running on your machine.

When you are done with development, switch to wherever you checked out ayai-deploy and run vagrant halt. This will turn off the Vagrant virtual machine and prevent it from hogging any resources.

The reason we chose to do this was to keep dependencies across multiple platforms synchronized and since there are CORS issues with running a web server/app server on two different domains. This, of course, can be circumvented, but has been left as an exercise to the reader.