mirror of https://github.com/nicotsx/zerobyte.git synced 2026-06-13 11:00:28 -04:00

Files

iven aed2c15709 Rename docker-compose.yml to compose.yaml (#935 )

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-10 20:04:00 +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 (#935 )

2026-06-10 20:04:00 +02:00

README.md

Add examples directory and runnable setups

2025-12-19 13:28:05 +01:00

README.md

Simplified Docker Compose (no remote mounts)

A reduced-privilege setup for Zerobyte when you do not need to mount NFS/SMB/WebDAV from inside the container.

Prerequisites

Docker + Docker Compose

Setup

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

Access

UI/API: http://<host>:4096

Trade-offs

✅ No SYS_ADMIN
✅ No /dev/fuse
✅ Still supports all repository backends (local, S3, GCS, Azure, rclone)
❌ Cannot mount remote shares from inside Zerobyte