[keycloak-dev] Appliance dist and WildFly feature packs

[Bill Burke]

On 9/16/2014 9:52 AM, Stan Silvert wrote:
> On 9/16/2014 9:39 AM, Bill Burke wrote:
>>
>> On 9/16/2014 5:59 AM, Stian Thorgersen wrote:
>>> WildFly 9 introduces features packs which seams ideal for us to build Keycloak upon.
>>>
>>> I'd like to start a "wildfly-9" branch of Keycloak that uses feature-packs and WildFly's built in mechanism to create the appliance distro. This would replace our current custom appliance-dist. Further I'd like us to have two flavours of Keycloak:
>>>
>>> * "appliance-lite": minimum Keycloak server only dist. For those that want a standalone Keycloak server. Builds on WildFly "web-lite" dist, but we need to add Hibernate, RestEasy and Connectors (datasources) as well
>>> * "appliance": full WildFly dist. For those that want to co-locate their JavaEE apps with the Keycloak server. Builds on the full WildFly dist.
>>>
>> We've discussed this before.
>>
>> The downside to a stripped down keycloak distro is the examples can't
>> run out of the box anymore and users will have to  download a full
>> Wildfly distro anyways and also configure it to run on different ports.
>>     They will have to edit example config files to point to the correct
>> ports.  Basically a lot more work to get things up and running for the
>> first time.
>>
> Hmm.  Perhaps the examples will be packaged as its own feature pack.
>
> A feature pack might make it even easier to get up and running. Today
> you still have to download the appliance, boot the server, import the
> test realm, and then build and deploy the examples.  I'd like to get rid
> of those steps.
>
> I think a lot of this depends on how good the provisioning tool turns
> out to be.

The screencast tutorials require you to manually create the realm and 
manually configure the applications.


-- 
Bill Burke
JBoss, a division of Red Hat
http://bill.burkecentral.com