jpmschweitzer/portainer-core
1
0
Fork 0
Code Issues Pull Requests Actions Packages Projects Releases Wiki Activity

feat: add Docker healthchecks, remove Uptime Kuma

Browse Source 
- Add healthcheck configurations to 13 stacks for Portainer status monitoring
- Remove Uptime Kuma service (replaced by Docker healthchecks)
- Clean up stale Heimdall references
- Update documentation and service counts

🤖 Generated with [Claude Code](https://claude.com/claude-code)

Co-Authored-By: Claude Opus 4.5 <noreply@anthropic.com>
This commit is contained in:
jpmschweitzer
2025-12-14 12:05:05 +01:00
co-authored by Claude Opus 4.5
parent 8793ff1779
commit 75c3950dd8
27 changed files with 142 additions and 169 deletions
Download Patch File Download Diff File Expand all files Collapse all files
AGENTS.md
+5 -12
View File
@@ -36,10 +36,9 @@ This is the `tower-of-joy` project - a containerized home server infrastructure
**External Access Rule:** All public/external services MUST route through Nginx Proxy Manager (NPM) for Let's Encrypt SSL management and unified logging. Never expose service ports directly to the internet (except NPM and Headscale).
**Service Maintenance**
- **Stack Management** the portainer (and docker), NPM and Uptime Kuma services are managed through the core-api service. To maintain settings and configurations of these systems, read the documentation at http://tower-of-joy:8083/docs and prefer to use the api functions over direct reads an edits.
- **Stack Management** the portainer (and docker) and NPM services are managed through the core-api service. To maintain settings and configurations of these systems, read the documentation at http://tower-of-joy:8083/docs and prefer to use the api functions over direct reads an edits.
**Service Integration Policy:** A service deployment is INCOMPLETE until cross-service integrations are implemented. Every new service MUST be integrated with:
- **Uptime Kuma:** Add health check monitor (use `scripts/setup-kuma-monitors.sh` as guide)
- **Organizr:** Configure service in dashboard (Settings → Tab Editor, Homepage Items)
- **docs/reference/CONTAINERS.md:** Document the service with full profile and configuration table
@@ -356,11 +355,6 @@ When deploying a NEW service, follow this complete checklist. A deployment is **
- [ ] Document access credentials securely
**Phase 3: Cross-Service Integration (MANDATORY)**
- [ ] **Uptime Kuma Integration:**
- Add HTTP monitor for service health check
- Set appropriate heartbeat interval (typically 60s)
- Verify monitor shows "Up" status
- Reference: `scripts/setup-kuma-monitors.sh`
- [ ] **Organizr Integration:**
- Add service URL and API token to Organizr (Settings → Tab Editor)
- Enable homepage widgets if supported
@@ -385,7 +379,7 @@ When deploying a NEW service, follow this complete checklist. A deployment is **
**Phase 5: Verification**
- [ ] Service accessible at documented URL
- [ ] Uptime Kuma shows service as "Up"
- [ ] Docker healthcheck shows healthy status
- [ ] Organizr displays service widget/tab correctly
- [ ] Service persists across container restart
- [ ] Backups configured (if service has important data)
@@ -394,10 +388,9 @@ When deploying a NEW service, follow this complete checklist. A deployment is **
```bash
# 1. Deploy Jellyfin container
# 2. Configure Jellyfin settings and add media
# 3. Add Jellyfin to Uptime Kuma (HTTP monitor)
# 4. Add Jellyfin to Organizr (homepage widgets + tab)
# 5. Document in CONTAINERS.md
# 6. Test all integrations work
# 3. Add Jellyfin to Organizr (homepage widgets + tab)
# 4. Document in CONTAINERS.md
# 5. Test all integrations work
# ✓ NOW the deployment is complete
```