top | item 43591862 (no title) clait | 11 months ago They were mistaken or maybe referring to an older version, because I definitively use rolling zero downtime updates from commits discuss order hn newest Onavo|11 months ago For true zero downtime, the connections have to be slowly drained, i.e. two all instances may exist at the same time. Does coolify support that? samfundev|11 months ago Coolify does support zero downtime deployments, but the documentation isn't live yet: https://github.com/coollabsio/documentation-coolify/blob/640...It uses docker stop once the new container is healthy with a 30 second timeout, which I believe lets existing connections drain out.
Onavo|11 months ago For true zero downtime, the connections have to be slowly drained, i.e. two all instances may exist at the same time. Does coolify support that? samfundev|11 months ago Coolify does support zero downtime deployments, but the documentation isn't live yet: https://github.com/coollabsio/documentation-coolify/blob/640...It uses docker stop once the new container is healthy with a 30 second timeout, which I believe lets existing connections drain out.
samfundev|11 months ago Coolify does support zero downtime deployments, but the documentation isn't live yet: https://github.com/coollabsio/documentation-coolify/blob/640...It uses docker stop once the new container is healthy with a 30 second timeout, which I believe lets existing connections drain out.
Onavo|11 months ago
samfundev|11 months ago
It uses docker stop once the new container is healthy with a 30 second timeout, which I believe lets existing connections drain out.