mirror of https://github.com/nicotsx/zerobyte.git synced 2026-06-15 03:50:37 -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

implement copilot and rabbitai suggestions

2025-12-19 14:39:57 +01:00

README.md

Mount an rclone config (for rclone repositories)

This example shows how to make an existing rclone configuration available inside the Zerobyte container.

Use this if you want to use rclone as a repository backend (Dropbox/Google Drive/OneDrive/etc.).

Prerequisites

Docker + Docker Compose
An existing rclone config directory on the Docker host

If you don't have one yet:

rclone config

Setup

Copy the env file:

cp .env.example .env

Edit .env and set RCLONE_CONFIG_DIR to the absolute path of your host rclone config directory.
Start the stack:

docker compose up -d

Access

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

Notes

This setup does not require SYS_ADMIN or /dev/fuse.
The rclone config is mounted read-only into /root/.config/rclone.