I definitely agree that:

- we need to make it easy to install

- an installer needs to be easy to maintain (reduce options in particular)

We should also (re)consider our delivery options:

- zip vs docker vs VM vs RPMs

We also can't do all, and it has an impact on how the various parts work together.

For the server, I think it would be extremely helpful to have a dedicated property file for all the typical configuration. By typical, I mean, the IP to the cassandra cluster, the IP to the Keycloak server, enable/disable the internal agent with username/password...

Does anyone know how we can keep the configuration.xml files but point to properties in a different file ? I think it would be extremely helpful for a user and an installer to just have to edit a simpe and documented property file rather than messing around with the standalone.xml file that change over time.

Thomas

On Wed, Jan 27, 2016 at 3:33 PM, Thomas Segismont <tsegismo@redhat.com> wrote:

Le 27/01/2016 13:19, Heiko W.Rupp a écrit :
> On 27 Jan 2016, at 12:48, Thomas Segismont wrote:
>
>> Simple scripts for common install tasks (add-user/etc...) should be
>> enough. And they should not require the server to be half-started but
>
> I am talking about this:
> http://www.mastertheboss.com/jbossas/wildfly9/configuring-wildfly-9-from-the-cli-in-offline-mode

Simple scripts could use the offline-cli, yes. AFAIU, The offline-cli
does not bind any port or deploy any component.

>
> Not what we had in RHQ.
>
>> simply operate on files.
>
> I don't think this is good for handling xml configs.

Do we have our own XML on top of what we already put inside standalone.xml?

_______________________________________________
hawkular-dev mailing list
hawkular-dev@lists.jboss.org
https://lists.jboss.org/mailman/listinfo/hawkular-dev