Jean-François Denise

@codylerum @hendratommy , FYI, using WF23 you can excute CLI script to adjust your configuration at runtime. We have an example that has been evolved to showcase the feature: https://github.com/wildfly-extras/wildfly-jar-maven-plugin/tree/master/examples/authentication...

@jamezp , yes. Good you logged it. Having standalone.sh (and bin dir) is convenient (at least for now), in order to "test" launching with standalone.sh.

@wisteso , thank-you for your report. We definitely need to evolve the postgresql example with a non cloud example. We will add it.You can use the same environment variables on...

@wisteso , the CLI approach is correct, it is the way to add multiple datasources, the Galleon feature-pack allows to add only a single datasource.

I was thinking at a path to a war (or any supported deployment) file that would be used during packaging time, not a Maven "dependency". So a new option in...

@chris-corless , the ability to reference an external deployment has been added. We plan to release an early access of the feature in 6.0.0.Alpha1. Let us know if that answers...

@chris-corless , in the end we didn't release a support for "server mode" that was offering the ability to package a war in the bootable JAR.

@codylerum , thank-you for your report. I have opened a PR for a systemd service based on bootable JAR: https://github.com/wildfly-extras/wildfly-jar-maven-plugin/pull/194

@codylerum , if your wildfly service contains the core-tools layer (that you can explicitly include and is included in datasources-web-server, jaxrs-server and cloud-server) you could start jboss-cli.sh from /opt/wildfly-bootable/wildfly/bin/jboss-cli.sh

@codylerum , that is currently the only source of information for a systemd integration. Shouldn't we instead evolve this PR with the shutdown script (that you mentioned) and merge it?