Simplify and document deploy procedures.

[timparenti]

Currently, different aspects of this repo appear to be deployed to /var/www/ctfws-timer and /home/ctfws-timer on the server, but the related section of README.md is incomplete and out-of-date:

ctfws-timer-web/README.md

Lines 7 to 9 in a78fe39

	## The Page
	The page `timer.html` is entirely self contained. To deploy, just ssh to the
	website server, navigate to `/home/www/activities/ctfws_timer`, and git pull.

Additionally, there is some special Apache configuration on the VirtualHost, presumably to ensure Django works properly on the application side.

@michaelfelixmurphy and I should work together to simplify this process, and update where these files should live on the server with respect to the new conventions implemented as part of the overall website migration project in February 2019. Then flesh out deployment documentation for the benefit of those less familiar with Django, as well as those who are likely to forget that you have to restart Apache.

[michaelfelixmurphy]

This is, of course, a very good point.

The README is not that far off in this particular area. The repo seems to have moved to /home/ctfws-timer. But the deploy procedure is still just pull (and maybe kick apache2 with a reload - there's probably a less invasive way to do this but it's what I do). The /var/www/ctfws-timer/ directory is just for static files (which are few and very rarely change). There is a Django collectstatic command to copy static files from the repo to the permanent static home, but it's basically never necessary.