Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Document configuring a read-only connection, explain security issues #6

Closed
simonw opened this issue Mar 13, 2021 · 1 comment
Closed
Labels
documentation Improvements or additions to documentation enhancement New feature or request security

Comments

@simonw
Copy link
Owner

simonw commented Mar 13, 2021

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.

@simonw simonw added documentation Improvements or additions to documentation enhancement New feature or request security labels Mar 13, 2021
@simonw simonw added this to the First non-alpha release milestone Mar 13, 2021
@simonw simonw changed the title Support reading from a read-only connection, document security issues Document configuring a read-only connection, explain security issues Mar 14, 2021
@simonw
Copy link
Owner Author

simonw commented Mar 14, 2021

As-of 88aae40 the tool requires a dedicated database alias called dashboard (that name can be changed using the DASHBOARD_DB_ALIAS setting).

simonw added a commit that referenced this issue Mar 15, 2021
@simonw simonw closed this as completed in f3eabeb May 9, 2021
simonw added a commit that referenced this issue May 9, 2021
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
documentation Improvements or additions to documentation enhancement New feature or request security
Projects
None yet
Development

No branches or pull requests

1 participant