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

How Should Multiple Libraries be handled #1067

Open
gabriel-vanzandycke opened this issue Jan 27, 2025 · 3 comments
Open

How Should Multiple Libraries be handled #1067

gabriel-vanzandycke opened this issue Jan 27, 2025 · 3 comments

Comments

@gabriel-vanzandycke
Copy link

First-of-all: thank you for this awesome software!

I tested docker icloudpd/icloudpd:latest on my OMV NAS to backup my photos library, and I would like to receive guidance on how to best handle multiple libraries to backup my shared library as well as my family members libraries.

From reading the documentation, it seems only one library can be used by icloudpd.

What would be the recommended way to backup the different libraries from the same user ? Is it possible to have the command icloudpd relaunched with a rotating list of libraries within the container ?

For the other users libraries, is there no better option than running one container per user ?

Thanks

@AndreyNikiforov
Copy link
Collaborator

You are right, to download assets using different configurations (accounts, libraries etc) one has to use multiple icloudpd runs (sequential or concurrent)

@gabriel-vanzandycke
Copy link
Author

Are there plans on handling both personal and shared libraries from a single call to icloudpd ?
I see there's a single library_object = icloud.photos.libraries[library] but we could naively iterate through a list of library_objects. Who is best placed to make such decision?

@AndreyNikiforov
Copy link
Collaborator

Are there plans on handling both personal and shared libraries from a single call to icloudpd ?

I do not have immediate plans to support multiple accounts/albums/libraries/etc.

Who is best placed to make such decision?

Since we identified the need, next step is to get commitment for the implementation. Then we can discuss smaller pieces as RFCs and/or PRs.

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

No branches or pull requests

2 participants