Skip to content
This repository has been archived by the owner on Jun 1, 2022. It is now read-only.

Commit

Permalink
Documented where our API exports go, refs #658
Browse files Browse the repository at this point in the history
  • Loading branch information
simonw authored Jun 10, 2021
1 parent 6cdbf73 commit 93fe234
Showing 1 changed file with 10 additions and 0 deletions.
10 changes: 10 additions & 0 deletions README.md
Original file line number Diff line number Diff line change
Expand Up @@ -11,6 +11,16 @@ Project background: [Spinning up a new Django app to act as a backend for Vaccin
- https://vial.calltheshots.us/ is production - manually deployed using `scripts/deploy.sh`
- https://vial-staging.calltheshots.us/ is our Google Cloud Run staging server - code is automatically deployed there on every commit

## API exports

VIAL exports data to static JSON (and GeoJSON) in Google Cloud buckets for use by other applications. These exports are triggered by Google Cloud Scheduler - see https://console.cloud.google.com/cloudscheduler?project=django-vaccinateca

- https://api.vaccinatethestates.com/ has the production exports from the `/api/exportVaccinateTheStates` endpoint
- https://staging-api.vaccinatethestates.com/ has the staging equivalent
- https://api.vaccinateca.com/ has API exports triggered by `/api/export` for our VaccinateCA data
- https://staging-api.vaccinateca.com/ has staging for that
- We also have an export to Mapbox, triggered by `/api/exportMapbox` - this export goes directly into their system

## Velma and Scooby

Scooby is our app for filing reports against locations.
Expand Down

0 comments on commit 93fe234

Please sign in to comment.