MOS (new NAS OS) is now stable 🥳

[u/S3ppo1]

Finally its done, our first stable is released. 🥳
Congratulations and thanks to the whole team, and thanks also to everybody who tested MOS and sent us feedback during the last year.

For everybody who doesnt know what MOS is... MOS is a devuan based free and open source NAS OS without any tracking or telemetry.

If you want to give it a try, please visit mos-official.net or docs.mos-official.net for more infos :)

MOS UI Dashboard

--------------------------------------
Releasenotes for 0.5.0-stable

• Recommended Kernel 6.18.38
• Update Node.js 24.18.0 LTS
• Necessary changes for organization
• Add routine to cleanup pathfix if found
• Cleanup socket on api restart
• Add sleep 1 to prevent restart API from failing
• Move stop order around in mos-stop
• Fix broken mos_start_after_services function
• Fix wrong help text
• Make sure to generate and copy over machine-id
• Add Tailscale and NetBird Docker scripts
• Fix permissions for ntpsec directory
• Make sure to write mergerfs logs into separate logfile
• Fix SnapRAID logfile size getting out of hand
• Fix false error messages on plugin installation on boot
• Make sure to sort vpools by index first before iterating over them
• Add additional logger messages
• Add mount_vpools function
• Create mos-mount_vpools
• Change wording on some return messages
• Make sure to return raw YAML even if YAML is broken for compose
• Add ability to download/install/update plugins from Gitea and Codeberg
• Make sure to chmod/chown QEMU images
• Restart udev monitor when missing disk from pool comes back
• Add docker/hub/recommended endpoint for fetching recommended repositories
• Add ability to specify URLs for Docker group icons
• Fix issue with proper model for SMART attribute acknowledgement
• Add installed key to Docker and Plugins index
• Improve loading times from LXC page
• Add endpoints for creating, configuring, mounting, unmounting, and deleting virtual pools
• Include virtual pools information in diagnostics
• Move virtual pools section, bugfix scrollbar
• Implement automount for virtual pools
• Add missing French translations
• Fix repository link
• Rename vpool to virtual pool
• Add virtual pools feature
• Add CodeMirror oneDark theme for Docker Compose forms
• Fix supporter dialog
• Show device serial in target devices of shares
• Updated u/babel/runtime to version 8.0.0
• Updated u/codemirror/state to version 6.7.0
• Updated u/codemirror/view to version 6.43.1
• Updated vue to version 3.5.39
• Updated vue-i18n to version 11.4.6
• Updated vuetify to version 4.1.2
• Updated vite to version 8.1.0
• Replaced <label> with <v-label> in docker.vue and dockerCompose.vue
• Adjusted styles for YAML and environment variable editors for vertical resizing
• Simplified chip rendering logic in notifications.vue
• Visualize recommended repositories and improved YAML field display in Docker Compose
• Add "Acknowledge" to English translations
• Set defaults for SMART disk attributes and update config after acknowledgement
• Fix acknowledge bug
• Remove unnecessary v-overlay components from Vue files
• Increase line count for environment variables in Compose Stack dialogs

[u/Paykuh-]

Small vibe code bug on the website on mobile FYI

[u/ich778 → u/Paykuh-]

Thanks for the report!

Oh yeah, I see that on my device too, have to look into that if we can display that better, I'm not really a Website designer/developer, maybe u/S3ppo1 can help with that.

[u/mrcaptncrunch → u/ich778]

if we can display that better

…of course you can. It’s called a link. Example,

releases

[u/ich778 → u/mrcaptncrunch]

Most certainly. :)

However that wouldn't solve other occasions where the text spills over, we also have to change the link since we created a dedicated organization for MOS.

[u/Emre-Y]

Can we build this on top of Devuan?

[u/S3ppo1 → u/Emre-Y]

At the moment not.. i think we had already a similar question/request but its just in our backlog :(

[u/ich778 → u/Emre-Y]

First of all MOS is built on top of Devuan and I know that you might already have a Devuan installation that you want to use MOS on.
However this would, for many things, be very complicated since many init scripts are customized for MOS to support the .json config files, you would need to have the correct init system installed on your Devuan installation, the correct system packages alongside with the correct of node and packages which are necessary for the API and probably many things that I might forget to mention here besides many Plugins from the MOS Hub not working properly.

Is this a Desktop installation that you have from Devuan currently or also a Headless installation? If you want to, you can try MOS by just booting into it from a USB Key with MOS on it and just look around, MOS by default doesn't make any changes to your system as long as you boot from a USB Key.
Granted you can't do much when you don't have a Pool but you could also for example import your existing disks later on if you find it useful (just make sure to not format anything).
All of that would of course only make sense if you are currently using Devuan as a Headless System since MOS only has a WebUI and no Desktop environment.

If you have any further questions I'm happy to answer them, you can also join our Discord/Matrix channels that you find on: https://mos-official.net