From f2140484e6f399bdb729c9a9964748686287d2c7 Mon Sep 17 00:00:00 2001 From: MickLesk <47820557+MickLesk@users.noreply.github.com> Date: Fri, 18 Sep 2026 07:58:58 +0200 Subject: [PATCH] scanopy: name the deployed binary what the unit starts singlefile mode writes the asset to /: local target_file="$app" [[ "${USE_ORIGINAL_FILENAME:-false}" == "true" ]] && target_file="$filename" so with the app renamed to Scanopy the binary lands at /usr/bin/Scanopy while the unit starts /usr/bin/scanopy-server, and the service never comes up on a fresh install. Rename it after the deploy, the same way the daemon block already renames "Scanopy Daemon". Keeping the app name is what matters here: it is also the version file (~/.scanopy), and changing it would make every existing container report an update it does not need. --- install/scanopy-install.sh | 1 + 1 file changed, 1 insertion(+) diff --git a/install/scanopy-install.sh b/install/scanopy-install.sh index ca173d9a9..a2ee2e9c3 100644 --- a/install/scanopy-install.sh +++ b/install/scanopy-install.sh @@ -16,6 +16,7 @@ update_os PG_VERSION=17 setup_postgresql PG_DB_NAME="scanopy_db" PG_DB_USER="scanopy" PG_DB_GRANT_SUPERUSER="true" setup_postgresql_db fetch_and_deploy_gh_release "Scanopy" "scanopy/scanopy" "singlefile" "latest" "/usr/bin" "scanopy-server-linux-$(arch_resolve)" +mv -f /usr/bin/Scanopy /usr/bin/scanopy-server msg_info "Configuring Scanopy" mkdir -p /opt/scanopy