Symlink ~/roundware-server to Apache code on production servers so manage.py works

[13rac1]

@hburgund and I discovered an issue with the production server upgrade process. We couldn't get Django migrations to run while using the roundware user (Note: vagrant user is used on development VMs.) The issue was install.sh was making another copy of the codebase for the roundware user, but deploy.sh was never updating it. The solution is for ~/roundware-server to always be symbolic link. On dev VMs it goes to /vagrant and on production systems it goes to /var/www/roundware/source/. The roundware or vagrant user .profile always deferences the symbolic link to create the PYTHON_PATH environment variable.

Now the following will work on a production machine (so it acts the same as on dev):

sudo su - roundware
cd ~/roundware-server/roundware
./manage.py migrate

This commit fixes the issue for new installations. The following will "upgrade" existing production installs:

sudo rm -rf /home/roundware/roundware-server/
sudo ln -snf /var/www/roundware/source/ /home/roundware/roundware-server