Continous deployment

Currently deploying requires that I SSH to our little server, pull latest, rebuild the images on the machine, run some docker commands, and then restart all of the processes. It'd be neat if merging to master did that for us

There are a ton of ways to do this. A couple ideas:

• Run a cron job on the target host that polls github every couple of minutes to see if there's a newer revision of master, if there is, pull it, and do the needful to replace the running service with a newer build
• Run a github actions agent on the box, and write an actions workflow to deploy it
• Interact with the DigitialOcean API in the github actions workflow to create a new host, run the setup, setup the latest build, and then cut traffic over to it (this is definitely waaaay overkill for our purposes and would actually create other problems for us)
• Run commands from github actions on our remote host over SSH (I don't really like this one either)

No files, tests, or entry points are identified. Start by reviewing the current SSH, pull, image rebuild, Docker command, and process restart steps on the target server, then choose and document one deployment approach; done means merging to master reliably deploys the updated service.