1:51 p.m.
Did you know with a flip of a switch that a jarless Keycloak distro can
be created? Just edit <root>/distribution/server-provisioning.xml and
remove extraction params:
<server-provisioning xmlns="urn:wildfly:server-provisioning:1.2"
extract-schemas="true">
<feature-packs>
<feature-pack groupId="org.keycloak"
artifactId="keycloak-server-feature-pack"
version="${project.version}"/>
</feature-packs>
</server-provisioning>
All the module.xml reference maven artifacts and when you boot the
distro it tries by default to resolve them in ~/.m2, you can even point
it to a remote distro and it will download the jars.
11:56 p.m.
I knew, but are there any benefits?
On 18 August 2017 at 20:51, Bill Burke <bburke(a)redhat.com> wrote:
Did you know with a flip of a switch that a jarless Keycloak distro
can
be created? Just edit <root>/distribution/server-provisioning.xml and
remove extraction params:
<server-provisioning xmlns="urn:wildfly:server-provisioning:1.2"
extract-schemas="true">
<feature-packs>
<feature-pack groupId="org.keycloak"
artifactId="keycloak-server-feature-pack"
version="${project.version}"/>
</feature-packs>
</server-provisioning>
All the module.xml reference maven artifacts and when you boot the
distro it tries by default to resolve them in ~/.m2, you can even point
it to a remote distro and it will download the jars.
_______________________________________________
keycloak-dev mailing list
keycloak-dev(a)lists.jboss.org
https://lists.jboss.org/mailman/listinfo/keycloak-dev
3:49 a.m.
Thanks for the tip!
I see the benefit just during development. Or is it some other?
Usually when I do changes in Keycloak sources in some module (eg. in
keycloak-model-jpa module) I need to:
1) Build the module with "mvn clean install"
2) Copy the keycloak-model-jpa.jar to the modules in my Wildfly server.
Or rebuild whole distro.
3) Restart the Wildfly
With this, you don't need step 2.
Still embedded undertow is best as you don't even need step 1 when
running KeycloakServer from Idea ;) And for UI only changes, even server
restart is not needed with embedded undertow and -Dresources option.
Marek
On 21/08/17 06:56, Stian Thorgersen wrote:
I knew, but are there any benefits?
On 18 August 2017 at 20:51, Bill Burke <bburke(a)redhat.com> wrote:
> Did you know with a flip of a switch that a jarless Keycloak distro can
> be created? Just edit <root>/distribution/server-provisioning.xml and
> remove extraction params:
>
> <server-provisioning xmlns="urn:wildfly:server-provisioning:1.2"
> extract-schemas="true">
> <feature-packs>
> <feature-pack groupId="org.keycloak"
> artifactId="keycloak-server-feature-pack"
version="${project.version}"/>
> </feature-packs>
> </server-provisioning>
>
> All the module.xml reference maven artifacts and when you boot the
> distro it tries by default to resolve them in ~/.m2, you can even point
> it to a remote distro and it will download the jars.
>
>
> _______________________________________________
> keycloak-dev mailing list
> keycloak-dev(a)lists.jboss.org
> https://lists.jboss.org/mailman/listinfo/keycloak-dev
>
_______________________________________________
keycloak-dev mailing list
keycloak-dev(a)lists.jboss.org
https://lists.jboss.org/mailman/listinfo/keycloak-dev
7:36 a.m.
I've been using a jarless distro since I first started working on
Keycloak. I like working with a "real" WF server instead of embedded
undertow. The tradeoff is that I do need to do step 1 (build the module).
The only thing you really need to change in server-provisioning.xml is
the copy-module-artifacts param. Just change it from true to false.
I have a have a bat file that builds jarless server, adds admin user,
and points the theme stuff to my dev directory:
cd c:\GitHub\keycloak\distribution\server-dist
call mvn clean
sed -i
's/copy-module-artifacts="true"/copy-module-artifacts="false"/'
/cygdrive/c/GitHub/keycloak/distribution/server-provisioning.xml
call mvn compile -DskipTests
sed -i
's/copy-module-artifacts="false"/copy-module-artifacts="true"/'
/cygdrive/c/GitHub/keycloak/distribution/server-provisioning.xml
cd c:\GitHub\keycloak\distribution\server-dist\target\keycloak*\modules
copy
c:\GitHub\keycloak\distribution\server-dist\src\main\modules\layers.conf
set NOPAUSE=true
cd c:\GitHub\keycloak\distribution\server-dist\target\keycloak*\bin
call add-user-keycloak -u admin -p admin
call jboss-cli --file=/bat/write-theme-dir.cli
The write-theme-dir.cli script is handy on its own:
embed-server --server-config=standalone.xml
/subsystem=keycloak-server/theme=defaults/:write-attribute(name=dir,value=/GitHub/keycloak/themes/src/main/resources/theme)
/subsystem=keycloak-server/theme=defaults/:write-attribute(name=cacheTemplates,value=false)
/subsystem=keycloak-server/theme=defaults/:write-attribute(name=cacheThemes,value=false)
On 8/21/2017 4:49 AM, Marek Posolda wrote:
Thanks for the tip!
I see the benefit just during development. Or is it some other?
Usually when I do changes in Keycloak sources in some module (eg. in
keycloak-model-jpa module) I need to:
1) Build the module with "mvn clean install"
2) Copy the keycloak-model-jpa.jar to the modules in my Wildfly server.
Or rebuild whole distro.
3) Restart the Wildfly
With this, you don't need step 2.
Still embedded undertow is best as you don't even need step 1 when
running KeycloakServer from Idea ;) And for UI only changes, even server
restart is not needed with embedded undertow and -Dresources option.
Marek
On 21/08/17 06:56, Stian Thorgersen wrote:
> I knew, but are there any benefits?
>
> On 18 August 2017 at 20:51, Bill Burke <bburke(a)redhat.com> wrote:
>
>> Did you know with a flip of a switch that a jarless Keycloak distro can
>> be created? Just edit <root>/distribution/server-provisioning.xml and
>> remove extraction params:
>>
>> <server-provisioning xmlns="urn:wildfly:server-provisioning:1.2"
>> extract-schemas="true">
>> <feature-packs>
>> <feature-pack groupId="org.keycloak"
>> artifactId="keycloak-server-feature-pack"
version="${project.version}"/>
>> </feature-packs>
>> </server-provisioning>
>>
>> All the module.xml reference maven artifacts and when you boot the
>> distro it tries by default to resolve them in ~/.m2, you can even point
>> it to a remote distro and it will download the jars.
>>
>>
>> _______________________________________________
>> keycloak-dev mailing list
>> keycloak-dev(a)lists.jboss.org
>> https://lists.jboss.org/mailman/listinfo/keycloak-dev
>>
> _______________________________________________
> keycloak-dev mailing list
> keycloak-dev(a)lists.jboss.org
> https://lists.jboss.org/mailman/listinfo/keycloak-dev
_______________________________________________
keycloak-dev mailing list
keycloak-dev(a)lists.jboss.org
https://lists.jboss.org/mailman/listinfo/keycloak-dev
9:02 a.m.
Helps in dev a lot like you said.
I was told Wildfly team builds it for their arquillian test harness.
Not sure why it would be beneficial.
Could define "profiles" that are small downloads and ready to run.
At least for Wildfly, saves disk space or allows for a mounted NFS
shared maven repo.
Jason Greene was talking about using shared docker data volumes +
mmapped jars. This kind of structure might be able to facilitate that.
On 8/21/17 4:49 AM, Marek Posolda wrote:
Thanks for the tip!
I see the benefit just during development. Or is it some other?
Usually when I do changes in Keycloak sources in some module (eg. in
keycloak-model-jpa module) I need to:
1) Build the module with "mvn clean install"
2) Copy the keycloak-model-jpa.jar to the modules in my Wildfly
server. Or rebuild whole distro.
3) Restart the Wildfly
With this, you don't need step 2.
Still embedded undertow is best as you don't even need step 1 when
running KeycloakServer from Idea ;) And for UI only changes, even
server restart is not needed with embedded undertow and -Dresources
option.
Marek
On 21/08/17 06:56, Stian Thorgersen wrote:
> I knew, but are there any benefits?
>
> On 18 August 2017 at 20:51, Bill Burke <bburke(a)redhat.com> wrote:
>
>> Did you know with a flip of a switch that a jarless Keycloak distro can
>> be created? Just edit <root>/distribution/server-provisioning.xml and
>> remove extraction params:
>>
>> <server-provisioning xmlns="urn:wildfly:server-provisioning:1.2"
>> extract-schemas="true">
>> <feature-packs>
>> <feature-pack groupId="org.keycloak"
>> artifactId="keycloak-server-feature-pack"
>> version="${project.version}"/>
>> </feature-packs>
>> </server-provisioning>
>>
>> All the module.xml reference maven artifacts and when you boot the
>> distro it tries by default to resolve them in ~/.m2, you can even point
>> it to a remote distro and it will download the jars.
>>
>>
>> _______________________________________________
>> keycloak-dev mailing list
>> keycloak-dev(a)lists.jboss.org
>> https://lists.jboss.org/mailman/listinfo/keycloak-dev
>>
> _______________________________________________
> keycloak-dev mailing list
> keycloak-dev(a)lists.jboss.org
> https://lists.jboss.org/mailman/listinfo/keycloak-dev
4:30 a.m.
Thanks for the hint! I didn't know about that and started using it
when working on adapters for WF. Less painful development now :-)
--Hynek
On Fri, Aug 18, 2017 at 8:51 PM, Bill Burke <bburke(a)redhat.com> wrote:
Did you know with a flip of a switch that a jarless Keycloak distro
can
be created? Just edit <root>/distribution/server-provisioning.xml and
remove extraction params:
<server-provisioning xmlns="urn:wildfly:server-provisioning:1.2"
extract-schemas="true">
<feature-packs>
<feature-pack groupId="org.keycloak"
artifactId="keycloak-server-feature-pack"
version="${project.version}"/>
</feature-packs>
</server-provisioning>
All the module.xml reference maven artifacts and when you boot the
distro it tries by default to resolve them in ~/.m2, you can even point
it to a remote distro and it will download the jars.
_______________________________________________
keycloak-dev mailing list
keycloak-dev(a)lists.jboss.org
https://lists.jboss.org/mailman/listinfo/keycloak-dev
--
--Hynek
2437
days inactive
2440
days old
5 comments
5 participants
participants (5)
-
Bill Burke -
Hynek Mlnarik -
Marek Posolda -
Stan Silvert -
Stian Thorgersen