Closed danrademacher closed 11 months ago
I filed a support ticket with the qgtunnel folks and we figured it out.
the qgtunnel file ()in this repo) has to look like this:
[qgtunnel.Walkmapper_MySQL]
accept = "127.0.0.1:3306"
connect = "142.11.243.132:3306"
encrypted = false
transparent = false
And the big thing was that the settings for Heroku for WALKOBSTRUCTION_MYSQL_HOST
have to be 127.0.0.1
because the configu above essentially tunnels from there to 142.11.243.132
via one of the two static IPs they provide as a service.
Makes sense.
Christine asked me a couple of weeks ago about getting a static IP assigned to the ETL script process on Heroku, since they have changed the Walkmapper database and need to safelist specific IPs for database access.
This is for the scripts here: https://github.com/GreenInfo-Network/nyc-crash-mapper-etl-script/tree/master/walkmapper
Not surprisingly, Heroku does not provide static IPs. Christine found a Heroku addon that does so, accessbile form the app on Heroku here:
I updated the ENV vars on that app to be the correct ones for the new database, and also updated the record in 1P
Then I asked the client to also safelist our office IP address. Loading the ENV vars locally and running
python walkmapper/mysql2carto.py
works as expected. I can access the DB and data is updated in CARTO.However, the QuotaGuard proxy is not configured properly.
When I run from Heroku, I get this:
Seems clear the IP is just not configured.
I tried this test they recommend and it seems to return an expected result:
So I filed this suport request:
┆Issue is synchronized with this Asana task