guacamole-commits mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Emmanuel Frecon (JIRA)" <j...@apache.org>
Subject [jira] [Created] (GUACAMOLE-146) Finer control of the tomcat context path in Docker
Date Wed, 21 Dec 2016 08:10:58 GMT
Emmanuel Frecon created GUACAMOLE-146:
-----------------------------------------

             Summary: Finer control of the tomcat context path in Docker
                 Key: GUACAMOLE-146
                 URL: https://issues.apache.org/jira/browse/GUACAMOLE-146
             Project: Guacamole
          Issue Type: Improvement
          Components: guacamole-docker
    Affects Versions: 0.9.10-incubating, 0.9.11-incubating
            Reporter: Emmanuel Frecon


The current auto-deployment of the guacamole within tomcat leads to having the regular tomcat
startup page mapped on {{/}} and guacamole mapped to {{/guacamole}}. Being able to control
where guacamole gets to be deployed and served by tomcat would provide an increased flexibility
when guacamole is fitted to existing architectures. For example, most docker-based deployments
will use reverse-proxying to provide scalability and security.

An initial fix for this is [available|https://github.com/apache/incubator-guacamole-client/pull/97/commits/1386239d3c12987daa774ed387a41c1471444f87].
However, this does not provide full flexibility. As [described|https://github.com/apache/incubator-guacamole-client/pull/97#issuecomment-268341268],
using an environment variable to control the context path would be a much better solution
as it would provide full flexibility while still maintaining backwards compabitibility.



--
This message was sent by Atlassian JIRA
(v6.3.4#6332)

Mime
View raw message