starred/ProxmoxVE
1
0
Fork 0
mirror of https://github.com/community-scripts/ProxmoxVE.git synced 2026-07-16 05:34:07 +03:00
Code Issues 23 Packages Projects Releases 44 Wiki Activity

[PR #6653] [MERGED] Improve backup of adventurelog folder #6176

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

📋 Pull Request Information

Original PR: https://github.com/community-scripts/ProxmoxVE/pull/6653
Author: @ThomasDetemmerman
Created: 8/8/2025
Status: ✅ Merged
Merged: 8/9/2025
Merged by: @michelroegl-brunner

Base: main ← Head: patch-1

📝 Commits (1)

  • d3995d4 Improve backup of adventurelog folder

📊 Changes

1 file changed (+1 additions, -4 deletions)

View changed files

📝 ct/adventurelog.sh (+1 -4)

📄 Description

✍️ Description

The code creates a folder named adventurelog-backup. It then attempts to copy files from various nested directories, such as /adventurelog/backend/server/.env. However, this fails because the required intermediate folders are not created beforehand. Personally, I would simplify the approach by copying the entire parent directory instead. Alternatively, the code could be modified to explicitly create all necessary subdirectories before copying the files. At the end of the script, the entire backup-folder is deleted. So I don't see any harm in just taking a copy of the entire adventurelog directory.

🔗 Related PR / Issue

Link: #

✅ 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/6653 **Author:** [@ThomasDetemmerman](https://github.com/ThomasDetemmerman) **Created:** 8/8/2025 **Status:** ✅ Merged **Merged:** 8/9/2025 **Merged by:** [@michelroegl-brunner](https://github.com/michelroegl-brunner) **Base:** `main` ← **Head:** `patch-1` --- ### 📝 Commits (1) - [`d3995d4`](https://github.com/community-scripts/ProxmoxVE/commit/d3995d4f592faf40f6a0c92ca00a0468d64c612a) Improve backup of adventurelog folder ### 📊 Changes **1 file changed** (+1 additions, -4 deletions) <details> <summary>View changed files</summary> 📝 `ct/adventurelog.sh` (+1 -4) </details> ### 📄 Description ## ✍️ Description The code creates a folder named `adventurelog-backup`. It then attempts to copy files from various nested directories, such as `/adventurelog/backend/server/.env`. However, this fails because the required intermediate folders are not created beforehand. Personally, I would simplify the approach by copying the entire parent directory instead. Alternatively, the code could be modified to explicitly create all necessary subdirectories before copying the files. At the end of the script, the entire backup-folder is deleted. So I don't see any harm in just taking a copy of the entire adventurelog directory. ## 🔗 Related PR / Issue Link: # ## ✅ 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) - [x] 🐞 **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. --- <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:17:40 +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#6176
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?