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

Support for multiple ports in default interface #1724

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

Originally created by @webysther on GitHub (Aug 16, 2025).

🌟 Briefly describe the feature

Today only the main port is show but some projects have many more

📝 Detailed description

Add like:

Default Interface(s):
label1: 80
label2: 443

Real Example:

Meilisearch

Default Interface(s):
                      server (tcp): 7700
                      ui (tcp): 24900


Jellyfin

Default Interface(s):
                      http (tcp): 8096
                      https (tcp): 8920
                      discovery (udp): 7359

💡 Why is this useful?

Sometimes some projects have really a good amount of ports

Originally created by @webysther on GitHub (Aug 16, 2025). ### 🌟 Briefly describe the feature Today only the main port is show but some projects have many more ### 📝 Detailed description Add like: ```txt Default Interface(s): label1: 80 label2: 443 Real Example: Meilisearch Default Interface(s): server (tcp): 7700 ui (tcp): 24900 Jellyfin Default Interface(s): http (tcp): 8096 https (tcp): 8920 discovery (udp): 7359 ``` ### 💡 Why is this useful? Sometimes some projects have really a good amount of ports
saavagebueno added the enhancement label 2025-11-20 05:15:33 -05:00
saavagebueno commented 2025-11-20 05:15:33 -05:00
Author
Owner
Copy Link

@MickLesk commented on GitHub (Aug 17, 2025):

And who is supposed to look after it? And understand it? That massively inflates everything. The main port of the application is completely sufficient.

I don't need the redis, API. PostgreSQL port in addition

@MickLesk commented on GitHub (Aug 17, 2025): And who is supposed to look after it? And understand it? That massively inflates everything. The main port of the application is completely sufficient. I don't need the redis, API. PostgreSQL port in addition
saavagebueno commented 2025-11-20 05:15:34 -05:00
Author
Owner
Copy Link

@webysther commented on GitHub (Aug 17, 2025):

And who is supposed to look after it? And understand it? That massively inflates everything. The main port of the application is completely sufficient.

I don't need the redis, API. PostgreSQL port in addition

For exposed ports I think is relevant, for internal ports inside the loopback of the LXC don't make sense.

I don't get about 'inflate everything', its about who will add this info for every script? I think this only need to be possible to people starting add the addittional ports.

@webysther commented on GitHub (Aug 17, 2025): > And who is supposed to look after it? And understand it? That massively inflates everything. The main port of the application is completely sufficient. > > I don't need the redis, API. PostgreSQL port in addition For exposed ports I think is relevant, for internal ports inside the loopback of the LXC don't make sense. I don't get about 'inflate everything', its about who will add this info for every script? I think this only need to be possible to people starting add the addittional ports.
saavagebueno commented 2025-11-20 05:15:34 -05:00
Author
Owner
Copy Link

@MickLesk commented on GitHub (Aug 17, 2025):

I find it absolutely unnecessary. But feel free to make a PR for it, I won't make one ^^

What does our frontend dev say? @BramSuurdje

@MickLesk commented on GitHub (Aug 17, 2025): I find it absolutely unnecessary. But feel free to make a PR for it, I won't make one ^^ What does our frontend dev say? @BramSuurdje
saavagebueno commented 2025-11-20 05:15:34 -05:00
Author
Owner
Copy Link

@webysther commented on GitHub (Aug 17, 2025):

I find it absolutely unnecessary. But feel free to make a PR for it, I won't make one ^^

What does our frontend dev say? @BramSuurdje

The community-scripts is absolutely unnecessary, we can do this with pain, wait? Also computers, just leave the cities and start making cheese from grass.

I get your point, why change if is perfect just for you(TM) :)

@webysther commented on GitHub (Aug 17, 2025): > I find it absolutely unnecessary. But feel free to make a PR for it, I won't make one ^^ > > What does our frontend dev say? [@BramSuurdje](https://github.com/BramSuurdje) The community-scripts is absolutely unnecessary, we can do this with pain, wait? Also computers, just leave the cities and start making cheese from grass. I get your point, why change if is perfect just for you(TM) :)
saavagebueno commented 2025-11-20 05:15:34 -05:00
Author
Owner
Copy Link

@tremor021 commented on GitHub (Aug 17, 2025):

Do you honestly expect us to track every single port every applications use? We have 367 scripts in our repo, i for one won't be tracking it.

The only port user cares about in 99,9% of use cases is the web UI port, if applicable. I have over 150 containers running accross multiple hosts and i never needed to know a single port other than web UI port.

Also, every suggestion you made so far is something YOU supposed to know. For the scripts all the stuff you asked for is irrelevant and requires work that noone really needs or wants...

The ports application uses, projects url, docs, etc.... This stuff you should know before you install the application or by reading the script.

We are not a release/app tracker

@tremor021 commented on GitHub (Aug 17, 2025): Do you honestly expect us to track every single port every applications use? We have 367 scripts in our repo, i for one won't be tracking it. The only port user cares about in 99,9% of use cases is the web UI port, if applicable. I have over 150 containers running accross multiple hosts and i never needed to know a single port other than web UI port. Also, every suggestion you made so far is something YOU supposed to know. For the scripts all the stuff you asked for is irrelevant and requires work that noone really needs or wants... The ports application uses, projects url, docs, etc.... This stuff you should know before you install the application or by reading the script. We are not a release/app tracker
saavagebueno commented 2025-11-20 05:15:34 -05:00
Author
Owner
Copy Link

@BramSuurdje commented on GitHub (Aug 17, 2025):

what @tremor021 said, if you really need more than just the UI port you can look at the relevant documentation about the project. most of the people just want to use the application

@BramSuurdje commented on GitHub (Aug 17, 2025): what @tremor021 said, if you really need more than just the UI port you can look at the relevant documentation about the project. most of the people just want to use the application
saavagebueno commented 2025-11-20 05:15:34 -05:00
Author
Owner
Copy Link

@CrazyWolf13 commented on GitHub (Aug 17, 2025):

Feel free to create a PR and maintain it, but I think 99.9% of the userbase does not care at all about that, and if someone really cares, a quick google search is probably still faster

@CrazyWolf13 commented on GitHub (Aug 17, 2025): Feel free to create a PR and maintain it, but I think 99.9% of the userbase does not care at all about that, and if someone really cares, a quick google search is probably still faster
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 enhancement
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#1724
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?