8:18 a.m.
----- Original Message -----
From: "Bill Burke" <bburke(a)redhat.com>
To: keycloak-dev(a)lists.jboss.org
Sent: Thursday, 2 January, 2014 3:12:10 PM
Subject: Re: [keycloak-dev] Keycloak release
On 1/2/2014 2:40 AM, Stian Thorgersen wrote:
> Happy New Year :)
>
> It would be great to release Keycloak alpha in a week or two. To get things
> started here's remaining work I'm aware of:
>
Want to do it ASAP.
> * Documentation - what's the status of docs? I'm happy to review, and also
> write some as well
Was going to start on docs after dist was finalized. There's still a
little bit of work to do there. See below.
> * Logo - Gabriel are you looking at this?
> * Website - Should we update to the new JBoss community theme used by
> WildFly, Infinispan, PicketLink, etc.?
jboss.org/keycloak is sufficient at the moment, IMO. Especially if we
have no logo. keycloak.org redirects there. If somebody wants to put a
site together, fine with me, but this isn't a skill set I have.
Jason told me that wildfly.org is on filemgmt.jboss.org/www_htdocs.
Pretty sure we have a keycloak directory there that is hooked up via my
ssh key.
I can start this - would be cool to have a logo and a nice website for alpha release, but
definitively not a blocker
> * Dist/examples - Upgrade to WildFly CR1. With WildFly CR1 they introduced
> a new minimal dist, maybe we could use this to reduce the dl size?
What's status on Openshift Quickstart? FYI, patching AS7 is no longer
required to run on AS7. Please see examples/as7-eap-demo/server. Are
you familiar with Docbook? Can you write up how to set up the Openshift
Quickstart?
The OpenShift Quickstart just downloads and extracts a dist from somewhere, so can be
upgraded to the WildFly dist by just changing the URL it downloads. I'll need to learn
Docbook in any case if we're using that for docs, so yes I can write the instructions
on getting it up and running on OpenShift.
I can also write some other sections if you want some help with docs.
For dist, I was going to provide the following downloads:
Zip 1 Appliance:
* examples/as7-eap-demo
* examples/wildfly-demo
* docs/
* A pre-configured Wildfly CR1 Dist
* adapters packaged as different jboss modules zips
* lib/as7-adapter
* lib/wildfly-adapter
* exploded server WAR
Zip 2:
* examples/docs
* adapters packaged as different jboss modules zips
* lib/as7-adapter
* lib/wildfly-adapter
* exploded server WAR
Is the lib/*-adapter needed?
What's the purpose of the exploded server WAR?
We would still need the following components to build on top of a
Wildfly minimal dist:
* Embeddable DB
* JPA
* Web
* JAX-RS
I was actually thinking of writing a utility that scanned a jboss
module's dist to determine subsystems and their dependencies. Its
pretty difficult to figure out now with the current Wildfly build.
If we do provide a slimmed-down dist, we should also provide the instructions to deploy
easily to a full WildFly. I imagine at least devs will want to have both their apps and
Keycloak on a single server.
--
Bill Burke
JBoss, a division of Red Hat
http://bill.burkecentral.com
_______________________________________________
keycloak-dev mailing list
keycloak-dev(a)lists.jboss.org
https://lists.jboss.org/mailman/listinfo/keycloak-dev