[
https://issues.apache.org/jira/browse/GUACAMOLE-1572?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17520191#comment-17520191
]
Jean-Benoit PAUX commented on GUACAMOLE-1572:
---------------------------------------------
Good catch, {{POSTGRESQL_SSL_MODE, POSTGRESQL_SSL_CERT_FILE,
POSTGRESQL_SSL_KEY_FILE, POSTGRESQL_SSL_ROOT_CERT_FILE}} have the same
behaviour (and doc doesn't include them).
[~vnick] should all these variables be renamed to POSTGRES to look like other
environment variables or the other way should all variables be renamed to
POSTGRES{*}QL{*} to look like exactly the variable names in the
{{guacamole.properties}} file ?
> Typo on specified environment variable postgres_auto_create_accounts
> --------------------------------------------------------------------
>
> Key: GUACAMOLE-1572
> URL: https://issues.apache.org/jira/browse/GUACAMOLE-1572
> Project: Guacamole
> Issue Type: Bug
> Components: Documentation, guacamole-docker
> Affects Versions: 1.4.0
> Reporter: Christian Galo
> Priority: Minor
> Labels: documentation
>
> In the documentation page [Installing Guacamole with
> Docker|https://guacamole.apache.org/doc/gug/guacamole-docker.html#guacamole-docker-postgresql-optional-vars]
> under _optional environment variables_ for _PostgreSQL Authentication_, the
> environment variable documented as {{POSTGRES_AUTO_CREATE_ACCOUNTS}} does not
> write to the resulting {{guacamole.properties}} file in the running
> container. When typed as {{POSTGRESQL_AUTO_CREATE_ACCOUNTS}} the environment
> variable is correctly written to {{guacamole.properties}}.
> This could be an issue with other environment variables. It might make sense
> to use the same spelling for postgres in both {{guacamole.properties}} and
> environment variables passed through docker to avoid these sort of bugs.
--
This message was sent by Atlassian Jira
(v8.20.1#820001)
