Milestones 5 and 6: release workflow and deployment, store guide and assets #4
Loading…
Reference in a new issue
No description provided.
Delete branch "deploy-plan"
Deleting a branch is permanent. Although the deleted branch may continue to exist for a short time before it actually gets removed, it CANNOT be undone in most cases. Continue?
Milestones 5 and 6. This is stacked on #3, so merge #1, then #3, then this one. Nothing has been deployed, released or submitted.
Milestone 5: deployment and releases
Built as you decided (
docs/deployment.mdrecords the decisions):wristmark.apps.ciepiela.org;.forgejo/workflows/release.ymlruns onvX.Y.Z, or by hand with a tag for a rollback:CHANGELOG.md's## [X.Y.Z]section. Without one, the release fails rather than making notes up.tools/build-watch.sh --package(monkeyc --package-app --release), signed withCONNECTIQ_DEVELOPER_KEY(base64 of the DER key). The key goes to a temporary file that is deleted afterwards..iqand the tarball (forgejo-release@v2). For a tag that already has a release, publishing is skipped: the action fails on an existing release (checked in its source), so the workflow asks the API first./healthzat the public address.The viewer's Dockerfile gets a
HEALTHCHECK; Docker reports the containerhealthy.HomeLab #126 adds the
homelab_appsentry, which gives this repository the deploy key andAPPS_TOKEN. What's left after it, including creating the app in the panel by hand, is indocs/deployment.md, "What is left to do".Milestone 6: store preparation
docs/publishing.mdis the step-by-step guide. A research pass read Garmin's pages, and every step cites one. Where Garmin's docs are silent, the guide says not documented instead of guessing: the version field, screenshot specs, file limits, the update flow and beta testers. It covers:Assets (
docs/store-assets/):#0055AA, a color in the 64-color palette Garmin asks for on MIP displays. They're generated bytools/generate-icon.mjs(with the launcher icon) and checked in CI. js-aruco2 detects ID 0 in all three icons.Privacy page:
viewer/public/privacy.html, in English and German, linked from the viewer. It says what stays in the browser and what the app host's proxy logs. Its contact isdawid@ciepiela.org; change it if you prefer another address.Manifest: declares German as well. Garmin says the declared languages decide the store's regions. The only string, the app's name, needs no translation.
Please check
.cz.toml, like your other repositories. I didn't add one, because every release also needs the signing key and goes to the store.Verified
viewer/test: 9 tests pass, including the privacy page under the CSP. The smoke test passes, and the container ishealthy.uses:and thedockerlabel.Not verified
Update 2026-11-16: the name, the contact, the release bot
wristmarkcompanion. The address stayswristmark.apps.ciepiela.org. The panel app must be namedwristmarkcompanion, because the release workflow finds it by the repository name. HomeLab #126 is updated to match.contact@ciepiela.org..cz.tomlis in: the release bot tags weekly, and the release workflow reads the bot's## X.Y.Z - datesections.CONNECTIQ_DEVELOPER_KEYis set. Do those first, or rerun the release workflow by hand with the tag afterwards.docs: deployment and release proposal (milestone 5, for decision)to Milestones 5 and 6: release workflow and deployment, store guide and assetseb55fff6e02668cc7e522668cc7e529a27cc7189