45b5c0d752
Add CLI command to import configuration from file or stdin, providing an alternative to the env-var-based automatic import on startup. Features: - `import-config --config <path>` to import from a mounted file - `import-config --stdin` to import from piped input (no file mount needed) - `import-config --dry-run` to validate config without importing Changes: - Add app/server/cli/commands/import-config.ts with new command - Register importConfigCommand in CLI index - Refactor config-import.ts: extract runImport() and add applyConfigImport() for direct config object import (used by CLI) - Update docs with both import methods (env var and CLI examples) |
||
|---|---|---|
| .. | ||
| 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.