[Tooling] Staging API Deployment Strategy

[lpatmo]

Context

We need a staging API that https://cbv3.netlify.app/ (our frontend staging app) can consume.

Figuring this out right now is also good practice for when we actually deploy to production. :)

Acceptance Criteria

[ ] Create a staging branch
[ ] Create a new Django workflow in Github Actions
https://github.com/codebuddies/backend/actions/new
[ ] Create a DigitalOcean droplet
[ ] Create a postgres DB on DigitalOcean
[ ] Figure out how to deploy from that staging branch into my new workflow in Github Actions (?) - probably related to the contents of the docker-compose-staging.yml file below.
[x] brew install doctl
[ ] Create a docker-compose-staging.yaml file
[ ] Add/remove environment variables in GitHub secrets at https://github.com/codebuddies/backend/settings/secrets
[ ] Basically, follow the amazing documentation Bill wrote up in https://github.com/codebuddies/backend/wiki/Production-Deployment

Other notes/screenshots

See: cbv3 notes doc
Also see: #65

[lpatmo]

(Ideally planning to look at this over the next few days in my free time, document in the notes doc, and will ask if I need help)

[BethanyG]

@lpatmo Is this still relevant? Can we close?

[lpatmo]

Er, actually this is still on my plate to do!

[stale]

This issue has been automatically marked as stale because it has not had recent activity. It will be closed if no further activity occurs. Thank you for your contributions.

[stale]

This issue has been automatically marked as stale because it has not had recent activity. It will be closed if no further activity occurs. Thank you for your contributions.