Underneath the vapp
Read this right after A vapp and an add-on. Every command here reads; none changes the cluster.
notes now carries every kind of file the ladder has written:
$ ls -1R /usr/share/shc/apps/notes/usr/share/shc/apps/notes:addonsapp.yamlbackup.yamlcompose.yamldatabase.vapp.yamldatabase.vplug.yamldatabase.vsocket.yamldatabase.vvars.yamlnotes.exporter.yamlschema.job.yamlvars.yaml
/usr/share/shc/apps/notes/addons:blog.addon.yamlapp.yaml, vars.yaml and compose.yaml make the app. schema.job.yaml is
a job its hooks run. backup.yaml says what a backup keeps, and
notes.exporter.yaml what an export hands over. The four database files
make the vapp, and addons/blog.addon.yaml presets it. pgweb’s
postgres.plug.yaml and the gateway’s s3.socket.yaml are the other two
kinds. The catalogue Postgres in /usr/lib/shc/apps/postgres is built from
the same kinds.
The installs and removals of both instances are in the audit record:
$ shc events ls --audit -s placed/shopCREATED AT CODE ACTOR STACK MESSAGE ID TENANT ENVIRONMENT2026-10-10T20:09:47.058310857Z A200121VDPUNI shc placed/shop uninstalled vdeployment shop from host placed 81b11543-9ec7-4008-8a1a-24565030a72c prod prod2026-10-10T20:09:34.192228549Z A200120VDPINS shc placed/shop installed vdeployment shop of database on host placed 00b54c24-aa5c-4d80-9716-3f45e2c5d43e prod prod$ shc events ls --audit -s placed/blogCREATED AT CODE ACTOR STACK MESSAGE ID TENANT ENVIRONMENT2026-10-10T20:09:49.759215764Z A200121VDPUNI shc placed/blog uninstalled vdeployment blog from host placed 041f6bbb-05cc-4948-b9d4-245d71f1842d prod prod2026-10-10T20:09:40.728427412Z A200120VDPINS shc placed/blog installed vdeployment blog of blog on host placed ec2e8b3e-f1e2-48bd-a238-6472a5f6f160 prod prodThe leader’s journal says why shop’s database stayed:
$ journalctl --no-pager -u shc --since '20 min ago' -o cat -g X200949VAPRETtime=2026-10-10T20:09:47.054Z level=WARN msg="vdeployment placed/shop retained, 1 cleanup job skipped, persisted plug data cleanup=False is not an explicit affirmative, the resources that cleanup would destroy are left in place" code=X200949VAPRET http_status=200 jobs="1 cleanup job" reason="persisted plug data cleanup=False is not an explicit affirmative" stack=placed/shop tenant=prodshop’s plug data was stored at install with cleanup false, so its
cleanup job was skipped. The value is the one the instance was installed
with: changing database.vvars.yaml later does not change it.
Next: The licence.