tim1mw / pycon_capture

Automated conference video capture and upload for PyconUK (and others)
4 stars 3 forks source link

Change filesystem structure #5

Open IanTaylorFB opened 5 years ago

IanTaylorFB commented 5 years ago

Currently the capture and upload filesystems are separate. We plan to combine these as described below.

Typical production code installation to /var/www/html/pycon_capture.

All video and other data files (including client secrets) will go into /var/www/data/... Within this, the following structure will be used:

/var/www/data/..
../config
../auth
../session_metadata
../video

config will contain the pycon_capture.yml configuration file, with conference-level settings. auth will contain the OAuth json files. session_metadata will contain the schedule data obtained from the website json endpoint. video contains all video files, as described further below.

The video structure will be

/var/www/data/video..
../live_stream
../<day>/edited_sessions
../<day>/more_editing_needed
../<day>/ready_for_upload
../<day>/could_not_start_upload
../<day>/completed_upload
../<day>/failed_upload

live_stream will contain the raw unedited live stream recordings All processed files are subdivided into <day> subdirectories. edited_sessions will contain the individual session video files, ready for checking. more_editing_needed will contain any files where further editing or checking is needed, for example audio/video sync issues. (This is effectively just a 'to-do' list.) ready_for_upload will contain all files that are ready to be uploaded to YouTube. could_not_start_upload will contain all files where we could not retrieve valid session metadata. completed_upload will contain all files where the upload was successful. failed_upload will contain all files where the upload was not successful.