What
In the versioned deploy layout (~/mining/pithead-vX.Y.Z plus a shared data/ root, see docs/operations.md), an upgrade copies .env into the new version directory, and the previous one keeps its own .env. The Compose project name is fixed (name: pithead in docker-compose.yml).
Running ./pithead uninstall in the kept previous version directory, for example to tidy it up, therefore acts on the live stack:
uninstall already keeps a version directory's own current symlink separate from any other version's. Nothing else does.
Expected
uninstall in a version directory that current does not point at refuses, or limits itself to that directory's own files, and says why. Leave the shared data root's proxy-tls alone unless this checkout is the one current names.
Found by review beside #2379; not fixed there.
What
In the versioned deploy layout (
~/mining/pithead-vX.Y.Zplus a shareddata/root, seedocs/operations.md), an upgrade copies.envinto the new version directory, and the previous one keeps its own.env. The Compose project name is fixed (name: pitheadindocker-compose.yml).Running
./pithead uninstallin the kept previous version directory, for example to tidy it up, therefore acts on the live stack:docker compose down -vstops the live containers and deletes the livecaddy_data,wallet_dataandtari_wallet_datavolumes<data root>/proxy-tls, the stratum TLS keypair the current version still serves and rigs pinuninstallalready keeps a version directory's owncurrentsymlink separate from any other version's. Nothing else does.Expected
uninstallin a version directory thatcurrentdoes not point at refuses, or limits itself to that directory's own files, and says why. Leave the shared data root'sproxy-tlsalone unless this checkout is the onecurrentnames.Found by review beside #2379; not fixed there.