snarfed
commented
8 years ago straw man: add all the app ids and secrets as circle environment variables, then write them to files in deploy.sh (if they don't already exist) before deploying.
another straw man: put them in the datastore. way more invasive, and would need new design and code to keep granary and o-d working for other users.
I'd like to set up continuous deployment for bridgy, granary, oauth-dropins, etc. background: https://circleci.com/docs/introduction-to-continuous-deployment/ https://circleci.com/docs/deploy-google-app-engine/
the catch is all the silo app ids and secrets in local files. circle lets us set environment variables that are available during test/deploy, but we need to get them into app engine. needs more thought.