Add support for running a command to get the database connection string in`postgrestools.jsonc`#292

remorses started this conversation inIdeas

Add support for running a command to get the database connection string in `postgrestools.jsonc`#292

remorses

Apr 1, 2025

· 2 comments· 3 replies

Return to top

Discussion options

remorses
Apr 1, 2025

I want to use the Supabase database directly instead of a local database, to do that you could add support for a config optiondbCommand to get the database uri via stdout

{"$schema":"./docs/schemas/latest/schema.json",// get the database uri using dotenv-cli npm package"dbCommand":"dotenv -- bash -c 'echo $DATABASE_URL'",// get database uri using doppler"dbCommand":"doppler secrets get --plain DATABASE_URL",}

This allows to get the database url using tools like Doppler or dotenv

You must be logged in to vote

Replies: 2 comments 3 replies

Comment options

psteinroe
Apr 1, 2025
Maintainer

Thanks for the suggestion!

Out of curiosity: why do you want to connect directly to the remote database? Latencies will be higher.

You must be logged in to vote

3 replies

Comment options

remorses Apr 1, 2025
Author

Latency shouldn’t be a big issue, I prefer using a remote database to make local setup easier

Comment options

It might be useful even in "local" contexts.
For instance we have a workstation which is shared by many users with one DB for each user.
The connection to each local DB is provided behind an environment variable (like so:$DEV_DB_URI).
Being able to get the URI without writing it directly in thepostgrestools.jsonc file would allow us to commit the config file for everyone.