ts-CATALOG

Canonical deployment catalog for all DAM ts-* self-hosted services.

Purpose

The ts-app-deploy skill reads this catalog to make smart, per-app decisions about Docker Compose configuration (which DB service to include, what port to use, what env vars to set, etc.).

Files

• catalog.yaml — structured catalog of every ts-* app
• README.md — this file

Schema

Each app entry in catalog.yaml has:

Field	Purpose
service	lowercase repo name (e.g. vikunja)
display_name	human-readable name (e.g. Vikunja)
image	Docker image name
image_tag	pinned version (or latest)
port	primary web UI port
db	database type (none/sqlite/postgres/mysql/mariadb)
architecture	single/app_db/app_db_cache/multi_service
first_run	setup_wizard/auto/seeded/none
test_status	untested/in_progress/verified/broken
test_date	ISO date of last successful test (if any)
repo	Gitea URL
notes	deployment gotchas, quirks, workarounds

Updating

When you test a new service:

1. Update the test_status field to verified
2. Update the test_date
3. Add any new gotchas to notes
4. Commit + push

When a service breaks:

1. Update the test_status field to broken
2. Document the issue in notes
3. Commit + push

The skill will pick up these changes automatically.