Implement Ability to Modify Storage Directory

[edplane]

It would be a nice feature to include within the dashboard the ability to specify a separate location (on another drive or network share) in which downloaded content is stored. Since the default location, /opt, is under root, for those of us who partition such that /root is separate and smaller than /home, defaulting to that location limits the size of the libraries we can install. Ideally I'd like to specify a separate disk entirely.

[broy55]

Same here. I built a home nas with a raid storage. I'd like the option to store all the ZIM's in my raid. Right now I had to manually modify the compose to do this, but I'm afraid things might break.

[jdhenshall]

I would like this ability also. I'd like to create a share on my home NAS for offline content

[CelticNinja2k26]

I have a NAS running Pop_OS, I'd like to install the whole thing to /mnt/RAID/nomad if I could.

[rg651]

I have the same problem. Command Center says I only have 3.1 GB available. NVME drive has over 700GB free space but inaccessible.

[neuhubereco]

pro tip - connect claude code or cursor AI to help you set it up. :-)

[timmills]

Yes - Ive just setup a new machine with a boot drive and additional 2TB SSD for data but it doesn't look like a supported config

[MaKeG0]

i think this feature is a big priority if we consider the self hosting basic idea and people would like to map nas storages or anything else

[edplane]

My solution was just to create a disk image file on my local NAS server, then set it up in fstab following the mounting of the server itself such that the img file mounts to /opt/project-nomad/storage. It seems to work for now. I'd imagine you could also make the storage folder a symlink to another folder somewhere else.

[timmills]

If this is the box we run out of the house with it would be great to be able to easily use internal storage - dont imagine it would take much via the Web UI to map a 2nd drive. (Also think if we were able to dump entire collections to a 2nd drive then share that drive with someone else and they could bulk copy the data from the drive to theirs it would save re-downloading and make distribution easier if there wasn't internet . (Or even better 2 machines on the same network could share repos)

…

On Wed, Mar 18, 2026 at 2:20 AM edplane ***@***.***> wrote: My solution was just to create a disk image file on my local NAS server, then set it up in fstab following the mounting of the server itself such that the img file mounts to /opt/project-nomad/storage. It seems to work for now. I'd imagine you could also make the storage folder a symlink to another folder somewhere else. — Reply to this email directly, view it on GitHub <#347 (comment)>, or unsubscribe <https://github.com/notifications/unsubscribe-auth/AAHWNTEUKD6AO2AWFVY243L4RFUMTAVCNFSM6AAAAACWSW7GY6VHI2DSMVQWIX3LMV43URDJONRXK43TNFXW4Q3PNVWWK3TUHMYTMMJXHE4DKNI> . You are receiving this because you commented.Message ID: <Crosstalk-Solutions/project-nomad/repo-discussions/347/comments/16179855@ github.com>

[cosminmihai0385]

I would also like to change the location of the storage directory and move it and organize it on my NAS.

[broodslawns]

I have a bunch of videos downloaded for offline access, all kinds of preparedness and tutorial vids, that I would like to just add to NOMAD somehow. Would be nice to either have a separate NFS or SMB share that it can pull from, or just have an upload option.

Big picture, would be cool to have a kind of 'Youtube' like GUI for videos and upload directly into that and just manage physical storage on a single disk rather than trying to be fancy with network shares since that sort of defeats the purpose of what this is trying to do. Though NOMAD is a victim of its own success and great design, because it's so good at what it does, people want it to do more and see its potential. Good job, guys.

[kane9287]

It's just docker under the hood. I'm toying with the idea of putting CasaOS on here for reverse proxy, it wouldn't be hard to add something like a YouTube type video app. I'll probably just use Claude to add a "Open Casa Here!" button. CosmosServer is another good option I'm toying with.

[chriscrosstalk]

This is actively being worked on. Custom storage paths are planned as part of the Advanced Features toggle in issue #271, with #367 as the canonical tracking issue for storage path configuration specifically.

In the meantime, the workaround is to symlink /opt/project-nomad to your desired location before running the install script.

[jakeaturner]

Just want to provide some clarification here:

NOMAD runs inside a Docker container, which acts as an isolated boundary between the app and your host system. Think of it like a ship in a bottle: Nomad can see out and manage containers on your host (via Docker-outside-of-Docker), but it cannot reach back through the glass to reconfigure the host itself.

Custom storage paths, mount points, and external drives (like iSCSI or SMB/NFS volumes) are already possible, but this will be up to your individual configuration on the host before NOMAD starts, and then passed in via the compose.yml. Once running, NOMAD has no way to move or remap its own foundation.

[darrendavid]

Unsure if this is the same issue or concern or not - I'm running NOMAD on TrueNAS Scale using the management_compose.yaml file provided. I have my database files on a fast NVMe mirror and I have my storage dir configured on a much larger ZFS pool with plenty of storage (see below) but when attempting easy setup NOMAD wants to place everything on overlay (I don't know what that volume is, and that free space indicator doesn't match anything on my system) instead of data/appdata/nomad where there is plenty of space. How do I tell NOMAD to use the larger storage dir for, well, storage?