Install Script detects old install with V4 install and misplaced env file

[gdeeble]

Over the past few days when I've tried to update using the install.sh file, it would fail, and I didn't know why, but would pull it locally and have it just continue. In having time to troubleshoot the issue, it looks like if you end up putting the .env file in /opt/pulse accidentally, it will cause the failure.

I would recommend checking if /etc/pulse/.env doesn't exist and V3 components like the node packages, etc, etc, then fail otherwise proceed. Not sure if this would be something to considered appropriate. Additionally, maybe offer to remove the V3 components if it detects a V4 installation.

[rcourtman]

hey @gdeeble, thanks for reporting this. you're right that the V3 detection was too aggressive and getting triggered by stray .env files in /opt/pulse.

just removed all the V3 detection code since V3 is deprecated and no longer supported anyway. the install script should work smoothly now even if there's a misplaced .env file.

fix is live in main, so the installer should work properly next time you run it.

[gdeeble]

Thank you! I see it updated. FYI, main: line 807: FRONTEND_PORT: unbound variable when I ran it to do the update to the stable build.

[gdeeble]

Closing out as resolved.