Version 1 plans #12
MydsiIversen
announced in
Announcements
Replies: 0 comments
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Uh oh!
There was an error while loading. Please reload this page.
-
Hello everyone!
First off, I just want to say a huge thank you for all the interest and excitement surrounding this project. It's truly amazing to see such a vibrant and engaged community growing around it. I’m beyond grateful for your support!
I wanted to take a moment to share my plans for the upcoming releases and the future of this project. Here's a breakdown of what you can expect in the next few weeks:
Upcoming Features:
I'm currently in the process of applying for GitHub Sponsorships, so if you’d like to support me and my work, that would be greatly appreciated—but absolutely not required! Regardless, I’m committed to continuing this project because I believe it addresses a critical need.
Ongoing Work:
I also have a separate project in the works—a full automation suite for Proxmox. This allows you to auto-provision VyOS and generate configurations from a GUI that can be applied with just one command. While still experimental, I’ve managed to successfully run tests for versions 1.4 and 1.5 in about 10-15 seconds per machine. This progress will really speed up development!
Version 1 Release:
Along with the automation suite and the features mentioned above, I’m planning to release a wiki with my testing configurations. It’ll serve as a community-driven resource to establish a “correct solution” as we move forward. As the project grows, it can get tricky to determine what’s the best approach, so having community input will be invaluable!
Version 2 Vision:
For version 2, I’m aiming for complete configurability. This will be a significant challenge, but it's something I’m excited to tackle. I expect to have this completed by May (though my exam schedule may slightly affect progress). This update won’t just focus on configuration changes—it will also feature a commit audit system, where every commit gathers key information, highlights differences, and potentially uses AI to point out where things may have gone wrong. This proactive approach to issue detection and log gathering will really enhance the overall experience!
Call to action!!!
Once again, thank you all for the incredible interest and support! The response has exceeded my expectations, and I couldn’t be more excited about what’s to come.
If anyone here has expertise in quality control, bug finding, or testing methodology, I’d love to connect. I want to set a high standard for this project from the start, and your help would be invaluable.
Thank you again, and let’s keep building something amazing together!
Beta Was this translation helpful? Give feedback.
All reactions