jonp

Have a team meeting scheduled for this PM to discuss this morning’s outage, the login issue, and a better notification message. Definitely some room to improve UX here.

Right now the team is entirely focused on bug fixes, QoL updates, and pool customization. When we go to shift focus onto our next major feature, we will also select another app for curation (maybe a few). We specifically started with Plex because it’s honestly A) one of the most popular and B) one of the most demanding for configuration. By starting with the hard stuff, we can really focus on honing in support and getting that experience just perfect as well as set a template for all future apps to come. As an example of this, we are very focused on improving the plex experience already. There are issues with remote access, resource assignment, and GPU-assisted transcoding. So those types of things will likely be addressed (at least in part) before we add another curated app. That being said, I am hopeful to really start cranking on a wider App Library sooner than later. Apps are one of the most important features of the product.

We are in phase 1 for apps right now, which means we are curating them by hand. Phase 2 will bring in additional community developers to help further curate. Phase 3 is offering the ability for users to load custom docker containers outside our curation.

Yes I believe we have this ability. I’ll look into it!

This is our first update yes. Doubt we will have another this week unless it’s a hotfix.

Hi there, There is nothing you need to do to receive the update. We've updated the command deck and you automatically receive the latest by logging in. In the future, we will have full OS updates that require a download to your local server, but we haven't reached that point yet. When we do, we'll add an update mechanism to the settings page.

No and honestly I really don’t care what browser anyone uses but I rarely see edge and it just seemed like an easy / fun troll tbh 😉. I hold no ill will towards any browser or platform. Use what you like! I also like quite a bit about Microsoft, though like with any mega tech corporation, it has its blemishes. I’m definitely still a PC guy through and through.

Timing is perfect for this topic. I appreciate you all waiting until 2025 to bring this up. The road to 1.0 blog post was just a way to set our targets out there. We didn't communicate a specific timeline because we honestly had no idea how much to estimate we would sell at launch, which would directly in turn impact our ability to expand the team and impact our timelines. We just felt that, conservatively, we would do well enough to deliver the blog post roadmap in 2025....yeah....we had no idea what was about to happen ;-). Beat our expectations by about 5x. With the success we've had, we just onboarded three new people to the company in the past 30 days, with a goal of bringing on at least two more developers in 2025 as well and potentially a few other admin hires. This has completely thrown our previous "back of the napkin" roadmap out the window. Let's just say, we're not going to be talking about features just for 1.0 anymore. You guys have given us enough runway to plot out PAST 1.0. Give us a little more time to get our bearings as we onboard new staff, prepare new development environments, implement new systems, and role out our first software updates. More communication coming soon.

Don't you worry! We have plans for you brave testers out there to keep you on a "beta" track that lets you test out the goodies as we're building them. Basically we will have feature-tagging so we can enroll certain users in new beta features for testing before they are ready for the stable track. When we get to that phase, more will be revealed 😉

Also there is a contact us form you can access at the bottom of this site or just email support@hexos.com.

Short answer, yes. This was a pretty quick update today and we were expecting 0 downtime. Reality is I think it was only down for minutes before back up. That said, future maintenance windows will be announced in advance to give people time to prepare. This was mostly backend infrastructure and a few small aesthetic things like fonts. Nothing worth writing up in a release notes post. This is NOT the update I've been talking about since December. The team is actively working on a bugfix release and we're hoping to publish it by end of next week.

As you will notice via the orange community announcement here, we are actively undergoing a maintenance window for the Command Deck to stage if for future updates. Some users will find themselves logged out of the deck while others may not. We will update this message once maintenance is complete. Thank you! UPDATE: As of 2:00 PM CST, Maintenance is complete.

Saw your post and I’ll add this to the list for us to curate. Seems like a good one!!

Just an fyi, we are not in a position to adjust the system requirements right now. In the future we may be able to provide lower recommendations based on use cases where less features are required. E.g. if you just need a basic file server, no apps, VMs, or other services, it may be possible to run the system reliably with less than 8gb of RAM. That being said, this likely wouldn’t happen until after 1.0. For now, feel free to experiment but if you have “out of memory” issues, you know why 😉

Definitely interested in this. Main concern is scammers. That said, I bet there is a happy middle ground. I would want to consult with our legal team before I commit to this, but I’m certainly not opposed to the idea.

Hey, I think you have some notifications that need clearing 😉

Hi there and sorry for the trouble you're experiencing. Not sure how your post got deleted but I will look into that. We are aware of this install issue affecting certain users and are looking into a fix. Can you repost your issue and send me a DM with a link to it so I can track it?

Screenshots!!

LOL! So true...

I have a feeling we'll see a lot more systems turn on after the holidays. The growth rate is actually pretty perfect for us right now. Enough to get a good sample size and yet not too much to overwhelm our ability to manage and respond to issues. I also think there is just a massive undercurrent of users that bought HexOS just to get in at the good price, with no real intention of deploying until we reach or get closer to 1.0.

Great feature idea. Having not spent more than 3 seconds thinking about the security implications, I totally see us doing this ;-). The tricky part is granular access control. Maybe you want them to see that server and even do a few things, but maybe you don't want them to be able to do EVERYTHING such as delete or shutdown/reboot. But I think we will have a solution for that too 😉

Yeah we probably should make a change to this policy. I'll review forum settings this week to lax this up a bit. Not looking to create more administrative burden for ourselves.

While I can't get into details just yet, there are multiple security-specific features planned for the future to improve our posture. This is simply the only way to functionally provide this right now with the current TrueNAS SCALE API. That being said, I greatly appreciate having those that are security conscious here on the forum and thank you for suggesting a solution with your post.

It's ok. The update you're seeing right now is 24.10.0.2. .1 and .2 are both hotfix-class releases with minor fixes for specific issues as documented here: https://forums.truenas.com/t/read-notice-truenas-scale-24-10-0-1-and-24-04-2-4-are-now-available/23413 https://forums.truenas.com/t/truenas-scale-24-10-0-2-and-24-04-2-5-are-now-available/23664 Updating to these shouldn't cause any issues with HexOS, but generally speaking, we do not want users updating using the SCALE UI. When you do, we won't provide direct support for issues. All of this said, it is our fault for the current confusion about updates because of how notifications work in the UI today. We pass through notifications directly from SCALE in the current beta, but in the future, we will parse out update notifications in HexOS in favor or our own mechanism. This is one of my shortlist items for improvement in the next HexOS beta update, which as a reminder, does not require you to download anything to your server.