Open Timetable Scraper Server

The official server implementation for the Open Timetable Scraper (OTS).

This application serves as both the backend API and the frontend dashboard. It manages authentication, schedules scraping jobs via providers, stores timetable data, and exposes an API for other applications to consume.

Caution

⚖️ LEGAL DISCLAIMER & LIMITATION OF LIABILITY

This project is an independent open-source tool. It is NOT affiliated with, authorized, maintained, sponsored, or endorsed by:

• The IGENSIA Education Group / Compétences & Développement (C&D) and all its member schools (including but not limited to: EPSI, WIS, IFAG, IHEDREA, IDRAC, IET, SUP'DE COM, 3A, ESAIL, VIVA MUNDI, etc.), or the developers/operators of the WigorServices platform.
• YMAG (Groupe SEPTEO) (developers of NetYpareo), Simplon.co, or any other educational institutions using these platforms.

Scope of Non-Affiliation & Intellectual Property

This disclaimer applies to all current and future providers included in this package (including but not limited to @studentsphere/ots-provider-wigor and @studentsphere/ots-provider-netypareo). All trademarks, logos, and brand names are the property of their respective owners. Their mention here is strictly for identification and technical compatibility purposes and does not imply any association or endorsement.

Responsible Use & Compliance

• Educational Purpose: This tool is provided for educational purposes and to facilitate interoperability.
• User Responsibility: It is the end-user's sole responsibility to ensure that using these scrapers/providers complies with their specific institution's Terms of Service (ToS), internal regulations, and local laws regarding automated data access.
• Account Risk: The developer assumes no liability for any consequences resulting from the use of this tool, including but not limited to: account suspensions, IP bans, access blocks, or any disciplinary/legal actions taken by the aforementioned groups or institutions.

"As Is" Warranty & Service Changes

The software is provided "as is", without warranty of any kind. Since this tool relies on parsing third-party web structures and pages, functionality may break at any time due to updates on the official portals (including WigorServices and NetYpareo portals).

By using this package or its providers, you acknowledge and agree to these terms in full.

Features

• Multi-Provider Support: Seamlessly integrates with any OTS-compliant provider (like @studentsphere/ots-provider-wigor).
• Automated Scraping: Uses BullMQ and Redis to schedule and execute timetable scraping jobs in the background.
• User Authentication: Secure authentication via Better Auth.
• Modern Dashboard: React + Vite frontend for managing your schedules and settings.
• REST API: Exposes timetable data for third-party integrations.

Development

Prerequisites

• Node.js 20+
• pnpm
• Redis (required for job queues)

Installation

1. Clone the repository (if you haven't already):

   git clone https://github.com/studentsphere-app/ots-server.git
   cd ots-server

2. Install dependencies:

   pnpm install

3. Configure Environment: Copy the example environment file and fill in your details:

   cp .env.example .env

   Make sure your Redis instance is running and reachable via REDIS_URL.

4. Run the Development Server: This command starts both the Express API and the Vite frontend dev server.

   pnpm run dev

Self-Hosting

You can easily host your own instance of the OTS Server using Docker and Docker Compose. This is the recommended method for production.

Prerequisites

• Docker
• Docker Compose

Quick Start with Docker Compose

1. Create a directory for your instance and create a docker-compose.yml file:

   services:
     app:
       image: ghcr.io/studentsphere-app/ots-server:latest # Or build locally
       ports:
         - "3000:3000"
       environment:
         - NODE_ENV=production
         - DATABASE_URL=file:/data/database.db
         - REDIS_URL=redis://redis:6379
         # Security Secrets (Generate strong random strings for these!)
         - BETTER_AUTH_SECRET=your_super_secure_random_string
         - ENCRYPTION_KEY=32_byte_long_random_string_exactly
         
         # URLs (Change these to your domain in production)
         - BETTER_AUTH_URL=http://localhost:3000
         - FRONTEND_URL=http://localhost:3000
         
         # Email Configuration (Optional but recommended)
         - SMTP_HOST=smtp.example.com
         - SMTP_PORT=587
         - SMTP_USER=your_user
         - SMTP_PASS=your_password
         - EMAIL_FROM="OTS Server <noreply@example.com>"
       volumes:
         - ots_data:/data
       depends_on:
         - redis
       restart: unless-stopped
   
     redis:
       image: redis:alpine
       volumes:
         - redis_data:/data
       restart: unless-stopped
   
   volumes:
     ots_data:
     redis_data:

   Note: If you are building from source, you can use the docker-compose.yml provided in this repository.

2. Start the services:

   docker-compose up -d

3. Access the Dashboard: Open your browser and navigate to http://localhost:3000 (or your configured domain).

Environment Variables

Variable	Description	Default
PORT	The port the server listens on	3000
DATABASE_URL	Connection string for the database (SQLite by default)	file:/data/database.db
REDIS_URL	Connection string for Redis	redis://redis:6379
BETTER_AUTH_SECRET	Required. Secret key for session signing	-
ENCRYPTION_KEY	Required. 32-byte key for encrypting credentials	-
BETTER_AUTH_URL	The full URL where the auth server is reachable	http://localhost:3000
FRONTEND_URL	The full URL where the frontend is reachable	http://localhost:3000
SMTP_HOST	SMTP server host for sending emails	localhost
SMTP_PORT	SMTP server port	1025
SMTP_USER	SMTP username	-
SMTP_PASS	SMTP password	-

License

MIT