jonp

SCALE updates are designed to persist all HexOS customizations, regardless of how they are applied (SCALE UI update or through our HexOS UI in the future). We still would prefer customers to stay in lockstep with our update method to ensure the best support.

Liking a lot of these ideas. Completely agree. However, I think we need to think about this deeper. I don't like the idea of these guides living in a forum where the help link in the UI redirects the user here. I think the content needs to be either presentable in a frame on our UI or linkable to an article on our docs. @Magnus may have some ideas on this. He's our creative director and responsible for UI/UX design. I love this. 100% great ideas. Absolutely doable. Could even integrate that into the product UI. So I think we could make a lot of that contextual. And then you have two ways of accessing the information: Traditional Docs: menu based nav as suggested by @Theo ; accessible via the hub UI help links: contextual links relevant to where the user is looking; accessible via the deck But both should be the same docs.

Working as intended. 😉

It's arguments like these that just hit me right in the gut. Such a basic, but perfect argument. Ugh. I'll see what we can do. No promises and definitely not for 1.0.

Hmm...might know a guy... 😉

Do you guys think they should just have their own forum or do you think we should create articles based on these? Very open to supporting this.

Ooh! That's a great idea!! Multi folder settings modifications. Saving this one!

Yup! We went through great pains to make our UI mobile responsive, and this will make porting it to mobile apps easier in the future. For now, navigating to the deck from mobile is already a pretty pleasant experience.

We went with IPS because we had familiarity with the platform and knew there were a number of features we wanted to deploy. Xenforo, discourse, and a bunch of other options are great too, but I don't believe I've found a forum "king" just yet. It really comes down to what you want to use it to do and right now, we are using a lot of features. That said, I couldn't agree more about the search option being too hidden. We will be updating that in the future.

lol! I love that you guys love the forums and I will definitely look into this, but priority right now is 100% focused on getting the beta roll out complete. Then we can breathe and make all sorts of fun forum improvements!! PRIORITIES PEOPLE!! 😉

Mostly right. So the UI/UX will update at a much faster pace during beta as we catch up to the underlying capabilities of TrueNAS SCALE. So a single TNS release such as 24.10 can actually carry us quite a ways before we need an underlying OS update. We're already starting to align though. We specifically choose 24.10 so we could focus on Docker and RAIDz expansion as early features. We're already eyeballing specific features in Fangtooth (25.04) for proper inclusion in HexOS. Furthermore, we really don't want users updating HexOS through the TrueNAS SCALE UI. We are going to be more reserved about pushing updates for new releases and wait primarily for TrueNAS .1 releases after their main releases for future updates. That is the one of the reasons HexOS is still in beta right now. 24.10 is stable, but 24.10.1 is the bugfix/hotfix release that comes after and that cadence is followed for all TrueNAS development cycles. We believe this is a better path for customers. Security updates will follow with proper cadence because again, the build's are being produced by iXsystems. This is all a function of our "Powered by TrueNAS" partnership. THAT said, we will have "beta" tracks potentially after 1.0 for HexOS where users will be on a .0 release (possibly even beta or RC), so you can test a new feature. Hefty warnings will be provided for anyone treading this path, so unless you have test gear, we won't encourage this. But for those that want to see the future a little early and help us test it out, you'll be on the inside track ;-).

Yes. We will have additional language support. If you're interested in participating, please email us at support@hexos.com with your interest.

bingo

Send an email to support@hexos.com and we'll get you squared away. By sure to do that from the email you used to register/purchase.

No docs just yet. Honestly the software is pretty self-explanatory and where its not, that's a bug ;-). Eventually I can see us creating guides for special use-cases / advanced user needs, but realistically we're trying to build this thing where docs are mostly unnecessary once you're in the UI. Lofty goal? Yes. But it's a good one! The exception to that will be app-specific setup guides which I think make sense for us to curate along with the app containers themselves.

On the to-do list. We will be doing this.

We refunded your purchase on Thursday December 5th. It takes 5-7 business days to process, but we didn't do a great job of communicating that latter part. Apologies for that.

LOL! These are hilarious!! "You can put your weed in there" is such a throwback SNL reference but I love it!

Questions relating to accounting and regional compliance are taking us a little longer to answer as we clarify details with finance/legal. We're growing fast, but this team is small, so any help you can provide would be appreciated. Drop me a DM with a template that meets the requirements and I'll see what I can do to put this on the fast track.

That's not quite right. Any code that is a derivative work needs to respect the license of that work. But if its an original work, that doesn't necessarily apply. There's technicalities to this, but in our case, we don't deliver any "code" in the ISO for HexOS right now. That's literally TrueNAS SCALE w/ a connector to our Command Deck (which is an open source package). Our primary code resides in two places: our cloud infrastructure and services and our UI/UX. We have plans to open source our UI/UX code but not our infrastructure (for obvious reasons). Hope this helps answer your question.

Hi there, Mixing and matching drives of different sizes with ZFS today does require you to give up the capacity on the larger-sized drives. For that reason, our wizard limits mixing to only with drives that are within 90% of the largest size drive in the pool. We will make this more configurable in the future. While we do believe mixing and matching different sized drives to be of value, the main feature that ZFS was missing prior to recent was the ability to expand one drive at a time (RAIDz Expansion). We do support this on HexOS today.

Not to be a party pooper, but I have only been doing this for people that came back to us up through December 4th and those that had legit purchasing problems. Beyond that, it feels like we're going back on our word to the customers that did buy on time.

This is really great insight and I appreciate the thorough explanation. As you can probably guess, we're not accountants or tax experts by trade ;-). I'm meeting with our accountant this week to shore up any issues on this. We will fix.

Absolutely guys. For this first phase of launch we went with minimalistic approach. This way we can narrow our support focus. We will be turning on 2FA in the near term.

Sorry all! Please try again! We had to update the address field in the top right. It looks like the color formatting is really off. We'll get that resolved. Our apologies.