duplicity-talk
[Top][All Lists]
Advanced

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

Re: [Duplicity-talk] [PATCH] adds prefix to swift backend


From: Remy van Elst
Subject: Re: [Duplicity-talk] [PATCH] adds prefix to swift backend
Date: Wed, 18 May 2016 09:37:08 +0200
User-agent: Mutt/1.5.23.1 (2014-03-12)

Would it be possible to also take a look at Large object support:

http://docs.openstack.org/developer/swift/overview_large_objects.html

for both the metadata as wel as the actual file archives uploaded?


On Wed, May 18, 2016 at 06:51:44AM +0000, Scott McKenzie via Duplicity-talk 
wrote:
>    Hi**Ghozlane
>    Thanks for your contribution.** I have ported it to the Azure backend
>    (which is based on the swift backend).
>    Could you please create a new branch in Launchpad**with your patch**and
>    propose it for merging?** It is more likely to make it's way in to
>    duplicity this way.
>    -Scott
>    On Mon, 9 May 2016 at 22:15 Ghozlane Toumi <address@hidden> wrote:
> 
>      Hi all,
>      Right now duplicity's swift backend only accept a container as target
>      (swift://container)
>      trying to use a prefix / pseudo folder (swift://container/backup/path )
>      results in a JSON exception.
>      This patch adds the abiliy to use path in the swift backend, in order to
>      have multiple backups to the same container neatly organized.
>      It borrows some code from the S3 backend, and is quite unobtrusive .
>      Ghozlane
>      _______________________________________________
>      Duplicity-talk mailing list
>      address@hidden
>      [3]https://lists.nongnu.org/mailman/listinfo/duplicity-talk
> 
> References
> 
>    Visible links
>    1. mailto:address@hidden
>    2. mailto:address@hidden
>    3. https://lists.nongnu.org/mailman/listinfo/duplicity-talk

> _______________________________________________
> Duplicity-talk mailing list
> address@hidden
> https://lists.nongnu.org/mailman/listinfo/duplicity-talk

Attachment: signature.asc
Description: PGP signature


reply via email to

[Prev in Thread] Current Thread [Next in Thread]