# Automated Backups to other Destinations Besides Amazon S3
**URL:** https://meta.discourse.org/t/automated-backups-to-other-destinations-besides-amazon-s3/27017
**Category:** Feature
**Tags:** docker
**Created:** [Março 31, 2015, 10:00am UTC](https://meta.discourse.org/t/automated-backups-to-other-destinations-besides-amazon-s3/27017 "2015-03-31T10:00:04Z")
**Posts on this page:** 20
**Page:** 1
### Author:  [@Jonathan\_Wexler](https://meta.discourse.org/u/Jonathan_Wexler)
#### Post date: [Março 31, 2015, 10:00am UTC](https://meta.discourse.org/t/automated-backups-to-other-destinations-besides-amazon-s3/27017/1 "2015-03-31T10:00:04Z")
Continuing the discussion from [Hot off the presses, automated backup support!](https://meta.discourse.org/t/hot-off-the-presses-automated-backup-support/13805/2):
> [@Hot off the presses, automated backup support!](https://meta.discourse.org/t/hot-off-the-presses-automated-backup-support/13805/2):
>
> Might already be in the works, but will you extend this to, lets say, FTP backup? =)
I also will not use S3 - what is that - AWS? I would like to use Dropbox or even some other backup solution as I find AWS totally convoluted.
How can I create a process where backups are sent to other destinations?
I will have to experiment, but this was my initial concern.
---
### Author:  [@codinghorror](https://meta.discourse.org/u/codinghorror)
#### Post date: [Março 31, 2015, 10:01am UTC](https://meta.discourse.org/t/automated-backups-to-other-destinations-besides-amazon-s3/27017/2 "2015-03-31T10:01:41Z")
You can make automatic local (on your server) backups and download them from your web browser to whatever destination you like.
---
### Author:  [@Jonathan\_Wexler](https://meta.discourse.org/u/Jonathan_Wexler)
#### Post date: [Março 31, 2015, 11:52am UTC](https://meta.discourse.org/t/automated-backups-to-other-destinations-besides-amazon-s3/27017/3 "2015-03-31T11:52:17Z")
Okay that answers my question - thanks.
---
### Author:  [@riking](https://meta.discourse.org/u/riking)
#### Post date: [Março 31, 2015, 7:09pm UTC](https://meta.discourse.org/t/automated-backups-to-other-destinations-besides-amazon-s3/27017/4 "2015-03-31T19:09:35Z")
For SFTP/SCP, they’ll be dropped in `/var/discourse/shared/standalone/backups/default`.
---
### Author:  [@Jonathan\_Wexler](https://meta.discourse.org/u/Jonathan_Wexler)
#### Post date: [Abril 1, 2015, 12:38am UTC](https://meta.discourse.org/t/automated-backups-to-other-destinations-besides-amazon-s3/27017/5 "2015-04-01T00:38:50Z")
I still think it is too complicated to use non-Amazon storage. Someone should make a better solution for this. I have to automate the drops on the server and then script it to other services - is something like that correct?
So the steps are:
1. Automatic backups from the server to: /var/discourse/shared/standalone/backups/default
2. Then, I have to get some kind of API or token access to the other third party service.
3. Then script it through sftp or scp or any other secure protocol.
Why not just include an option to send to other storage services on this page?
---
### Author:  [@riking](https://meta.discourse.org/u/riking)
#### Post date: [Abril 1, 2015, 12:46am UTC](https://meta.discourse.org/t/automated-backups-to-other-destinations-besides-amazon-s3/27017/6 "2015-04-01T00:46:35Z")
> [@Jonathan\_Wexler](#):
>
> 1. Automatic backups from the server to: /var/discourse/shared/standalone/backups/default
Not quite what Discourse actually sees, but close enough.
> [@Jonathan\_Wexler](#):
>
> 2. Then, I have to get some kind of API or token access to the other third party service.
> 3. Then script it through sftp or scp or any other secure protocol.
Nope, you can skip #2. Just run a cronjob to grab the latest one.
---
### Author:  [@Jonathan\_Wexler](https://meta.discourse.org/u/Jonathan_Wexler)
#### Post date: [Abril 1, 2015, 12:56am UTC](https://meta.discourse.org/t/automated-backups-to-other-destinations-besides-amazon-s3/27017/7 "2015-04-01T00:56:39Z")
Ya seems simple to do actually.
Also, because Discourse is in a Docker container, can I just automate a container upload to Docker Hub periodically?
And a download sync of the Discource Docker container would be useful - this has me thinking of a much better solution that Amazon S3.
---
### Author:  [@riking](https://meta.discourse.org/u/riking)
#### Post date: [Abril 1, 2015, 12:58am UTC](https://meta.discourse.org/t/automated-backups-to-other-destinations-besides-amazon-s3/27017/8 "2015-04-01T00:58:24Z")
> [@Jonathan\_Wexler](#):
>
> Also, because Discourse is in a Docker container, can I just automate a container upload to Docker Hub periodically?
In order to do that, you need to:
- `./launcher bootstrap app` on a build server
- upload (or `docker save`) THAT container, which is specific to YOUR site
- download or `docker load` that container on the destination
It’s a lot of work for mostly no gain, except when you’re on a scale similar to the [discourse.org](http://discourse.org) hosting.
---
### Author:  [@codinghorror](https://meta.discourse.org/u/codinghorror)
#### Post date: [Abril 1, 2015, 2:52am UTC](https://meta.discourse.org/t/automated-backups-to-other-destinations-besides-amazon-s3/27017/9 "2015-04-01T02:52:15Z")
PRs are welcome in this area. If someone wants to build a FTP backup transfer plugin, or a Dropbox one, or Google Drive, that’d be fine.
---
### Author:  [@Jonathan\_Wexler](https://meta.discourse.org/u/Jonathan_Wexler)
#### Post date: [Abril 1, 2015, 3:36am UTC](https://meta.discourse.org/t/automated-backups-to-other-destinations-besides-amazon-s3/27017/10 "2015-04-01T03:36:10Z")
There should be a drop-drop to select which cloud storage to backup to automatically.
See screenshot below:
I followed how the Tagger plugin incorporation did not happen right, so when @codinghorror simply states to add it as a pull request it seems like he is pushing it aside, when, for example, the Tagger plugin was also really import and is still quite cumbersome to get working.
Something like automatic backups should be given a much higher priority.
I also feel features should be speced right here in this Discourse forum, not in GitHub, which, after all, is a separate website in reality.
If we map out the process, say in LucidChart, and just post a screenshot of it here, I think any software architect would understand how to build it.
@sam I have been a technical writer for many years, and the first thing to get clear is the language of the project, which is a lesson I learnt especially here in Montreal as we work in French and English and produce a lot of software.
It is very simplistic to think everyone wants to rely on Amazon storage when there are a lot of other very good providers, both US based, and worldwide.
Something like this:
And also an easy option to backup the whole Docker container to Docker Up should be done:
---
### Author:  [@sam](https://meta.discourse.org/u/sam)
#### Post date: [Abril 1, 2015, 3:49am UTC](https://meta.discourse.org/t/automated-backups-to-other-destinations-besides-amazon-s3/27017/12 "2015-04-01T03:49:12Z")
> [@Jonathan\_Wexler](#):
>
> By PR, do you mean “personal request”?
He means a Pull Request, which in turn mean is somebody cares to write the computer code to make it happen then we are fine with that.
---
### Author:  [@Jonathan\_Wexler](https://meta.discourse.org/u/Jonathan_Wexler)
#### Post date: [Abril 1, 2015, 4:53am UTC](https://meta.discourse.org/t/automated-backups-to-other-destinations-besides-amazon-s3/27017/13 "2015-04-01T04:53:40Z")
I submitted it to GitHub.
---
### Author:  [@codinghorror](https://meta.discourse.org/u/codinghorror)
#### Post date: [Abril 1, 2015, 5:06am UTC](https://meta.discourse.org/t/automated-backups-to-other-destinations-besides-amazon-s3/27017/14 "2015-04-01T05:06:42Z")
Sorry, misunderstanding, pull request means you do the work to build the feature by writing the code to implement it. Or paying someone else to.
---
### Author:  [@Jonathan\_Wexler](https://meta.discourse.org/u/Jonathan_Wexler)
#### Post date: [Abril 1, 2015, 5:25am UTC](https://meta.discourse.org/t/automated-backups-to-other-destinations-besides-amazon-s3/27017/15 "2015-04-01T05:25:34Z")
Why is it called pull request then? What is being pulled?
You mean you pull the code from Github, do the work, then submit it for community approval?
Peut-être on doit changer la terminologie un peut car les mots technique sont très mal construit pour les processus très technique.
---
### Author:  [@Mittineague](https://meta.discourse.org/u/Mittineague)
#### Post date: [Abril 1, 2015, 5:37am UTC](https://meta.discourse.org/t/automated-backups-to-other-destinations-besides-amazon-s3/27017/16 "2015-04-01T05:37:00Z")
It’s a github thing
IMHO if I am submitting something “push” does seem more appropriate.
Why is it `vagrant up` but not `vagrant down`?
Or if `vagrant halt` why not `vagrant start`?
Why do arrays start at “0” instead of “1”?
Ah, the logic of techies is more than enough to confound 😉
---
### Author:  [@Jonathan\_Wexler](https://meta.discourse.org/u/Jonathan_Wexler)
#### Post date: [Abril 1, 2015, 6:35am UTC](https://meta.discourse.org/t/automated-backups-to-other-destinations-besides-amazon-s3/27017/17 "2015-04-01T06:35:06Z")
Yes I completely agree. They should have read 0 : The Biography of a Dangerous Idea.
Here’s a pic, and let’s see if anyone can explain this with technical language:
---
### Author:  [@zogstrip](https://meta.discourse.org/u/zogstrip)
#### Post date: [Abril 1, 2015, 8:12am UTC](https://meta.discourse.org/t/automated-backups-to-other-destinations-besides-amazon-s3/27017/18 "2015-04-01T08:12:44Z")
> [@Jonathan\_Wexler](#):
>
> Why is it called pull request then? What is being pulled?
I recommend that you read the tutorial about [how to use pull requests](https://help.github.com/articles/using-pull-requests/).
The **TL;DR** is that you write some code and then ask the owners of the repository to pull your code in.
> [@Jonathan\_Wexler](#):
>
> Peut-être on doit changer la terminologie un peut car les mots technique sont très mal construit pour les processus très technique.
“`Pull request`” est un terme connu par **tous** les développeurs qui utilisent GitHub 😉
* * *
“`Pull request`” is a well known term by **all** the developers who uses GitHub 😉
---
### Author:  [@codinghorror](https://meta.discourse.org/u/codinghorror)
#### Post date: [Abril 1, 2015, 8:25am UTC](https://meta.discourse.org/t/automated-backups-to-other-destinations-besides-amazon-s3/27017/19 "2015-04-01T08:25:40Z")
To be clear, I think multiple backup destinations is a good idea, we just have no bandwidth to work on it at the moment and none of our paying customers are specifically asking for it.
---
### Author:  [@Falco](https://meta.discourse.org/u/Falco)
#### Post date: [Outubro 6, 2016, 2:35pm UTC](https://meta.discourse.org/t/automated-backups-to-other-destinations-besides-amazon-s3/27017/20 "2016-10-06T14:35:56Z")
[https://meta.discourse.org/t/discourse-backups-to-dropbox/51176?u=falco](https://meta.discourse.org/t/discourse-backups-to-dropbox/51176)
---
### Author:  [@chapoi](https://meta.discourse.org/u/chapoi)
#### Post date: [Dezembro 4, 2025, 11:35am UTC](https://meta.discourse.org/t/automated-backups-to-other-destinations-besides-amazon-s3/27017/21 "2025-12-04T11:35:49Z")