scanopy: name the deployed binary what the unit starts

singlefile mode writes the asset to <target>/<app name>: 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.
scanopy: make the rollback restore the whole old setup
2026-10-03 00:17:45 -04:00 · 2026-09-18 07:58:58 +02:00 · 2026-09-18 07:58:32 +02:00 · 2026-09-18 07:46:53 +02:00 · 2026-09-18 07:46:15 +02:00
2 changed files with 15 additions and 9 deletions
--- a/ct/scanopy.sh
+++ b/ct/scanopy.sh
@@ -32,12 +32,16 @@ function update_script() {
    exit
  fi

-  if check_for_gh_release "scanopy-server" "scanopy/scanopy"; then
+  if check_for_gh_release "Scanopy" "scanopy/scanopy"; then
    msg_info "Stopping services"
    systemctl stop scanopy-server
    [[ -f /etc/systemd/system/scanopy-daemon.service ]] && systemctl stop scanopy-daemon
    msg_ok "Stopped services"

+    cp -f /usr/bin/scanopy-server /usr/bin/scanopy-server.bak 2>/dev/null || true
+    cp -f /opt/scanopy/.env /opt/scanopy/.env.bak
+    cp -f /etc/systemd/system/scanopy-server.service /etc/systemd/system/scanopy-server.service.bak
+
    if ! grep -q "PUBLIC_URL" /opt/scanopy/.env; then
      sed -i "\|_PATH=|a\\SCANOPY_PUBLIC_URL=http://${LOCAL_IP}:60072" /opt/scanopy/.env
    fi
@@ -46,11 +50,8 @@ function update_script() {
    sed -i 's|^WorkingDirectory=/opt/scanopy/backend$|WorkingDirectory=/opt/scanopy|' /etc/systemd/system/scanopy-server.service
    systemctl daemon-reload

-    cp -f /usr/bin/scanopy-server /usr/bin/scanopy-server.bak 2>/dev/null || true
-
-    fetch_and_deploy_gh_release "scanopy-server" "scanopy/scanopy" "singlefile" "latest" "/usr/bin" "scanopy-server-linux-$(arch_resolve)"
-
-    rm -rf /opt/scanopy/backend /opt/scanopy/ui
+    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

    if [[ -f /etc/systemd/system/scanopy-daemon.service ]]; then
      fetch_and_deploy_gh_release "Scanopy Daemon" "scanopy/scanopy" "singlefile" "latest" "/usr/local/bin" "scanopy-daemon-linux-$(arch_resolve)"
@@ -76,11 +77,15 @@ function update_script() {
    if [[ "$healthy" -ne 1 ]]; then
      systemctl stop scanopy-server
      [[ -f /usr/bin/scanopy-server.bak ]] && mv -f /usr/bin/scanopy-server.bak /usr/bin/scanopy-server
+      mv -f /opt/scanopy/.env.bak /opt/scanopy/.env
+      mv -f /etc/systemd/system/scanopy-server.service.bak /etc/systemd/system/scanopy-server.service
+      systemctl daemon-reload
      systemctl start scanopy-server
-      msg_error "New server did not answer /api/health, restored the previous binary"
+      msg_error "New server did not answer /api/health, restored the previous version"
      exit 1
    fi
-    rm -f /usr/bin/scanopy-server.bak
+    rm -rf /opt/scanopy/backend /opt/scanopy/ui
+    rm -f /usr/bin/scanopy-server.bak /opt/scanopy/.env.bak /etc/systemd/system/scanopy-server.service.bak
    [[ -f /etc/systemd/system/scanopy-daemon.service ]] && systemctl start scanopy-daemon
    msg_ok "Updated successfully!"
  fi
--- a/install/scanopy-install.sh
+++ b/install/scanopy-install.sh
@@ -15,7 +15,8 @@ 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)"
+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
Author	SHA1	Message	Date
MickLesk	f2140484e6	scanopy: name the deployed binary what the unit starts singlefile mode writes the asset to <target>/<app name>: 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.	2026-09-18 07:58:58 +02:00
MickLesk	34b9c447ed	scanopy: make the rollback restore the whole old setup The health check put the previous binary back but nothing else, and the source tree it needs was already gone by then: the update deleted /opt/scanopy/ui before starting the new server, and removed SCANOPY_WEB_EXTERNAL_PATH from the env at the same time. A failed health check therefore left the old binary running without the UI it serves from disk, so the rollback produced an API-only server. Back up the env file and the unit alongside the binary, restore all three when the check fails, and delete the source tree only once the new server has answered. Nothing the old version needs is removed before the new one has proven itself.	2026-09-18 07:58:32 +02:00
CanbiZ (MickLesk)	64d0becd62	Fix case sensitivity in fetch_and_deploy_gh_release	2026-09-18 07:46:53 +02:00
CanbiZ (MickLesk)	4663415b28	Update service names from 'scanopy-server' to 'Scanopy'	2026-09-18 07:46:15 +02:00