-
Notifications
You must be signed in to change notification settings - Fork 28
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
3x: Allow homarus to use faststart #170
3x: Allow homarus to use faststart #170
Conversation
Cherry-pick fastart code to 3.x
b458f82
to
78501e3
Compare
Fix fixture file path Fix fixture file path
78501e3
to
8975498
Compare
I spun up the new islandora-playbook is Crayfish 3.x and then applied this PR. The video derivative didn't work and the logs show:
|
Shouldn't we be using a temp directory instead? Or, even better, something configurable? |
Codecov ReportBase: 76.67% // Head: 75.55% // Decreases project coverage by
Additional details and impacted files@@ Coverage Diff @@
## 3.x #170 +/- ##
============================================
- Coverage 76.67% 75.55% -1.13%
- Complexity 158 159 +1
============================================
Files 6 6
Lines 583 589 +6
============================================
- Hits 447 445 -2
- Misses 136 144 +8
Help us with your feedback. Take ten seconds to tell us how you rate us. Have a feature suggestion? Share it here. ☔ View full report at Codecov. |
So, question for the @Islandora/committers, am I being paranoid with my discomfort that we are dropping these processing files in a directory that it publicly accessible to anyone who can reach the Crayfish webserver? I mean, sure, Isle doesn't expose the Crayfish containers to the public web, but that doesn't mean others won't, and someone can keep pinging crayfish.example:8000/homarus/static/ to see what files are in process, even if they will be removed once they get shipped back to Drupal. Normally our derivatives will be publicly available anyway, but some will be subject to restrictions and that just feels like a security gap. Let me know if I'm being overly paranoid and I'll smash the green button. |
Honestly, probably worth bringing up on the tech call. |
Any reason why we shouldn't use a system temp directory instead of a public one? We are sending the binary back in the response, not a download link... |
Ideally, I think, we would be using unnamed/anonymous files similar to what ... though that's not to say that having the target file system used as configuration could not be useful, and may be something of a moot point if we do indeed need to pass a file name to ffmpeg (which... may not be 100% necessary? For example, running things on CLI, redirecting things to/from files can be handled more or less transparently, behind the scenes managing to deal with the files directly... whether or not things via |
I think making the directory configurable makes sense. That way, people can decide if they need it to be a public or a private directory and handle it themselves. |
Is this ready to test again, @bibliophileaxe? |
This is ready for review now. |
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.
👍 It works, but I don't have a fragmented MP4 file to test with.
Rebase with 3.x
Original Issue: Islandora/documentation#2162