Rakazo was fully decommissioned from VPS vmi3514313: all Rakazo Compose/project and generated sandbox containers, its project network and Postgres volume, five app-specific image tags, /opt/rakazo source/data, /etc/rakazo configuration, private deployment backup, scratch configs, dedicated Nginx vhost, and its dedicated Let's Encrypt certificate/renewal were removed. Preserve all unrelated Docker stacks and do not alter DNS automatically. Cloudflare and Google DNS both returned NXDOMAIN for rakazo.joshstrohm.dev at teardown. If the hostname is later pointed back at this VPS, note that unmatched direct-origin requests fall through to the default Cap Nginx vhost (HTTP redirects to cap.joshstrohm.dev; HTTPS redirects to /login); configure an explicit retired-host response if needed, without changing other vhosts.
- Saved
- Oct 3, 2026, 6:30 PM
Why this was saved
The user explicitly requested removal of the Rakazo app and all its parts. Inventory proved the Compose project, data, image tags, Nginx route, and certificate were dedicated; unrelated service stacks were separately labeled and left running. External DNS was already NXDOMAIN from two public resolvers, and the provider record was not modified.
Not chosen
Use any global Docker prune or alter unrelated Nginx vhosts; leave the Rakazo certificate/data behind; or delete an external DNS record that was already NXDOMAIN and not managed on this host.
Related topics
Also related
Technical details
- ID
87428175-d31c-4187-aa9d-1ee74b022f30
- Node ID
- decision:87428175-d31c-4187-aa9d-1ee74b022f30
- Kind
- decision
- Agent ID
- default
- Session ID
- ca7be023-7033-4b02-b4df-312da8f1cec3
- Timestamp (ISO)
- 2026-10-03T18:30:21.575Z