This repository is private.
All pages are served over SSL and all pushing and pulling is done over SSH.
No one may fork, clone, or view it unless they are added as a member.
Every repository with this icon (
) is private.
Every repository with this icon (
) is private.
This repository is public.
Anyone may fork, clone, or view it.
Every repository with this icon () is public.
Every repository with this icon (
) is public.
Executables
blanket-cfg
blanket-cfg could be moved to a more traditional Ruby class which would allow for better testing, especially since I’m not 100% clear what the ultimate target for this executable will be.
Brainstorming
Right now, the command to get blanket set up is:
blanket-cfg --task=taskname --source=Subversion --sink=S3I am wondering whether I’d rather have some syntax like
blanket configure taskname -o Subversion -i S3then
blanket tasknameto actually perform the backup. I am wondering if this will work, though, considering the directory based nature of the config setups.
