migration/deno-v4 #1
Reference in New Issue
Block a user
Delete Branch "migration/deno-v4"
Deleting a branch is permanent. Although the deleted branch may continue to exist for a short time before it actually gets removed, it CANNOT be undone in most cases. Continue?
@philkunz Please have a look. I think I did everything for v4 that we discussed.
Critical fixes for v3→v4 migration: 1. install.sh: Auto-update systemd service file during migration - Calls 'nupst service enable' before restarting service - Only when migrating from v3 (OLD_NODE_INSTALL=1) - Ensures service file has correct v4 paths 2. ts/systemd.ts: Fix hardcoded v3 paths in service template - ExecStart: /opt/nupst/bin/nupst daemon-start (v3, broken) → /usr/local/bin/nupst service start-daemon (v4, correct) - Description: Updated to 'Deno-powered UPS Monitoring Tool' - Added RestartSec=10 (prevent rapid restart loops) - Removed NODE_ENV=production (not needed for Deno) - WorkingDirectory: /tmp → /opt/nupst Without these fixes: - Service fails to start after migration - Service file points to non-existent /opt/nupst/bin/nupst - Users must manually run 'nupst service enable' Discovered via Docker migration testing in test/manualdocker/LGTM.