Files
frigate/web
Josh Hawkins a2e7e5c991 set the secure cookie flag when the request arrived over tls
The session cookie only got the Secure flag from auth.cookie_secure, which defaults to false even though TLS is on by default, so browsers would send it over plain HTTP. The cookie is now Secure whenever nginx reports an https scheme, and nginx passes that scheme to the /auth subrequest so refreshed cookies match. cookie_secure still forces the flag for a reverse proxy that terminates TLS in front of plain-HTTP Frigate.
2026-10-18 12:18:58 -05:00
..
2024-06-19 08:11:51 -06:00
2026-10-18 04:50:25 -10:00
2026-10-10 15:01:33 -05:00
2026-10-18 04:50:25 -10:00
2026-06-16 08:56:52 -05:00
2026-10-10 15:01:33 -05:00
2026-10-10 15:01:33 -05:00
2024-06-19 08:11:51 -06:00
2026-04-22 09:19:30 -06:00
2026-10-10 15:01:33 -05:00
2024-01-31 12:56:11 +00:00
2026-09-15 14:02:02 -06:00

This is the Frigate frontend which connects to and provides a User Interface to the Python backend.

Web Development

Installing Web Dependencies Via NPM

Within /web, run:

npm install

Running development frontend

Within /web, run:

PROXY_HOST=<ip_address:port> npm run dev

The Proxy Host can point to your existing Frigate instance. Otherwise defaults to localhost:5000 if running Frigate on the same machine.

Extensions

Install these IDE extensions for an improved development experience:

  • eslint