3:09 p.m.
On Tue, Sep 9, 2025 at 3:08 PM Brian Stansberry <bstansbe(a)redhat.com> wrote:
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.
Doh! I missed your follow up post telling people about this!
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> 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 to host this script.
>
> The installation process would simply be:
>
> ```
> $ curl -s 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:
>
> ```
> $ curl -s https://jmesnil.github.io/wildfly.org/sh/install-glow | 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.
> 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/
>
> 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(a)lists.jboss.org
> To unsubscribe send an email to wildfly-dev-leave(a)lists.jboss.org
> Privacy Statement: https://www.redhat.com/en/about/privacy-policy
> 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
--
Brian Stansberry
Architect, JBoss EAP
WildFly Project Lead
He/Him/His