Implement deployment mechanisms

[campb303]

webqueue2 has grown into a complex system with several steps to setup a development environment and a production environment. It takes upwards of 20 minutes to set these up by hand and it would greatly reduce testing/deployment time to have these actions scripted. Below are rough descriptions of how the deployment scripts should behave.

Deployment Script

1. Check for linting errors (babel for JSX and JS, pylint for Python)
   • Fail if linting isn't successful and show linting errors
2. Run tests (Jest for JSX and JS, pytest for Python)
   • Fail if tests aren't successful and show unsuccessful tests
3. Rebuild documentation(s)
4. Build the frontend
5. Bundle the frontend build, API files and API requirements file
6. Deploy to the desired server(s)
7. Start the web server for the frontend
8. Start the API server for the backend

Separating functionality and allowing for a production side upgrade path should be a consideration and thought through during the development of this tooling.

[campb303]

#45 is related to this.

[campb303]

Marking as a duplicate of #11