SVI/ProxmoxVE
1
0
Fork 0
mirror of https://github.com/community-scripts/ProxmoxVE.git synced 2026-03-31 06:34:17 -04:00
Code Issues 2.6k Packages Projects Releases 10 Wiki Activity

[PR #1200] [MERGED] Keep Lubelogger data after update to a new version #2880

New Issue
Closed
opened 2025-11-20 05:32:20 -05:00 by saavagebueno · 0 comments
saavagebueno commented 2025-11-20 05:32:20 -05:00
Owner
Copy Link

📋 Pull Request Information

Original PR: https://github.com/community-scripts/ProxmoxVE/pull/1200
Author: @JcMinarro
Created: 1/3/2025
Status: ✅ Merged
Merged: 1/3/2025
Merged by: @michelroegl-brunner

Base: main ← Head: fix/lubelogger-update-script

📝 Commits (1)

  • a2ea1e7 Keep Lubelogger data after update to a new version

📊 Changes

1 file changed (+12 additions, -3 deletions)

View changed files

📝 ct/lubelogger.sh (+12 -3)

📄 Description

🛠️ Note:
We are meticulous about merging code into the main branch, so please understand that pull requests not meeting the project's standards may be rejected. It's never personal!
🎮 Note for game-related scripts: These have a lower likelihood of being merged.

✍️ Description

The previous update script for Lubelogger removed all local data that a user could have.
On this PR I am keeping all folders that are indicated on the Docker Compose as volumes to persist data.
Some of the folders are not created until the user add any data there, so we need to do a prevent check before backup old ones.

Please remove unneeded lines!

🛠️ Type of Change

Please check the relevant options:

  • Bug fix (non-breaking change that resolves an issue)
  • New feature (non-breaking change that adds functionality)
  • Breaking change (fix or feature that would cause existing functionality to change unexpectedly)
  • New script (a fully functional and thoroughly tested script or set of scripts)

✅ Prerequisites

The following steps must be completed for the pull request to be considered:

  • Self-review performed (I have reviewed my code to ensure it follows established patterns and conventions.)
  • Testing performed (I have thoroughly tested my changes and verified expected functionality.)
  • Documentation updated (I have updated any relevant documentation)

📋 Additional Information (optional)

Provide any extra context or screenshots about the feature or fix here.

🔄 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/1200 **Author:** [@JcMinarro](https://github.com/JcMinarro) **Created:** 1/3/2025 **Status:** ✅ Merged **Merged:** 1/3/2025 **Merged by:** [@michelroegl-brunner](https://github.com/michelroegl-brunner) **Base:** `main` ← **Head:** `fix/lubelogger-update-script` --- ### 📝 Commits (1) - [`a2ea1e7`](https://github.com/community-scripts/ProxmoxVE/commit/a2ea1e77aef83719714180182e280f41b31c4f92) Keep Lubelogger data after update to a new version ### 📊 Changes **1 file changed** (+12 additions, -3 deletions) <details> <summary>View changed files</summary> 📝 `ct/lubelogger.sh` (+12 -3) </details> ### 📄 Description > **🛠️ Note:** > We are meticulous about merging code into the main branch, so please understand that pull requests not meeting the project's standards may be rejected. It's never personal! > 🎮 **Note for game-related scripts:** These have a lower likelihood of being merged. --- ## ✍️ Description The previous update script for Lubelogger removed all local data that a user could have. On this PR I am keeping all folders that are indicated on the [Docker Compose](https://github.com/hargata/lubelog/blob/main/docker-compose.yml#L11-L17) as volumes to persist data. Some of the folders are not created until the user add any data there, so we need to do a prevent check before backup old ones. - - - **_Please remove unneeded lines!_** - Related Issue: #1199 - Related PR: # (if applicable) - Related Discussion: []()(if applicable) --- ## 🛠️ Type of Change Please check the relevant options: - [x] Bug fix (non-breaking change that resolves an issue) - [ ] New feature (non-breaking change that adds functionality) - [ ] Breaking change (fix or feature that would cause existing functionality to change unexpectedly) - [ ] New script (a fully functional and thoroughly tested script or set of scripts) --- ## ✅ Prerequisites The following steps must be completed for the pull request to be considered: - [x] Self-review performed (I have reviewed my code to ensure it follows established patterns and conventions.) - [x] Testing performed (I have thoroughly tested my changes and verified expected functionality.) - [ ] Documentation updated (I have updated any relevant documentation) --- ## 📋 Additional Information (optional) Provide any extra context or screenshots about the feature or fix here. --- <sub>🔄 This issue represents a GitHub Pull Request. It cannot be merged through Gitea due to API limitations.</sub>
saavagebueno added the pull-request label 2025-11-20 05:32:20 -05:00
Sign in to join this conversation.
No Branch/Tag Specified
Branches Tags
Labels
Clear labels
🛑 Failure to comply with the guidelines
breaking change
bug
bug
bugfix
deferred
delete script
dependencies
enhancement
external
feature
github
help wanted
Implemented in VED waiting push to Main
in project pipeline
invalid
investigation
json
maintenance
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
No Label pull-request
Milestone
No items
No Milestone
Projects
Clear projects
No project
Assignees
Clear assignees
saavagebueno
No Assignees
1 Participants
Notifications
Due Date
No due date set.
Dependencies

No dependencies set.

Reference: SVI/ProxmoxVE#2880
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?