5a4f4641b4
- Add ImportResult type to track succeeded/warnings/errors counts across all import functions - Implement multi-layer repository duplicate detection: - URL-based check (same path/bucket/endpoint already registered) - Restic repo check (path is already a restic repository) - Name-based fallback check - Standardize logging between CLI and env var import methods with logImportSummary() - CLI exits with code 1 when import has errors - Remove shortId override for local repo migrations (use full path with isExistingRepository instead) - Update example JSON and README: - Document that local repo path is optional (defaults to /var/lib/zerobyte/repositories) - Add existing-local-repo example with isExistingRepository: true - Add S3 endpoint field to example - Expand config behavior docs to explain all repository skip conditions - Improve .gitignore to exclude all JSON except example template |
||
|---|---|---|
| .. | ||
| basic-docker-compose | ||
| config-file-import | ||
| directory-bind-mount | ||
| rclone-config-mount | ||
| secrets-placeholders | ||
| simplified-docker-compose | ||
| tailscale-sidecar | ||
| README.md | ||
Examples
This folder contains runnable, copy/paste-friendly examples for running Zerobyte in different setups.
Table of contents
Basic usage
- Basic Docker Compose — standard deployment with remote mount support (includes
SYS_ADMIN+/dev/fuse). - Simplified Docker Compose (no remote mounts) — reduced-privilege deployment (no
SYS_ADMIN, no/dev/fuse). - Bind-mount a local directory — back up a host folder by mounting it into the container.
- Mount an rclone config — use rclone-based repository backends by mounting your rclone config.
- Secret placeholders + Docker secrets — keep secrets out of the DB using
env://...andfile://...references. - Config file import (Infrastructure as Code) — pre-configure volumes/repos/schedules/users on startup.
Advanced setups
- Tailscale sidecar — run Zerobyte behind a Tailscale sidecar using shared networking.