jonp

Settings > Locations is where this functionality will live but it doesn't have the ability to remap locations in use at this time (have to do it before you load them up) but will have that in the future! When you install an app that requires a folder for say media, we auto create those folders for you to use to store them in, but if you have already manually done that, we have to add the ability to the command deck to remap those (coming in the future). For now you could remap via the truenas UI but it requires a bit of handholding from a TrueNAS rockstar to know what you're doing in there 😉

If you've installed an app using the TN user interface, you're going to be managing that app through TN for controls for a while. Supporting migration from TN to HexOS managed apps is not on the roadmap right now, but may be in the future. That said, if you remove the app from TN (but not your user data), you can then install it from HexOS. You will have to reconfigure the app but the user data will remain intact.

Apps are running in docker containers. They install preferably to an SSD pool but will default to whatever you have if only HDDs are present (performance may be impacted depending on the applications storage performance requirements and other concurrent usage). The OS boot drive does not store the applications themselves or their configuration data. All of that is stored on one of your storage pools. The OS boot device stores the distribution itself and it's configuration settings. That's it. Apps do not run in full VMs. VMs would be useful for non-containerized applications (if you have any requirements for that) or non-Linux based workloads (e.g. Windows). Not necessary for Plex or Jellyfin Apps work similar to a VM from a control standpoint. You can start, stop, and update them independently from one another. And if an app goes completely haywire, removing it does NOT remove the associated user data (e.g. removing Plex/Jellyfin does not delete your content). Hope this helps!

This man devs! Not sure I could of said any of it better myself.

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.

Appreciate the criticism and we take it in stride. I respect everything you and others post, both good and bad. Sometimes raw emotional responses can cause gut check reactions of "you're kicking my baby" but I don't let myself see it that way. You're obviously passionate about our project or you wouldn't be here pointing out all the ways in which we can do better. I also respect not wanting a refund and I look forward to the day when I see a post from you saying, "ok, this was totally worth it and I'm glad I bought." 💯 Agreed. Our CTO has a proposal for us this quarter to do exactly what you're talking about. It's premature to share but know that we are on the same page and intend to do this. We intentionally built the global HexOS messaging system for this back with the Q2 release. We now want to expand that to include notifications for app-specific issues like this. But keep in mind that was not the original plan for 1.0 so the scope is no increasing, which is fine, but we still have other projects and objectives to hit, one of which is the Local UI which is a much bigger project than I think anyone realizes. It's complicated by the fact that our actual footprint on the ISO today is very small and we do not want to bake any of our UI into that ISO either. Instead, we have to build a full container/app for this which we are doing, but it's a huge project and we have a senior dev completely focused on it right now. I feel like a broken record saying this, but a big part of our struggles this year is bootstrapping the business. Money doesn't solve everything, but it sure as heck would have helped to hire a lot more developers and app specialists right at the beginning of this year, but we opted for a more fiscally conservative approach to hiring to ensure we don't grow too big too fast and make commitments to employees we can't keep without proving our business model first. Expansion is a big part of our plans for 2026 and will help us get more focused on individual layers of the software. Sure, but that comes with its own set of challenges and problems. Again, everything is still in flux and user data is not at risk. The worst anyone should have to deal with is reconfiguring immich from scratch which of course isn't ideal, but let's be honest here, it's also not the end of the world or an unrealistic expectation given the beta nature of both us and Immich itself. Comms of course could be better, always. But we are doing the best we can with what we have for now and we would just ask people to be patient while we work through it. This was all part and parcel of participating in the beta and if that's not going to work for anyone, waiting to deploy until more polish is applied would be the right approach. I've already spent hours reading and replying here and the more we try to get ahead on comms, the less time we spend on building and getting to a release. Every hour is a choice and often there are no options that will satisfy everyone. Still totally understand the frustrations, but this is the last I'll be commenting on this today so I can get back to work with the rest of the team. Our new docs site is a great place for us to put a guide for immich issues and resolving them in the future. Stay tuned for more, but know that we don't have the ability to always drop everything we are doing to shift focus to an issue like this when we are in the middle of other projects. There can be a lag time and that is something everyone here will have to accept while participating in the beta. Again, if that doesn't work for anyone, wait for the polish to come before deploying.

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

😞 I totally get this disappointment. I don't even blame you. We are targeting a more casual user and I can see how users like yourself may have had a higher expectation closer to that of a video game beta, where it's really software that's functionally complete, but just testing integrity of the infrastructure for multiplayer and game balance. You might find a bug or two, but nothing too crazy because part of the purpose of the beta is to build hype for the game prior to release, as we just saw with Battlefield 6 Open Beta. All of that said, we did say this was beta and listed out all the risks in the very first post you read to get it downloaded and installed. Furthermore, we actually had a second fix in for th migration issue for Q3 but due to another immich update, it broke again literally the day before the Q3 release and we missed it because QA was the week prior. This was just a very unfortunate coincidence. It seems like you specifically may be very frustrated with us and not happy with your experience. If you would like, I will refund your purchase. We don't want anyone feeling raw about their transaction, so if you want to take me up on that, feel free to drop me a DM. We are a small but growing team and will speak to our plans to get even better about this for post 1.0. We will be building an Apps team that will be responsible for ensuring our curations remain solid and that we handle these types of issues better. This analogy was spot on. Appreciate you taking the time to lay that all out.

To be fair, we actually did fix the issue referenced in that post. However, additional issues have crept up especially with the recent updates to Immich in preparation for their 2.0 release. One major change they made actually requires users to go through a migration process (a choice by the app developers). It's important to remember that Immich is a free-to-use self-hosted solution, which means that sometimes they may need to do things like this as opposed to the slick polish you'd see on a commercial product. That being said, we're still incredibly impressed with Immich and see it's future very bright.

We actually began the VM work last year but it started breaking as TrueNAS was making changes to the underlying stack. As such, VMs were delayed as a feature. 25.10 promises even more improvements to the VM stack and API so we aren't going to resume work on them until that is stabilized. In the meantime basic start and stop functionality exists in our command deck so if you create a VM in TrueNAS it will show up for basic controls in our UI.

We've discovered a handful of different issues with immich plaguing users. We are on the case and it's a priority issue for us!

Agreed. Thread has run it's course.

Good catch. @jerod we should probably map those folders automatically for qBittorrent.

Thank you for the thoroughly detailed report! This definitely helps. @jerod and the team and looking into this further and exploring different paths to resolve.

I think there may be a few gremlins at play here and it's worth spending a little time investigating given the amount of feedback we see here.

We've stated previously our intentions to skip past 25.04 entirely in favor of 25.10 when it drops. The Q3 update is for the Command Deck.

Team and I are reviewing it tomorrow a bit deeper. Thought we had this resolved for all but apparently not 😡

You may need to clear your browser history on Chrome. I thought the deck was down for a sec because of your post and I couldn't find my server, but it turned out my Internet had gone down at the same time. Apologies to our dev team for starting a false alarm ;-).

Investigating!

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 😉