media-frontend

media.ccc.de frontend

The frontend is generated by nanoc. To increase visibility the project is hosted on github: https://github.com/voc/media-frontend

However the deployment uses a seperate git server on koeln.media.ccc.de

gitolite@koeln.media.ccc.de:media-frontend

Setup local working repository:

  1. git remote set origin git@github.com:voc/media-frontend.git
  2. git remote add live gitolite@koeln.media.ccc.de:media-frontend
  3. git co master
  4. git reset –hard origin/master # (dangerous)

Usual workflow:

  1. git co master
  2. git pull origin # resolve conflicts
  3. git push live # if this fails big problem
  4. git co deployment-media.ccc.de
  5. git rebase master
  6. git push -f live

Never push the deployment-media.ccc.de branch to github, as it contains database passwords and such.

We still use the mirrorbrain generated torrents. So they don't exist in the filesystem, but are generated on the fly with matching webseeds.

 curl -L http://cdn.media.ccc.de/INDEX.gz | zgrep congress/2014 | ruby -ane 'puts "http://cdn.media.ccc.de/#{$F[2][2..-1]}.torrent"' 

TODO: remove mirrorbrain torrents and have real torrents in the filesystem, generate with large enough chunk size, but not to large for streaming, or remove webseeds and use dedicated seed boxes.

  • media-frontend.1426436860.txt.gz
  • Last modified: 2015/03/15 17:27
  • by mazdermind