66b3e414a0
Official ghcr.io/go-shiori/shiori:v1.7.0. Single container, SQLite in a named volume. Default admin (shiori/gopher) is auto-created on first run. Catalog field changes from initial categorization: - first_run: setup_wizard → auto (Shiori's wizard detection is broken in v1.7.0; the app auto-creates the admin account instead). - image_tag: latest → v1.7.0 (pinned to a specific release). - notes: documents the wizard bug and the auto-admin workaround.
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 everyts-*appREADME.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:
- Update the
test_statusfield toverified - Update the
test_date - Add any new gotchas to
notes - Commit + push
When a service breaks:
- Update the
test_statusfield tobroken - Document the issue in
notes - Commit + push
The skill will pick up these changes automatically.