#2962 - Allow backup to use cdn_transfer mechanism
| Identifier | #2962 |
|---|---|
| Issue type | Feature request or suggestion |
| Title | Allow backup to use cdn_transfer mechanism |
| Status | Closed (rejected) |
| Tags |
Type: Cloudification (custom) |
| Handling member | Chris Graham |
| Addon | backup |
| Description | Call cdn_transfer hooks from the backup system, to possibly copy a backup file to one of the configured CDN services. This is effectively automated off-site backup.
(e.g. to Dropbox, if #1392 is implemented) The CDN transfer hooks decide, based on paths, what would syndicate. So it would be configured by having exports/backups in the path. Probably that should be a default. Consider also stripping out the direct support the backup system has for backing up to FTP, and make this code into a cdn_transfer hook too. That way anything can benefit from the same system. |
| Steps to reproduce | |
| Related to | #1392 - Adding images from Photobucket, Flickr and Perhaps Facebook |
| Funded? | No |
The system will post a comment when this issue is modified (e.g., status changes). To be notified of this, click "Enable comment notifications".


Comments
If we want it stored on shared storage, we can do that with NFS already. We just mount it correctly. Even S3 can be mounted using FUSE.
It's best to leave cdn_transfer just for specifically transferring uploads to edge networks / for people who don't have enough disk space for user uploads and cannot set up FUSE.