EAP 7/WildFly 10 CLI can now modify the configuration w/o running the server at all. Maybe that fits the bill.

~jd

On Wed, Jan 27, 2016 at 6:48 AM, Thomas Segismont <tsegismo@redhat.com> wrote:

Totally agree with Mazz (with respect to the rabbit hole).

Simple scripts for common install tasks (add-user/etc...) should be
enough. And they should not require the server to be half-started but
simply operate on files.

Le 26/01/2016 22:47, John Mazzitelli a écrit :
> After seeing the work involved in prior products' installers, it is my recommendation we do everything in our power to avoid writing a custom installer and to not worry about covering all customization/configuration possibilities.
>
> Perhaps we write a simple bash script that takes a few parameters and does a bunch of simple file manipulations to change standalone.xml, push files from here to there, that kind of thing. But unless we want to devote alot of time and resources to do it "right" let's try avoid writing an installer. That is a rabbit hole I don't think we should commit to going down right now.
>
> Just my $0.02 based on past experience.
>
> ----- Original Message -----
>> On 26 Jan 2016, at 14:25, John Doyle wrote:
>>
>>> Is ansible a viable technology for this?
>>
>> I am sure that we can supply playbooks for
>> users that already use Ansible.
>> I am not sure though that "requiring" Ansible
>> to get a decent install / start experience is
>> the way forward.
> _______________________________________________
> hawkular-dev mailing list
> hawkular-dev@lists.jboss.org
> https://lists.jboss.org/mailman/listinfo/hawkular-dev
>

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