Deploy plumbing so Petal can run on the public VPS behind the Traefik already on that box, with vLLM reached over headscale. - Dockerfile: node build -> go build -> alpine runtime. CGO stays off (modernc SQLite is pure Go), so the runtime layer exists only for ffmpeg (read-aloud transcodes Piper's WAV) and tzdata (the companion's bedtime nag and night mode read the local clock). Runs as uid 10001 with /data as the single writable mount. - docker-compose.yml: Traefik labels following this host's convention (external `traefik` network, `web-secure` entrypoint, `default` cert resolver). Petal publishes no host port. ./data is a bind mount, not a named volume, so the nightly backup and a restore are reachable from the host. - Piper runs as two sibling containers rather than host systemd units. The plan assumed Piper was already installed on the VPS; it is not, the host has no lingering user session to keep user units alive, and containers keep the TTS ports on an internal network unreachable from anywhere but Petal. One image, voice chosen per service, model cached in a shared volume -- so the pt-PT voice is a new service, not a new image. - db.Backup + a `-backup` flag: VACUUM INTO, not a file copy. Petal runs in WAL mode, so the newest committed pages may live in petal.db-wal; copying the three files separately can capture a torn mid-checkpoint state. VACUUM INTO reads one coherent snapshot without taking a write lock, and emits a single file with no -wal/-shm companions. Refuses an existing destination so a failed run can't destroy the last good backup. - deploy/backup-petal.sh: nightly snapshot, compress, push to millenia over headscale with a post-transfer size check, prune both sides. - deploy/petal.env.example: LLM_TIMEOUT raised 30s -> 90s for the WAN+VPN round trip, since the voice and collocation passes send a whole document and the timeout is a hard deadline on Complete.
23 lines
855 B
Bash
Executable File
23 lines
855 B
Bash
Executable File
#!/usr/bin/env bash
|
|
# Fetch the configured voice if the shared volume doesn't have it yet, then
|
|
# serve it. The download is the only step that needs the internet, and it runs
|
|
# once per voice for the life of the volume — Petal itself stays offline-first.
|
|
set -euo pipefail
|
|
|
|
voice="${PIPER_VOICE:?PIPER_VOICE must be set}"
|
|
data_dir="${PIPER_DATA_DIR:-/voices}"
|
|
port="${PIPER_PORT:-5000}"
|
|
|
|
if [ ! -f "${data_dir}/${voice}.onnx" ]; then
|
|
echo ">> downloading voice ${voice} into ${data_dir}"
|
|
python -m piper.download_voices "${voice}" --data-dir "${data_dir}"
|
|
fi
|
|
|
|
echo ">> serving ${voice} on :${port}"
|
|
# 0.0.0.0 is safe here: the container sits on Petal's internal compose network
|
|
# with no published ports, so only Petal can reach it.
|
|
exec python -m piper.http_server \
|
|
-m "${voice}" \
|
|
--data-dir "${data_dir}" \
|
|
--host 0.0.0.0 --port "${port}"
|