We’re in the process of revamping our beta program and have some exciting updates!
In addition to offering access to the latest Hudu build, we’re implementing a newsletter to keep our beta community better informed on updates and provide more opportunities for feedback and collaboration.
Participation in the beta program is completely voluntary. How much you engage with Hudu via the beta program is also voluntary. Ideally, we are looking for users who are willing to provide constructive feedback on new features and are okay with finding bugs. If you just want to have access to the beta version of Hudu, that’s okay too.
How it works:
Interested users can sign up for the beta newsletter here. By signing up, you’ll receive email updates ahead of each new beta release outlining:
- What is included in the update (think release notes but much more narrow in scope and much more detailed).
- How to submit bugs.
- How to share feedback.
Some important things to note:
- There will be bugs. If bugs or performance issues are a deal breaker for your instance, the beta program may not be a good fit.
- Features can change in both appearance and functionality prior to official release.
- This is a new initiative for us. We appreciate your patience as we work to improve and grow the beta program over time.
If this sounds like something you’re interested in, please click here to sign up for the beta newsletter!
FAQ
Q: Why should I sign up for the newsletter?
A: Signing up for our beta program newsletter is the best way to stay informed of products updates and gives you the opportunity to provide feedback on beta features.
Q: Do I have to sign up for the emails to get the beta version?
A: No. We have an open beta program that allows any self-hosted user to gain access to the beta version of the Hudu web platform. You can get the beta version of Hudu without getting the newsletter, but you’ll get more out of the beta program if you opt in to the newsletter too.
Q: What about the mobile app?
A: At this time, our beta program does not include the mobile app. We hope to expand the program to include the mobile app in the future.
Q: What about the Hudu extension and Hudu Assist?
A: Enabling beta updates for your web platform does not translate to beta updates for the Hudu extension. However, if you are a Hudu extension and/or Assist user, we encourage you to sign up for the beta program newsletter, as we plan to share beta versions of the extension and Assist with beta testers on an individual basis.
Q: I want to participate in the beta program but I am not self-hosted; what do I do?
A: At this time, the Hudu beta build is available to self-hosted users only. If you are not-self hosted but are interested in testing beta versions of the Hudu mobile app and/or extension, please sign up for the beta program newsletter so you’ll be notified of opportunities to do so.
Q: How is this different from contacting the Hudu support team with bugs and feedback?
A: The beta program will focus on specific areas and features of Hudu, not the Hudu platform as a whole. With each beta release, we’ll share specifics on the beta feature you should be trying out and how to submit bugs/feedback on it. The Hudu support team will continue to help troubleshoot and answer questions regarding the production build of Hudu. If you are using the beta version of Hudu and happen to find a bug that doesn’t have anything to do with a beta feature, you should contact the Hudu support team like usual.
Q: How do I install the beta version?
A: Run:
1. Take a backup of the server
2. cd ~/hudu2
3. sudo docker-compose down
4. Edit the docker-compose.yml file and change BOTH occurrences of hududocker/hudu:latest to hududocker/hudubeta:latest
5. Run sudo docker-compose pull
6. Run sudo docker-compose up -d
1. Take a backup of the server
2. cd ~/hudu2
3. sudo docker-compose down
4. Edit the docker-compose.yml file and change BOTH occurrences of hududocker/hudu:latest to hududocker/hudubeta:latest
5. Run sudo docker-compose pull
6. Run sudo docker-compose up -d
Q: How do I uninstall the beta version?
A: Change lines to "latest" then run "sudo docker compose down && sudo docker compose pull" then "sudo docker compose up -d" where your env and yml file are.