Add a way to disable transit about headway HOT 3 CLOSED

So I guess this warrants a Config.ts to the frontend.

It would be extra nice if his can be a runtime config and changed without editing a separate file and rebuilding, though.

I see three options for that:

1. Configure using env vars: Read config.json values from a static URL. Add config.json.template to /etc/nginx/templates/ in Docker build and let nginx serve it from the envsusbst target.
2. Configure using env vars: Use sub_filter in nginx to replace some magic strings with the values.
3. Configure using file: Read config.json values from a static URL. Serve it from file like already done with bbox.txt.

I would go for 1 or 3.

from headway.

This is a really naive question, for which I apologize, but would it be feasible to have this be a run-time loadable module? Such that if a person didn't often use transit, but did once in a while, the transit module could be loaded (at, presumably, considerable one-time expense), and then flushed after some period (a couple of hours?) of inactivity, or when more pressing needs for that memory arose? From a social-responsibility perspective, having instances which are never able to supply transit directions, and thus make transit directions unpredictably available, would be a disincentive to transit use, which would be a bad thing.

from headway.

Not naive! The issue with that is building the OpenTripPlanner index requires a one-time cost in latency that's completely unacceptable for an end-user, and moveover the machine running the stack might not be able to spare the RAM to build the graph or run OTP.

from headway.