<div dir="ltr">You can chuck it into standalone/configuration/themes for production as well. The docs suggest to not do that as in production you want a stable set of files and make sure all nodes in a cluster has the same versions. Themes are also by default cached, both on the server side and in the browser.</div><div class="gmail_extra"><br><div class="gmail_quote">On 18 January 2016 at 08:59, Juraci Paixão Kröhling <span dir="ltr"><<a href="mailto:juraci@kroehling.de" target="_blank">juraci@kroehling.de</a>></span> wrote:<br><blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex"><span class="">On 16.01.2016 23:29, Travis De Silva wrote:<br>
> I don't think wildfly does hot deployment for modules.<br>
<br>
</span>How about adding/removing the module via the Wildfly CLI?<br>
<br>
module add --name=the.theme... --resources=...jar<br>
<br>
- Juca.<br>
<div class="HOEnZb"><div class="h5">_______________________________________________<br>
keycloak-user mailing list<br>
<a href="mailto:keycloak-user@lists.jboss.org">keycloak-user@lists.jboss.org</a><br>
<a href="https://lists.jboss.org/mailman/listinfo/keycloak-user" rel="noreferrer" target="_blank">https://lists.jboss.org/mailman/listinfo/keycloak-user</a><br>
</div></div></blockquote></div><br></div>