You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
{{ message }}
Instantly share code, notes, and snippets.
tomholford
Building decentralized sovereign infrastructure ~datder-sonnet @urbit
Rolling deploy plan for RemiliaNET using docker-rollout — zero-downtime deployments with container draining
Plan: Switch to Rolling Deploys with docker-rollout
Context
Deployments currently use docker compose up -d --pull always --force-recreate, which stops and recreates all containers simultaneously, causing 10-30 seconds of downtime per deploy. docker-rollout eliminates this by scaling up new containers alongside old ones, health-checking, then removing old containers — zero-downtime.
The original investigation (gist from ~4 months ago) identified removing container_name as a blocker. That's now resolved — PR #628 confirmed all application services have no container_name and no host ports:.
First deploy does NOT require manually stopping stacks. docker-rollout works with running containers — it scales up alongside them, waits for health, then removes old ones. No manual intervention needed.
Get a new neural-net generated face jpg via This Person Does Not Exist
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters