Metadata-Version: 2.5
Name: cctv-stack
Version: 0.3.0
Summary: A packaging-first self-hosted CCTV stack built on Frigate.
Project-URL: Homepage, https://github.com/aravindmyd/cctv-stack
Project-URL: Repository, https://github.com/aravindmyd/cctv-stack
Project-URL: Issues, https://github.com/aravindmyd/cctv-stack/issues
Author: Jothika Raja
License:                                  Apache License
                                   Version 2.0, January 2004
                                http://www.apache.org/licenses/
        
           TERMS AND CONDITIONS FOR USE, REPRODUCTION, AND DISTRIBUTION
        
           1. Definitions.
        
              "License" shall mean the terms and conditions for use, reproduction,
              and distribution as defined by Sections 1 through 9 of this document.
        
              "Licensor" shall mean the copyright owner or entity authorized by
              the copyright owner that is granting the License.
        
              "Legal Entity" shall mean the union of the acting entity and all
              other entities that control, are controlled by, or are under common
              control with that entity. For the purposes of this definition,
              "control" means (i) the power, direct or indirect, to cause the
              direction or management of such entity, whether by contract or
              otherwise, or (ii) ownership of fifty percent (50%) or more of the
              outstanding shares, or (iii) beneficial ownership of such entity.
        
              "You" (or "Your") shall mean an individual or Legal Entity
              exercising permissions granted by this License.
        
              "Source" form shall mean the preferred form for making modifications,
              including but not limited to software source code, documentation
              source, and configuration files.
        
              "Object" form shall mean any form resulting from mechanical
              transformation or translation of a Source form, including but
              not limited to compiled object code, generated documentation,
              and conversions to other media types.
        
              "Work" shall mean the work of authorship, whether in Source or
              Object form, made available under the License, as indicated by a
              copyright notice that is included in or attached to the work
              (an example is provided in the Appendix below).
        
              "Derivative Works" shall mean any work, whether in Source or Object
              form, that is based on (or derived from) the Work and for which the
              editorial revisions, annotations, elaborations, or other modifications
              represent, as a whole, an original work of authorship. For the purposes
              of this License, Derivative Works shall not include works that remain
              separable from, or merely link (or bind by name) to the interfaces of,
              the Work and Derivative Works thereof.
        
              "Contribution" shall mean any work of authorship, including
              the original version of the Work and any modifications or additions
              to that Work or Derivative Works thereof, that is intentionally
              submitted to Licensor for inclusion in the Work by the copyright owner
              or by an individual or Legal Entity authorized to submit on behalf of
              the copyright owner. For the purposes of this definition, "submitted"
              means any form of electronic, verbal, or written communication sent
              to the Licensor or its representatives, including but not limited to
              communication on electronic mailing lists, source code control systems,
              and issue tracking systems that are managed by, or on behalf of, the
              Licensor for the purpose of discussing and improving the Work, but
              excluding communication that is conspicuously marked or otherwise
              designated in writing by the copyright owner as "Not a Contribution."
        
              "Contributor" shall mean Licensor and any individual or Legal Entity
              on behalf of whom a Contribution has been received by Licensor and
              subsequently incorporated within the Work.
        
           2. Grant of Copyright License. Subject to the terms and conditions of
              this License, each Contributor hereby grants to You a perpetual,
              worldwide, non-exclusive, no-charge, royalty-free, irrevocable
              copyright license to reproduce, prepare Derivative Works of,
              publicly display, publicly perform, sublicense, and distribute the
              Work and such Derivative Works in Source or Object form.
        
           3. Grant of Patent License. Subject to the terms and conditions of
              this License, each Contributor hereby grants to You a perpetual,
              worldwide, non-exclusive, no-charge, royalty-free, irrevocable
              (except as stated in this section) patent license to make, have made,
              use, offer to sell, sell, import, and otherwise transfer the Work,
              where such license applies only to those patent claims licensable
              by such Contributor that are necessarily infringed by their
              Contribution(s) alone or by combination of their Contribution(s)
              with the Work to which such Contribution(s) was submitted. If You
              institute patent litigation against any entity (including a
              cross-claim or counterclaim in a lawsuit) alleging that the Work
              or a Contribution incorporated within the Work constitutes direct
              or contributory patent infringement, then any patent licenses
              granted to You under this License for that Work shall terminate
              as of the date such litigation is filed.
        
           4. Redistribution. You may reproduce and distribute copies of the
              Work or Derivative Works thereof in any medium, with or without
              modifications, and in Source or Object form, provided that You
              meet the following conditions:
        
              (a) You must give any other recipients of the Work or
                  Derivative Works a copy of this License; and
        
              (b) You must cause any modified files to carry prominent notices
                  stating that You changed the files; and
        
              (c) You must retain, in the Source form of any Derivative Works
                  that You distribute, all copyright, patent, trademark, and
                  attribution notices from the Source form of the Work,
                  excluding those notices that do not pertain to any part of
                  the Derivative Works; and
        
              (d) If the Work includes a "NOTICE" text file as part of its
                  distribution, then any Derivative Works that You distribute must
                  include a readable copy of the attribution notices contained
                  within such NOTICE file, excluding those notices that do not
                  pertain to any part of the Derivative Works, in at least one
                  of the following places: within a NOTICE text file distributed
                  as part of the Derivative Works; within the Source form or
                  documentation, if provided along with the Derivative Works; or,
                  within a display generated by the Derivative Works, if and
                  wherever such third-party notices normally appear. The contents
                  of the NOTICE file are for informational purposes only and
                  do not modify the License. You may add Your own attribution
                  notices within Derivative Works that You distribute, alongside
                  or as an addendum to the NOTICE text from the Work, provided
                  that such additional attribution notices cannot be construed
                  as modifying the License.
        
              You may add Your own copyright statement to Your modifications and
              may provide additional or different license terms and conditions
              for use, reproduction, or distribution of Your modifications, or
              for any such Derivative Works as a whole, provided Your use,
              reproduction, and distribution of the Work otherwise complies with
              the conditions stated in this License.
        
           5. Submission of Contributions. Unless You explicitly state otherwise,
              any Contribution intentionally submitted for inclusion in the Work
              by You to the Licensor shall be under the terms and conditions of
              this License, without any additional terms or conditions.
              Notwithstanding the above, nothing herein shall supersede or modify
              the terms of any separate license agreement you may have executed
              with Licensor regarding such Contributions.
        
           6. Trademarks. This License does not grant permission to use the trade
              names, trademarks, service marks, or product names of the Licensor,
              except as required for reasonable and customary use in describing the
              origin of the Work and reproducing the content of the NOTICE file.
        
           7. Disclaimer of Warranty. Unless required by applicable law or
              agreed to in writing, Licensor provides the Work (and each
              Contributor provides its Contributions) on an "AS IS" BASIS,
              WITHOUT WARRANTIES OR CONDITIONS OF ANY KIND, either express or
              implied, including, without limitation, any warranties or conditions
              of TITLE, NON-INFRINGEMENT, MERCHANTABILITY, or FITNESS FOR A
              PARTICULAR PURPOSE. You are solely responsible for determining the
              appropriateness of using or redistributing the Work and assume any
              risks associated with Your exercise of permissions under this License.
        
           8. Limitation of Liability. In no event and under no legal theory,
              whether in tort (including negligence), contract, or otherwise,
              unless required by applicable law (such as deliberate and grossly
              negligent acts) or agreed to in writing, shall any Contributor be
              liable to You for damages, including any direct, indirect, special,
              incidental, or consequential damages of any character arising as a
              result of this License or out of the use or inability to use the
              Work (including but not limited to damages for loss of goodwill,
              work stoppage, computer failure or malfunction, or any and all
              other commercial damages or losses), even if such Contributor
              has been advised of the possibility of such damages.
        
           9. Accepting Warranty or Additional Liability. While redistributing
              the Work or Derivative Works thereof, You may choose to offer,
              and charge a fee for, acceptance of support, warranty, indemnity,
              or other liability obligations and/or rights consistent with this
              License. However, in accepting such obligations, You may act only
              on Your own behalf and on Your sole responsibility, not on behalf
              of any other Contributor, and only if You agree to indemnify,
              defend, and hold each Contributor harmless for any liability
              incurred by, or claims asserted against, such Contributor by reason
              of your accepting any such warranty or additional liability.
        
           END OF TERMS AND CONDITIONS
        
           APPENDIX: How to apply the Apache License to your work.
        
              To apply the Apache License to your work, attach the following
              boilerplate notice, with the fields enclosed by brackets "[]"
              replaced with your own identifying information. (Don't include
              the brackets!)  The text should be enclosed in the appropriate
              comment syntax for the file format. We also recommend that a
              file or class name and description of purpose be included on the
              same "printed page" as the copyright notice for easier
              identification within third-party archives.
        
           Copyright 2026 Jothika Raja
        
           Licensed under the Apache License, Version 2.0 (the "License");
           you may not use this file except in compliance with the License.
           You may obtain a copy of the License at
        
               http://www.apache.org/licenses/LICENSE-2.0
        
           Unless required by applicable law or agreed to in writing, software
           distributed under the License is distributed on an "AS IS" BASIS,
           WITHOUT WARRANTIES OR CONDITIONS OF ANY KIND, either express or implied.
           See the License for the specific language governing permissions and
           limitations under the License.
