- #Spideroak delete account how to#
- #Spideroak delete account install#
- #Spideroak delete account trial#
Once it finally completes, go back to your local workstation to see if you can find your backup. I don’t know what SpiderOak is doing exactly but sometimes it can take several minutes to complete the syncing. The call to “SpiderOakONE –batchmode” will probably make this command run slowly. Hmm… perhaps you don’t want to wait at 5am just to test if the script works. It will run our backup script at 5am everyday. crontab -eĪdd the following line, save and exit: 0 5 * * * /home/dokku/backup_db.sh OUT_BACKUP 2>&1 To automate our DB backups, we’ll add a cronjob. Then we run SpiderOakONE with the –batchmode flag to make it do its thing and shutdown immediately after. Give the correct permission to the file: chmod +x /home/dokku/backup_db.shĪs you can see, we use our Dokku postgres plugin to dump our db and we gzip the result in our db_backups folder. usr/local/bin/dokku postgres:export myapp > "/home/dokku/db_backups/myapp-`date +%Y-%m-%d`.dump" Create a shell scriptĬreate a new file in /home/dokku and name it backup_db.sh. Great, SpiderOak is all configured! Time to setup our database backups. The output should look like this: Including.Ĭurrent selection on device #2: u'myapp-droplet' (local)ĮxcludeFile:/root/SpiderOak Hive/.Icon.pngĮxcludeFile:/root/SpiderOak Hive/Desktop.iniĮxcludeFile:/root/SpiderOak Hive/.directory Then we include this folder in SpiderOak: SpiderOakONE -include-dir=/home/dokku/db_backups Let’s create a folder for our DB backups mkdir /home/dokku/db_backups
Wait until the end of the syncing process.
Enter a descriptive name, something like myapp-droplet. Simply press Enter as suggested to set up a new device. To reinstall a device, enter the id (leave blank to set up a new device):ĭon’t type any number. You will have to provide your SpiderOak login info. What will we do? Simple, we just run the following command: SpiderOakONE -setup=. We must now configure SpiderOak but we don’t have any GUI on our server.
#Spideroak delete account install#
You’re now ready to install SpiderOak apt-get install spideroakone Look at it straight in the eye and IGNORE IT without showing mercy. If you get the following error: W: GPG error: release Release: The following signatures couldn't be verified because the public key is not available: NO_PUBKEY A6FF22FF08C15DD0 Open your sources.list file nano /etc/apt/sources.listĪnd add the following line at the end: deb release restricted Log to your DigitalOcean droplet by typing: ssh Note that if you don’t mind syncing your personal Hive on your DigitalOcean droplet, you can leave the option enabled. Still on your local workstation, go to your SpiderOak preferences: For this reason, we should disable the Hive Folder syncing. You put something personal in your Hive on your local computer and oops, it will be sent to your droplet! That sounds not very good to me. One problem of using the Hive for our backups is that it will sync everything. It is a convenient way to have things running quickly without configuring shared folders manually. All files added to the Hive folder of a device are automatically synced to the Hive folder in every other devices. SpiderOak creates the SpiderOak Hive folder in the installation process.
You can leave the default options for now: Next step is to register your local computer with SpiderOak.įinally, you will be presented a screen to select what you want to sync from your local computer to the cloud. You should be presented with the following screen: Then, choose the correct client for your distribution: On the SpiderOak page, click on downloads We will first install the client on our local workstation and create our account. Thanks to NoName in the comments for asking me to clarify this point. After that, the cost is $7 per month for 30 GB storage.
#Spideroak delete account trial#
UPDATE: Whilst SpiderOak is not free, they offer a 60-days free trial for 2GB storage (no credit card required). Their zero-knowledge architecture will make sure our data remains private. We will use SpiderOak to store our backups. It’s not a question of not having enough money to pay someone else, it’s because we are smart and resourceful! See, it already feels better when we see it in this light! We are freelancers (or small development teams) and we are used to get our hands dirty and do stuff by ourselves. Sure, you can enable weekly backups of your whole droplet on DigitalOcean (the cost is minimal), but for a database it is wiser to backup at least once a day.
If you haven’t read the first part, you should do it before reading any further.
#Spideroak delete account how to#
Now that we know how to setup a rails application using Dokku on a DigitalOcean droplet, it might be a good time to think about automating our database backups.
0 kommentar(er)
