starred/ProxmoxVE
1
0
Fork 0
mirror of https://github.com/community-scripts/ProxmoxVE.git synced 2026-03-01 11:19:48 +03:00
Code Issues 23 Packages Projects Releases 34 Wiki Activity

[PR #7519] [MERGED] Pulse: standardise install/update with Pulse repo script #6744

New Issue
Closed
opened 2026-02-05 07:35:49 +03:00 by OVERLORD · 0 comments
OVERLORD commented 2026-02-05 07:35:49 +03:00
Owner
Copy Link

📋 Pull Request Information

Original PR: https://github.com/community-scripts/ProxmoxVE/pull/7519
Author: @vhsdream
Created: 9/9/2025
Status: ✅ Merged
Merged: 9/9/2025
Merged by: @MickLesk

Base: main ← Head: pulse

📝 Commits (1)

  • e512965 Pulse: standardise install/update with Pulse repo script

📊 Changes

2 files changed (+8 additions, -10 deletions)

View changed files

📝 ct/pulse.sh (+5 -8)
📝 install/pulse-install.sh (+3 -2)

📄 Description

✍️ Description

  • revert the pulse => pulse-backend service name change
  • remove message about older installs
  • symlink pulse binary to /usr/local/bin

I tested this and it seems to be possible to install Pulse with this script, and then update with the script in the Pulse repo. The only issue is that the ~/.pulse file is not updated, so if a user runs update in the LXC it will re-install the update.

@rcourtman what do you think about having your script just add the ~/.pulse file in the root user directory when it installs/updates?

🔗 Related PR / Issue

Link: https://github.com/rcourtman/Pulse/issues/430

✅ Prerequisites (X in brackets)

  • Self-review completed – Code follows project standards.
  • Tested thoroughly – Changes work as expected.
  • No security risks – No hardcoded secrets, unnecessary privilege escalations, or permission issues.

🛠️ Type of Change (X in brackets)

  • 🐞 Bug fix – Resolves an issue without breaking functionality.
  • ✨ New feature – Adds new, non-breaking functionality.
  • 💥 Breaking change – Alters existing functionality in a way that may require updates.
  • 🆕 New script – A fully functional and tested script or script set.
  • 🌍 Website update – Changes to website-related JSON files or metadata.
  • 🔧 Refactoring / Code Cleanup – Improves readability or maintainability without changing functionality.
  • 📝 Documentation update – Changes to README, AppName.md, CONTRIBUTING.md, or other docs.

🔄 This issue represents a GitHub Pull Request. It cannot be merged through Gitea due to API limitations.

## 📋 Pull Request Information **Original PR:** https://github.com/community-scripts/ProxmoxVE/pull/7519 **Author:** [@vhsdream](https://github.com/vhsdream) **Created:** 9/9/2025 **Status:** ✅ Merged **Merged:** 9/9/2025 **Merged by:** [@MickLesk](https://github.com/MickLesk) **Base:** `main` ← **Head:** `pulse` --- ### 📝 Commits (1) - [`e512965`](https://github.com/community-scripts/ProxmoxVE/commit/e512965a668fb73e2ea2e2302353c10cf9a5bcf5) Pulse: standardise install/update with Pulse repo script ### 📊 Changes **2 files changed** (+8 additions, -10 deletions) <details> <summary>View changed files</summary> 📝 `ct/pulse.sh` (+5 -8) 📝 `install/pulse-install.sh` (+3 -2) </details> ### 📄 Description ## ✍️ Description - revert the pulse => pulse-backend service name change - remove message about older installs - symlink pulse binary to /usr/local/bin I tested this and it seems to be possible to install Pulse with this script, and then update with the script in the Pulse repo. The only issue is that the `~/.pulse` file is not updated, so if a user runs `update` in the LXC it will re-install the update. @rcourtman what do you think about having your script just add the `~/.pulse` file in the root user directory when it installs/updates? ## 🔗 Related PR / Issue Link: https://github.com/rcourtman/Pulse/issues/430 ## ✅ Prerequisites (**X** in brackets) - [x] **Self-review completed** – Code follows project standards. - [x] **Tested thoroughly** – Changes work as expected. - [x] **No security risks** – No hardcoded secrets, unnecessary privilege escalations, or permission issues. --- ## 🛠️ Type of Change (**X** in brackets) - [ ] 🐞 **Bug fix** – Resolves an issue without breaking functionality. - [ ] ✨ **New feature** – Adds new, non-breaking functionality. - [ ] 💥 **Breaking change** – Alters existing functionality in a way that may require updates. - [ ] 🆕 **New script** – A fully functional and tested script or script set. - [ ] 🌍 **Website update** – Changes to website-related JSON files or metadata. - [x] 🔧 **Refactoring / Code Cleanup** – Improves readability or maintainability without changing functionality. - [ ] 📝 **Documentation update** – Changes to `README`, `AppName.md`, `CONTRIBUTING.md`, or other docs. --- <sub>🔄 This issue represents a GitHub Pull Request. It cannot be merged through Gitea due to API limitations.</sub>
OVERLORD added the pull-request label 2026-02-05 07:35:49 +03:00
Sign in to join this conversation.
No Branch/Tag Specified
Branches Tags
Labels
Clear labels
Implemented in VED waiting push to Main
breaking change
bug
bug
bugfix
deferred
delete script
dependencies
enhancement
external
feature
github
help wanted
in project pipeline
invalid
investigation
json
maintenance
needs triage
new script
new script
nice to have
not a script issue
not planned
organization
pull-request
Mirrored from GitHub Pull Request
 question
refactor
rename script
security
update script
website
wontdo
🛑 Failure to comply with the guidelines
No Label pull-request
Milestone
No items
No Milestone
Projects
Clear projects
No project
Assignees
Clear assignees
OVERLORD
No Assignees
1 Participants
Notifications
Due Date
No due date set.
Dependencies

No dependencies set.

Reference: starred/ProxmoxVE#6744
Delete Branch "%!s()"

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?