Shared Folders

Zitat von MIkey6283

Hi

I have been watch installation videos and i noticed that it is possible to insert the shared folder when binding folders when installing applications. Is this only available in OMV4 as i am unable to find this directory as per the screenshot. At the moment i use the Relative Path. where can i locate this directory with out have to use the Relative Path all the time?

forum.openmediavault.org/wsc/index.php?attachment/19656/

The problem with using shared folders, it was causing problems with docker, so it was disabled. You can enable shared folders... even in OMV 5 I do believe, just can't remember how.

IMO, Your best bet in your situation is learn to use the symlinks plugin. Personally I created a folder called "NAS" on the root directory (you'll have to do this at command line).. then any directory I want easy access to at the command line level, I just symlink it under that directory and it makes it very easy to cd into (ie, cd /NAS/Media). This makes it where my docker-compose files almost write themselves... (see examples)

version: "2.1"
services:
  calibre-web:
    image: ghcr.io/linuxserver/calibre-web
    container_name: calibre-web
    environment:
      - PUID=1000
      - PGID=100
    volumes:
      - /NAS/AppData/calibre:/config
      - /NAS/Media/eBooks:/books
      - /etc/localtime:/etc/localtime:ro
    ports:
      - 8219:8083
    restart: unless-stopped

---
version: "2.1"
services:
  airsonic:
    image: ghcr.io/linuxserver/airsonic
    container_name: airsonic
    environment:
      - PUID=1000
      - PGID=100
    volumes:
      - /NAS/AppData/airsonic:/config
      - /NAS/Media/Music:/music
      - /NAS/Media/Music/.Playlists:/playlists
      - /NAS/Media/Music/.Podcasts:/podcasts
      - /etc/localtime:/etc/localtime:ro
    ports:
      - 4028:4040
    restart: unless-stopped

Zitat von MIkey6283

Kim0201

Thanks for your reply & examples it is the examples that help newbies like me. i have already setup my ssd drive with Media. config , appdata & general, for the time being until i learn more . I tried symlinks but go my self into trouble. i will look into this again, i thought that this addon was about to cease according to what i read about It.

I was going to set up a docker folder in appdata , is this correct way to go so that i can install docker containers as and when ?

Thanks again.

Even if it did cease (it seems to be a fairly simple plugin and has been around forever, so not sure why it would.. but I'm not a plugin dev..).. setting up symlinks at the command line is very simple. If that didn't come from ryecoaaron I wouldn't read to much into it.

How you set up your docker containers, is strictly up to you.. I try to keep it simple and consistent.... So ALL of my media (movies, tv shows, music, books, etc.) are mapped somewhere under Media... my AppData folder, is where I keep all the "config" directories referenced by some containers...

ken@openmediavault:~$ cd /NAS
ken@openmediavault:/NAS$ ls
AppData  Media
ken@openmediavault:/NAS$ cd Media
ken@openmediavault:/NAS/Media$ ls
Movies  Music  Photos  Random_Videos  TV  Torrents  eBooks
ken@openmediavault:/NAS/Media$ cd /NAS/AppData
ken@openmediavault:/NAS/AppData$ ls
airsonic  calibre  heimdall  nextcloud  nextclouddb  portainer  swag
ken@openmediavault:/NAS/AppData$ 

What issue did you run into with symlinks.. just curious?

Edit: Heres how it looks under the symlink plugin, the main thing to keep in mind, is everything that isn't symlinked under /NAS, is directly on the OS drive... so if you start manually creating folders under /NAS... depending on what you are doing you could fill up your OS drive quickly.

So in my example, if I create a directory at the command line level /NAS/Something (without symlinking it)... /Something will be on the OS drive, not the data drives. If you're putting a lot of data in /Something, it could quickly fill up your OS drive. On the other hand if I create a directory at the command line /NAS/Media/Here , the directory Here , will automatically be symlinked, since /Media is a symlinked directory. That's about as clear as I can make it and if you "ran into trouble", I'm guessing that was your issue.

Zitat von KM0201

Even if it did cease (it seems to be a fairly simple plugin and has been around forever, so not sure why it would.. but I'm not a plugin dev..).. setting up symlinks at the command line is very simple. If that didn't come from ryecoaaron I wouldn't read to much into it.

The symlink plugin is not going anywhere. It is easy to port to new versions of OMV.

Zitat von Highlander88

I am using the symlink plugin but is annoying to jump continuously between the filesystem section and the symlink plugin to be sure that you are pointing to the right drive

When do you do this? I guess I don't understand why someone would do this. If you make the symlink very similar to the filesystem label, there shouldn't be any guessing and switching.

Zitat von Highlander88

I don't know, maybe is only an issue for me but there are these very lengthy mountpoints that are hard to relate to an hard drive, especially when the names are similar when you are in symlink plugin screen, having a way to have a friendly label for viewing purposes, or be able to create custom symlinks directly from the filesystem would be more practical in my opinion. Or maybe I am missing something?

I understand the friendly label but when are you using the lengthy mountpoints? They aren't used in the OMV web interface in most cases. Do you not have the label column visible in your filesystem tab?

Zitat von Highlander88

I don't know, maybe is only an issue for me but there are these very lengthy mountpoints that are hard to relate to an hard drive, especially when the names are similar when you are in symlink plugin screen, having a way to have a friendly label for viewing purposes, or be able to create custom symlinks directly from the filesystem would be more practical in my opinion. Or maybe I am missing something?

The idea of symlinks is simply to make command line access easier (or in the case of docker-compose, volumes are easier to set up) If you've got your symlinks setup, under most circumstances you can do not need the absolute paths anymore.

You can try to set up disk labels, but if your drives have data I don't believe you can do that after the fact (and it doesn't work in all situations anyway). You set up the symlinks, so do you not consider /mnt/nvme-01 friendly enough?

Or maybe I'm not understanding your question.

While that seems practical to say it, implementing it would likely be far more of a chore.

Personally I find the symlinks plugin extremely simple and never use absolute paths anymore.

Zitat von Highlander88

I am starting to do the same, I am migrating all the docker-compose files to symlinks

If you set it up properly, it becomes absurdly simple... It's to the point for me I don't even have to look at my volumes anymore when I'm creating containers... since my path are all very consistent, I just know what they are.

---
version: "2.1"
services:
  mariadb:
    image: ghcr.io/linuxserver/mariadb
    container_name: piwigodb
    network_mode: swag_default
    environment:
      - PUID=1000
      - PGID=1000
      - MYSQL_ROOT_PASSWORD=***
      - MYSQL_DATABASE=***
      - MYSQL_USER=***
      - MYSQL_PASSWORD=***
    volumes:
      - /NAS/AppData/piwigodb/:/config
      - /etc/localtime:/etc/localtime
    ports:
      - 3306:3306
    restart: unless-stopped
  piwigo:
    image: ghcr.io/linuxserver/piwigo
    container_name: piwigo
    #network_mode: swag_default
    environment:
      - PUID=1000
      - PGID=100
    volumes:
      - /NAS/AppData/piwigo/:/config
      - /NAS/Media/Piwigo/:/gallery
    ports:
      - 8220:80
    restart: unless-stopped

version: "2.2"
services:
  airsonic:
    image: ghcr.io/linuxserver/airsonic
    container_name: airsonic
    network_mode: swag_default 
    environment:
      - PUID=1000
      - PGID=100
    volumes:
      - /NAS/AppData/airsonic:/config
      - /NAS/Media/Music:/music
      - /NAS/Media/Music/.Playlists:/playlists
      - /NAS/Media/Music/.Podcasts:/podcasts
      - /etc/localtime:/etc/localtime:ro
    ports:
      - 4040:4040
    restart: unless-stopped