starred/ProxmoxVE
1
0
Fork 0
mirror of https://github.com/community-scripts/ProxmoxVE.git synced 2026-02-05 00:29:55 +03:00
Code Issues 11 Packages Projects Releases 10 Wiki Activity

Allow specifying external services (S3, database, cache) during installation to skip auto-deployment. #776

New Issue
Closed
opened 2026-02-04 21:24:45 +03:00 by OVERLORD · 1 comment
OVERLORD commented 2026-02-04 21:24:45 +03:00
Owner
Copy Link

Originally created by @schneider-de-com on GitHub (Apr 8, 2025).

🌟 Briefly describe the feature

Allow specifying external services (S3, database, cache) during installation to skip auto-deployment.

📝 Detailed description

Currently, services like S3-compatible storage, databases (e.g., PostgreSQL), and caching systems (e.g., Redis) are automatically deployed as part of the installation process. This limits flexibility for users who already operate these components in their infrastructure.

I would like to be able to specify during installation (e.g., via configuration files or prompt) that these services should not be installed, and instead provide connection details for external equivalents.

💡 Why is this useful?

  • Enables integration with existing infrastructure
  • Avoids deploying unnecessary components, saving resources
  • Increases adoption potential for users in more complex
Originally created by @schneider-de-com on GitHub (Apr 8, 2025). ### 🌟 Briefly describe the feature Allow specifying external services (S3, database, cache) during installation to skip auto-deployment. ### 📝 Detailed description Currently, services like S3-compatible storage, databases (e.g., PostgreSQL), and caching systems (e.g., Redis) are automatically deployed as part of the installation process. This limits flexibility for users who already operate these components in their infrastructure. I would like to be able to specify during installation (e.g., via configuration files or prompt) that these services should not be installed, and instead provide connection details for external equivalents. ### 💡 Why is this useful? - Enables integration with existing infrastructure - Avoids deploying unnecessary components, saving resources - Increases adoption potential for users in more complex
OVERLORD added the enhancement label 2026-02-04 21:24:45 +03:00
OVERLORD commented 2026-02-04 21:24:54 +03:00
Author
Owner
Copy Link

@MickLesk commented on GitHub (Apr 8, 2025):

Break all Scripts. Bloat all Scripts. Simple: No.

The user can remove and customize it himself afterwards. I don't want 400 lines of scripts to include any exceptions and whiptails so that users can connect any third-party systems.

@MickLesk commented on GitHub (Apr 8, 2025): Break all Scripts. Bloat all Scripts. Simple: No. The user can remove and customize it himself afterwards. I don't want 400 lines of scripts to include any exceptions and whiptails so that users can connect any third-party systems.
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 enhancement
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#776
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?