Deployment automation pipeline using Github Actions

[monikkaelyse]

Description

We would like to set up Github Actions to automatically deploy so that this is no longer a manual step and the site is more up to date.

Expected Behavior

• When a branch is merged to develop, the staging server is updated
• When any branch is merged to main (no other branch should be merged to main besides develop, but could be a hotfix..), the prod server is updated

Here are the current deployment steps (please see Updating Techtonica's Website doc for more detail)

1. SSH into DreamHost server
2. Navigate to appropriate directory for "server", for example "testing.techtonica.org"
3. Activate the virtual environment: source bin/activate
4. Change to the source directory: cd techtonica/
5. Pull the latest code using git pull
6. Update the requirements by running pip-sync (or pip install -r requirements.txt)
7. Stop and start the gunicorn process

  systemctl --user stop gunicorn_testing
  systemctl --user enable gunicorn_testing
  systemctl --user restart gunicorn_testing

Acceptance Criteria

• When a branch is merged to develop, the staging server is updated
• When any branch is merged to main, prod server is updated

Additional Context

There may occasionally be environment variables that need updating, those go into .env files stored under each ___.techtonica.org directory
The login credentials for the server should be stored in the github secrets and then referenced in the github actions so they are not exposed
The virtual env activation command will change once the new environments are created for the python upgrade

[monikkaelyse]

@daaimah123 Please let me know if I missed any steps or details. Should we reserve the testing server for just one off testing? Or should staging be on main branch and testing is for develop?