Overview
The manual task of updating route information could be turned into an automated process.
Problem
Updating route information requires the deployment of the entire frontend codebase. This is a manual task, and the codebase (including presentation layer and business logic) need not be tied to the json data for routes.
Proposed Solution
A GitHub Actions workflow can run the main function in compare_scheduled_and_rt.py to generate new data.
The updated data can either live in the chn-ghost-buses repo or in s3.
The front end can fetch route data from a remote host instead of the local codebase. A proof of concept is here. By replacing the route json, the information data can be updated without a deployment.
Overview The manual task of updating route information could be turned into an automated process.
Problem Updating route information requires the deployment of the entire frontend codebase. This is a manual task, and the codebase (including presentation layer and business logic) need not be tied to the json data for routes.
Proposed Solution
compare_scheduled_and_rt.py
to generate new data.