Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Propose upstream change to duplicity so this module can be used with it #2

Open
Gu1 opened this issue Nov 29, 2014 · 2 comments
Open

Comments

@Gu1
Copy link
Owner

Gu1 commented Nov 29, 2014

https://code.launchpad.net/~bruno-poirier/duplicity/duplicity/+merge/243218

@Gu1
Copy link
Owner Author

Gu1 commented Nov 30, 2014

Oh, sorry @adrien-delhorme, I saw too late about your own proposed merge for this. So I withdrew mine.
Both were really similar anyway.

Why make a separate backend just for HubiC though ? IMHO duplicity should have only one pyrax backend that can be configured to use any identity module and credential file.

@adrien-delhorme
Copy link

I shared your opinion about making a separate backend for hubic, but when I asked duplicity team (https://answers.launchpad.net/duplicity/+question/256130), Kenneth Loafman answered that it "make sense to make a new backend for Hubic. It would give better isolation.". So, why not.

My branch has just been merged this afternoon onto duplicity project!
And I'm currently working on a duplicity port for Synology DSM.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
Development

No branches or pull requests

2 participants