How eastsidepreparatoryschool/epschedule works
Project type and purpose
• EPSchedule is a full-stack, schedule-delivery web application for Eastside Preparatory School.
• Backend: Python code running on Google App Engine (GAE).
• Frontend: Polymer-based static assets (HTML/CSS/JS).
• Data store: Firebase Realtime Database (and possibly Cloud Storage for photos/keys).
• Auxiliary: cron jobs for periodic schedule updates and a set of Python scripts for data crawling/formatting.
File structure
• Top-level configuration:
• app.yaml, cron.yaml (GAE service + cron definitions)
• firebase.json, database.rules.json, .firebaserc (Firebase config)
• .github/workflows/*.yml (CI: tests, deploy)
• Backend code:
• main.py (entry point, HTTP handlers)
• app.py, update.py, scripts/*.py (data-gathering & upload utilities)
• cron/ (scheduled tasks + unit tests)
• requirements.txt (Python dependencies)
• Frontend assets:
• static/ (Polymer components: js, css, html, images, favicon)
• templates/ (Jinja/HTML templates served by GAE)
• Data/testing artifacts:
• data/*.json (master_schedule & test fixtures)
• main_test.py, cron/test_*.py (pytest suite)
README for architectural hints
• Mentions GAE + Polymer.
• Service account credentials are used to read “schedules, photos, and crypto keys” from GCP.
• CI via GitHub Actions runs pytest and deploys to App Engine.
• Scripts automate master schedule crawling and uploading.