You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
<p>For security reasons, this API is best self-hosted. However, we provide an example API for you to test before installing. To use the API however, you have to send your PG connection via HTTPS headers.</p>
253
-
<p>We DO NOT log these headers anywhere. But still, we HIGHLY recommend that you just self-host (we have tried to make this easy for you). Use the demo API at your own risk.</p>
254
-
<p>Database connection headers are not required for self-hosting. You can set ENV vars with your default connection details so that you don't pass connection details over a network.</p>
249
+
<p>For security reasons, this API is best self-hosted and set up with ENV_VARS with the default connection string.</p>
250
+
<p>If you want to use this with multiple Postgres instances, you can pass the connection string as a header but it must be encrypted.</p>
For security reasons, this API is best self-hosted. However, we provide an example API for you to test before installing. To use the API however, you have to send your PG connection via HTTPS headers.
62
+
For security reasons, this API is best self-hosted and set up with ENV_VARS with the default connection string.
66
63
67
-
We DO NOT log these headers anywhere. But still, we HIGHLY recommend that you just self-host (we have tried to make this easy for you). Use the demo API at your own risk.
68
-
69
-
Database connection headers are not required for self-hosting. You can set ENV vars with your default connection details so that you don't pass connection details over a network.
64
+
If you want to use this with multiple Postgres instances, you can pass the connection string as a header but it must be encrypted.
0 commit comments