Start proxy within a Node/Express application, and run on a client in Heroku about cloud-sql-proxy

[mm-wang]

It was a bit convoluted, but I did get it to work using a specific instantiation of the Procfile using a bash script to download and start the instance.

For others' reference, I used a file called proxy.sh that looks like below:

#!/bin/bash
wget https://dl.google.com/cloudsql/cloud_sql_proxy.linux.386
mv cloud_sql_proxy.linux.386 cloud_sql_proxy
chmod +x cloud_sql_proxy
./cloud_sql_proxy -instances=[instance-name]=tcp:3306 -credential_file=[path-to-file]

and a Procfile that looks like this:

web: (bash ./proxy.sh &) & node start.js

[hfwang]

You will need to do this work yourself, but you can download the proxy and add it to your slug using a custom buildpack. You would then also need to write a script (and use that in your Procfile) that starts both the proxy and the express server together.

A coworker pointed me to heroku's pg-bouncer that uses a very similar strategy, which you can look at: https://github.com/heroku/heroku-buildpack-pgbouncer

Sorry that this is pretty convoluted.

[valentinoli]

This was very helpful. Thank you!

[hfwang]

Thanks for figuring this out!

[PandhuWibowo]

@mm-wang does it work? Where is getting the credential file?

[enocom]

I would assume the credential file lives next to the app code, but isn't checked in. But I haven't tried this myself.

[mm-wang]

I haven't looked at this anytime recently, but I think I had a file that listed the credentials that was not checked in, as was suggested. It seems as if this is still a possibility:

https://github.com/GoogleCloudPlatform/cloudsql-proxy/blob/main/cmd/cloud_sql_proxy/cloud_sql_proxy.go#L104-L108