https://github.com/tteck/Proxmox/discussions/4025 Skip to content Navigation Menu Toggle navigation Sign in * Product + GitHub Copilot Write better code with AI + Security Find and fix vulnerabilities + Actions Automate any workflow + Codespaces Instant dev environments + Issues Plan and track work + Code Review Manage code changes + Discussions Collaborate outside of code + Code Search Find more, search less Explore + All features + Documentation + GitHub Skills + Blog * Solutions By company size + Enterprises + Small and medium teams + Startups By use case + DevSecOps + DevOps + CI/CD + View all use cases By industry + Healthcare + Financial services + Manufacturing + Government + View all industries View all solutions * Resources Topics + AI + DevOps + Security + Software Development + View all Explore + Learning Pathways + White papers, Ebooks, Webinars + Customer Stories + Partners * Open Source + GitHub Sponsors Fund open source developers + The ReadME Project GitHub community articles Repositories + Topics + Trending + Collections * Enterprise + Enterprise platform AI-powered developer platform Available add-ons + Advanced Security Enterprise-grade security features + GitHub Copilot Enterprise-grade AI features + Premium Support Enterprise-grade 24/7 support * Pricing Search or jump to... Search code, repositories, users, issues, pull requests... Search [ ] Clear Search syntax tips Provide feedback We read every piece of feedback, and take your input very seriously. [ ] [ ] Include my email address so I can be contacted Cancel Submit feedback Saved searches Use saved searches to filter your results more quickly Name [ ] Query [ ] To see all available qualifiers, see our documentation. Cancel Create saved search Sign in Sign up Reseting focus You signed in with another tab or window. Reload to refresh your session. You signed out in another tab or window. Reload to refresh your session. You switched accounts on another tab or window. Reload to refresh your session. Dismiss alert {{ message }} tteck / Proxmox Public * * Notifications You must be signed in to change notification settings * Fork 2.3k * Star 14.1k * Code * Issues 0 * Pull requests 0 * Discussions * Actions * Security * Insights Additional navigation options * Code * Issues * Pull requests * Discussions * Actions * Security * Insights Moving forward #4025 tteck announced in Announcements Moving forward #4025 @tteck tteck Nov 1, 2024 * 12 comments * 43 replies Return to top Discussion options * {{title}} Something went wrong. Quote reply [213] tteck Nov 1, 2024 Maintainer - The community needs to unite and make some important decisions about the path forward. Has a new fork become the go-to choice? Is there a new frontend that we're rallying behind? This site will soon be archived, and time is limited. Let's make these decisions together. Beta Was this translation helpful? Give feedback. 36 You must be logged in to vote 18 [?] 46 All reactions * 18 * [?] 46 Replies: 12 comments * 43 replies * Oldest * Newest * Top Comment options * {{title}} Something went wrong. Quote reply [162] zenodotus280 Nov 1, 2024 - I just read your update on the other discussion - many thanks for your great work! Is there a fork of this project already? Which frontend are you referring to? I only access these scripts through GitHub directly. I hope there is someone who can bear the torch! Beta Was this translation helpful? Give feedback. 5 You must be logged in to vote All reactions 1 reply @BramSuurdje Comment options * {{title}} Something went wrong. Quote reply BramSuurdje Nov 1, 2024 - if you go to my github profile you will see a proxmox-helper-scripts repo. that is an alternative website that i have created. as for forks. to my understanding there and none as of right now Beta Was this translation helpful? Give feedback. 3 All reactions * 3 Comment options * {{title}} Something went wrong. Quote reply [328] XPGeek Nov 1, 2024 - Only recently discovered this, nothing productive to add, but a big thank you from the Internet ether. May life treat you as well as you have treated us, godspeed. Beta Was this translation helpful? Give feedback. 11 You must be logged in to vote All reactions 0 replies Comment options * {{title}} Something went wrong. Quote reply edited * {{editor}}'s edit {{actor}} deleted this content . {{editor}}'s edit Something went wrong. [478] MickLesk Nov 1, 2024 - How about transitioning to a community-driven project structure? Similar to the MagicMirror project, which began with one developer handling pull requests and evolved into a community-led effort, we could adopt a model where key contributors take on the responsibility of maintaining and developing the project together. This approach would create a structured environment, ensuring that the project remains active and evolves collaboratively. With the original site set to be archived soon, a community-driven model could offer both sustainability and continuity. I'd be willing to take on such a role, and I believe the other three active pull request contributors would be open to it as well. ( @havardthom @remz1337 @nicedevil007 ....) Beta Was this translation helpful? Give feedback. 13 You must be logged in to vote 29 All reactions * 29 13 replies Show 8 previous replies @MickLesk Comment options * {{title}} Something went wrong. Quote reply MickLesk Nov 1, 2024 - Sounds good, I hope this community-driven idea like @MickLesk suggested it comes alive. I like the idea with the 2/3 eye until merge principle. So will you @MickLesk fork/create an organsation? Yes, of course I can. But I'll wait and see (1-3 days) if there are any good ideas or similar :-) Beta Was this translation helpful? Give feedback. 4 All reactions * 4 @Mellowlynx Comment options * {{title}} Something went wrong. Quote reply Mellowlynx Nov 1, 2024 - I also think MickLesk is the one to manage the fork, as he is active. As stated before, I will haply moderate while learning. Beta Was this translation helpful? Give feedback. 3 All reactions * 3 @Aloe-recite Comment options * {{title}} Something went wrong. Quote reply Aloe-recite Nov 1, 2024 - @MickLesk great idea, as long as at least 3 trusted people manually approve of new stuff after thoroughly checking it out and act as community leads and arbitrators (not sure if I got the correct translation of the word I had in mind but yo got the idea), also to avoid the future development being stolen or the community used in a malicious way or who knows what. Such great and well known communities like this one are always at risk unfortunately and there has been plenty of drama in so many projects that one must be exceptionally careful now. Kudos to you for your dedication and commitment! Beta Was this translation helpful? Give feedback. All reactions @remz1337 Comment options * {{title}} Something went wrong. Quote reply remz1337 Nov 1, 2024 - @MickLesk yes I'd be happy to work with you to maintain this. Beta Was this translation helpful? Give feedback. 3 All reactions * 3 @jl-678 Comment options * {{title}} Something went wrong. Quote reply edited * {{editor}}'s edit {{actor}} deleted this content . {{editor}}'s edit Something went wrong. jl-678 Nov 1, 2024 - I have always been amazed at the scope of @tteck activities. Such amazing work! Do we consider assigning ownership of certain scripts to specific people to simplify maintenance and upgrades? Just a thought. It would also allow more people to contribute and "specialize" in certain areas. Beta Was this translation helpful? Give feedback. All reactions Comment options * {{title}} Something went wrong. Quote reply [213] tteck Nov 1, 2024 Maintainer Author - Always remember, safety first! Beta Was this translation helpful? Give feedback. 8 You must be logged in to vote 18 All reactions * 18 1 reply @Smile2Grow Comment options * {{title}} Something went wrong. Quote reply Smile2Grow Nov 1, 2024 - I also think that safety is one of, if not the most important topic. These scripts require real expertise. They cannot be developed using copy/paste. Even an AI cannot guarantee the aspect of secure development today or in the foreseeable future. Many people who use your scripts will probably have the need, but not the ability. The question is who can and wants to take responsibility for this? A second aspect for me would be the discussion of further development. I could imagine that getting into the subject and providing context are useful topics that could be conveyed on the website. Beta Was this translation helpful? Give feedback. 2 All reactions * 2 Comment options * {{title}} Something went wrong. Quote reply [783] BramSuurdje Nov 1, 2024 - I'm interested in stepping up as the front-end maintainer for this project. I've been responsible for maintaining a redesigned website of this project I developed for a school project, which I've updated and maintained over time. Github Repository: https://github.com/BramSuurdje/ proxmox-helper-scripts Beta Was this translation helpful? Give feedback. 8 You must be logged in to vote 7 4 [?] 4 All reactions * 7 * 4 * [?] 4 2 replies @deku-m Comment options * {{title}} Something went wrong. Quote reply deku-m Nov 1, 2024 - I wonder if we can also transfer helper-scripts.com domain or make new one and make your frontend to it eventually with all scripts. Continue the know legacy website of tteck and known URL. Credits go to both of you. What should we think of taking this over not only maintainers and contributers? Beta Was this translation helpful? Give feedback. All reactions @tteck Comment options * {{title}} Something went wrong. Quote reply tteck Nov 1, 2024 Maintainer Author - helper-scripts.com Expires: April 26, 2030 then it's up for grabs. Unless a sweat offer comes in. Beta Was this translation helpful? Give feedback. 10 All reactions * 10 Comment options * {{title}} Something went wrong. Quote reply [320] Zedris Nov 1, 2024 - just wanted to say @tteck. hat I had no idea of homelabbing or proxmox and have learned a ton spent many many nights learning and understanding your scripts and proxmox and overall have given me many many hours of happiness and joy. I truly hope all the best and love and know that you do touch peoples lives without knowing them or interacted directly with them. <3 Beta Was this translation helpful? Give feedback. 1 You must be logged in to vote [?] 7 All reactions * [?] 7 1 reply @kjkent Comment options * {{title}} Something went wrong. Quote reply kjkent Nov 1, 2024 - I wonder how many lives they've touched in some way solely through contributions here -- whether it be sparking hobbies, helping to develop career skills, helping people run their businesses, entertain their families, etc. Given the popularity of the project, and the array of uses that Proxmox has in the homelab and beyond, I reckon it's a laudable number. I hope the rest of the time they have here is peaceful. Beta Was this translation helpful? Give feedback. 1 All reactions * 1 Comment options * {{title}} Something went wrong. Quote reply [161] oerix Nov 1, 2024 - Instead of archiving, maybe having a few trusted contributors added to the project? Honestly speaking, I don't like the sound of forking the project, as it will just become abandonware. Beta Was this translation helpful? Give feedback. 1 You must be logged in to vote All reactions 7 replies Show 2 previous replies @Mellowlynx Comment options * {{title}} Something went wrong. Quote reply Mellowlynx Nov 1, 2024 - I think he is suggesting a fork, so his original can be archived in his name. Yes, transferring ownership is an option, but might later in however many years, erase his name over time. Archived, it will stay some sort of time capsule. I get both sides, and could not make this decision. Beta Was this translation helpful? Give feedback. All reactions @tteck Comment options * {{title}} Something went wrong. Quote reply tteck Nov 1, 2024 Maintainer Author - I know some contributors got frustrated with my insistence on coding things a certain way, but my goal was to make the code easier to understand and consistent, rather than requiring people to learn a new approach each time. Beta Was this translation helpful? Give feedback. 10 [?] 6 All reactions * 10 * [?] 6 @oerix Comment options * {{title}} Something went wrong. Quote reply oerix Nov 1, 2024 - I was the only person I truly trusted with this code. For this reason, the repository will be archived to preserve its integrity. Anyone wishing to continue the project will need to create a fork. I'm not sure how much of your time is limited, but maybe you can still manually approve new contributions when you have time? While, that being said, that will lead you to having built trust, which then you can gradually transfer ownership with your name still attached to the project. All in all, please do what's best for you, and I'd like to thank you for the great scripts and contributions you had kindly made available for us all. Beta Was this translation helpful? Give feedback. All reactions @tteck Comment options * {{title}} Something went wrong. Quote reply tteck Nov 1, 2024 Maintainer Author - I have very limited time left on earth. weeks Beta Was this translation helpful? Give feedback. 10 [?] 12 1 All reactions * 10 * [?] 12 * 1 @MickLesk Comment options * {{title}} Something went wrong. Quote reply MickLesk Nov 1, 2024 - @tteck It's hard for all of us to hear what you're going through right now. No one should have to face this, and I think I'm speaking for thousands of people when I say: thank you. You're a genius, and your scripts have made Proxmox so much more accessible for so many. Just over a year ago, Proxmox was nearly uncharted territory for me, but through your work, I discovered its true potential. I've grown so much because of it--more than even in my professional life--and I've found so many exciting new projects along the way. Sure, there were times we didn't always agree, but that only showed how passionate you are and how much this community means to you. We'll do everything we can to honor your legacy and keep reaching new people with the work you started. You've reached legendary status with us, and as long as Proxmox exists, your impact will never be forgotten. Beta Was this translation helpful? Give feedback. [?] 21 All reactions * [?] 21 Comment options * {{title}} Something went wrong. Quote reply [213] tteck Nov 1, 2024 Maintainer Author - Create a generic fork or clone e.g. https://github.com/helper-scripts /ProxmoxVE That gives the "helper-scripts" room to branch out if needed e.g. https://github.com/helper-scripts/next new thing Just a thought. It's yours to do with as you will, together. Beta Was this translation helpful? Give feedback. 6 You must be logged in to vote All reactions 16 replies Show 11 previous replies @judeibe Comment options * {{title}} Something went wrong. Quote reply judeibe Nov 1, 2024 - I like this, but wouldn't it be beneficial to make community-scripts an organization instead of a user. Beta Was this translation helpful? Give feedback. 1 All reactions * 1 @tteck Comment options * {{title}} Something went wrong. Quote reply tteck Nov 1, 2024 Maintainer Author - You may be correct, the team should look into this. Beta Was this translation helpful? Give feedback. All reactions @BramSuurdje Comment options * {{title}} Something went wrong. Quote reply BramSuurdje Nov 1, 2024 - agree w @judeibe. way better then an account Beta Was this translation helpful? Give feedback. All reactions @MickLesk Comment options * {{title}} Something went wrong. Quote reply MickLesk Nov 1, 2024 - Community-Scripts is now migrated to organisation, thx for feedback :-) Beta Was this translation helpful? Give feedback. 5 All reactions * 5 @SkilledAlpaca Comment options * {{title}} Something went wrong. Quote reply SkilledAlpaca Nov 1, 2024 - It seems that this is going to the new and dedicated fork or is there still a choice being made? Beta Was this translation helpful? Give feedback. All reactions Comment options * {{title}} Something went wrong. Quote reply [213] pmontgo33 Nov 1, 2024 - Can I ask that in whatever form this project continues, it be renamed tteck-scripts? You've touch so many during your time here, and I'm not sure thank you is enough. You've been in my thoughts since your announcement. Beta Was this translation helpful? Give feedback. 5 You must be logged in to vote [?] 3 All reactions * [?] 3 1 reply @tteck Comment options * {{title}} Something went wrong. Quote reply tteck Nov 1, 2024 Maintainer Author - Just continuing the work is enough. Beta Was this translation helpful? Give feedback. [?] 10 All reactions * [?] 10 Comment options * {{title}} Something went wrong. Quote reply [101] simonmcnair Nov 1, 2024 - I'm happy to host a site /moderate and/or do whatever. I'm just not great at writing bash. I understand it tho. I am happy to take on paying for helper-scripts so it can remain. Let me know. Beta Was this translation helpful? Give feedback. 1 You must be logged in to vote All reactions 0 replies Comment options * {{title}} Something went wrong. Quote reply edited * {{editor}}'s edit {{actor}} deleted this content . {{editor}}'s edit Something went wrong. [152] Outsmart2383 Nov 1, 2024 - tteck many thanks for your contribution. I am deeply saddened to read your latest update. I wish you the best. It feels wrong to be discussing the future of your helper scripts, but, that is the purpose of this thread. As someone who is an extreme novice I wanted to pose a few questions to the community: 1. What's the best way of verifying the safety of these scripts going forward? Let's pose the unlikely scenario that the "trusted members" become compromised. What steps can we take as individuals to check the code, if we can't analyse it effectively ourselves? I just pasted one of the scripts into ChatGPT and asked it to check for anything maliscous. As would be expected, it said it all looked okay, but is this a reliable? Could we create a custom GPT (or does one exist?) that can effectively scan a script for issues? 2. How are updates handled for instances that have been deployed by existing scripts? Can we continue simply updating our containers/ services using the existing update command, or, will we need to somehow configure a link to the new repo? Is the only risk to users when a new script is used to deploy a new service, or, could a bad actor also cause existing services that were set up with the scripts to be compromised also? Beta Was this translation helpful? Give feedback. 1 You must be logged in to vote All reactions 1 reply @Mellowlynx Comment options * {{title}} Something went wrong. Quote reply edited * {{editor}}'s edit {{actor}} deleted this content . {{editor}}'s edit Something went wrong. Mellowlynx Nov 1, 2024 - @Outsmart2383 1. The best way is to check a script before using it. There are multiple ways to include malicious code/payload, and preparing for everything is not possible. So before an update or new script is pushed, it should also be checked. (there are automated checks for this btw, but it will require a human check as well) The installation process uses reusable scripts: build.func, create_lxc.sh, and install.func. Changes to them should not happen often, and should also be extra checked, as that are used in all scripts. But it's up to all of us to test before pushing it to main branch for example and report strange findings. (Check the The XZ Utils Backdoor story, a sophisticated way of trying to add a backdoor in the code) 2. There will be a need for a local change, to update the script behind the update command to point to the new URL. Maybe this can be done with an update to the current install scripts if they also have the update function in them, or a separate wget command with a scrip that makes the changes. Another option is a one-liner that will update everything for you. This is something that needs to be checked and then made and deployed. Beta Was this translation helpful? Give feedback. 3 All reactions * 3 Comment options * {{title}} Something went wrong. Quote reply [162] wisie Nov 1, 2024 - Just want to say thanks for everything you've done. I check the change log far too often then I should admit as I'm always interested in what's recently been packaged. Wishing you all the best and thank you Beta Was this translation helpful? Give feedback. 1 You must be logged in to vote All reactions 0 replies Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment Category Announcements Labels None yet 23 participants @tteck @judeibe @Mellowlynx @XPGeek @nayzm @lslvxy @remz1337 @wisie @zenodotus280 @jl-678 @pmontgo33 @SkilledAlpaca @Smile2Grow @Zedris @deku-m @MickLesk @BramSuurdje @kjkent @CrazyWolf13 @simonmcnair @Outsmart2383 and others Heading Bold Italic Quote Code Link --------------------------------------------------------------------- Numbered list Unordered list Task list --------------------------------------------------------------------- Attach files Mention Reference Menu * Heading * Bold * Italic * Quote * Code * Link * * Numbered list * Unordered list * Task list * * Attach files * Mention * Reference Select a reply Loading Create a new saved reply 1 reacted with thumbs up emoji 1 reacted with thumbs down emoji 1 reacted with laugh emoji 1 reacted with hooray emoji 1 reacted with confused emoji [?] 1 reacted with heart emoji 1 reacted with rocket emoji 1 reacted with eyes emoji Footer (c) 2024 GitHub, Inc. Footer navigation * Terms * Privacy * Security * Status * Docs * Contact * Manage cookies * Do not share my personal information You can't perform that action at this time.