Differences

This shows you the differences between two versions of the page.

--- operation:publishing [2016/03/27 11:44] – [Releasing workflow] derpeter
+++ operation:publishing [2017/11/13 10:41] (current) – derpeter
@@ Line 3: / Line 3: @@
 In general we are using [[https://media.ccc.de]] as primary publishing platform for our recordings. For [[https://events.ccc.de/2015/01/03/the-youtube-and-stream-dump-problem/|some reasons]] we are also publishing to [[https://youtube.com/user/mediacccde|youtube]]. We created a [[https://github.com/voc/publishing|publishing script]] that covers all two publishing destinations.
-== Deployment
+== Operation
-The publishing script is deployed on ''live.ber.c3voc.de'' in ''voc'' user home ''~/publishing''. Before starting releasing, you should follow the following steps:
+The publishing script is deployed on ''live.ber.c3voc.de'' in ''voc'' user home ''~/publishing''. It is executed by a SystemD Unit names publishing.
+The script receives all parameters needed for publishing from the tracker. There is no event specific configuration on the script side.
-  - Configure [[:c3tracker|tracker]]
+=== Folders & Permissions
-  - Start a screen session as ''voc'' user
-  - Pull current publishing script version: ''cd ~/publishing; git pull origin master''
-  - Add media publishing ssh key to ssh agent: ''ssh-add ~/.ssh/upload_key''
-  - Start publishing script: ''./script_H_media_ccc_upload.py''
-== Releasing workflow
+=== Offsite sub-format encoding
-  - Talk is in tracker state ''ready to release''
-  - The publishing worker should run in a loop on a machine that has local access to the video files
-  - The script need write permissions to the directory where the files are stored
-  - The script will collect all meta data needed and will create events and recordings on media.
-  - Depending on the settings the script will publish to media.ccc.de and / or YouTube
-  - If something goes wrong the ticket in the tracker should present a error message