Skip to content

Latest commit

 

History

History
85 lines (51 loc) · 2.66 KB

Readme.md

File metadata and controls

85 lines (51 loc) · 2.66 KB
Raw

Github Container Pulls Docker Pulls

SportEasy Calendar Connector

Generates ICS from SportEasy

Simple and rapid use

Go to https://sporteasy-calendar-connector.tbmc.ovh

Add SportEasy events to Google Calendar

  1. Click here:

FromUrl

  1. Paste generated default URL here

FromUrlPasteHere

Installation with Docker

Example docker-compose.yml

Application listen on port 5000.

The same image is available from 2 different registry:

Host Docker image
Github ghcr.io/tbmc/sporteasy-calendar-connector:latest
Docker Hub tbmc/sporteasy-calendar-connector:latest

How to use it

Populate .env

You need to populate .env with at least you SportEasy username and password. You can also add team_id to only have event of only one team instead of all your teams.

To get all team names and IDs you can use list_teams.py after populating username and password in .env.

Encode logins

With script

You can use env_to_base64.py script with .env populated.

Manually

Generate logins

Take json and transform it to base64, then url encode it

{
  "username": "...",
  "password": "...",
  "team_id": 123456
}

team_id is optional.

With my server

You can use mine, but at your own risk.

⚠️ Data in base64 are not ciphered.

https://sporteasy-calendar-connector.tbmc.ovh/api?data={base64Data}

You can add a parameter disable_save_login to disable saving of logins and password, but it deactivates links in event description to set present or absent. Without saving logins, it can not connect to SportEasy servers.

https://sporteasy-calendar-connector.tbmc.ovh/api?data={base64Data}&disable_save_login=True

Info

SportEasy block IPs from server providers, so you should have a domestic IP.