zerobyte/examples/tailscale-sidecar/.env.example
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

22 lines
686 B
Text

# --- Zerobyte ---
TZ=UTC
# --- Tailscale ---
# Create an auth key in the Tailscale admin console.
# Recommended: ephemeral + pre-approved (or tagged) key.
TS_AUTHKEY=tskey-auth-xxxxxxxxxxxxxxxxxxxx
# How this node should appear in your tailnet.
TS_HOSTNAME=zerobyte
# Kernel-mode (false) vs userspace-mode (true).
# - false: requires /dev/net/tun on the host
# - true: works on Docker Desktop / hosts without TUN, but you must also remove
# the /dev/net/tun device mapping from compose.yaml
TS_USERSPACE=false
# Optional extra args passed to `tailscale up`.
# Examples:
# TS_EXTRA_ARGS=--accept-dns=true
# TS_EXTRA_ARGS=--advertise-tags=tag:backup --accept-routes
TS_EXTRA_ARGS=