License-File: LICENSE
Keywords: backblaze-b2,cctv,frigate,nvr,self-hosted,video-surveillance
Classifier: Development Status :: 3 - Alpha
Classifier: Intended Audience :: System Administrators
Classifier: License :: OSI Approved :: Apache Software License
Classifier: Operating System :: POSIX :: Linux
Classifier: Programming Language :: Python :: 3
Classifier: Programming Language :: Python :: 3.12
Classifier: Programming Language :: Python :: 3.13
Classifier: Topic :: Multimedia :: Video
Classifier: Topic :: System :: Systems Administration
Requires-Python: >=3.12
Requires-Dist: pyyaml>=6.0
Requires-Dist: tzdata>=2024.1
Provides-Extra: dev
Requires-Dist: pytest>=8.0; extra == 'dev'
Requires-Dist: ruff>=0.6; extra == 'dev'
Provides-Extra: mqtt
Requires-Dist: paho-mqtt>=2.1; extra == 'mqtt'
Provides-Extra: storage
Requires-Dist: boto3>=1.34; extra == 'storage'
Description-Content-Type: text/markdown

# cctv-stack

[![CI](https://github.com/aravindmyd/cctv-stack/actions/workflows/ci.yml/badge.svg)](https://github.com/aravindmyd/cctv-stack/actions/workflows/ci.yml)
[![Publish](https://github.com/aravindmyd/cctv-stack/actions/workflows/publish.yml/badge.svg)](https://github.com/aravindmyd/cctv-stack/actions/workflows/publish.yml)

Self-hosted CCTV built on **Frigate**, adding the four things Frigate deliberately leaves
to the operator:

1. **Canonical clips** — every review becomes one file at a deterministic path.
2. **Durable cloud backup** — clips are uploaded to Backblaze B2 exactly once.
3. **Independent retention** — local cleanup that never deletes an un-uploaded clip.
4. **Health surfaces** — each service reports whether it is actually working.

Every installation is independent: no central hub, no cross-site data, no inbound
connectivity requirement.

---

## Status

| Capability | State |
|---|---|
| Detect → canonical clip | ✅ |
| Upload to Backblaze B2, exactly once | ✅ |
| Local retention (upload-aware) | ✅ |
| Cloud retention and reconciliation | ⬜ |
| Aggregate status page and alerting | ⬜ |
| One-command client installer and signed bundle | ⬜ |
| Backup, restore, upgrade | ⬜ |

v0.3 is usable for a local-only installation or a B2-backed one. The deferred work, and
why it is deferred, is in [`docs/plans/backlog.md`](docs/plans/backlog.md). The client-site
delivery plan is [`docs/plans/packaging.md`](docs/plans/packaging.md).

## How it fits together

```text
 cameras ──RTSP──> Frigate ──review──> clip-worker ──> data/clips/... ──> uploader ──> B2
                      │                                    │
                      └── recordings (recovery window)      └── cleanup (only after upload)
```

Frigate does camera ingest, detection, recording and review segmentation. The
`clip-worker` cuts **one canonical clip per review item**. The uploader pushes it once,
and cleanup deletes a local clip only after its upload is terminal-success (INV-1).

MQTT is the low-latency path. The Frigate review sweep is the guarantee: if the broker or
the worker was down, the next sweep still materialises the clip. A review arriving twice
produces one clip, not two.

## Quick start

**Requirements:** `git`, Linux x86_64 or arm64 (macOS is supported for development),
Docker Engine with the Compose v2 plugin, and disk space for Frigate's recordings. The
first real run pulls the Frigate image and builds the CCTV image, so expect several
minutes.

```bash
git clone https://github.com/aravindmyd/cctv-stack.git
cd cctv-stack
./install.sh
```

The first run creates the two files that only you can fill in, then exits:

| File | Contains | Committed? |
|---|---|---|
| `.env` | Camera RTSP URLs, timezone, optional B2 credentials | **No** — gitignored |
| `config/cameras.yml` | Camera names, clip padding, retention policy | **No** — gitignored |

Edit both, then run `./install.sh` again. It validates the configuration, generates
Frigate's config, builds the image, starts the stack, and waits until Frigate answers.

Frigate's UI is HTTPS on `https://127.0.0.1:8971` (loopback only). The certificate is
self-signed, so the browser warns once. Port 5000 and MQTT are never published.

Clips land at:

```text
data/clips/<camera>/YYYY/MM/DD/HH-MM-SS.mp4
data/clips/<camera>/YYYY/MM/DD/HH-MM-SS.mp4.json
```

The sidecar records the review, event ids, requested boundaries, coverage, size and
SHA-256. The clips tree uses the **site timezone**; Frigate's own recordings tree uses
**UTC** — both are deliberate ([ADR-0017](docs/adr/0017-time-handling.md)).

A clip appears **after** the visit ends, not during it: Frigate keeps the review open
until the alert cutoff passes. There is no partial clip by design.

## What runs

| Service | Role |
|---|---|
| **Frigate** | Camera ingest, detection, recording and review segmentation |
| **clip-worker** | Materialises completed reviews at the canonical path, with a sidecar |
| **uploader** | Uploads to B2 through a storage adapter, with a persisted retry state machine. Reports `DISABLED` when no bucket is configured and exits `78` on a half-configuration |
| **cleanup** | Enforces local retention; refuses to delete a clip whose upload is not terminal-success |
| **config** | One-shot generator: `cameras.yml` → Frigate's config (INV-3) |
| **mosquitto** | MQTT broker, internal only |
| **status-collector** | ⬜ not built yet |

### Health surfaces

| Surface | Address | Notes |
|---|---|---|
| Frigate UI | `https://127.0.0.1:8971` | HTTPS, self-signed, loopback only |
| Uploader | `http://127.0.0.1:8082/health` | `DISABLED` without a B2 bucket |
| Cleanup | `http://127.0.0.1:8083/health` | Local retention state |
| Frigate API, MQTT | not published | Reachable only on the compose network |

## Configuration

The split is deliberate and load-bearing:

- **`config/cameras.yml`** is the single source of truth for cameras (INV-3). Frigate's
  config is generated from it and must never be hand-edited.
- **`.env`** holds location values and secrets: RTSP URLs, B2 keys, ports, data path.

Both real files are gitignored. `.env.example` and `config/cameras.example.yml` are the
templates. Never commit the filled-in versions, and never paste an RTSP URL or B2 key into
an issue. If a credential is exposed, follow
[`docs/runbooks/rotate-credentials.md`](docs/runbooks/rotate-credentials.md).

Camera names are lowercase kebab-case because they become filesystem paths and cloud
object keys.

## Published artefacts

| Artefact | Where | Published when |
|---|---|---|
| Branch image | `ghcr.io/aravindmyd/cctv-stack:edge` | Every merge to `main`/`master` |
| Commit image | `ghcr.io/aravindmyd/cctv-stack:sha-<short>` | Every merge |
| Version image | `ghcr.io/aravindmyd/cctv-stack:<version>` | A `v*` tag |
| Python package | `pypi.org/project/cctv-stack` | A `v*` tag |
| Wheel and sdist | Workflow artefact, and GitHub Release on tags | Every merge / tag |

```bash
docker pull ghcr.io/aravindmyd/cctv-stack:edge
pip install cctv-stack
```

The image is the runtime. `pip install cctv-stack` installs the four CLI entry points
(`cctv-clip-worker`, `cctv-config`, `cctv-uploader`, `cctv-cleanup`) but **not** Frigate,
Compose, or site configuration. The complete client-site install is the signed release
bundle in [`docs/plans/packaging.md`](docs/plans/packaging.md).

## Development

```bash
uv sync
uv run pytest                    # unit suite; live tests skip without Docker/S3
uv run ruff check .
uv run ruff format --check .

./tests/integration/run.sh       # live S3 suite against RustFS; needs Docker
./tests/e2e/run.sh               # synthetic camera → real clip; needs Docker + Frigate
```

The unit suite is **717 passed, 19 skipped** without a configured S3 endpoint or a running
Docker daemon. CI runs pre-commit, unit tests on Python 3.12 and 3.13, the pip-install
fallback, live integration, and the synthetic e2e pipeline. The publish workflow builds
the multi-arch image and the Python distributions.

## Documentation

- [`docs/index.md`](docs/index.md) — documentation map and reading order
- [`docs/architecture/hld.md`](docs/architecture/hld.md) — how the system fits together
- [`docs/architecture/invariants.md`](docs/architecture/invariants.md) — rules that must never break
- [`docs/runbooks/install.md`](docs/runbooks/install.md) — the target operator runbook (M6; the current installer is the two-run flow above)
- [`docs/plans/roadmap.md`](docs/plans/roadmap.md) — what gets built, in what order
- [`docs/plans/backlog.md`](docs/plans/backlog.md) — deliberately deferred work
- [`docs/plans/packaging.md`](docs/plans/packaging.md) — client-site delivery and release artefacts

## License

Apache-2.0 — see [`LICENSE`](LICENSE). The reasoning is in
[`docs/plans/opensourcing.md`](docs/plans/opensourcing.md).
