media.ccc.de

(cdn.)media.ccc.de a collection of servers hosting our recordings. It was also the name of the software we run there which is now called Voctweb, don't get confused. It's currently running at https://media.ccc.de with five servers, as well as a couple of sponsored mirrors run by third-parties.

koeln.media.ccc.de (CDN Master) and

app.media.ccc.de (Rails Application Server) and

berlin-ak.ftp.media.ccc.de (Mirror)

berlin.media.ccc.de (Mirror) not in use anymore.

dortmund.media.ccc.de (Mirror)

There are also a number of Mirrors provided by external entities.

The source code can be found on:

https://github.com/voc/voctoweb

Just for reference, here are the old sources before the merge of front and backend

https://github.com/voc/media-frontend

https://github.com/cccc/media-backend

More about it's inner works are explained in the Froscon9 talk "Konferenzorganisation in Ruby" by Mario Manno.

Maintainance

https://video.pads.ccc.de/media-todo here we collect things that need to be fixed in concern of the content (NOT the software)

Software issues are trackt in the github issue tracker

Naming

upload-frontend: (not jet implemented) external frontend for enduser uploads

media-backend: active admin interface to manage conferences, events, recordings and news

media-frontend: media.ccc.de

Administration (internal)

Goaccess Stats

https://voc@app.media.ccc.de/stats/nginx.html

https://voc@koeln.media.ccc.de/stats/nginx.html

Mirror Brain

neue_mirrors_hinzufuegen, add new mirrors, example emails

Managing containers

Database container pinky

Mirrorbrain container brain

Elastic Search container snowball

Mirror statistics

http://ftp.fau.de/cgi-bin/show-mirror-status.cgi

http://ftp.fau.de/cgi-bin/show-ftp-stats.cgi

http://mirror.eu.oneandone.net/info.html

https://mirror.netcologne.de/munin/netcologne.de/mirror.netcologne.de/index.html

https://ftp.darmstadt.ccc.de/mrtg/

Mirror contacts

see restricted page: mirror contacts

IP Logging

(Stand: 21.05.2018 meise)

koeln.media.ccc.de

nginx: /16 Prefixe

rsync: /32

vsftp: /32

mirrorbits: nix

app.media.ccc.de

nginx:

access: /16 Prefixe

error: /32

rails app via puma: /32

berlin.media.ccc.de

nginx: /32 (teilweise /16)

rsync: /32 via syslog

Development-Umgebung aufsetzen

# for ubuntu and debian one might want to install vagrant from upstream
# (https://www.vagrantup.com/downloads.html), because of a packaging bug:
# https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=818237
$ sudo apt-get install vagrant virtualbox
$ vagrant plugin install vagrant-hostsupdater
$ vagrant up
$ vagrant ssh -c 'cd /vagrant && ./bin/update-data'
http://media.ccc.vm:3000/ <- Frontend
http://media.ccc.vm:3000/admin/ <- Backend
Backend-Login:
Username: admin@example.org
Password: media123

Subtitles-Support für ein Event anknipsen

Wenn auf ein Event gesubtitelt wird, kann dafür Support in Media angeknipst werden. Dadurch werden auf der Download-Seite weitere Links zum Subtitling-System aktiviert mit der Bitte beim Schreiben zu helfen.

Dazu im Media-Backend das Metadata-Feld, welches JSON akzeptiert, wie folgt füllen:

{
"subtiles": true
}

Testi-Deployment

See https://github.com/voc/voctoweb for instructions

bundle exec cap staging $*

Produktiv-Deployment

wird auf einer eigenen Seite Produktiv-Deployment beschrieben.