Closed cjcolvar closed 7 years ago
@cam156 Thanks for your comments. I think I responded or handled them in the last commit I pushed. @mjgiarlo Do you mind reviewing as well since you looked over things while they were WIP?
@cjcolvar You bet.
@mjgiarlo I think I took care of everything that isn't documentation or comments changes. I'll come back to those later today/tomorrow.
@cjcolvar OK, thanks! Ping me when it's :green_heart: and all ready to go.
@mjgiarlo Ready. Any additional changes you'd like to see?
@cjcolvar Taking one last look. Thanks for all the changes, and yr patience!
:tada: Thanks for the contribution! Great work. (Do you want/need a new release now that this is merged?)
The ActiveEncode runner allows using ActiveEncode within hydra-derivatives to generate derivatives using the adapters supported by ActiveEncode. Currently Amazon Elastic Transcoder is the only production ready adapter available but prototypes exist for zencoder and shingoncoder (FFmpeg through ActiveJob). The key differences between ActiveEncode and hydra-derivatives are:
In support of this a source file service and output file service have been added. The
RemoteServiceFile
takes the:source
option and calls a method of that name on the source object to determine the source file path or url to send to the processor. ThePersistExternalFileOutputService
creates anActiveFedora::File
with a url to the derivative output instead of storing the actual bit contents of the derivative in Fedora.Documentation is added for configuring and using the ActiveEncode runner with Amazon Elastic Transcoder which seems like the main use case for users at this point.
Thanks to @val99erie for a lot of this work.