[~dffrench]:
1. If using docker compose these can be set there like in [app-metrics|https://github.com/aerogear/aerogear-app-metrics/blob/fc70de7e74/docker-compose.yml#L24-L27]. Postgres will pick up the set of PG env vars we support. In app-metrics we support [this set|https://github.com/aerogear/aerogear-app-metrics/blob/c37fb04460868d64a5b6a1ab22860b1b55b848d4/pkg/config/config.go#L52] of env vars. Re setting of these env vars, these are [picked up by go from the local environment|https://github.com/aerogear/aerogear-app-metrics/blob/c37fb04460868d64a5b6a1ab22860b1b55b848d4/pkg/config/config.go#L51-L61] where the app is running, and should just need to be set in the local environment where the app is running.
2. Postgres does not appear to be used [in the mobile-developer-console repo|https://github.com/aerogear/mobile-developer-console/search?q=postgres&unscoped_q=postgres]
3. I could guess but I'm afraid I don't know. We've mimiced the approach used in app-metrics of providing a docker compose file, and see no reason why this would not be sufficient for local development once it's the docker-compose file is kept current. This would be a good question for you to ask on the aerogear mailing list though. |
|
