jimmy/postgrest
1
0
Fork 0
Code Issues Pull Requests Actions Packages Projects Releases Wiki Activity

Reorder release notes for v8.0

Browse Source
This commit is contained in:
steve-chavez
2021-08-10 00:26:24 -05:00
parent ff30d4d417
commit fcabf4012b
4 changed files with 37 additions and 43 deletions
Download Patch File Download Diff File Expand all files Collapse all files
configuration.rst
+3 -3
View File
@@ -404,7 +404,7 @@ To reload the configuration without restarting the PostgREST server, send a SIGU
killall -SIGUSR2 postgrest
This method does not reload :ref:`env_variables_config` and it will not work for reloading a Docker container configuration. In these cases, you need to restart the PostgREST server or use :ref:`in_db_config` as an alternative.
This method does not reload :ref:`env_variables_config` and it will not work for reloading a Docker container configuration. In these cases, you need to restart the PostgREST server or use the :ref:`in_db_config` as an alternative.
.. important::
@@ -433,12 +433,12 @@ For example, you can configure :ref:`db-schema` and :ref:`jwt-secret` like this:
ALTER ROLE authenticator SET pgrst.db_schema = "tenant1, tenant2, tenant3"
ALTER ROLE authenticator SET pgrst.jwt_secret = "REALLYREALLYREALLYREALLYVERYSAFE"
Note that underscores(``_``) need to be used instead of dashes(``-``) for the in-database config options.
.. important::
For altering a role in this way, you need a SUPERUSER. You might not be able to use this configuration mode on cloud-hosted databases.
Note that underscores(``_``) need to be used instead of dashes(``-``) for the options when the configuration is inside the database.
When using both the configuration file and the in-database configuration, the latter takes precedence.
.. danger::