With S3 for example a common side-effect are high costs due to I/O operations, which are charged by some providers like AWS.

Now to make it more suitable, Cloudron team might think of a way to implementing that in the storage I think what is worth mentioning here is that block storage and object storage are fundamentally two different things and using them interchangeably might cause unexpected side-effects. They recommend to do it, before the installation, but, I did it after the installation (only with the default data in the Nextcloud) and it didn't complain. So inside the container you simply have to add a inside the config directory array(

The beauty of it, it's managed by the Nextcloud App itself so you have no modification to make inside nor outside of the container. That idea always stuck around but never truly searched for an alternative until now.īasically today I was looking how to configure/mount wasabi via the plugin External Storage and I found this article where it explain how to use an s3 storage as backend storage for Nextcloud. A long time ago, I tried to mount a s3/webdav directory on Cloudron via fstab to use is as a storage for apps like Nextcloud, but it failed mainly because of a DNS situation.

Backblaze wasabi