Hey all, I’m getting a jump on building a custom extension for 1.6.0 and wanted to make sure I’m following the correct build process to get it built, loaded, and environment variables in the container.
The first thing is adding your custom extension code to be built to the guacamole-client/extensions folder and updating the guacamole-client/extensions/pom.xml such that it gets built when the guacamole-client build process is called. This should produce a target .jar file. Then, to get the custom extension .jar to persist from the builder docker container into the final docker container you have to update the guacamole-client/guacamole-docker/build.d/000-build-and-install-guacamole.sh file to make a folder in the $DESTINATIONS/extensions for your custom extension .jar to go into and then copy your jar from the $BUILD_DIR/extensions/<extension>/target/<extension>-1.6.0.jar to the $DESTINATION/extensions/<extension> folder that was just created. Then, to get the environment variables to carry over from the compose file, you have to add a line to the bottom of the guacamole-client/guacamole-docker/build.d/010-map-guacamole-extensions.sh file with a mapping for your extension name and environment variable names. Then, you build the guacamole-client docker container and run the compose file with the extension mapped environment variable ending with _ENABLED to have the extension load at runtime. Am I missing anything else? It seems to be working, I just wanted to get this all documented because I didn’t see anything updated in the staging/1.6.0 version of the website yet about the process so I just kinda had to play with the build process until I figured out what it was doing. Thanks! -Nathaniel Belles --------------------------------------------------------------------- To unsubscribe, e-mail: [email protected] For additional commands, e-mail: [email protected]
