daniel/furtka-apps
1
1
Fork 0
Code Issues Pull requests Projects Releases 7 Packages Wiki Activity Actions
furtka-apps/CHANGELOG.md

37 lines
1.5 KiB
Markdown
Raw Normal View History

chore: bootstrap furtka-apps catalog repo Initial layout: apps/fileshare/ (seeded from daniel/furtka apps/), CI (JSON + manifest validator + shellcheck), release pipeline (tag-driven, mirrors core repo), vendored manifest schema for offline validation. The core repo (daniel/furtka) at 26.6-alpha keeps apps/fileshare as a seed so offline first-boot still has an installable app; this catalog becomes authoritative once a box has synced at least once. Co-Authored-By: Claude Opus 4.7 (1M context) <noreply@anthropic.com>
2026-04-20 14:14:50 +02:00
# Changelog
All notable changes to the Furtka apps catalog will be documented here.
Format: [Keep a Changelog](https://keepachangelog.com/en/1.1.0/).
Versioning: CalVer (`YY.N`) — same scheme as the core Furtka repo.
## [Unreleased]
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
## [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`.
chore: bootstrap furtka-apps catalog repo Initial layout: apps/fileshare/ (seeded from daniel/furtka apps/), CI (JSON + manifest validator + shellcheck), release pipeline (tag-driven, mirrors core repo), vendored manifest schema for offline validation. The core repo (daniel/furtka) at 26.6-alpha keeps apps/fileshare as a seed so offline first-boot still has an installable app; this catalog becomes authoritative once a box has synced at least once. Co-Authored-By: Claude Opus 4.7 (1M context) <noreply@anthropic.com>
2026-04-20 14:14:50 +02:00
## [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).
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
[Unreleased]: https://forgejo.sourcegate.online/daniel/furtka-apps/compare/26.7-alpha...HEAD
[26.7-alpha]: https://forgejo.sourcegate.online/daniel/furtka-apps/releases/tag/26.7-alpha
chore: bootstrap furtka-apps catalog repo Initial layout: apps/fileshare/ (seeded from daniel/furtka apps/), CI (JSON + manifest validator + shellcheck), release pipeline (tag-driven, mirrors core repo), vendored manifest schema for offline validation. The core repo (daniel/furtka) at 26.6-alpha keeps apps/fileshare as a seed so offline first-boot still has an installable app; this catalog becomes authoritative once a box has synced at least once. Co-Authored-By: Claude Opus 4.7 (1M context) <noreply@anthropic.com>
2026-04-20 14:14:50 +02:00
[26.6-alpha]: https://forgejo.sourcegate.online/daniel/furtka-apps/releases/tag/26.6-alpha
Reference in a new issue Copy permalink