Maintenance Guide

Whether you're helping to run HackUCF or another organization, you will likely run into some maintenance issues and deployment concerns. Here's a collection of some common tasks.

Knowledge of Google's API structure, how to run Django commands, and Google API permissions can help.

New academic year's coming up. What do I do?

Congrats on maintaining someone else's application...!

Read How it Works. Then you should:

1. Back up last year's database. Maybe save it somewhere?
   1. ./manage.py dumpdata | bzip2 > ~/1996-1997_ppl.json.bz2
2. Delete the database or redeploy somewhere else
3. Change FILE_ID for membership and resumes to the new sheet IDs, if applicable.
4. Ensure any new sheets conform to the required formats (do a dry run on the sheet data if the semester hasn't started yet)
5. If the previous maintainer will not have access to the new sheet IDs:
   1. Reauthenticate ppl with your account - ./manage.py update_membership --noauth_local_webserver
   2. Create yourself a superuser - ./manage.py createsuperuser
   3. Consider removing previous superusers after you think everything's working
6. Find someone to update ppl's code and documentation this year

How do I make the site automatically update?

Schedule the following commands to run periodically:

./manage.py update_membership -m insertmailchimpkeyhere
./manage.py update_resumes

ppl's first deployment ran this every two hours.