Release 2.21.0: non-destructive media and scoped player sync
Publish Docker Image / build-and-push-existing-registry (./build/Dockerfile, web, pulse-signage-web) (push) Successful in 1m36s
Publish Docker Image / build-and-push-existing-registry (./build/Dockerfile.player, player, pulse-signage-player) (push) Successful in 31s

This commit is contained in:
lzstealth committed 2026-10-26 21:46:33 +00:00
1 parent 24df245ea1
commit 7cff39dc76
35 files changed
+2009 -949

No files matched your search

+10
View File
@@ -263,6 +263,16 @@ Remote stack ports:
- `pulse-signage` - shared media and cache volume for the remote player.
### Local Development
- `media/web` - source media and server-side cache shared by web and bridge.
- `media/player-local` - isolated storage for the direct local player.
- `media/player-remote` - isolated storage for the bridge-connected remote dev player.
The local dev player keeps `PLAYER_INTERNAL_URL` pointing to the Docker player service. Set `BRIDGE_PUBLIC_URL` only in the remote player's environment, using the public HTTPS bridge address. Do not set it in the shared local environment, because it switches a player into remote mode.
Web and player services automatically create a `.storage-id` file in their media root. Keep that file when moving the same storage folder. When copying media into an independent player folder, omit or remove the copied `.storage-id` so the service creates a different identity; otherwise separate folders would be mistaken for shared storage. No additional environment setting is required.
## Networks
Each compose file creates its own named network: