Add Storj and Filebase as Backup options

[marcusquinn]

• https://www.storj.io
• https://filebase.com

I realise these things can be done with the generic S3 API Compatible settings - but I think there's some good karma value in having them specifically detailed and documented; in that their communities and products seem ethically aligned with Cloudron's aims and community, and will likely bring cross-pollination of champions for each.

Related posts

• https://forum.cloudron.io/topic/5168/cost-effective-backup-backblaze-b2-or-wasabi-or/3
• https://forum.cloudron.io/topic/1805/backup-target-tardigrade-io-storj-io-a-secure-decentralised-storage-network
• https://forum.cloudron.io/topic/4170/storj-node

[marcusquinn]

Revisiting these, mentioning here in case it catches the eye of others interested in similar.

[atridad]

I was unable to get Filebase working. On a side note, they are a nightmare to deal with for simply deleting an account. Still hasn't happened yet. Boy do they really want me to stay...

Definitely frustrating anytime a service doesn't let you delete your own account.

[arshsahzad]

hi @girish, It's a good time to add storj as a backup solution in cloudron natively,

I was a beta user of Storj.io (Tardigrade.io) in 2019, now for the last 5 months, I'm using storj.io as my main object storage provider due to pricing, never got any problem yet...

[girish]

@arshsahzad @marcusquinn Are storj and filebase the same ? I can add both/either , just want to understand the difference. Are they different companies?

I see https://www.storj.io/blog/introducing-filebase-to-the-storj-community but storj.io itself has a pricing page.

[girish]

Just noticed filebase itself has a cloudron page - https://docs.filebase.com/configurations/third-party-configurations/backup-client-configurations/cloudron

[marcusquinn]

@girish I believe they are separate, so need to be added separately as-such.

It seem that FileBase uses Storj as one of its layers, but adds additional features and redundancy beyond the Storj layer, hence the value-add higher pricing.

I just think both ethically aligned with the vision here, and having named support, as opposed to generic, is a nod to their efforts in providing a decentralised and competitive alternative to the incumbents.

I think recent events certainly show us that censorship is an ongoing concern, and replicated redundancy is a necessity to mitigate the risks of what might have been unlikely one day, and has suddenly happened another.