-
Notifications
You must be signed in to change notification settings - Fork 2.9k
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
Migration: Backend, Rake file, Photos import #8298
Conversation
15a1421
to
7fe914c
Compare
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Thanks for the separate PR 🍪
8c9aab6
to
73f556b
Compare
73f556b
to
6a9c14d
Compare
@Flaburgan @SuperTux88 I've sent some changes. What else is a MUST to change here? |
6a9c14d
to
6be7dd1
Compare
6be7dd1
to
6dc7c1e
Compare
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
So there is still the security problem with importing photos. But I'm fine with excluding photos import from this PR, but then it needs to be removed from here, since the current state is an active security problem.
I've also created diaspora/diaspora_federation#119 for the federation part of the photos-migration, to tell other pods the new path so they can migrate photos on bulk and don't need a message for every single photo. If there are conflicts with filenames, where a photo from the archive can't be imported, it either needs to be deleted (and then also federate the deletion), or be imported on a different filename (and then it would need to federate the updated filename with a single photo message). But since I don't expect many conflicts, this should be fine, but it still needs to be handled correctly.
6dc7c1e
to
ae1d4ef
Compare
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
The PR still contains the photo import logic including the security problem, if you want to move the handling of photos to another PR (which I'm fine with), it needs to be removed here.
And besides a few small other things I think this is looking good. 👍
ae1d4ef
to
c570dff
Compare
Fixes #8255 |
If a photo with the same filename already exists, generate a new random filename, and re-federate the photo with that filename. This ensures users can't modify their archive to overwrite other users photos.
c570dff
to
d3c2407
Compare
Looks good to me ! 👍🏻 |
Merged, thanks for the initial work and for the fast review of my changes to it @tclaus 🍪 |
This is just the backend part extracted from the larger Upload Migration PR #8274
All UI stuff relies on this backend.
Rake file for Command line Import is included. I hope that with this smaller PR (based on the latest development) we can let thinks work faster.
@Flaburgan
Salutations, mon ami.