brackup-restore config file access

[Kostas Chatzikokolakis]

Damn, after countless times entering those keys I was this close from
learning my 60 character amazon secret key by heart. Now you ruined it.

Seriously, awesome patch, makes the world a better place to live :)

Speaking of annoying things, each time I do a gc I watch brackup-restore
downloading hundreds of megabytes of .brackup files, while the same
files already exist on my disk. It would be great if brackup-restore
could take as an argument the directory of the local .brackup files, and
avoid downloading files that are already there. The filename is
different, by we can find the timestamp from the local .brackup file.
Anyway, not that important, but a bit annoying.

Kostas

PS. Still haven't found the time to work on the lowmem patches, but I will.



Gavin Carr wrote:
> brackup-restore is supposed to not require a brackup config file,
> and ignores it even if it's available (see doc/design-decisions.txt).
> 
> I've just committed a patch to allow brackup-restore targets to 
> access their section of the config file (if it's available), which
> allows you to do restores without having to enter passwords (if the
> original config file is available).
>  
> Only the ftp target has been updated so far, but that seems to work 
> nicely. I'll update the others tomorrow.
>
> A minor change required to support that was including the target 
> name in the brackup metafile metadata ('TargetName'), so that we 
> know which section of the config file to load for restores.
> 
> Cheers,
> Gavin
> 
>