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 13 Packages Projects Releases 10 Wiki Activity

Scripts intended for direct LXC install not documented correctly #169

New Issue
Closed
opened 2026-02-04 16:56:56 +03:00 by OVERLORD · 5 comments
OVERLORD commented 2026-02-04 16:56:56 +03:00
Owner
Copy Link

Originally created by @di5cord20 on GitHub (Dec 13, 2024).

Originally assigned to: @BramSuurdje on GitHub.

Please verify that you have read and understood the guidelines.

yes

What type of issue is this?

Bug

A clear and concise description of the issue.

I noticed that scripts that are meant to be run directly in the LXC console are not stating as such on the web.

Current:
To create a new Proxmox VE VS Code Server , run the command below in the Proxmox VE Shell.

Change to:
To create a new Proxmox VE VS Code Server , run the command below in the LXC console.

Which browser are you using?

Chrome

If relevant, including screenshots or a code block can be helpful in clarifying the issue.

No response

Please provide detailed steps to reproduce the issue.

No response

Originally created by @di5cord20 on GitHub (Dec 13, 2024). Originally assigned to: @BramSuurdje on GitHub. ### Please verify that you have read and understood the guidelines. yes ### What type of issue is this? Bug ### A clear and concise description of the issue. I noticed that scripts that are meant to be run directly in the LXC console are not stating as such on the web. Current: To create a new Proxmox VE VS Code Server , run the command below in the Proxmox VE Shell. Change to: To create a new Proxmox VE VS Code Server , run the command below in the LXC console. ### Which browser are you using? Chrome ### If relevant, including screenshots or a code block can be helpful in clarifying the issue. _No response_ ### Please provide detailed steps to reproduce the issue. _No response_
OVERLORD added the website label 2026-02-04 16:56:56 +03:00
OVERLORD commented 2026-02-04 16:57:00 +03:00
Author
Owner
Copy Link

@MickLesk commented on GitHub (Dec 13, 2024):

Which ones are you talking about? It's in the VS Code. I just did a bigger PR. https://github.com/community-scripts/ProxmoxVE/pull/812

@MickLesk commented on GitHub (Dec 13, 2024): Which ones are you talking about? It's in the VS Code. I just did a bigger PR. https://github.com/community-scripts/ProxmoxVE/pull/812
OVERLORD commented 2026-02-04 16:57:08 +03:00
Author
Owner
Copy Link

@di5cord20 commented on GitHub (Dec 13, 2024):

When I view the website, I see this:
Screenshot from 2024-12-13 08-58-06

Not sure why that happens, as I see the below in the JSON code:
8c1b48453c/json/code-server.json (L35)

This applies to other scripts like File Browser, Tailscale, and likely others.

@di5cord20 commented on GitHub (Dec 13, 2024): When I view the website, I see this: ![Screenshot from 2024-12-13 08-58-06](https://github.com/user-attachments/assets/9b92ea5a-43ec-4b7a-95a3-4e2324816256) Not sure why that happens, as I see the below in the JSON code: https://github.com/community-scripts/ProxmoxVE/blob/8c1b48453ca91b9c9ca43b52db8d2e62eba02b47/json/code-server.json#L35 This applies to other scripts like File Browser, Tailscale, and likely others.
OVERLORD commented 2026-02-04 16:57:12 +03:00
Author
Owner
Copy Link

@MickLesk commented on GitHub (Dec 13, 2024):

That Execute within an existing LXC Console stands above.
image

@BramSuurdje any idea for this "To create a new Proxmox VE VS Code Server , run the command below in the Proxmox VE Shell." ?

@MickLesk commented on GitHub (Dec 13, 2024): That Execute within an existing LXC Console stands above. ![image](https://github.com/user-attachments/assets/5045b688-b55a-4a5a-ad50-6beca41b66e2) @BramSuurdje any idea for this "To create a new Proxmox VE VS Code Server , run the command below in the Proxmox VE Shell." ?
OVERLORD commented 2026-02-04 16:57:17 +03:00
Author
Owner
Copy Link

@BramSuurdje commented on GitHub (Dec 29, 2024):

To fix this would require some additional work. Currently, all it does is check the file path, determine if it is "ct/vm" or "misc," and base the text on that.

@BramSuurdje commented on GitHub (Dec 29, 2024): To fix this would require some additional work. Currently, all it does is check the file path, determine if it is "ct/vm" or "misc," and base the text on that.
OVERLORD commented 2026-02-04 16:57:18 +03:00
Author
Owner
Copy Link

@MickLesk commented on GitHub (Jan 3, 2025):

Actually Not Planned. Ive set it into on Hold and Take a notice about it

@MickLesk commented on GitHub (Jan 3, 2025): Actually Not Planned. Ive set it into on Hold and Take a notice about it
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 website
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#169
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?