Good idea, Jeff. I'm slowly catching up on email after being out most of 3 weeks! I see that your PR also adds an 'install-wildfly' script, presumably for analogous use via curl. I wanted to call attention to that on this thread as people reading this may not want to look at the PR and won't be aware. That script works by downloading the latest tar from GitHub and unzipping it. We're generally trying to push people away from focusing on the zips/tars and toward using Galleon-tools. But personally I think this is ok, and in the future there's nothing to stop us changing the script to have it instead find/install a tool and provision locally. - Brian On Fri, Sep 5, 2025 at 4:18 AM Jean-Frederic Mesnil via wildfly-dev < wildfly-dev(a)lists.jboss.org&gt; wrote: -- Brian Stansberry Architect, JBoss EAP WildFly Project Lead He/Him/His

On 9 Sep 2025, at 22:08, Brian Stansberry <bstansbe(a)redhat.com&gt; wrote: This Message Is From an External Sender This message came from outside your organization. <https://us-phishalarm-ewt.proofpoint.com/EWT/v1/AdhS1Rd-!-XFVHHo5WEM1f9W1... Report Suspicious Good idea, Jeff. I'm slowly catching up on email after being out most of 3 weeks! I see that your PR also adds an 'install-wildfly' script, presumably for analogous use via curl. Thanks, I updated the PR[1] title and description to reflect that I want to have installation scripts for both WildFly & Glow. We're generally trying to push people away from focusing on the zips/tars and toward using Galleon-tools. But personally I think this is ok, and in the future there's nothing to stop us changing the script to have it instead find/install a tool and provision locally. I agree. While we are pushing to use provisionings tool to install WildFly, the reality is that a lot of users are still depending on the zips so let’s make their lives easier. One of the reason I want to add these scripts is to make it simpler to switch from using “WildFLy as a zip” to “provisioned WildFly”. Let’s use the example of a simple CRUD application that is put into a container. With WildFly as a zip, we do 1. Install WildFly from the zip (this is done in our base wildfly image) 2. ADD the application deployment 3. ADD the JBoss Module for the JDBC drivers 4. ADD (or run CLI scripts) to modify the standalone.xml With a “provisioned WildFly server”, the order of sequence is flipped and much simpler 1. ADD the application deployment 2. Install Glow 3. Scan the deployment with GLOW (and enable the datasource layers that will provision the JDBC drivers and the standalone.xml modifications) The Containerfile to achieve this is quite simple[2]. The key difference is that the provisioned WildFly server only contains what is needed to run the application (smaller image size, resource consumption, and security attack surface). As an example, using the todo-backend quickstart, I go from a 814MiB image from “WildFly as a zip” to a 512 MiB image with the provisioned server resulting in a 37% decrease in image size. If we want to help the users go in that direction, the steps to install Glow needs to be simple and this installation script achieves this. Jeff [1] https://github.com/wildfly/wildfly.org/pull/838 [2] https://github.com/jmesnil/wildfly-container/blob/glow_integration/Docker... - Brian On Fri, Sep 5, 2025 at 4:18 AM Jean-Frederic Mesnil via wildfly-dev <wildfly-dev@lists.jboss.org<mailto:wildfly-dev@lists.jboss.org>> wrote: Hi, I’m working on using Glow to build a container image that would provision a WildFly server based on the deployments that are ADDed to the Containerfile. To do so, I need to install Glow from my Containerfile. The instructions are not complex[1] but we can improve the user experience by automating it. This would improve the usage of Glow by making it very easy to install. We could have the standard usage of curl-ing a shell script that would do the actual work. All we need is a good place to host that script. I was thinking of using wildfly.org<http://wildfly.org > to host this script. The installation process would simply be: ``` $ curl -s https://wildfly.org/sh/install-glow<https://wildfly.org/sh/install-glow > | sh ``` And WildFly Glow is installed from the local directory and ready to be used. By default, the latest version is installed. Otherwise, you can use the GLOW_VERSION env var to use another version. I did this on my fork of wildfly.org<http://wildfly.org >: ``` $ curl -s https://jmesnil.github.io/wildfly.org/sh/install-glow<https://jmesnil.... > | sh 🔍 Fetching latest release from GitHub... ⬇️ Downloading: https://github.com/wildfly/wildfly-glow/releases/download/1.5.0.Final/wil... > 📦 Extracting WildFly Glow... 🚀 Installing to /Users/jmesnil/tmp/wildfly-glow 💡 To install shell command completion, you can run: source <(./wildfly-glow/wildfly-glow completion) ✅ Installation of WildFly Glow 1.5.0.Final complete! ``` I’ve opened a PR for it at https://github.com/wildfly/wildfly.org/pull/838<https://github.com/wil... >. Don’t hesitate to give your feedback and comments in the PR. Once we have done that for WildFly Glow, I’m planning to do something similar with Prospero. Jeff [1] https://github.com/wildfly/wildfly-glow?tab=readme-ov-file#using-the-wild... > -- Jeff Mesnil Software Engineer Red Hat JBoss EAP http://jmesnil.net/<http://jmesnil.net/ > IBM Unless otherwise stated above: Compagnie IBM France Siège Social : 17, avenue de l'Europe, 92275 Bois-Colombes Cedex RCS Nanterre 552 118 465 Forme Sociale : S.A.S. Capital Social : 664 614 175,50 € SIRET : 552 118 465 03644 - Code NAF 6203Z _______________________________________________ wildfly-dev mailing list -- wildfly-dev@lists.jboss.org<mailto:wildfly-dev@lists.jboss.org> To unsubscribe send an email to wildfly-dev-leave@lists.jboss.org<mailto:wildfly-dev-leave@lists.jboss.org> Privacy Statement: https://www.redhat.com/en/about/privacy-policy<https://www.redhat.com/... > List Archives: https://lists.jboss.org/archives/list/wildfly-dev@lists.jboss.org/message... > -- Brian Stansberry Architect, JBoss EAP WildFly Project Lead He/Him/His -- Jeff Mesnil Software Engineer Red Hat JBoss EAP http://jmesnil.net/ IBM Unless otherwise stated above: Compagnie IBM France Siège Social : 17, avenue de l'Europe, 92275 Bois-Colombes Cedex RCS Nanterre 552 118 465 Forme Sociale : S.A.S. Capital Social : 664 614 175,50 € SIRET : 552 118 465 03644 - Code NAF 6203Z