Skip to content
Switch branches/tags
This branch is up to date with master.

Latest commit


Git stats


Failed to load latest commit information.
Latest commit message
Commit time
  webfrontend, meta data editor and API.

Build Status Code Climate


Every talk (alias event, in other systems also called lecture or session) is assigned to exactly one conference (e.g. the congress or lecture series like datengarten or openchaos) and consists of multiple files alias recordings. These files can be video or audio recordings of the talk in different formats and languages (live-translation), subtitle tracks as srt or slides as pdf.

Public GraphQL API

The newest API endpoint is at, implementing a GraphQL endpoint with Apollo Federation. This allows clients to only request the attributes they need, while all data needed per screen can be fetch in a single request. We tried to clean up the type names and call talks lecture and files assets (previously known as recordings). Please create issues if you are missing anything.

Example query:

query LectureQueryExample {
  lectureBySlug(slug: "36c3-10652-bahnmining_-_punktlichkeit_ist_eine_zier") {
    videos {


The public API provides a programmatic access to the data behind Consumers of this API are typically player apps for different ecosystems, see for a 'full' list. The whole API is "discoverable" starting from ; Available methods:


The id's are internal database ids, not to be confused with remote talk ids (alias pentabarf/frab id), e.g. which is also accessible via Same for conferences: is the same response as


curl -H "CONTENT-TYPE: application/json" http://localhost:3000/public/conferences

The resulting JSON will contain URLs to each of the individual conferences.

Additionally the API for events and recordings uses RFC-5988 HTTP header based pagination to reduce the server load.

curl -H "CONTENT-TYPE: application/json" "http://localhost:3000/public/events?page=10"

Private REST API

The private API is used by our (video) production teams. They manage the content by adding new conferences, events and other files (so called recordings). All API calls need to use the JSON format. An example API client can be found as part of our publishing-script repository: . The api_key has to be added as query variable, or in the JSON request body.

Most REST operations work as expected. Examples for resource creation are listed on the applications dashboard page.

Create conference

You can use the API to register a new conference. The conference acronym and the URL of the schedule.xml are required. However folders and access rights need to be setup manually, before you can upload images and videos.

curl -H "CONTENT-TYPE: application/json" -d '{
  }' "http://localhost:3000/api/conferences"

Create event

To add event (e.g. a talk or lecture) the conference it is part of via acronym, and define generate a random guid. You can add images to an event, like the poster image. For an explanation what the timeline_url and thumbnails_url parameters are, see

curl -H "CONTENT-TYPE: application/json" -d '{
    "acronym": "frab123"
  }' "http://localhost:3000/api/events"

Update event

curl  -i -X PATCH -H "CONTENT-TYPE: application/json" -d '{
      "tags": ["foo", "bar", "baz", "2018"]
  }' "http://localhost:3000/api/events/1c4d8ad8-e072-11e8-981a-6c400891b752"

Create recording

Recordings are added by specifying the parent events guid, an URL and a filename. The recording length is specified in seconds.

curl -H "CONTENT-TYPE: application/json" -d '{
  }' "http://localhost:3000/api/recordings"


Create news items


Update promoted flag of events by view count


Update view counts of events viewed in the last 30 minutes


Set up development environment

A convenient way to set up an environment for developing voctoweb is Docker.

First, install Docker and Docker Compose – you will probably find them in your distribution's package manager.

Then, clone this repository, make it your working directory, and run the following command:


You can now reach the voctoweb frontend at The backend is at, with the default username and the password media123. You can stop the running containers using Ctrl-C. To start them again, just run docker-compose up.

The whole application directory is mounted into the containers, so all changes you make to the files are reflected inside the application automatically. To run commands inside the voctoweb container, run docker-compose run voctoweb $COMMAND. If you ever need to rebuild the containers (because of new dependencies, for example), run the docker-compose build command again.

Image and video files in docker/content are tried first, if missing live data from is used.

Install for Production

Ruby Version

ruby 2.6.0


  • redis-server >= 2.8
  • elasticsearch
  • postgresql
  • nodejs

Quickstart / Development Notes

## for ubuntu 15.10

# install deps for ruby
sudo apt-get install git-core curl zlib1g-dev build-essential libssl-dev libreadline-dev \
libyaml-dev libsqlite3-dev sqlite3 libxml2-dev libxslt1-dev libcurl4-openssl-dev \
python-software-properties libffi-dev libgdbm-dev libncurses5-dev automake libtool bison

# install deps for voctoweb
sudo apt-get install redis-server libpqxx-dev

# install node.js
sudo apt-get install nodejs

# install rvm
gpg --keyserver hkp:// --recv-keys 409B6B1796C275462A1703113804BB82D39DC0E3 7D2BAF1CF37B13E2069D6956105BD0E739499BDB
\curl -O
\curl -O
gpg --verify rvm-installer.asc rvm-installer
bash rvm-installer stable
source ~/.rvm/scripts/rvm

# install ruby 2.6.0
rvm install ruby-2.6.0

# install bundler
gem install bundler

# postgresql setup
sudo -u postgres -i
createuser -d -P voctoweb

# obtaining & setting up a voctoweb instance
git clone
cd voctoweb
bundle install
rake db:migrate
rake db:fixtures:load

Run Development-Server manually

source ~/.rvm/scripts/rvm
rails server -b

# done
http://localhost:3000/ <- Frontend
http://localhost:3000/admin/ <- Backend
  Password: media123

Production Deployment Notes

Copy and edit the configuration file config/settings.yml.template to config/settings.yml.

You need to create a secret token for sessions, copy env.example to .env.production and edit.

Asset creation

Compile your assets with RAILS_ENV=production bin/rails assets:precompile

Database Creation & Fixtures import

Setup your database in config/database.yml needed.

rake db:setup

Services (job queues, cache servers, search engines, etc.)



#!/usr/bin/env puma

directory '/srv/www/media-site/current'
rackup "/srv/www/media-site/current/"
environment 'production'

pidfile "/srv/www/media-site/shared/tmp/pids/"
state_path "/srv/www/media-site/shared/tmp/pids/puma.state"
stdout_redirect '/srv/www/media-site/current/log/puma.error.log', '/srv/www/media-site/current/log/puma.access.log', true

threads 4,16

bind 'unix:///srv/www/media-site/shared/tmp/sockets/media-site-puma.sock'
bind 'tcp://'

workers 2

on_restart do
  puts 'Refreshing Gemfile'
  ENV["BUNDLE_GEMFILE"] = "/srv/www/media-site/current/Gemfile"

First Login

Login as user with password media123. Change these values after the first login.


voctoweb – the frontend and backend software behind




No releases published


No packages published