Sirius: CTU Time management API

Build Status Code Climate Coverage Status Inline docs Dependency Status

Sirius is a Timetable management API, which is used at CTU FIT to transform regular timetables into accurate calendars. Main Sirius output are calendar events and their collections (calendars). Same events can be viewed from different perspectives, creating different calendar types (personal, room or course calendar).

Main timetable data source is KOS IS, which is accessed via KOSapi. Timetables from KOS are then converted to events according to scheduling rules and exceptions stored in local Sirius database. Currently supported output data formats are JSON (for client apps) and iCalendar (for users).

API documentation

Documentation of resources which Sirius provides is currently available here.

Looking for help?

If you need help with adding you personal calendar to the calendar software you are using, check out our wiki tutorial page.

If you have an issue with your personal calendar or any other problems, feel free to use project issues on Github or you could just message us directly.

Suggestions, ideas and contributions

We are welcome to suggestions and ideas about this project. Please use project issues to discuss it if you have one.

If you feel you could improve project in some way, you can fork this repo and send a pull request with your change. If you consider adding a new feature or significantly changing behaviour of an existing one, it would be nice to discuss it with project maintainers beforehand, otherwise there is a possibility that your pull request might not get accepted.


After cloning this repo, run script/setup to bootstrap your configuration. This will create .env file in project root with reasonable defaults that you can change after that.


  • Ruby/MRI 2.3+
  • PostgreSQL 9.5+
  • ElasticSearch 1.* (not mandatory, used only for /search resource)

Environment variables

Variables put into .env file will be automatically loaded by Foreman.

You will need an OAuth 2.0 credentials (for KOSapi and Usermap API) from the Apps Manager and local PostgreSQL database and ElasticSearch. If you don’t need the /search resource, then you can omit ElasticSearch (just put any URI into ELASTIC_URL to pass check).


Running server and rake tasks

To start the API server, just run foreman start. If everything is configured properly, server should start and be accessible on port 5000 by default.

To load parallels from KOSapi and and schedule them, call foreman run rake sirius:events. Or you can call individual tasks:

  • sirius:events:import - fetches parallels from KOSapi to local database
  • sirius:events:import_students - fetches students assigned to stored parallels
  • sirius:events:plan - plans stored parallels
  • sirius:events:assign_people - assigns people (students and teachers) to planned events