Page Comparison

...

When Matterhorn the Avalon worker is running on a different server than Avalon and they don't share the same filesystem (and filesystem paths) for both the Rails web upload directory and dropbox, Avalon uses something called a working file path.  The working file path is the full path for the file itself, and is used to refer to a copy of the originally uploaded file to where Matterhorn Worker has access and at a path shared by both servers.  The working file path is stored on the MasterFile so that it can be cleaned up by a background job after the MasterFile has finished processing.

Image Added

encoding:
  working_file_path: '/srv/shared/ingest'

For example, if Matterhorn Worker is running on a different server and MatterhornWorker's ingest directory is '/srv/matterhornshared/ingest' and mounted on the Avalon server at the same location and Avalon's dropbox directory is '/srv/avalon/dropbox' then Settings.matterhornencoding.mediaencoding_file_path should be configured to be '/srv/matterhornshared/ingest'.  Note that Matterhorn's ingest directory needs to be mounted at the directories must be named the same location on both the Avalon and Matterhorn servers for Avalon to be able to ingest due to the use of absolute paths and not relative paths.  The working file path is only used when Settings.matterhorn.media_path is configured and is used in all of the ways ingest happens: web upload, web upload skip transcoding, web dropbox, web dropbox skip transcoding, batch ingest, batch ingest skip transcoding, and batch ingest pre-transcoded derivatives.  The working file path is stored on the MasterFile so that it can be cleaned up by a background job after the MasterFile has finished processing.  Note that this does not affect AWS configurations since they shouldn't have Settings.matterhorn.media_path setWorker server and the Avalon server since absolute paths are sent to Worker from Avalon.