> where we should have (and ended on) docker / compose
We ended up doing this too.
Do you have any links to deploying docker-compose in production? We've not been able to find out much. However our solution seems to work well - am keen to find out how other people are managing host setup, updating and remotely controlling docker-compose
In our setup, we essentially use docker-compose as a process manager:
- Updates with docker-compose.yml via git syncs
- Logging via journald (which in turn is forwarded)
- Simple networking with `network: host` and managing
firewalls at the host level with dashboard/labelling
- Restarts / Launch on startup with `restart: always` policy
IMO, more straightforward in the past
1) Entrusting everything to a package manager or build script which might break on a new version release
2) Maintaining ansible script repository to do the host configuration, package management and updates for you - these too always need manual intervention on major version updates
We ended up doing this too.
Do you have any links to deploying docker-compose in production? We've not been able to find out much. However our solution seems to work well - am keen to find out how other people are managing host setup, updating and remotely controlling docker-compose
In our setup, we essentially use docker-compose as a process manager:
- Updates with docker-compose.yml via git syncs
- Logging via journald (which in turn is forwarded)
- Simple networking with `network: host` and managing firewalls at the host level with dashboard/labelling
- Restarts / Launch on startup with `restart: always` policy
IMO, more straightforward in the past
1) Entrusting everything to a package manager or build script which might break on a new version release
2) Maintaining ansible script repository to do the host configuration, package management and updates for you - these too always need manual intervention on major version updates