Improve deployment process

[lparsons]

• [ ] Review Django Deployment Checklist
• [ ] Update this issues with specific steps as needed
• [ ] Document deployment steps to serve as a guide for production and future automation with ansible

[lparsons]

Basic deployment process at https://nplcadmindocs.princeton.edu/index.php/TraceBase#Deployment_Process. This should be improved for the next cycle.

[hepcat72]

Note, I added:

https://nplcadmindocs.princeton.edu/index.php/TraceBase#TraceBase_Documentation

[lparsons]

Note, I added:

https://nplcadmindocs.princeton.edu/index.php/TraceBase#TraceBase_Documentation

Thanks @hepcat72. I would suggest that we keep that sort of documentation together with the code in the repository. I'd like to keep as much in GitHub along with the code as possible. Only Princeton specific things should really need to be in the NPLCAdmin docs (e.g. server addresses, file paths, apache configs, etc.)

[hepcat72]

Note, I added: https://nplcadmindocs.princeton.edu/index.php/TraceBase#TraceBase_Documentation

Thanks @hepcat72. I would suggest that we keep that sort of documentation together with the code in the repository. I'd like to keep as much in GitHub along with the code as possible. Only Princeton specific things should really need to be in the NPLCAdmin docs (e.g. server addresses, file paths, apache configs, etc.)

I had trouble finding information about the docs deployment and my instinct was to look where the other deployment info was (in nplcadmin), but I tried not to duplicate the info in the repo - just create a reference to it (aside from the brief summary), since it had taken me awhile to discover it was where it was. I didn't know that it even existed, so I think referencing it in nplcadmin is appropriate, though I generally agree with you where it should live.