Files

62 lines
1.5 KiB
Markdown

# Docker Compose Example
This directory shows two Docker Compose patterns:
- `compose.yaml`: Frigate and the camera-control bridge run side by side in the
same Compose project.
- `compose.sidecar-only.yaml`: only the bridge is added next to an existing
Frigate container on an existing Docker network.
In both patterns, the bridge manages exactly one Frigate instance.
## Full Stack
1. Build the bridge image from the repository root:
```bash
docker build -t frigate-camera-control-bridge:1.0 .
```
2. Copy the env template:
```bash
cp examples/docker-compose/camera-control.env.example examples/docker-compose/camera-control.env
```
3. Edit `examples/docker-compose/camera-control.env` and set MQTT plus camera
credentials.
4. Start the stack:
```bash
docker compose -f examples/docker-compose/compose.yaml up -d
```
The fallback GUI will be available on:
```text
http://localhost:5011/
```
## Sidecar Next To Existing Frigate
Use `compose.sidecar-only.yaml` when Frigate is already running in Docker and
the bridge only needs to join the same network.
1. Make sure the external network in the example exists and contains Frigate:
```bash
docker network ls
```
2. Edit `compose.sidecar-only.yaml`:
- set `networks.frigate-network.external` to the network name used by Frigate,
- set `FRIGATE_URL` to the Frigate container DNS name or another reachable URL.
3. Start only the bridge:
```bash
docker compose -f examples/docker-compose/compose.sidecar-only.yaml up -d
```