jonp Posted 7 hours ago Posted 7 hours ago We are extremely close to releasing HexOS Local, our solution for accessing/managing your HexOS servers through a locally installed application on your server. Before we roll this out to all current users, we are looking for a handful that are able/willing to help us test the migration process. The requirements are pretty simple: 1) Users that agree to enroll in this early access test will have ALL of their servers migrated (we cannot apply the test to just a single server, so if you have multiple, it's all or nothing). 2) Users must have a discord account as those accepted will be invited to our new discord server for the purposes of bug reporting and support needs. If you are interested in helping us test this, please drop a DM to @mill3000 with the subject "HexOS Local Early Access" and be sure to include your Discord username in the message. Any questions, post them here! Thanks everyone!! 1 2
Remy B Posted 5 hours ago Posted 5 hours ago (edited) Can you clarify on the risks with the data on the pools if going in this HexOS Local beta ? Would the worst case scenario be loosing the truenas/hexos install ? Also, is this part of the v1 HexOS realease ? or are we still in v0.xx version ? Edited 5 hours ago by Remy B
jonp Posted 5 hours ago Author Posted 5 hours ago Should be no risk to data loss at all. The biggest risk is getting disconnected from our deck for server administration. That's why we want users to be able to talk to us via discord so that we can quickly remediate those types of problems if they occur. The big switch here initially is going to be authentication. We're moving to key cloak and we set up a more robust infrastructure to enable us to migrate users between production and development environments very easily. While we've done a ton of internal testing on this, we just want to be extra cautious before doing a mass migration of thousands of users all at once. Technically this is still pre 1.0, but the only things that really remain for us are hexos local and some improvements to our health monitoring systems. 2
FangerZero Posted 2 hours ago Posted 2 hours ago What does testing all entail? Like is there a checklist to follow, obviously if any thing random comes up, but yeah? Would love to be useful since it sounds like my pools won't be affected. Is there a way to back up settings just in case the OS goes haywire?
jonp Posted 1 hour ago Author Posted 1 hour ago 50 minutes ago, FangerZero said: What does testing all entail? Like is there a checklist to follow, obviously if any thing random comes up, but yeah? Would love to be useful since it sounds like my pools won't be affected. Is there a way to back up settings just in case the OS goes haywire? At this point, just using HexOS to create folders, users, install apps, etc. just like normal. Use it both locally and remotely. That's really it. At this point, the main thing we're testing is that it works correctly, navigating you to the local interface when on LAN, and giving you remote access via the deck when away. If you can break your system (non-critical data only), there are a few specific cases we would like to see users test like destroying the pool used by apps (Docker) manually via TrueNAS, then renavigate to deck.hexos.com to see if you can remediate the issue. Obviously not asking anyone with real data on their systems to do this, but for those that have test setups, just beat the heck out it and see what breaks. We test internally pretty rigorously, but there's always edge cases that we can miss and this is the chance to find those as best we can.
Recommended Posts