Production deployer might run `docker-compose` before running `init-letsencrypt.sh`
The following discussion from !769 (merged) should be addressed:
-
@kageurufu started a discussion: (+1 comment) This is likely to fail since the certbot container creates
data/
as root, so the user running init-letsencrypt will not have permissions.If you run accidentally run docker-compose before you run init-letsencrypt.sh then you have to manually delete “~/exosphere/deploy/prod/main-server/data” as rot
@cmart said:
On one hand, that would require a failure to follow instructions. On the other hand, yes, someone might run
docker-compose up
before reading. I'd like to not block merging this, but happy to track for follow-up.
What success would look like: one way or another, deployer is less likely to get stuck.