Mount Struktur

[fisi]

Hallo Miteinander,

aktuell können Volumes in den Apps nur nach "/media/{volume name}" gemountet werden.

Für manche Apps wäre es doch sinnvoll das Ziel selbst zu bestimmen. So wäre es beispielsweise bei der Nextcloud App möglich den Storage für die Daten einfacher auszulagern. Zudem wäre es dann sinnvoll, Mounts schon beim installieren der App mit angeben zu können.

Es stellt sich dann nur die Frage, wie Backups der Volumes gelöst werden können, denn aktuell werden Volumes nicht gesichert.

Wie seht Ihr das?

VG Fisi

[necrevistonnezr]

@fisi Hi, since this is an english speaking forum, I believe you rather get an answer if you repeat your request in English...

[BrutalBirdie]

Fast translation with https://www.deepl.com/translator no guarantee for the validity or quality.

---

Hello everyone,

currently volumes in the apps can only be mounted to "/media/{volume name}".

For some apps it would be useful to define the target itself. For example, in the Nextcloud app it would be possible to more easily swap out the storage for the data. It would also make sense to be able to specify mounts when installing the app.

The only question then is how backups of the volumes can be solved, because currently volumes are not backed up.

How do you see this?

VG Fisi

Translated with www.DeepL.com/Translator (free version)

[girish]

@BrutalBirdie said in Mount Struktur:

For example, in the Nextcloud app it would be possible to more easily swap out the storage for the data

Can you (or someone) elaborate more on this? What does it mean to swap out the storage for the data? What happens to the previous data?

[BrutalBirdie]

@girish more like hotswap.
Extending /app/data/ with the mounted volume aka. copying all /app/data to the volume replacing /app/data with the mount.

[girish]

@BrutalBirdie ah ok. That's what we implemented in 7.2. The https://docs.cloudron.io/volumes/ docs have changed a bit to reflect that. See also https://docs.cloudron.io/apps/#data-directory where you can select a volume now!

[fisi]

@girish Now it would only be helpful if the mount target can be freely selected in the container.

[nebulon]

To give a bit more context from the support ticket, which triggered this. The idea was for apps like Nextcloud to be able to store various things from /app/data in different storage volumes, the example is:

volumes:

/home/yellowtent/appsdata/APPID:/var/www/html
/home/yellowtent/appsdata/APPID:/var/www/html/custom_apps
/home/yellowtent/appsdata/APPID:/var/www/html/config
/mnt/storage/data/APPID:/var/www/html/data

Mostly I think this is not a bad idea, to have in this case nextcloud plugins/apps on a fast storage to not slow down the app, while mounting a larger slower volume for the actual data put in nextcloud.

Currently this is not possible, but this thread could help collect requirements for implementing this in the future.

[girish]

This is indeed a good idea to have plugins/code in fast SSD disk instead of the "storage" disk. I guess one way is to also have multiple data directories for this (something which @MooCloud_Matt has been advocating for, but for a different use case). Mmm..