tfaour
94d67f7767
Build and push server image / build-and-push (push) Successful in 39s
New Gitea Actions workflow builds both board variants and publishes them as release assets whenever firmware/version.txt is bumped. The server can now poll that repo's releases (next to the existing manual upload) and either surface an "Update frame" button or, with "Automatically apply updates" checked, stage the new build itself -- the frame still only updates on its own next wake either way.
26 lines
1.1 KiB
Plaintext
26 lines
1.1 KiB
Plaintext
services:
|
|
espresso-frame-server:
|
|
image: git.thumeit.com/tfaour/espresso-frame-server:latest
|
|
build: .
|
|
ports:
|
|
- "8420:8420"
|
|
volumes:
|
|
- ./data:/data
|
|
environment:
|
|
- CONFIG_PATH=/data/config.json
|
|
- IMMICH_URL=http://your-immich-host:2283
|
|
- IMMICH_API_KEY=your-immich-api-key-here
|
|
# Optional: gates the entire server -- the web UI (/, /api/*) AND
|
|
# every device-facing /frame/* endpoint -- behind this shared secret.
|
|
# Leave unset to keep it all open on a trusted LAN, same as before.
|
|
# Paste the same value into the ESP32's captive portal setup form
|
|
# (Access Token field) so it's sent on every device request and gets
|
|
# embedded automatically in the manage-menu/share QR codes.
|
|
- MANAGEMENT_TOKEN=changeme
|
|
# Optional: only needed if the Gitea repo configured in the web UI's
|
|
# "Firmware Gitea repo URL" field is private. A read-only PAT is
|
|
# enough -- it's sent to that repo's releases API/asset downloads
|
|
# only, never exposed via the web UI or any API response.
|
|
- GITEA_FIRMWARE_TOKEN=your-gitea-pat-here
|
|
restart: unless-stopped
|