Setup Automated Continuous Deployment

[DrewMcArthur]

Ideally, when a new push to main happens (or a new release is created), the production server pulls those changes and restarts the server, maybe to a staging.pmsky.social url to check it first, and doing it in a way that minimizes downtime.

problems:

• GitHub.com doesn't support IPv6 (i know, right?)
• neither does radicle
• gitlab organizations can't have free access tokens

potential solution:

• setup a deploy key / token on the gitlab repo
• on GitHub pushes to main, push to gitlab
• hit server's web hook, which runs a local script to pull updates from gitlab and reboot the app server

[DrewMcArthur]

using cloudflare's WARP so now ipv4 stuff isn't an issue, should be able to setup a simple web hook server side to pull, build, and restart on pushes to main

ideally with some failover, so no downtime?