SVI/ProxmoxVE
1
0
Fork 0
mirror of https://github.com/community-scripts/ProxmoxVE.git synced 2026-07-23 22:33:39 -04:00
Code Issues 2.6k Packages Projects Releases 10 Wiki Activity

Homepage Dashboard release branch #247

New Issue
Closed
opened 2025-11-20 04:45:39 -05:00 by saavagebueno · 10 comments
saavagebueno commented 2025-11-20 04:45:39 -05:00
Owner
Copy Link

Originally created by @pafade89 on GitHub (Dec 28, 2024).

✅ Have you read and understood the above guidelines?

Yes

📜 What is the name of the script you are using?

Homepage Dashboard

📂 What was the exact command used to execute the script?

bash -c "$(wget -qLO - https://github.com/community-scripts/ProxmoxVE/raw/main/ct/homepage.sh)"

📝 Provide a clear and concise description of the issue.

I think it make sense not to use the dev branch but instead ne single releases. Also an benefit is that after switching the branch tbe version is shown correct in the right corner of homepage.

⚙️ What settings are you using?

  • Default Settings
  • Advanced Settings

🖥️ Which Linux distribution are you using?

Debian 12

🔄 Steps to reproduce the issue.

No version in the right low corner ;)

❌ Paste the full error output (if available).

No errors

🖼️ Additional context (optional).

No response

Originally created by @pafade89 on GitHub (Dec 28, 2024). ### ✅ Have you read and understood the above guidelines? Yes ### 📜 What is the name of the script you are using? Homepage Dashboard ### 📂 What was the exact command used to execute the script? bash -c "$(wget -qLO - https://github.com/community-scripts/ProxmoxVE/raw/main/ct/homepage.sh)" ### 📝 Provide a clear and concise description of the issue. I think it make sense not to use the dev branch but instead ne single releases. Also an benefit is that after switching the branch tbe version is shown correct in the right corner of homepage. ### ⚙️ What settings are you using? - [X] Default Settings - [ ] Advanced Settings ### 🖥️ Which Linux distribution are you using? Debian 12 ### 🔄 Steps to reproduce the issue. No version in the right low corner ;) ### ❌ Paste the full error output (if available). No errors ### 🖼️ Additional context (optional). _No response_
saavagebueno commented 2025-11-20 04:45:40 -05:00
Author
Owner
Copy Link

@se-bastiaan commented on GitHub (Dec 29, 2024):

If I read your issue correctly, you are proposing the use of homepage releases instead of pulling from the dev branch. Is that correct?

The script currently looks at the latest release on GitHub and then downloads the attached zip file. So I would say that what you want is already how it works.

To show the version of homepage in the UI the correct environment variables need to be set like
NEXT_PUBLIC_VERSION=$RELEASE NEXT_PUBLIC_REVISION='source' pnpm run build

In their own build pipeline for Docker these are derived from the metadata action, which takes it from the Git tag.

@se-bastiaan commented on GitHub (Dec 29, 2024): If I read your issue correctly, you are proposing the use of homepage releases instead of pulling from the dev branch. Is that correct? The script currently looks at the latest release on GitHub and then downloads the attached zip file. So I would say that what you want is already how it works. To show the version of homepage in the UI the correct environment variables need to be set like `NEXT_PUBLIC_VERSION=$RELEASE NEXT_PUBLIC_REVISION='source' pnpm run build` In their own build pipeline for Docker these are derived from the metadata action, which takes it from the Git tag.
saavagebueno commented 2025-11-20 04:45:40 -05:00
Author
Owner
Copy Link

@pafade89 commented on GitHub (Dec 30, 2024):

Thank you for your fast response. When I use your command the following version indicator is now shown:

image

@pafade89 commented on GitHub (Dec 30, 2024): Thank you for your fast response. When I use your command the following version indicator is now shown: ![image](https://github.com/user-attachments/assets/13fceb36-c14c-4213-bbc7-3c7debf9082e)
saavagebueno commented 2025-11-20 04:45:40 -05:00
Author
Owner
Copy Link

@se-bastiaan commented on GitHub (Dec 30, 2024):

Yes I meant that the script needs to be adjusted to set the version. If you want to set it to a specific version with the application already installed you should set NEXT_PUBLIC_VERSION=v0.10.6

@se-bastiaan commented on GitHub (Dec 30, 2024): Yes I meant that the script needs to be adjusted to set the version. If you want to set it to a specific version with the application already installed you should set `NEXT_PUBLIC_VERSION=v0.10.6`
saavagebueno commented 2025-11-20 04:45:41 -05:00
Author
Owner
Copy Link

@pafade89 commented on GitHub (Dec 30, 2024):

@se-bastiaan Thank you very much for #1107 =)

@pafade89 commented on GitHub (Dec 30, 2024): @se-bastiaan Thank you very much for #1107 =)
saavagebueno commented 2025-11-20 04:45:41 -05:00
Author
Owner
Copy Link

@se-bastiaan commented on GitHub (Dec 31, 2024):

could we reopen this?

@se-bastiaan commented on GitHub (Dec 31, 2024): could we reopen this?
saavagebueno commented 2025-11-20 04:45:41 -05:00
Author
Owner
Copy Link

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

yep

@MickLesk commented on GitHub (Dec 31, 2024): yep
saavagebueno commented 2025-11-20 04:45:41 -05:00
Author
Owner
Copy Link

@pafade89 commented on GitHub (Jan 1, 2025):

It still doesn't seem to be working properly.

Screenshot_2025-01-01-12-56-28-323_com.android.chrome-edit.jpg

@MickLesk can you reopen?

@pafade89 commented on GitHub (Jan 1, 2025): It still doesn't seem to be working properly. ![Screenshot_2025-01-01-12-56-28-323_com.android.chrome-edit.jpg](https://github.com/user-attachments/assets/061fb6b1-fc9c-4c77-8047-4034abdc4af4) @MickLesk can you reopen?
saavagebueno commented 2025-11-20 04:45:41 -05:00
Author
Owner
Copy Link

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

New PR needed only

@MickLesk commented on GitHub (Jan 1, 2025): New PR needed only
saavagebueno commented 2025-11-20 04:45:42 -05:00
Author
Owner
Copy Link

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

Please Test the new merge in 10-15min again and give Feedback

@MickLesk commented on GitHub (Jan 1, 2025): Please Test the new merge in 10-15min again and give Feedback
saavagebueno commented 2025-11-20 04:45:42 -05:00
Author
Owner
Copy Link

@pafade89 commented on GitHub (Jan 1, 2025):

For me, it works now perfectly. =)

image

@pafade89 commented on GitHub (Jan 1, 2025): For me, it works now perfectly. =) ![image](https://github.com/user-attachments/assets/a5dabc27-4a27-4244-bba5-194238f774a4)
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
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#247
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?