media-frontend

This is an old revision of the document!


= media.ccc.de frontend

== update from git

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:

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

Usual workflow:

  • git co master
  • git pull origin # resolve conflicts
  • git push live # if this fails big problem
  • git co deployment-media.ccc.de
  • git rebase master
  • git push -f live

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

== get all torrent hashes 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 16:27
  • by mazdermind