Yes that would be great and would be nice if we could also drop just a
'standalone' theme (not bundled with a provider) zip into the deployment
folder
Le mar. 10 janv. 2017 à 06:09, Stian Thorgersen <sthorger(a)redhat.com> a
écrit :
+1
It should be fairly simple to achieve as we have support for pluggable
theme providers (
https://github.com/keycloak/keycloak/blob/master/server-spi-private/src/m...
).
On 9 January 2017 at 22:05, Dmitry Telegin <mitya(a)cargosoft.ru> wrote:
> Hi,
>
> The new provider deployer is incredibly cool! But could this approach
> be extended to themes, so that they'd be deployed from the same
> archive?
>
> As of 2.5.0, the preferred way to deploy providers is via the
> "deployments" directory. But let's imagine a complete Keycloak
> extension that comprises several providers and a GUI theme. ATM, there
> are three deployment options:
> - old school: package everything into a JAR and deploy it as a module;
> - package providers and themes separately, deploy the former via the
> new mechanism and the latter as a module;
> - package everything into a single JAR and deploy via the new
> mechanism. This dynamically deployed module, according to JBoss/WildFly
> conventions, will be named "deployment.my-module-XYZ.jar"; use this
> name in the main config to load theme from the module. This is hacky
> and requires restart, which renders unusable the whole idea of hot
> (re)deployment.
>
> However, there could be another option, more natural and simple one,
> that is to automatically deploy providers *and* themes from the same
> archive placed into the "deployments" directory. What do you think?
>
> Cheers,
> Dmitry
> _______________________________________________
> 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