d74f516336
* feat: file-based provisionning of volumes and repos docs: provisioning example chore: ui improvements * chore: ci issues |
||
|---|---|---|
| .. | ||
| basic-docker-compose | ||
| directory-bind-mount | ||
| provisioned-resources | ||
| rclone-config-mount | ||
| 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.
- Provisioned repositories and volumes — operator-managed provisioning with env/file references kept in a mounted JSON file.
Advanced setups
- Tailscale sidecar — run Zerobyte behind a Tailscale sidecar using shared networking.