make Pulse installation non-interactive

[rcourtman]

Description

Streamline Pulse installation to leverage its new web-based configuration system, removing all interactive prompts and manual configuration steps.

Related PR/Issue: #4827 (previous discussion about making Pulse non-interactive)

Prerequisites

• Self-review – The code follows the project standards
• Tested – Changes work as expected (removes prompts, uses web config)
• No security risks – No hardcoded secrets or permission issues

Type of Change

• 🐞 Bug fix – Resolves the issue of interactive prompts during LXC creation
• ✨ New feature – Leverages Pulse's web-based configuration system
• 🌍 Website update – Updates JSON note to reflect new configuration method
• 🔧 Refactoring / Code Cleanup – Simplifies installation process

Changes Made

1. Removed all interactive prompts - Installation runs completely unattended
2. Removed .env setup - No longer needed as Pulse handles configuration through web UI
3. Removed configuration messages - Users configure through the web interface
4. Changed install directory - From /opt/pulse-proxmox to /opt/pulse for cleaner paths
5. Updated JSON note - Now mentions web-based setup wizard instead of manual .env editing

Context

Pulse v3.13.0+ features a complete web-based configuration system with automatic setup detection. When users navigate to the URL after installation, Pulse automatically shows a setup wizard for entering Proxmox credentials. No SSH or manual file editing required.

This provides the ideal community script experience - completely hands-off installation with all configuration handled through the modern web interface.

[MickLesk]

I mark this as Breaking change, because Paths Changes and i think an new build (create new LXC) is better

By the way, do you need to edit the pulse.sh too? Because Paths

[rcourtman]

Good catch! I've updated pulse.sh to align with the new path structure and removed the .env handling since Pulse now uses web-based configuration.

Regarding the path change - you're right it's technically breaking, but it also resolves a potential copyright concern with using 'pulse-proxmox' in the directory name. The new /opt/pulse path is cleaner and avoids any trademark issues. Since this affects the installation script for new containers, existing users won't be impacted unless they recreate their container.

[CrazyWolf13]

@rcourtman Existing users are definitely impacted, if an existing user will upgrade using the update function, I'll will fail, no?
Because the service still uses the old path, and also the old-path is not removed?

maybe you could do the following:
Detect if the user still has the old pulse-proxmox installation, if so, (up to you to decide)

• Warn user and fix service files automatically by changing the systemd service via some sed/regex, also remove the old installation.
• Tell the user to recreate the LXC (more work for user)

[MickLesk]

555 installs of Pulse

1. Breaking Change - create new LXC
2. Migration Part (i think useless, more work for us, for little Help.)

[rcourtman]

Thanks for the feedback. I apologize for the path change - I understand it may seem unnecessary given the issues it causes, but unfortunately I'm already quite far along this path in my development. This should be the last time the path needs to change.

I've enhanced the migration logic in the Pulse project's installer script (scripts/install-pulse.sh in https://github.com/rcourtman/Pulse) to address the breaking change concerns.

When users with existing /opt/pulse-proxmox installations run the updated installer script, it will automatically:

• Detect the old installation and migrate it to /opt/pulse
• Create backup before migration with full rollback capability
• Update service files and preserve all user data
• Show clear migration notice and require user confirmation

This minimizes disruption to existing installations while maintaining the cleaner path structure. Users would need to run the installer again and the migration happens automatically.

Would this address your concerns about breaking existing installations?

[rcourtman]

I can go back to the old path if needed. @MickLesk since you mentioned you use Pulse, perhaps you could try the migration in my install script? If it works, you'll have peace of mind that existing users have an easy path to switch. If it doesn't, we can stick to the old path and I'll make adjustments on my end.

[MickLesk]

I think we should use the new path, only an Check If old directory "please recreate the LXC after Breaking Change (Link to PR)