basforge

Search titles, text and the “If it doesn’t work” cases.

    RU

    A disabled stack doesn’t stay on the server “for reference”

    A stopped stack with a database and keys either goes to an archive off the server or gets deleted. The configs stay in git history anyway.

    What usually gets left behind

    An old copy of a password vault, a DNS token on a server where Traefik hasn’t run in ages, certificates for someone else’s domain, _old and _backup directories with databases. All of it leaks in a breach and is of no use.

    The order for removing a stack that lives in git: git pull first — git removes its own files — then rm -rf of what’s left: .env and data (Server configs in git). Before that, check that no neighbour still has volumes on its path (A missing volume path).