Brain

On 2026-03-21, five apps on svc-apps were identified as targets for moving their compose definitions into corresponding /home/svc-admin/appstack directories. Apps: - trilium - vaultwarden - linkwarden - mealie - vikunja Docker container labels referenced these old compose metadata paths: - /data/compose/6/docker-compose.yml -> trilium - /data/compose/7/docker-compose.yml -> vaultwarden - /data/compose/8/docker-compose.yml -> linkwarden - /data/compose/9/docker-compose.yml -> mealie - /data/compose/10/docker-compose.yml -> vikunja Those /data/compose paths did not exist on disk when checked from svc-apps, so they appear to be stale label metadata rather than currently accessible files. New corresponding appstack paths created: - /home/svc-admin/appstack/trilium/docker-compose.yml - /home/svc-admin/appstack/vaultwarden/docker-compose.yml - /home/svc-admin/appstack/linkwarden/docker-compose.yml - /home/svc-admin/appstack/mealie/docker-compose.yml - /home/svc-admin/appstack/vikunja/docker-compose.yml Current data paths in use before migration: - /home/svc-admin/appstack/trilium-data - /home/svc-admin/appstack/vaultwarden-data - /home/svc-admin/appstack/linkwarden-data - /home/svc-admin/appstack/mealie-data - /home/svc-admin/appstack/vikunja-cache - /home/svc-admin/appstack/vikunja-files - /home/svc-admin/appstack/vikunja-tmp Placeholder compose files were created in the new appstack directories as temporary markers. Actual compose reconstruction can happen later. --- **2026-03-21 18:57:05 UTC | Created via MCP**