mirror of
https://github.com/nicotsx/zerobyte.git
synced 2026-06-15 12:00:29 -04:00
aed2c15709
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/
Bind-mount a local directory
This example shows how to back up a host directory by bind-mounting it into the Zerobyte container.
It uses the simplified setup (no remote mounts).
Prerequisites
- Docker + Docker Compose
Setup
- Copy the env file:
cp .env.example .env
-
Edit
.envand setHOST_DATA_DIRto the directory you want to back up. -
Start the stack:
docker compose up -d
Use in Zerobyte
- Create a new volume of type Directory
- Select the mounted path shown in the compose file:
/mydata
Access
- UI/API:
http://<host>:4096