GUACAMOLE-2114: Custom base for CATALINA_BASE and GUACAMOLE_HOME#1099
GUACAMOLE-2114: Custom base for CATALINA_BASE and GUACAMOLE_HOME#1099tiborauer wants to merge 27 commits intoapache:mainfrom
Conversation
GUACAMOLE-2114: Custom CATALINA_BASE
GUACAMOLE-2114: Custom base for CATALINA_BASE and GUACAMOLE_HOME
GUACAMOLE-2114: WEBAPPS_BASE, handle if not empty
GUACAMOLE-2114: fix pre-configured GUACAMOLE_HOME
@tiborauer Can you clarify what sort of use case requires storing
|
|
@mike-jumper Thank you for clarifying your motivation! I believe it works very well for isolated Docker-only cases. I am using it in a K8s cluster; however, with somewhat different challenges. Having application data on a pre-specified location (on a persistent volume):
|
GUACAMOLE-2114: fix features for pre-configured GUACAMOLE_HOME
GUACAMOLE-2114: fix features for pre-configured GUACAMOLE_HOME
GUACAMOLE-1746: Refactor
|
@tiborauer : Please clean up the commits - you have several Merge commits along with ones from different issues (GUACAMOLE-1746). The only commits present should be ones specifically for the GUACAMOLE-2114 issue. |
Allowing a custom base, rather than the ones randomly created in /tmp, would enable storing the program's data in a user-defined location. This feature would be particularly useful on Kubernetes, where the lifecycle of the program's data independent from that of the program would improve robustness. Also, the program's data could be shared with sidecar containers to extend functionality.