vh/esh-pfi-infrastructure
1
0
Fork 0
Code Issues 7 Pull Requests Actions Packages Projects Releases Wiki Activity

chore(augaman): remove the fv-ml1 instance (Prime)

Browse Source 
Prime removed the second instance after the v0.1.3 bench. esh-ml1 handles a face
in ~48 ms, sits in the house next to the cameras, and holds the verified
backup. fv-ml1's gallery was empty (0 identities). The container, gallery volume,
image, compose dir (with its .env), backup dir and build sources are removed from
fv-ml1. GPU_ID / CARD_SUFFIX stay in the compose for any future second host.
This commit is contained in:
vh
2026-09-27 01:31:25 -07:00
parent 0118e57c83
commit ad484c3c99
4 changed files with 15 additions and 22 deletions
Download Patch File Download Diff File Expand all files Collapse all files
stacks/augaman/.env.example
+2 -4
View File
@@ -13,17 +13,15 @@ HOST_IP=10.0.50.80
# The host's card index for the GPU reservation (default 0). The container always
# sees its one card as index 0, so AUGAMAN_CUDA_DEVICE_ID never changes.
# esh-ml1: 0 (the only card) fv-ml1: 1 (the utility card, beside vllm-coder)
# esh-ml1: 0 (the only card). fv-ml1 used 1 while its instance existed (removed 2026-09-27).
GPU_ID=0
# Appended to the Homepage card name so the two instances are distinguishable.
# Note the leading space. esh-ml1 (the primary) leaves it empty.
# fv-ml1: CARD_SUFFIX=" (fv-ml1)"
# Note the leading space, e.g. CARD_SUFFIX=" (fv-ml1)". esh-ml1 leaves it empty.
CARD_SUFFIX=
# Where the backup CLI writes gallery.db. Owned 10001:10001 (the container user),
# mode 0700. On esh-ml1 it is the restic stage dir, so the backup run that copies the
# gallery here is the same run that ships it off-box (README "Backup").
# fv-ml1 (fixtures-only, no scheduled gallery backup): /opt/docker/backup/augaman.
BACKUP_DIR=/var/lib/restic/stage/augaman
# >= 32 visible-ASCII characters. Source of truth is the vault: