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 2016/09/02 21:34:20 UTC
[jira] [Commented] (GUACAMOLE-99) Do not require Docker link for
guacd
[ https://issues.apache.org/jira/browse/GUACAMOLE-99?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15459656#comment-15459656 ]
Michael Jumper commented on GUACAMOLE-99:
-----------------------------------------
Current work-in-progress is on [the "guacd-env" branch of my GitHub fork|https://github.com/mike-jumper/incubator-guacamole-client/tree/guacd-env]. I have defined the following additional environment variables:
|| Name || Description ||
| {{GUACD_HOSTNAME}} | The hostname where guacd is listening for connections. Required if the "guacd" Docker link is not used. |
| {{GUACD_PORT}} | The port to connect to if not using the "guacd" Docker link. If unspecified, this defaults to 4822. |
> 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
>
> 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)