media-frontend

Differences

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

Link to this comparison view

Both sides previous revision Previous revision
Next revision
Previous revision
Last revisionBoth sides next revision
media-frontend [2015/01/11 16:22] mmmedia-frontend [2015/03/15 17:27] – remote mazdermind
Line 1: Line 1:
 += 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.
 +
 +<code> 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"' </code>
 +
 +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.txt
  • Last modified: 2018/09/11 11:15
  • by derpeter