configure npm commands to use admin credentials for operations that require them
add npm script and command to create databases in the DO cluster for developers
background
Locally deployed databases are useful, but when the API is deployed it won't use a locally deployed database. When trying to run the commands in this repo against the (already deployed) database cluster in DO called zoning-api, it became clear that there are two types of connections: those that require admin privileges and those that do not.
In the issue https://github.com/NYCPlanning/ae-data-flow/issues/2, I described a potential approach to databases and users that was inspired by the one used for PFF (described here). These changes enable that implementation.
screenshots
a development db created by running these commands, structured using pg:migrate, and modified using in-progress commands in the new ae-data-flow repo:
per relevant issue here this PR is no longer needed because AE's data flow process will only touch the API DB at the final stage: replacing rows in tables
we're using development DBs for data flow dev and tabling the idea of development DBs for API dev
related to https://github.com/NYCPlanning/ae-data-flow/issues/2
changes
background
Locally deployed databases are useful, but when the API is deployed it won't use a locally deployed database. When trying to run the commands in this repo against the (already deployed) database cluster in DO called
zoning-api
, it became clear that there are two types of connections: those that require admin privileges and those that do not.In the issue https://github.com/NYCPlanning/ae-data-flow/issues/2, I described a potential approach to databases and users that was inspired by the one used for PFF (described here). These changes enable that implementation.
screenshots
a development db created by running these commands, structured using
pg:migrate
, and modified using in-progress commands in the newae-data-flow
repo: