Media Encoding Server
credentials.conffile with the WordPress and Network storage credentials (Please note the syntax - no spaces and your user and password wrapped in double quotes.):
/System/Library/LaunchDaemonsand give it the proper permissions: 644 / root:wheel. This allows the watch processes to be run automatically.
- From the terminal in the directory these scripts are located, run
encoding-server, or reboot
The watch directories are hardcoded into the
encoding-server script. The basic structure
looks like this:
``` /FTP /<campus_short_name> ```
<campus_short_name> is RHO, RHMV, etc. Once received, they are stored in an Output and Source folder within the campus short name folder within the
STOREPATH directory, as defined in the
Below is an explaination of the watch/encode/upload process.
- The scripts start watching the FTP folders
- After the file is uploaded, the FTP server renames it, which triggers the watch
- The process scripts are then triggered and find the most recent file
- The file is then converted using ffmpeg into a streaming video file as well as an mp3.
- When the encoding process completes, the source moved
Sourcefolder, and the converted files are moved into the
Outputfolder. These folders are explained in the Directory Structure section.
- Finally, the two output files are uploaded to WordPress
- Remove all hardcoded stuff, like paths to network drives
- Create a start/stop action: