[keycloak-dev] Quickstarts on keycloak GH organization

[Sebastien Blanc]

On Tue, Jan 17, 2017 at 8:43 AM, Stian Thorgersen <sthorger at redhat.com>
wrote:

>
>
> On 16 January 2017 at 12:09, Sebastien Blanc <sblanc at redhat.com> wrote:
>
>> Hi !
>>
>> As you probably know we already have a set of quickstarts in this repo
>> https://github.com/redhat-developer/redhat-sso-quickstarts.
>>
>> With Stian, we decided to mirror this repo into the keycloak organization
>> and this mirror will now be the "leading" repository meaning that all
>> updates/fixes should happen here and will after that be ported back to the
>> redhat-sso-quickstart repo.
>>
>> Some important points :
>>
>>  * A cleanup is needed for the keycloak quickstarts, for instance, all
>> occurrences to RH-SSO / EAP needs to be replaced by Keycloak / WildFly. A
>> first PR tackling this is available :
>> https://github.com/keycloak/keycloak-quickstarts/pull/1   , feel free to
>> review it to see if we missed any occurrence.
>>
>
> I merged this. One comment is that we should just target the latest
> WildFLy release (10.1) rather than WF 8, 9 and 10.
>
I was wondering about the same while I was updating the READMEs. Actually
that will make it easier, I will update the readmes.

>
>
>>
>> * We also introduced keycloak BOMs for these quickstarts. For now these
>> are
>> only available here :  https://github.com/stianst/keycloak/tree/BOMS
>>
>> * For a better User Experience, master will be based on the latest stable
>> Keycloak release and the branch "dev" will be used for new development.
>>
>
> I'll get the release CI to update the master branch whenever a KC release
> is done. Ideally I'd like to have  a single command to run at the root pom
> to do that. I.e. mvn versions:set.
>
Speaking of CI, do we want CI for the quickstarts ?

>
>
>>
>> * The remaining examples from
>> https://github.com/keycloak/keycloak/tree/master/examples needs to be
>> integrated into this new quickstarts repo. This is probably the biggest
>> task
>>
>
> +1 We'll need to discuss what and how though. Some quickstarts duplicate
> what we had in examples, while others will be more a straightforward port.
>
I will start a separate thread for that.

>
>
>>
>> * A PR containing SpringBoot/Spring Security quickstarts will follow
>> today.
>>
>
> Merged
>
>
>>
>> * The NodeJS quickstart (
>> https://github.com/redhat-developer/redhat-sso-quickstarts/
>> tree/7.1.x-devel/service-nodejs
>> ) needs to be copied as well to the keycloak repo.
>>
>
> Merged
>
>
>>
>> We still need to define a "process" to keep KC and RH-SSO quickstarts in
>> sync (full manual, half scripted ... ).
>>
>
> Fully automated is the aim!
>
>
>>
>> If you have any question, feel free to ask.
>>
>> Sebi
>> _______________________________________________
>> keycloak-dev mailing list
>> keycloak-dev at lists.jboss.org
>> https://lists.jboss.org/mailman/listinfo/keycloak-dev
>>
>
>