Website rework #12764
Replies: 12 comments 38 replies
-
|
There's no URL in your post. The URL: https://community-scripts.github.io/ProxmoxVE/
|
Beta Was this translation helpful? Give feedback.
-
Beta Was this translation helpful? Give feedback.
-
|
Ah so that's the new website? I thought the current website was just being refactored. To avoid confusion, could you include it in the post? Edit: it has already been included now. |
Beta Was this translation helpful? Give feedback.
-
|
Maybe also include a redirect from https://community-scripts.github.io/ProxmoxVE/ to the new website. |
Beta Was this translation helpful? Give feedback.
-
|
at friday, we are working on some little things, then we switch this too. 😄 |
Beta Was this translation helpful? Give feedback.
-
|
First of all, huge respect to everyone involved in this project. The amount of work that goes into maintaining these scripts in your free time is genuinely impressive, and I use them regularly in my Proxmox setup. I'm missing some details on script pages - like the OS of the LXC container is no longer shown or the update script source / reference. Both of these were useful for quickly evaluating scripts before running them. Would be great to have them back. This may be subjective but for me it's actually more difficult to browse and find scripts compared to the old layout. For changes like this, a community feedback thread beforehand could help catch issues early and keep users in the loop. -- |
Beta Was this translation helpful? Give feedback.
-
|
only first view. |
Beta Was this translation helpful? Give feedback.
-
|
Wow, looking forward to it :) |
Beta Was this translation helpful? Give feedback.
-
Feedback welcome
|
Beta Was this translation helpful? Give feedback.
-
|
I'm also running into a lot of friction. I used to be able to click my bookmark and immediately see the latest scripts, now I'm met with loads of dead-space, huge filter buttons, the need to click an extra button and scroll to see what's new... [Expand] The wasted space worsens as recently viewed scripts increases
[Expand] The search function is off, in a few waysEntering `jellyfin` into the "Search scripts..." input in the header navigation returns a _limited to 5 results_ of various "arr" apps and Threadfin with no Jellyfin in sight. Despite my exceptions, pressing return/enter on this search term does not perform any action one would expect. Instead, for the expected search function, you must already be under the "All Scripts" page ( Some suggestions I would like to make:
[Expand] Visual example of above changes
I also added some bonus breathing space in the top nav for my narrow viewport
|
Beta Was this translation helpful? Give feedback.
-
|
hi @lichenophile, first off thank you so much. I went ahead and fixed most of the things you pointed out. The PR for this should be live somewhere this week.
|
Beta Was this translation helpful? Give feedback.
-
|
Seems to be down? Or it might just be me - I know Malwarebytes and other security tools are blocking the entire community-scripts domain since some of their subdomains were flagged for phishing... % curl -I -v https://community-scripts.org
|
Beta Was this translation helpful? Give feedback.
-
|
Works fine here. |
Beta Was this translation helpful? Give feedback.
-
|
Yes, it was Malwarebytes (web protection) on my end... just in case anyone else experiences this. Here's the full picture: The root cause is a blacklisted IP, not actually malicious content. The analytics.community-scripts.org subdomain resolved to IP 77.165.18.225, which was listed on the Spamhaus ZEN blocklist Because the community-scripts.org domain has a subdomain on a Spamhaus-listed IP, security tools that do broad domain The maintainers acknowledged they had "no clue what happened" and said they planned to migrate their Umami analytics TL;DR: Not a real threat — a Spamhaus hit on a shared-hosting IP dragged the whole domain's reputation down. Sources:
|
Beta Was this translation helpful? Give feedback.
-
|
This is a completely new VPS server hosted in Germany. I don't know how often they update the values, but apparently nothing is happening there. |
Beta Was this translation helpful? Give feedback.
-
|
It could be that the floating IP address was previously used by malware or a C&C, so perhaps it's still blacklisted at some services. But maybe not: https://www.abuseipdb.com/check/85.215.195.56 |
Beta Was this translation helpful? Give feedback.
-
|
Probably best to change this on your README.md to prevent confusion
Also I can get to helper-scripts.com, but I am directed to the community-scripts.com - and Malwarebytes is blocking it. |
Beta Was this translation helpful? Give feedback.
-
|
Looks great! |
Beta Was this translation helpful? Give feedback.
-
|
Really like the new site. Superb. One small suggestion. In the details box on a script page could you add a 1-click copy button to the config line, the same as you have on the script command itself. Save us having to highlight / right click / copy all the time. |
Beta Was this translation helpful? Give feedback.
-
Thank you for your feedback, appreciate it :)
|
Beta Was this translation helpful? Give feedback.
-
|
Brilliant, thank you |
Beta Was this translation helpful? Give feedback.
-
|
Could it be that the website is not up to date? I seem to be missing the NetBird LXC, Immich Frame LXC, etc. They are both marked as "In Development" on the new website. |
Beta Was this translation helpful? Give feedback.
-
|
Thanks for brining this up. During the last days we changed how the meta data system works and not all Github action where correctly in place. I corrected the issue directly in the database. When you notice anything else let us know pls! |
Beta Was this translation helpful? Give feedback.
-
|
I really appreciate the work that went into the redesign of the site. However, I personally found the previous design easier to use. In my opinion, the new layout feels a bit more cluttered and harder to navigate. Many elements appear much larger than before, which makes it harder to get a quick overview of the available scripts. The biggest usability issue for me is the navigation when opening a script. In the previous design, the menu on the left stayed visible while viewing a script, which made it very easy to switch to another one. In the new design, the left menu disappears when you open a script, so you always have to go back to the previous page to select a different script. Maybe it would be possible to keep the left navigation visible, or add a quick way to switch between scripts while viewing one. Just wanted to share some feedback from a usability perspective. Thanks for all the work that goes into maintaining this project! |
Beta Was this translation helpful? Give feedback.
-
|
First of all, congratulations on the new website and on all the work behind it. I really appreciate the work of the Helper Scripts community. What you have built is incredibly useful for a huge number of Proxmox users, and the credit for those scripts belongs entirely to the community and its maintainers. I maintain ProxMenux, a tool that helps users manage and automate many Proxmox tasks from a centralized menu. One of its features is a catalog that allows users to browse and launch Helper Scripts directly from within ProxMenux in a more guided way. The goal has never been to compete with Helper Scripts, but to complement them. Many users appreciate the convenience of running community scripts from inside ProxMenux, while still knowing that the scripts themselves come from your project. In fact, I always try to give clear credit to the source. For example, when users exit the Helper Scripts section in ProxMenux, they see a message inviting them to visit your website to discover more scripts and stay updated. The reason I am writing is because the recent website and metadata changes seem to have removed or changed the public JSON structure that I was using to build the Helper Scripts catalog inside ProxMenux. My workflow used that metadata to generate an index every few hours so the catalog could stay up to date. I completely understand that your architecture and website need to evolve. I was simply wondering if there might be a clean way for external tools like ProxMenux to consume the script metadata in the future. For example:
I would be happy to adapt ProxMenux to whatever format makes the most sense for your project. Thanks again for the excellent work you are doing for the Proxmox community. |
Beta Was this translation helpful? Give feedback.
-
|
Perfect, thank you. That makes sense. So the installer path is derived from the script type plus the slug. I will resolve the type mapping and adapt the ProxMenux catalog builder accordingly. Thanks again for the clarification. |
Beta Was this translation helpful? Give feedback.
-
Beta Was this translation helpful? Give feedback.
-
|
Perfect, thank you all very much. That clarifies it completely. I will adapt the ProxMenux catalog builder to derive the installer path from the script type and slug using that structure. I really appreciate your help and your openness with this integration. |
Beta Was this translation helpful? Give feedback.
-
install_methods and script_notes are depricated and will be deleted. Those are now json blob inline fields in script_scripts |
Beta Was this translation helpful? Give feedback.
-
Ok thank! |
Beta Was this translation helpful? Give feedback.
-
|
RSS does not show the latest scripts, but the ones that are in “In development.” |
Beta Was this translation helpful? Give feedback.
-
|
Is the source code of the new https://community-scripts.org site open source and available on GitHub? If yes, what repo is it in? |
Beta Was this translation helpful? Give feedback.
-
|
It is not (yet?, we dont know atm if we make it public) public, so no sourcecode to look at. |
Beta Was this translation helpful? Give feedback.
-
|
Is there any way to contribute to the website. |
Beta Was this translation helpful? Give feedback.
-
Not at this moment |
Beta Was this translation helpful? Give feedback.
-
|
Amazing work all! I also found the previous site easier for navigating just because of the persistent left side panel. The new site seem to be a huge step up in terms of one stop info. |
Beta Was this translation helpful? Give feedback.
Uh oh!
There was an error while loading. Please reload this page.
Uh oh!
There was an error while loading. Please reload this page.
-
We are happy to announce the New Proxmox VE Community Scripts Website!
The Proxmox ecosystem has always been driven by passionate homelab enthusiasts, system administrators, and open-source contributors. One of the most valuable resources to emerge from this community is the Proxmox VE Helper Scripts project — a large collection of automation scripts designed to simplify the setup and management of Proxmox environments.
To make these tools easier to discover and use, we’ve launched a new website:
Check it here!
This new platform serves as the central hub for browsing, learning about, and using the growing collection of Proxmox helper scripts.
What Are Proxmox VE Helper Scripts?
Proxmox VE Helper Scripts are a collection of community-created automation tools that streamline common tasks within a Proxmox Virtual Environment. These scripts automate the deployment and configuration of Linux containers (LXC), virtual machines (VMs), and system utilities, allowing users to quickly build complex environments with minimal manual setup.
Why a New Website?
As the project continued to grow, the need for a dedicated, easy-to-navigate platform became clear. The new website was built to provide:
The website highlights the full collection of scripts and makes it easier than ever to find and deploy the tools you need.
What You Can Find on the Website
The new site makes it simple to explore available scripts and quickly find what you need for your Proxmox setup.
URL: https://community-scripts.org/
Script Library
Browse a large collection of scripts designed for deploying services, containers, and virtual machines. These scripts cover a wide range of applications, from home automation and networking tools to development environments and monitoring platforms.
Quick Installation Commands
Each script includes a ready-to-run command that allows you to deploy a service directly from your Proxmox node with minimal setup.
Documentation and FAQs
The site also provides documentation and answers to common questions about installation methods, updates, and troubleshooting.
Community Integration
The project encourages participation through GitHub issues, discussions, and contributions. Developers can submit new scripts, improve documentation, or help test compatibility.
Built by the Community, for the Community
One of the greatest strengths of this project is that it remains entirely community-driven. The scripts are created, tested, and maintained by users who actively run Proxmox in their own environments.
This collaborative model ensures that the project continues to evolve alongside real-world use cases in homelabs, labs, and production environments.
Get Started
Explore the new website here:
Browse the available scripts, discover new tools, and contribute to the project if you'd like to help improve the Proxmox ecosystem.
Beta Was this translation helpful? Give feedback.
All reactions