Both apps grow an `open_url` manifest field so the core UI can render an Open button that deep-links into the app. fileshare uses smb:// to trigger the OS file manager; uptime-kuma uses http://{host}:3001/ for the browser. No image or compose changes. - fileshare 0.1.1 → 0.1.2 - uptime-kuma 1.0.0 → 1.0.1
1.9 KiB
1.9 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.8-alpha - 2026-04-21
Changed
- fileshare bumped to v0.1.2: adds
open_url(smb://{host}/files) so the core UI can render an Open button that deep-links to the share. - Uptime Kuma bumped to v1.0.1: adds
open_url(http://{host}:3001/) for the same UI Open button. No image or compose changes.
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 volumefurtka_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 thedaniel/furtkaseed 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 vendoredfurtka.manifest.load_manifest+ cross-checks compose volume references).