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 #1622] [CLOSED] New Script: Synology VM #3122

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

📋 Pull Request Information

Original PR: https://github.com/community-scripts/ProxmoxVE/pull/1622
Author: @tim104979
Created: 1/20/2025
Status: ❌ Closed

Base: main ← Head: main

📝 Commits (10+)

  • 8e3cded Add files via upload
  • b6430e0 Merge pull request #1 from tim104979/Synology-VM-Script
  • c3e49e5 Add files via upload
  • 12a9a7b Add files via upload
  • b029367 Delete Synology-VM-Install.sh
  • 799ee9a Delete SynologyVM.json
  • 0ad44b5 Update and rename SynologyVM.json to Synologyvm.json
  • 894f6a9 Update Synologyvm.json
  • 0b4f0da Update and rename Synology-VM-Install.sh to synology-vm.sh
  • 535c967 Update synology-vm.sh

📊 Changes

2 files changed (+454 additions, -0 deletions)

View changed files

➕ json/synology-vm.json (+34 -0)
➕ vm/synology-vm.sh (+420 -0)

📄 Description

✍️ Description

Tested on my own proxmox EV worked great!

  • Related Issue: #
  • Related PR: #
  • Related Discussion: #

✅ 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.)

🛠️ 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)

📋 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/1622 **Author:** [@tim104979](https://github.com/tim104979) **Created:** 1/20/2025 **Status:** ❌ Closed **Base:** `main` ← **Head:** `main` --- ### 📝 Commits (10+) - [`8e3cded`](https://github.com/community-scripts/ProxmoxVE/commit/8e3cded5a88c1e4b01110755950ca9eaec7e2420) Add files via upload - [`b6430e0`](https://github.com/community-scripts/ProxmoxVE/commit/b6430e053697ce0cacba56546557e5cf43ba3a48) Merge pull request #1 from tim104979/Synology-VM-Script - [`c3e49e5`](https://github.com/community-scripts/ProxmoxVE/commit/c3e49e5bef540886ae603739c9d2a81dd394ffb1) Add files via upload - [`12a9a7b`](https://github.com/community-scripts/ProxmoxVE/commit/12a9a7be79752fcfeaea556c8cdfb1e29a43bce5) Add files via upload - [`b029367`](https://github.com/community-scripts/ProxmoxVE/commit/b029367a2d6092878d6f19ba5bb7639cf69ab38f) Delete Synology-VM-Install.sh - [`799ee9a`](https://github.com/community-scripts/ProxmoxVE/commit/799ee9af3c26f581fa65c77906a534a7c8318d24) Delete SynologyVM.json - [`0ad44b5`](https://github.com/community-scripts/ProxmoxVE/commit/0ad44b522d11f77df6d4e1f296cbee638706e17b) Update and rename SynologyVM.json to Synologyvm.json - [`894f6a9`](https://github.com/community-scripts/ProxmoxVE/commit/894f6a9f8e1682e649fb22d87215b3be42f262da) Update Synologyvm.json - [`0b4f0da`](https://github.com/community-scripts/ProxmoxVE/commit/0b4f0dad1bad369a356cb78028e115f8558e530f) Update and rename Synology-VM-Install.sh to synology-vm.sh - [`535c967`](https://github.com/community-scripts/ProxmoxVE/commit/535c96781cb3f3dfe5d9350396c4e288be7c9298) Update synology-vm.sh ### 📊 Changes **2 files changed** (+454 additions, -0 deletions) <details> <summary>View changed files</summary> ➕ `json/synology-vm.json` (+34 -0) ➕ `vm/synology-vm.sh` (+420 -0) </details> ### 📄 Description ## ✍️ Description Tested on my own proxmox EV worked great! - - - - Related Issue: # - Related PR: # - Related Discussion: # - - - ## ✅ 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.) ## 🛠️ 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) - [x] New script (a fully functional and thoroughly tested script or set of scripts) --- ## 📋 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:33:32 -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#3122
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?