'objectstore' => 
array (
  'class' => '\\OC\\Files\\ObjectStore\\S3',
  'arguments' => 
  array (
    'bucket' => 'yourbucketname',
    'key' => 'YOURKEY',
    'secret' => 'YOURSECRET',
    'hostname' => 'nyc3.digitaloceanspaces.com',
    'region' => 'nyc3',
    'port' => 443,
    'use_ssl' => true,
    'use_path_style' => true,
  ),
),
);

I added this to the very end of my config.php, and before the last closing );

Functionality tested and working. Uploads and downloads happen directly within the DO Spaces bucket. Configuration persists between reboots.

I am new to Cloudron, so I am not certain if these changes will persist after updates to the Nextcloud app or Cloudron.

@girish This article suggests there's an old and a new way to do this, so I wonder if we're all talking about the same thing?

• https://autoize.com/s3-compatible-storage-for-nextcloud/

old = adding an additional S3 store from within NC running locally.
new = setting up NC with S3 as primary storage.

• https://autoize.com/s3-compatible-storage-for-nextcloud/

This is not a problem with NC, but of the underlying architecture chosen.

There is a way to make this work well, but one must understand all the pieces, as if you ignore one, it will be the lowest common denominator and bottleneck.

It is an Enterprise Deployment afterall.

for example: https://help.nextcloud.com/t/high-aws-s3-costs-due-to-nextcloud-requests/68687 and https://help.nextcloud.com/t/high-traffic-to-primary-storage-s3-from-nextcloud/83185 .

@privsec Just reading this, not sure if you've read? I'm not saying i can't be done, just that we gave up. Maybe this helps? I'm still reading: https://autoize.com/s3-compatible-storage-for-nextcloud/

This is along the same lines as my advanced object store usage option above.

I didn't know this was possible from within NC, but it appears they engineered it in. Very smart & clever.

They are essentially caching everything recent in /tmp and background syncing to the object store over time.
The user experience is good as it's all mostly local, and the capacity is greatly extended as the Object Store is vast.

I've designed this for other use cases at IBM, and wrote their Redbook on it, hence advanced prior knowledge.

For this article to be applied in Cloudron, we'd need a new packaged NC App that is configured for this before the setup/install. Then one can point it at a local Minio instance or external S3 object store.

So, I wouldn't dismiss this aim, just with speed cautions, and the cautions in the article that the storage would then be unbrowsable directly without the NC database metadata interface, so it also has mass disruption risks if that were lost.

ie. Get a VPS with a large amount of disk mounted locally.

When I include that piece of info in the config file, nextcloud either error's out or it does not use the S3 bucket as its primary storage.

From reading the above article, is sounds like it might need to be that Cloudron has 2 x versions of Nextcloud packaged, or at least an option in installing to make it setup for S3 storage

Ihmo no second app necessary, the drawback is though that the s3 backend can only be enabled before any data is added to the app.

I am however sceptical if adding network latency for file access is such a smart idea. Especially for a php application.

Anything I can do to help make launching costs low is sought after, while keeping user experience high

Probably needs one of the @appdev team to have a read and confirm or deny.

I agree it would be interesting and our past experience might have been what this article above solves.

Let's get more opinions on this, someone else might also have a need and interest and be willing to try themselves too.

It might work for something like Video storage where there's fewer files but I just don't fancy the slow user experience costs and would always opt for speed over price since time is so much more expensive if users are spending too much waiting on their file services to show results.

I have decided (atleast for now till I find a better solution) to give each user on nextcloud a wasabi bucket as a external storage drive, and restrict only them to be able to access that bucket.

I am now working on trying to figure out how to remove the built in files for nextcloud to just have the external storage folder listed with the nextcloud folders/files within the wasabi drive.

In regards to Cyber Duck/Mountain Duck, whats the difference between the external storage connection in nextcloud and them ? Is there a performance difference?

Minio can be used as a storage gateway.

See if you can connect Minio to Wasabi, if you can in gateway mode, then see if you can mount the local Minio instance in Linux, even if s3fs, it would be local.

Thank you for your detailed responses.

Ill have to play around with the external storage options for nextcloud to see if that will work out or not.

Its an interesting workaround/hack, lol.