[keycloak-dev] Branches for the quickstarts

[Bruno Oliveira]

Latest and master were created. The branches quickstarts-dev and kc-3.0.0
deleted.

So now we have:

- Latest: all the stuff stable and in sync with the latest release of
Keycloak server
- master: all the stuff based on the latest commits from Keycloak on master.

On Fri, May 19, 2017 at 4:03 AM Stian Thorgersen <sthorger at redhat.com>
wrote:

> The default branch regardless what it's called should be the branch users
> should use for the latest Keycloak release. The reasoning for that is that
> a user when trying the quickstarts should not have to do a clone then
> checkout another branch.
>
> We could either go with:
>
> 1. master (default branch) and dev
> 2. latest (default branch) and master
>
> My vote goes to option 2.
>
> On 19 May 2017 at 01:41, Bruno Oliveira <bruno at abstractj.org> wrote:
>
>> I truly feel that we are talking about completely different things.
>>
>> But you can add your considerations to this Jira:
>> https://issues.jboss.org/browse/KEYCLOAK-3577
>>
>> On Thu, May 18, 2017, 4:58 PM Stan Silvert <ssilvert at redhat.com> wrote:
>>
>> > What we really need for the quickstarts is something Bill has been
>> > talking about for a long time.
>> >
>> > It's a bundle of Keycloak and examples that just boots up and works.
>> > Otherwise, the quickstarts are way too hard to get running.  Nobody
>> > wants to spend 2 or 3 hours on a "quickstart". That's what I had to do
>> > recently and I already know what's going on.  I hate to think about what
>> > someone new to Keycloak needs to go through just to see an example.
>> >
>> > This doesn't have to mean that everything runs in the same WildFly
>> > instance like the old demo dist.  The problem with that was that it
>> > didn't show Keycloak set up as a stand-alone server.
>> >
>> > What you need is a single bundle that lets you run Keycloak standalone
>> > and a standalone app server.  I see a couple of ways to do it:
>> > 1) Use domain mode where you get a domain controller, Keycloak instance,
>> > and app server instance all in the same JVM.
>> > 2) Use two separate server configs and run in two JVM's.
>> >
>> > I think #2 is the best.  The Keycloak instance runs on port 8180 and the
>> > app server runs on 8080.  You only need one download of
>> > WildFly/Keycloak, but you package it with two configs.  So you have:
>> > /bin
>> > /modules
>> > /domain (don't actually need this one)
>> > /standalone
>> > /keycloak
>> >
>> > To run Keycloak (preloaded with quickstart realm):
>> >  > standalone --server-config=keycloak
>> > -Djboss.socket.binding.port-offset=100
>> >
>> > To run app server (preloaded with quickstart apps):
>> >  > standalone
>> >
>> >
>> >
>> > On 5/18/2017 1:59 PM, Bruno Oliveira wrote:
>> > > Hmmm I'm not sure about that. That would be the completely opposite of
>> > what
>> > > we already do to any repository today. If people want the stable
>> release
>> > of
>> > > the quickstarts they could just get 3.x or download the zip files,
>> nope?
>> > >
>> > > On Thu, May 18, 2017 at 2:15 PM Sebastien Blanc <sblanc at redhat.com>
>> > wrote:
>> > >
>> > >> We should also consider the opposite : master is the stable released
>> > >> version and a branch for development . I already had confused people
>> > >> downloading KC server and cloning the QuickStarts and expecting it to
>> > work.
>> > >> But tbh I do not have a string opinion on that.
>> > >> Le jeu. 18 mai 2017 à 18:57, Bruno Oliveira <bruno at abstractj.org> a
>> > >> écrit :
>> > >>
>> > >>> While working today on the fix of some quickstarts. I'm
>> > >>> considering to create a separated branch only for stable versions of
>> > the
>> > >>> quickstarts.
>> > >>>
>> > >>> In this way 'master' would be used only for development based on the
>> > >>> latest bits from Keycloak repo. And 3.1.x, to the latest stable
>> > >>> release on Maven central.
>> > >>>
>> > >>> Does it make any sense?
>> > >>>
>> > >>> --
>> > >>>
>> > >>> abstractj
>> > >>>
>> > >> _______________________________________________
>> > >>> keycloak-dev mailing list
>> > >>> keycloak-dev at lists.jboss.org
>> > >>> https://lists.jboss.org/mailman/listinfo/keycloak-dev
>> > >>>
>> > > _______________________________________________
>> > > keycloak-dev mailing list
>> > > keycloak-dev at lists.jboss.org
>> > > https://lists.jboss.org/mailman/listinfo/keycloak-dev
>> >
>> > _______________________________________________
>> > keycloak-dev mailing list
>> > keycloak-dev at lists.jboss.org
>> > https://lists.jboss.org/mailman/listinfo/keycloak-dev
>> _______________________________________________
>> keycloak-dev mailing list
>> keycloak-dev at lists.jboss.org
>> https://lists.jboss.org/mailman/listinfo/keycloak-dev
>>
>
>