Using tardigrade with nextcloud as primary storage

Hello, I found this article.

Finally came the moment when after being from version v2 I will start using the cloud provided by Storj instead of just providing my infrastructure for it.
Is it possible for my nextcloud on the VPS server to use the Tardigrade space fully? Can all data uploaded to nextcloud can be transferred to Tardigrade immediately and directly and my VPS doesn’t need space for it or maybe Tardigrade, in this case, can only be used for backups from NextCloud?


i searched the forum for exactly the answer to this same question but i see no one has commented :frowning:

@jocelyn are you able to help please?

the documentation refers to using tardigrade as a backup source, but we want to know if it can be used as the primary storage for next cloud please.

1 Like

I am currently working on using the builtin S3 swift adapter to switch out the local storage for S3 compliant storage.
This would then mean you need to run an S3 Gateway on the same machine and point it towards it.

Once i have that up and running, i can post the How-To here.


I have a proof-of-concept fork of nextcloud with integrated.

With that setup you don’t need the S3 gateway.

It’s probably better to distribute it in the nextcloud app store which still requires some work.


That really sounds promising and i am personally looking forward to it!

That said, i can report back how to enable full primary storage for nextcloud:

First of all its recommended to start without having your nextcloud being started, else you will lose access to all of your data that has been stored until that point using the previous storage method (likely local disk) and the DB state also gets inconsistent with whats in the new primary storage.

  1. Create an instance of our S3 Gateway near your nextcloud instance (or on it depending on the load).
  2. Add this to your config and make sure that the use_path_style flag is set to true
'objectstore' =>
    array (
        'class' => '\\OC\\Files\\ObjectStore\\S3',
        'arguments' =>
        array (
        'bucket' => 'nextcloud',
        'autocreate' => true,
        'key' => '<ACCESS_KEY_ID',
        'secret' => '<SECRET_KEY_ID',
        'hostname' => '<IP-OF-S3-GATEWAY>',
        'port' => 7777,
        'use_ssl' => false,
        'use_path_style' => true,
  1. Start your nextcloud instance.
  2. Give the instance a bit of time to sync the initial data structure over into the network.

This worked for our internal Nextcloud Instance just fine.


Are your aware of the issues with Nextcloud and the Gateway?