Decommission Wallos safely and archive any retired stack directory #24

Closed
opened 2026-07-01 16:17:25 +01:00 by nimmo · 2 comments
Owner

Goal

Resolve the stray Wallos footprint safely before future service-stack update runs prune anything unexpectedly.

Acceptance Checklist

  • Disable or remove the Wallos public resource in Pangolin.
  • Determine the actual host where Wallos lived, if any.
  • Confirm whether a stack directory still exists.
  • If a stack directory exists, move it out of /srv/stacks into /srv/stacks-archive.
  • Confirm no retired docker-compose.yml remains in the active update path.

Procedure Outline

  1. Inspect Pangolin resources.
  2. Use Beszel to find candidate hosts.
  3. On the actual host, inspect Docker and stack directories.
  4. Archive any remaining Wallos stack directory outside /srv/stacks.

Reason

The note calls out that /srv/stacks/update.sh later runs prune operations, so retired stacks should not remain under the active update path.

## Goal Resolve the stray Wallos footprint safely before future service-stack update runs prune anything unexpectedly. ## Acceptance Checklist - Disable or remove the Wallos public resource in Pangolin. - Determine the actual host where Wallos lived, if any. - Confirm whether a stack directory still exists. - If a stack directory exists, move it out of `/srv/stacks` into `/srv/stacks-archive`. - Confirm no retired `docker-compose.yml` remains in the active update path. ## Procedure Outline 1. Inspect Pangolin resources. 2. Use Beszel to find candidate hosts. 3. On the actual host, inspect Docker and stack directories. 4. Archive any remaining Wallos stack directory outside `/srv/stacks`. ## Reason The note calls out that `/srv/stacks/update.sh` later runs prune operations, so retired stacks should not remain under the active update path.
nimmo added reference main 2026-07-11 21:53:24 +01:00
Author
Owner

Wallos decomissioned

Wallos decomissioned
Author
Owner

Wallos decomissioned

Wallos decomissioned
nimmo closed this issue 2026-07-11 21:54:25 +01:00
Sign in to join this conversation.
No assignees
1 participant
Notifications
Due date
The due date is invalid or out of range. Please use the format "yyyy-mm-dd".

No due date set.

Dependencies

No dependencies set

Reference
nimmo/nixos-config#24
No description provided.