Feature #8133
Develop a Symbiosis: community edition
Status: | New | Start date: | ||
---|---|---|---|---|
Priority: | Normal | Due date: | ||
Assignee: | - | % Done: | 0% | |
Category: | - | |||
Target version: | sid |
Description
…that strips out Bytemark specific stuff.
Discuss :)
--
Rajesh Joshi
Head of External Communications
Bytemark Hosting
t: 01904 890890
e: josh@bytemark.co.uk
w: bytemark.co.uk
History
#1
Updated by Steve Kemp about 5 years ago
Suspect there are only two parts of the code which are Bytemark-specific:
- The uplaod of backups.
- The upload of hostnames/dns.
Shouldn't be hard to strip out the latter - and providing that the user reads the documentation the former can be updated if rsync path is updated.
I'd love to see an S3 compatible backup solution though; I suspect that might be useful and valuable. The hard part is dropping in a new backend, and I think the correct solution might involve looking at alternatives to backup2l
.
#2
Updated by Patrick Cherry over 4 years ago
- Tracker changed from Bug to Feature
- Target version set to sid