Document configuring a read-only connection, explain security issues #6
Labels
documentation
Improvements or additions to documentation
enhancement
New feature or request
security
Milestone
Best practice for this tool will be configuring a read-only role with access to an allow-list of tables, as described here: https://til.simonwillison.net/postgresql/read-only-postgresql-user
I'm going to continue supporting read-only transactions against a regular connection purely because Heroku charge $50/month minimum for the ability to add extra read-only users to a database.
The text was updated successfully, but these errors were encountered: