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. However, this does not provide full flexibility. As described, 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.