This is a StartOS service-package repository — it builds a .s9pk for StartOS.
Develop it inside a StartOS packaging workspace created by start-cli s9pk init-workspace,
which provides the packaging guide and agent context one level up. If you're reading this in a
bare clone with no workspace, the full guide is at https://docs.start9.com/packaging.
Work this package's TODO.md from top to bottom. Keep README.md (technical reference for an AI support or administering agent) and instructions.md (end-user docs) in sync with your changes.
- This is Sparrow Wallet's Frigate, an Electrum server — not the Frigate NVR project. Every search result for "Frigate Docker" is the NVR. Verify against https://github.com/sparrowwallet/frigate before acting on anything you read elsewhere.
- Three build variants share one package id.
VARIANT(generic/nvidia/amd) selects the image and the hardware requirement instartos/manifest/index.ts; theMakefile'sTARGETSfans them out one s9pk per variant-arch, and CI builds all four leaves. An unrecognisedVARIANTthrows rather than silently packing the generic image — keep it that way. Build one locally withmake generic-x86/make nvidia-x86/make amd-x86; baremake x86builds the generic image under the unsuffixed name. - The
amdvariant pulls the-rocmimage, not-amd.remcoros/frigate-dockerpublishes both (-amdis Mesa Rusticl,-rocmis TheRock's ROCm OpenCL); this package ships ROCm. Don't "fix" the tag to match the variant name. startos/utils.tsexists for dependents, not for this package — it exports the Electrum host id and container port so another package can resolve Frigate over the bridge without a literal.