<div dir="ltr">I definitely agree that:<div> - we need to make it easy to install</div><div> - an installer needs to be easy to maintain (reduce options in particular)</div><div><br></div><div>We should also (re)consider our delivery options:</div><div> - zip vs docker vs VM vs RPMs</div><div>We also can't do all, and it has an impact on how the various parts work together.</div><div><br></div><div>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... </div><div>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.</div><div><br></div><div>Thomas</div><div><br></div><div><br></div><div><br></div></div><div class="gmail_extra"><br><div class="gmail_quote">On Wed, Jan 27, 2016 at 3:33 PM, Thomas Segismont <span dir="ltr"><<a href="mailto:tsegismo@redhat.com" target="_blank">tsegismo@redhat.com</a>></span> wrote:<br><blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex"><span class="">Le 27/01/2016 13:19, Heiko W.Rupp a écrit :<br>
> On 27 Jan 2016, at 12:48, Thomas Segismont wrote:<br>
><br>
>> Simple scripts for common install tasks (add-user/etc...) should be<br>
>> enough. And they should not require the server to be half-started but<br>
><br>
> I am talking about this:<br>
> <a href="http://www.mastertheboss.com/jbossas/wildfly9/configuring-wildfly-9-from-the-cli-in-offline-mode" rel="noreferrer" target="_blank">http://www.mastertheboss.com/jbossas/wildfly9/configuring-wildfly-9-from-the-cli-in-offline-mode</a><br>
<br>
</span>Simple scripts could use the offline-cli, yes. AFAIU, The offline-cli<br>
does not bind any port or deploy any component.<br>
<span class=""><br>
><br>
> Not what we had in RHQ.<br>
><br>
>> simply operate on files.<br>
><br>
> I don't think this is good for handling xml configs.<br>
<br>
</span>Do we have our own XML on top of what we already put inside standalone.xml?<br>
<div class="HOEnZb"><div class="h5">_______________________________________________<br>
hawkular-dev mailing list<br>
<a href="mailto:hawkular-dev@lists.jboss.org">hawkular-dev@lists.jboss.org</a><br>
<a href="https://lists.jboss.org/mailman/listinfo/hawkular-dev" rel="noreferrer" target="_blank">https://lists.jboss.org/mailman/listinfo/hawkular-dev</a><br>
<br>
<br>
</div></div></blockquote></div><br></div>