sneak
83986626a4
Remove old container before creating new one instead of trying to keep it for rollback. Rollback isn't safe anyway because database migrations may have been applied by the new container. The old stop-then-rollback approach failed because Docker doesn't allow two containers with the same name, even if one is stopped. |
||
|---|---|---|
| .. | ||
| app | ||
| auth | ||
| deploy | ||
| notify | ||
| webhook | ||