Skip to content

Feature/frigate#505

Open
DewaldOosthuizen wants to merge 3 commits into
novaspirit:masterfrom
DewaldOosthuizen:feature/frigate
Open

Feature/frigate#505
DewaldOosthuizen wants to merge 3 commits into
novaspirit:masterfrom
DewaldOosthuizen:feature/frigate

Conversation

@DewaldOosthuizen

@DewaldOosthuizen DewaldOosthuizen commented Jun 15, 2026

Copy link
Copy Markdown

Summary

This pull request introduces a new Frigate app template for Pi-Hosted, including a Docker Compose stack, a detailed documentation file, and updates to contributor workflows. The changes make it easier for users to deploy Frigate with sensible defaults and for contributors to validate their changes locally before submitting pull requests.

Why This Is Needed

Frigate is an open source network video recorder (NVR) with real-time local object detection for IP cameras. It is commonly deployed alongside Home Assistant and supports multiple camera streams, motion review, recordings, and live restreaming. There is also no existing way for new contributors to check for any linting errors across the app unless a specific IDE or editor has a built-in mechanism. To enforce a standard, we should have a common way to check any linting errors, which is why the Makefile was added.

What Changed

  • Updated docs/Contributors.md to document the new local validation workflow and encourage contributors to use it before opening a pull request.

Added

  • Added a new app template for Frigate NVR, including metadata, environment variables, port mappings, and documentation links in template/apps/frigate.json.
  • Introduced a corresponding Docker Compose stack file stack/frigate.yml with required volumes, environment variables, and resource limits for Frigate deployment.
  • Added a comprehensive setup and usage guide in docs/frigate.md, covering prerequisites, configuration, hardware notes, and troubleshooting steps.
  • Added Makefile targets (lint-json, lint-yaml, ci) for validating JSON and YAML files locally, helping contributors catch errors before PR submission.

Screenshots

image image

Checklist

  • Have you checked to ensure there aren't other open Pull Requests for the same update/change?
  • Does your submission pass tests?
  • Have you linted your code locally prior to submission?
  • Have you added an explanation of what your changes do and why you'd like us to include them?
  • Have you updated documentation, as applicable?

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

1 participant