(no title)
dsgrillo | 4 years ago
Both have a similar setup:
- 1 droplet with docker pre-installed from DigitalOcean
- clone directly the repo from github
- together with the code, I have a folder with a bunch of docker images (caddy, mysql, php, redis, etc.) that I can easily spin up.
- for any release, I manually ssh, git pull and run the migrations (if any) and manually rebuild any docker image if needed
- I have daily jobs that dumps and zip the entire DB to S3
- if I have some deployment that I know will break any functionality during deployment, I warn the users before and accept that downtime.
- never had to handle a "hard" rollback till now.
I've planned to change this setup for while, but until now, didn't find any reason that justifies the effort.I spend 20$ (10$ per droplet) + few cents on S3 per month with them.
No comments yet.