jonp

We moved the blog to the docs site. I'll chat with @csmanel about getting RSS support for it.

You nailed it! We are loving playwright.

I fixed it that night. We migrated all the previous blog posts to the doc site as well as updated the link to it from the home page.

Kudos to the entire team for their hard work on this. Proper testing is a key component of our focus on delivering an excellent user experience and will continue to be integral to our mission. Great work to all involved!

One interesting thing is I was actually his software support contact behind the scenes (previous job) and helped him a lot with the multi seat gaming videos starting with 2 gamers 1 cpu but especially the 7 gamers one with the custom water block for the AMD cards. I had him setup remote access including a webcam that was pointed at all the monitors on the ground so I could see them light up for gpu pass through. Was a helluva project!!

This is actually something we intend to do using vfio stubbing if that's what you're referring to here. VMs are a 2026 objective for us.

Hi there and welcome! What apps and services do you think you'll be running and how many users? What about total storage needs? Have you already purchased the gear or not quite yet? Depending on your specific needs, there may be options to go with that would be less power draw and less noise too. Not sure if that's a factor you want to consider.

@mill3000 can you take care of this gentlemen's request? Thank you!

Agreed. Thread has run it's course.

Fyi, Q3 update went live today along with a new docs site: docs.hexos.com We are listening to you guys!

Hey all. Q3 update coming Monday. Bunch of other goodies and content with it.

Fair point. We are planning to update the site for end of year with more content and details. I'll make sure this gets addressed. There are three types of issues that can exist for a given app: issues with the app itself (responsibility of the app developer), issues with the TrueNAS-cataloged container (responsibility of TrueNAS), and issues with the app curation itself (responsibility of HexOS). For issues with the app, if we can clearly identify the problem, we have no problem carrying the torch up to the app author to get proper visibility if required. For issues with the cataloged app in TrueNAS, we can escalate to TrueNAS directly for intervention if we can identify the root cause properly. For issues with the curation, we can quickly modify our curation using the new system to push out a fixes. We also will have a new docs site that will launch with the Q3 update explaining out the curation system works and how others can participate to help us fast-track the curation of other apps while we continue to work on core features.

We officially announced our intention to delay VM support as part of the Q1 status update back in March. Since then, its important to note that TrueNAS pivoted their VM strategy again when they decided to drop Incus for traditional VMs and go back to their previous implementation with libvirt (as of 25.04.2). Due to all of this, we decided it would be best to restart the VM implementation in 2026 once development is finalized. I can see the confusion here, but we never promised all of these features would be delivered with the 1.0 release. Our focus on 1.0 is achieving platform stability. Furthermore, you're forgetting one pretty major feature that wasn't listed on the site: Local UI. This is the next feature we are focusing on after the Q3 release. Snapshots and Buddy Backups are still possibilities for this year, but likely would continue to carry the "beta" tag into 2026 to give more time for public testing. The Q3 update is nearly complete, which will carry some pretty big features including MULTIPLE new curated apps and folder support for Apple Time Machine/Quotas. Furthermore, we will have a new "Experimental Features" toggle that will enable users to create Encrypted folders as well as provide access to our new app templating/install scripts solution.

So actually we do want to have an official discord (in fact, we already have it "parked" so-to-speak), but we want to wait to roll it out when we can be more prepared to manage it. Our team is entirely revving on dev cycles right now and adding comms platforms to manage to an already thinly spread set of resources is only going to overwhelm and delay development. Bottom line is that I'm all we've got for official comms right now and I'm spread insanely thin at the moment. I really want to hire someone to take over communications for me, but the timing for that is more likely Q4 or even Q1 2026.

I dig tunnels 😉