furtka-apps/CHANGELOG.md
Daniel Maksymilian Syrnicki f377a5a387
All checks were successful
CI / validate (push) Successful in 20s
CI / shellcheck (push) Successful in 31s
Release / release (push) Successful in 37s
feat(uptime-kuma): add status-monitor app to the catalog
louislam/uptime-kuma:1 with one data volume and port 3001. Admin
account bootstrapped from the first browser visit to :3001 — no
Furtka settings form needed. Catalog release 26.7-alpha.

Co-Authored-By: Claude Opus 4.7 (1M context) <noreply@anthropic.com>
2026-04-20 15:34:28 +02:00

1.5 KiB

Changelog

All notable changes to the Furtka apps catalog will be documented here. Format: Keep a Changelog. Versioning: CalVer (YY.N) — same scheme as the core Furtka repo.

Unreleased

26.7-alpha - 2026-04-20

Added

  • Uptime Kuma (v1.0.0, image louislam/uptime-kuma:1). Self-hosted status monitor — pings hosts, checks HTTPS endpoints, watches Docker containers, and screams on Telegram/webhook when something breaks. No manifest settings: the admin account is created on the first browser visit to port 3001. Persists history + config via one namespaced volume furtka_uptime-kuma_data.

26.6-alpha - 2026-04-20

Added

  • Initial catalog release. Carries one app: fileshare (v0.1.1, SMB share over dperson/samba). Copied from the daniel/furtka seed so boxes on 26.6 see the same fileshare bits whether they pull the catalog or fall back to the bundled seed.
  • Release pipeline + CI parity with the core repo: scripts/build-catalog-tarball.sh, scripts/publish-catalog-release.sh, scripts/validate-catalog.py (CI guardrail — loads every manifest via the vendored furtka.manifest.load_manifest + cross-checks compose volume references).