Contact
MenuClose
Back to Work

Automation / Web App · 2025

Course Monitor

An open seat, without the constant refreshing.

THE PROJECT

Personal project · December 2025

MY CONTRIBUTION

Solo developer

The idea.

A full class meant checking the same page again and again. I built a monitor to watch for an opening instead.

The work.

I built the Python/Selenium checks, Supabase history, and email alerts, with a dashboard to follow course status.

The result.

9 sections · every 2 minutes · ~2 months. Used for my Spring 2026 registration.

Recorded seat checks for an individual section.
How it works

I developed a Python/Selenium workflow that checked nine course sections every two minutes for approximately two months. Supabase kept the check history, and email alerts brought openings back to me without constant refreshing.

Tools Python · Selenium · Supabase · Email

  • Separated repeated availability checks from historical records and email notifications.
  • The repository includes a web dashboard, monitoring controls, and course/status/history API routes.
  • A Dockerfile packages the application; configuration stays separate from the monitoring logic.

Selenium checks → Python logic → Supabase history → Email alerts

The hosted dashboard shows recorded history. Run the monitor locally for live checks and seat-opening email alerts.