bus

nyc-bus-transit-nearby-go-postgres-redis-leaflet

🚀 Mobile web app for discovering public transit in NYC. 🚀

https://github.com/coding-to-music/nyc-bus-transit-nearby-go-postgres-redis-leaflet

From / By Brian Seitz https://github.com/brnstz/bus

https://github.com/brnstz/bus

Environment variables:

GitHub

git init
git add .
git remote remove origin
git commit -m "first commit"
git branch -M main
git remote add origin git@github.com:coding-to-music/nyc-bus-transit-nearby-go-postgres-redis-leaflet.git
git push -u origin main

Beta version: https://token.live

Dependencies

• Go 1.6+
• PostgreSQL 9.3+ with PostGIS
• Flyway
• Redis
• NPM
• Grunt
• JQuery
• Bootstrap
• Leaflet

Target platform

• Ubuntu 14 LTS

Supported agencies

Binaries

The full system consists of three binaries. Each binary can be configured using environment variables and typically are run as daemons. They are located under the cmds/ directory.

busapi

busapi is the queryable HTTP API. It also delivers static assets.

busloader

busloader downloads static GTFS files and loads those files into the db. When it's finished loading a set of files, it updates materialized views queried by busapi.

busprecache

busprecache contacts agency-specific live data sources and writes raw response data to Redis. busapi reads that data to present live departure and vehicle location data.

Architecture

Config

Shared cache and external partner config

busapi and busprecache use these values to config Redis and external partner sites.

Shared database config

All three binaries use the following database config. busloader must have a writeable database, but busprecache and busapi can use a read-only replica.

busapi config

busloader config

busprecache config

No specific config, just the shared cache and db configs above.

Automation

In the automation/ directory, there is a sample of how to fully deploy the system. A full configuration for a deploy consists of an inventory file and a group_vars/ file. The included config is called inventory_vagrant. For security reasons (the API keys), the vars are encrypted in this repo. You can create your own config and deploy it locally by doing the following:

# Create vagrant server
$ cd automation/vagrant
$ vagrant up
$ cd ../..

# Overwrite group vars with defaults
$ cd automation/group_vars
$ cp defaults.yml inventory_vagrant.yml

# Add your API keys
$ vim inventory_vagrant.yml
$ cd ../..

# Deploy the system
$ cd automation
$ ./build.sh && ./deploy.sh inventory_vagrant db_install.yml db_migrations.yml api.yml web.yml loader.yml precache.yml

# If all goes well, system is available on http://localhost:8000

Quickstart

Loading all data can take a long time. You can shortcut this process by filtering for a few specific routes and data files.

# Load only the G and L train info and exit after initial load
export BUS_GTFS_URLS="http://web.mta.info/developers/data/nyct/subway/google_transit.zip"
export BUS_ROUTE_FILTER="G,L"
export BUS_LOAD_FOREVER="false"
busloader