History

ivenos 38b49debb1 Rename docker-compose.yml to compose.yaml Aligns the project with the current Compose Specification, which designates compose.yaml as the canonical filename and treats the docker-compose.yml name as a legacy fallback. Renames every compose file in the repo (the root dev/e2e stack, the deployment examples under examples/, and the integration-test infra stack) and updates all documentation, the integration test runner, the capability hint messages, and the .gitattributes pattern accordingly. No top-level version field was present to remove. Functional behavior is unchanged: docker compose discovers either filename, so existing deployments are not affected by the rename. Reference: https://docs.docker.com/compose/intro/compose-application-model/		2026-06-02 21:09:47 +02:00
..
.env.example	Add examples directory and runnable setups	2025-12-19 13:28:05 +01:00
compose.yaml	Rename docker-compose.yml to compose.yaml	2026-06-02 21:09:47 +02:00
README.md	Add examples directory and runnable setups	2025-12-19 13:28:05 +01:00

Basic Docker Compose

Minimal "standard" deployment for Zerobyte.

This setup enables remote mount backends (NFS/SMB/WebDAV) from inside the container by granting the required capability and FUSE device.

Prerequisites

cp .env.example .env
docker compose up -d

This example uses cap_add: SYS_ADMIN and /dev/fuse to support mounting remote volumes.
Do not place /var/lib/zerobyte on a network share.