[keycloak-dev] Remove built-in themes from themes directory

[Stian Thorgersen]

That's just messy

On Fri, 20 Sep 2019 at 13:36, Stan Silvert <ssilvert at redhat.com> wrote:

> How about having both?
>
> Out of the box, it's in development mode and it uses what we have today.
> But we show warnings everywhere that you are in development mode.
>
> In production mode, it always uses the zip.
>
> On 9/20/2019 3:52 AM, Stian Thorgersen wrote:
>
> Making things easy and just working is a high priority to us, but I wonder
> if it would actually be easier and more guaranteed to just work if built-in
> themes is in a zip. Arguments are basically:
>
> * Prevents anyone modifying the built-in themes, which if you do would
> bring you problems later on
> * Makes it easier to update as the whole themes directory can be kept.
> Currently the built-in themes has to be replaced, but not custom themes
>
> What might actually be real nice is to have a little tool to work with
> themes. Something like
>
> kc-theme create --theme mytheme --parent keycloak
> kc-theme list-templates --type login
> kc-theme add-custom-template --theme mytheme --template login.ftl
> kc-theme add-custom-messages --theme mytheme --language en
>
> On Thu, 19 Sep 2019 at 20:00, Asbjørn Thegler <asbjoern at deranged.dk>
> wrote:
>
>> On Thu, Sep 19, 2019 at 7:14 PM Stan Silvert <ssilvert at redhat.com> wrote:
>> > The easier it is to get that first "success" the greater the chance he
>> > will continue onward and choose Keycloak.
>> Being new to KeyCloak - this is something I can agree with. The glee
>> of running a project that just works the first time is amazing.
>>
>> It's part of the reason we stuck with KeyCloak, if I'd have to guess.
>>
>
>