We read every piece of feedback, and take your input very seriously.
To see all available qualifiers, see our documentation.
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
@timlinux : We need to set up github pages with a DNS entry. Need to figure out how private info will be managed.
The text was updated successfully, but these errors were encountered:
@Ann26 What all are the private details we need to store?
Db host and credentials? Anything else?
I think we can use a scheme whereby only the flood upload and other write parts of the database use authentication like this:
https://postgrest.org/en/v4.1/auth.html#logins
For the rest we could use a publicly visible configuration and ensure that the user using the postgrest backend has only read availability.
If that all looks too time consuming, let's simply run it on a dedicated hetzner box.
Sorry, something went wrong.
No branches or pull requests
@timlinux : We need to set up github pages with a DNS entry. Need to figure out how private info will be managed.
The text was updated successfully, but these errors were encountered: