You are viewing a plain text version of this content. The canonical link for it is here.
Posted to commits@guacamole.apache.org by "Michael Jumper (JIRA)" <ji...@apache.org> on 2017/01/22 23:14:26 UTC
[jira] [Resolved] (GUACAMOLE-99) Do not require Docker link for
guacd
[ https://issues.apache.org/jira/browse/GUACAMOLE-99?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Michael Jumper resolved GUACAMOLE-99.
-------------------------------------
Resolution: Done
> Do not require Docker link for guacd
> ------------------------------------
>
> Key: GUACAMOLE-99
> URL: https://issues.apache.org/jira/browse/GUACAMOLE-99
> Project: Guacamole
> Issue Type: Improvement
> Components: guacamole-docker
> Reporter: Michael Jumper
> Assignee: Michael Jumper
> Priority: Minor
> Fix For: 0.9.11-incubating
>
>
> For MySQL, PostgreSQL, and LDAP, the Guacamole Docker image can use either a hostname+port provided via environment variables *or* a Docker link. For guacd, however, this is not done. A Docker link is universally required.
> It should be trivial for similar {{GUACD_HOSTNAME}} and {{GUACD_PORT}} environment variables to be supported. Doing this would close a feature gap, and allow the Docker images to be used in situations where Docker links won't always be appropriate (such as when a cluster of guacd instances exist behind a load balancer).
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)