If that's what you are doing why not just go to Wasabi? It is cheaper, storage is the only thing that they do and downloads is free until the GB transferred is under GB stored per month.
I've never heard of them -- how long have they been around?
Replacing Dropbox in favor of DigitalOcean spaces
61–70 of 201 posts
Re: Replacing Dropbox in favor of DigitalOcean spaces
#62I have a 50TB+ NAS in my garage rack. Which I'm not utilizing completely. I wonder if there is a market for renting out some of my storage for someone else's encrypted backups. Something like a website, where I can list my price/gb & connection speed -- or maybe people could swap. Maybe I want to store 5TB off site and I'm willing to let someone else store their 5TB on my server. The website would act as the middleman for introducing the two customers.
Re: Replacing Dropbox in favor of DigitalOcean spaces
#63I wouldn't trust that script too much: there is no error checking at all. What happens when s3cmd fails and after two months you discover the "Vault sync succeded" emails you have been getting were all illusory? If the author is reading: please take the time to update your example, including proper error checking (at least "set -eu"), otherwise the people on the internet that are going to copy your script are in for…
I haven't looked at the code but the author would benefit from using shellcheck.
Re: Replacing Dropbox in favor of DigitalOcean spaces
#64Earlier quoted context omitted.
I agree with you. I should add a disclaimer that this is still being worked on. I will add what you proposed. Thanks for your input.
Always start all your bash scripts with set -e You'll never regret it and might be very very very happy it was there. And if you start with that, then as you work on the shell script, you'll be more likely to make the script be idempotent (checking for files before copying, checking for lines in files before appending/sed'ing etc.) Idempotent >> non-idempotent for "alter the state on an end point" things.
[deleted]
Re: Replacing Dropbox in favor of DigitalOcean spaces
#65I have a 50TB+ NAS in my garage rack. Which I'm not utilizing completely. I wonder if there is a market for renting out some of my storage for someone else's encrypted backups. Something like a website, where I can list my price/gb & connection speed -- or maybe people could swap. Maybe I want to store 5TB off site and I'm willing to let someone else store their 5TB on my server. The website would act as the middlema…
Siacoin and Filecoin are basically this; you can store small parts of files under contracts that give you crypto in return. Occasionally you'll get tested by the network to check if it's online, and you have the files you should have. A good use of crypto, though last time I looked the ROI wasn't great as a host.
Re: Replacing Dropbox in favor of DigitalOcean spaces
#66If that's what you are doing why not just go to Wasabi? It is cheaper, storage is the only thing that they do and downloads is free until the GB transferred is under GB stored per month.
I looked at Wasabi not long ago.
> For customers that use Wasabi’s pay-as-you-go pricing model, Wasabi has a minimum monthly charge associated with 1 TB of storage ($5.99/month). If you store less than 1 TB of active storage in your account, your total charge will still be $5.99/month (plus any applicable taxes). See FAQ#4 for more details.
> With Wasabi minimum storage retention policy, minimum number of days are as follows:
> 90 days (default) for customers using Wasabi’s pay-as-you-go pricing model
Wasabi's not intended for small-scale use cases.
Re: Replacing Dropbox in favor of DigitalOcean spaces
#67I have a 50TB+ NAS in my garage rack. Which I'm not utilizing completely. I wonder if there is a market for renting out some of my storage for someone else's encrypted backups. Something like a website, where I can list my price/gb & connection speed -- or maybe people could swap. Maybe I want to store 5TB off site and I'm willing to let someone else store their 5TB on my server. The website would act as the middlema…
Siacoin and Filecoin are basically this; you can store small parts of files under contracts that give you crypto in return. Occasionally you'll get tested by the network to check if it's online, and you have the files you should have. A good use of crypto, though last time I looked the ROI wasn't great as a host.
That sounds more taxing on my connection than what I was thinking. Not really up for 100 connections, but if I'm matched up with 1 or 2 other users then that would seem ok.
Re: Replacing Dropbox in favor of DigitalOcean spaces
#68I have a 50TB+ NAS in my garage rack. Which I'm not utilizing completely. I wonder if there is a market for renting out some of my storage for someone else's encrypted backups. Something like a website, where I can list my price/gb & connection speed -- or maybe people could swap. Maybe I want to store 5TB off site and I'm willing to let someone else store their 5TB on my server. The website would act as the middlema…
The amount of liability you'd be taking on would make it absolutely not worth it for 2 customers and a few dollars a month in income.
On the opposite end, I'd trust Google or Dropbox with my encrypted backup much more than a rack in someone's garage on a home internet connection.
Re: Replacing Dropbox in favor of DigitalOcean spaces
#69When I read "Replacing Dropbox", reading about a 1 way sync system for backing up a single system isn't what jumps to mind. The magic of Dropbox is that it sync files across multiple computers and allows multiple people to share files. This doesn't do any of that. You can use Dropbox for that, but there are definitely cheaper/ more robust solutions.
Well to be fair the remote backup is the part that's hardest to recreate with a self-hosted solution.
Is it? I used to do something similar with a couple rsync commands. In fact I think the rsync solution is more robust because you can create incremental backups.
Re: Replacing Dropbox in favor of DigitalOcean spaces
#70Earlier quoted context omitted.
I agree with you. I should add a disclaimer that this is still being worked on. I will add what you proposed. Thanks for your input.
Always start all your bash scripts with set -e You'll never regret it and might be very very very happy it was there. And if you start with that, then as you work on the shell script, you'll be more likely to make the script be idempotent (checking for files before copying, checking for lines in files before appending/sed'ing etc.) Idempotent >> non-idempotent for "alter the state on an end point" things.
Also, "unofficial bash strict mode" is terrific, especially if you intend to distribute a script:
http://redsymbol.net/articles/unofficial-bash-strict-mode/
set -euo pipefail
IFS=$'\n\t'