How toyama170402/rishu-app works
Project type and purpose
• This is a multi-service, containerized monorepo that centers on a full-stack web application (“rishu-app” Next.js frontend) together with its supporting subsystems:
• A Go-based REST API (“syllabus-backend”)
• A TypeScript scraper/scheduler (“syllabus-scrape”)
• A static mock server for local HTML fixtures (“mock-page”)
• An additional syllabus-oriented frontend (“syllabus-frontend”)
• An NGINX reverse-proxy in front of all HTTP services
• A relational database (configured in the Go service)
• External data source (“risyu API” / kurisyushien.org)
File structure
• Top-level orchestrator:
• docker-compose.yml / docker-compose.dev.yml spins up all containers
• .devcontainer/… provides VS Code “Reopen in Container” definitions for each service
• Services under root:
• frontend/ → Next.js + React + MUI application (the rishu-app UI)
• syllabus-backend/ → Go module exposing HTTP routes, DB config, controllers, repositories, schemas
• syllabus-scrape/ → Node.js/TypeScript CLI with scheduler, Puppeteer/Cheerio scrapers, storage adapters
• mock-page/ → Dockerized HTTP server serving static HTML/TSV for local scraping tests
• syllabus-frontend/ → Another React/Remix-style app for browsing syllabus data
• nginx/ → Single Dockerfile + default.conf.template for routing
README for additional insights
• The README focuses on the “rishu-app” UI (frontend/)
• Technology stack: Next.js, React, MUI, TypeScript, Node.js, Docker, Dev Containers, Vercel, external risyu API
• Describes use cases: support for lottery-based course registration at Kanazawa University