On 12/2/2014 7:55 AM, Stan Silvert wrote:
On 12/2/2014 4:52 AM, Stian Thorgersen wrote:
> Should we upgrade to WF 8.2 and also do some changes to the distro before release?
I don't see a reason not to go to WF 8.2. If we do that, let me know so
I can run a quick smoke test on the subsystem before we release.
>
> With regards to distro we should move the adapters and examples into separate
downloads. Also, we should move the examples into a separate github project
(keycloak/keycloak-examples). This will make it easier for those that wants to fork the
examples separately.
>
> Also, we should consider a download based on the web-lite profile. For non-JavaEE
apps, containers (Docker) and those that want to run a standalone KC server it would be
nice to have a small as possible distro.
Depending on how the feature pack turns out, we might be able to offer
many flavors of the appliance distro without any additional effort. We
could have:
EAP6 + Keycloak
AS7 + Keycloak
WF8 (web) + Keycloak
WF8 (full) + Keycloak
WF 9 beta (web) + Keycloak
WF 9 beta (full) + Keycloak
etc.
IMO, we just need:
* war-dist
* appliance-dist
Appliance distribution would have the most stable platform available.
Since we can't distribute EAP, then it would be the most stable and
maintained version of Wildfly that allows us to cluster and deploy Keycloak.
--
Bill Burke
JBoss, a division of Red Hat
http://bill.burkecentral.com