Same category of risk as the gitea :nightly issue: floating dev/beta tags let watchtower silently pull unvetted upstream builds. couchdb had no tag at all (implicit :latest); filebrowser and statping only publish beta/dev channels upstream so pinned to the exact version in use rather than a moving target.
24 lines
675 B
YAML
24 lines
675 B
YAML
services:
|
|
filebrowser:
|
|
container_name: filebrowser-colleen-hd
|
|
# No stable channel exists upstream for this project (only beta/preview
|
|
# tags are published) — pinned to the exact version in use instead of the
|
|
# floating :beta tag so watchtower can't silently jump versions.
|
|
image: gtstef/filebrowser:1.5.4-beta
|
|
environment:
|
|
FILEBROWSER_CONFIG: "data/config.yaml"
|
|
TZ: "America/New_York"
|
|
volumes:
|
|
- /mnt/nas_backup:/folder
|
|
- /srv/filebrowser-colleen-hd:/home/filebrowser/data
|
|
ports:
|
|
- 3427:80
|
|
networks:
|
|
- npm-network
|
|
restart: unless-stopped
|
|
|
|
networks:
|
|
default:
|
|
npm-network:
|
|
external: true
|