Conversation
An app dropped from the config no longer appears in Status(), so its open "down" incident never resolved — it lingered forever as an active incident (e.g. "Notesnook — down 1.4h" long after the app was removed). checkIncidents now prunes stale health tracking and incident history for apps no longer present, on each detection pass. Control-plane incidents (App == "") are kept. Co-Authored-By: Claude Opus 4.8 <noreply@anthropic.com>
Grid-mode app cards are now draggable. The new order persists to panel settings (Settings.Order) and list mode respects it too, so the two views never drift. groupApps sorts each category bucket by the saved order — unranked apps keep their config order, after the ranked ones. Reordering is constrained to within a category: a card can only be dropped in its own category's container, and because bucketing is by the config category, a name's position in Order can never move an app to a different category. New guarded POST /order handler persists the order; the client re-renders from the same server template. Co-Authored-By: Claude Opus 4.8 <noreply@anthropic.com>
Deploying roost-gh with
|
| Latest commit: |
0a07d85
|
| Status: | ✅ Deploy successful! |
| Preview URL: | https://ce083ea7.roost-gh.pages.dev |
| Branch Preview URL: | https://develop.roost-gh.pages.dev |
README + site now cover the two recent panel changes: drag-and-drop card reordering in grid view (persisted to panel.json, honoured in list, within a category only), and automatic pruning of incidents for apps removed from the config (so a deleted app can't linger as a permanently-open "down" incident). Co-Authored-By: Claude Opus 4.8 <noreply@anthropic.com>
Consolidates the run modes into one section after the quickstart: local (the default + roost enable), an always-on server (copy config/credentials, or the lighter remote: ssh option), and — new — running a dev laptop and a prod box at the same time. The two-machine case documents the one hard rule (one cloudflared per tunnel) and the pattern that makes it work: a separate tunnel + distinct hostnames per environment (e.g. everest vs everest-local), with a note that the two stacks keep isolated data on purpose. Co-Authored-By: Claude Opus 4.8 <noreply@anthropic.com>
New entry covering how repo changes reach both installs: the binary locally via go install / build, the binary on the box via the deploy-web.yml auto-deploy on merge to main (build → scp → install → restart roost-web), and app source via roost deploy. Clarifies that only roost-web auto-restarts on the box — a stack change still needs roost up / roost deploy. Co-Authored-By: Claude Opus 4.8 <noreply@anthropic.com>
The Settings-page/panel.json section enumerated email, view, theme, mask, interval, and tech labels but not the click-set fields. Add featured pins (featured:) and the grid drag-and-drop card order (order:), both written by the panel rather than hand-edited. Co-Authored-By: Claude Opus 4.8 <noreply@anthropic.com>
A command-first, copy-paste runbook — the "technical notes" for day-to-day work: git workflow + keeping a fork current, syncing the roost binary on the laptop (go install) and the box (deploy-web.yml on merge to main), adding apps (roost add / --repo / panel), updating from GitHub (roost deploy / Pull & redeploy / manual git pull + rebuild), the forked-app recipe (root Dockerfile, framework override, the Postgres role-on-existing-volume gotcha with the exact psql commands), common ops (rebuild/recreate/caddy reload/psql/disk), and the two-environment layout. Linked from the README Project section. Co-Authored-By: Claude Opus 4.8 <noreply@anthropic.com>
Add docs/runbook.md to the site — in the resources line under Commands and in the footer nav — alongside the config reference and examples. Co-Authored-By: Claude Opus 4.8 <noreply@anthropic.com>
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
1 participant
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
🎉 Release day | By @cdrrazan
2 commit(s) develop → main. Merging deploy sthe fresh changes!.
🚀 Features
🐛 Fixes