Exclude hardware.ini from the deploy rsync so --delete cannot erase it

This commit is contained in:
pgdalmeida 2026-09-16 18:27:27 +02:00
parent b97df0adf2
commit 08a6f7c1fa
Signed by: pedro.almeida
GPG Key ID: D4A6C394DF13F1D7
1 changed files with 9 additions and 0 deletions

View File

@ -183,6 +183,14 @@ ssh "$REMOTE_HOST" "mkdir -p '$REMOTE_DIR'"
# config, operator-exported camera settings, captured output) and are # config, operator-exported camera settings, captured output) and are
# deliberately NOT mirrored, so a deploy never clobbers them. # deliberately NOT mirrored, so a deploy never clobbers them.
# #
# hardware.ini is excluded for the same reason but one step further: it normally
# lives in /etc/fire_gimbal_control/, out of reach of this rsync entirely, and
# the exclude covers the fallback location (beside config.ini) that the
# resolution chain also accepts. Without it, --delete would erase a machine's
# assembly description on the next deploy - the same way it once erased a
# freshly exported camera profile. --push-config does NOT override this: the
# assembly of a tower is not something you push from a dev box.
#
# The profile XMLs matter especially: they are exported on the DEVICE from the # The profile XMLs matter especially: they are exported on the DEVICE from the
# VimbaX Viewer, which is where the camera is, so they exist nowhere in this # VimbaX Viewer, which is where the camera is, so they exist nowhere in this
# repo. Without these excludes `--delete` erases them on the next deploy - which # repo. Without these excludes `--delete` erases them on the next deploy - which
@ -214,6 +222,7 @@ rsync -avz --delete \
--exclude '.vscode' \ --exclude '.vscode' \
--exclude '__pycache__' \ --exclude '__pycache__' \
--exclude '.deploy.env' \ --exclude '.deploy.env' \
--exclude 'hardware.ini' \
"${CONFIG_EXCLUDES[@]}" \ "${CONFIG_EXCLUDES[@]}" \
--exclude 'config.ini.bak-*' \ --exclude 'config.ini.bak-*' \
--exclude 'config/camera_profiles/**/*.xml' \ --exclude 'config/camera_profiles/**/*.xml' \