Update changelog v4.2.13

CHANGELOG.md

@@ -1,3 +1,8 @@
+### **4.2.13** (2021-12-08)  
+  
+- Fix broken link about how to import fonts #62  
+- Add a video to show how to test the theme in a local container    
+  
 ### **4.2.12** (2021-12-08)  
   
 - Update post build instructions    

README.md

@@ -374,7 +374,8 @@ this limitation doesn't apply, you can import fonts however you see fit.
 -   If it is possible, use Google Fonts or any other font provider.
 -   If you want to host your font recommended approach is to move your fonts into the `public`
     directory and to place your `@font-face` statements in the `public/index.html`.  
-    Example [here](https://github.com/InseeFrLab/onyxia-ui/blob/0e3a04610cfe872ca71dad59e05ced8f785dee4b/public/index.html#L6-L51).
+    Example [here](https://github.com/garronej/keycloakify-demo-app/blob/9aa2dbaec28a7786d6b2983c9a59d393dec1b2d6/public/index.html#L27-L73)
+    (and the font are [here](https://github.com/garronej/keycloakify-demo-app/tree/main/public/fonts/WorkSans)).
 -   You can also [use non relative url](https://github.com/garronej/keycloakify-demo-app/blob/2de8a9eb6f5de9c94f9cd3991faad0377e63268c/src/fonts.scss#L16) but don't forget [`Access-Control-Allow-Origin`](https://github.com/garronej/keycloakify-demo-app/blob/2de8a9eb6f5de9c94f9cd3991faad0377e63268c/nginx.conf#L17-L19).
 
 # Implement context persistence (optional)
@@ -466,10 +467,10 @@ It's all-right because every statement that can fail is inside an `<#attempt><#r
 
 The problem of templates taking a long time to load only happens in the test environment, when you have a console logging all the above-mentioned `.ftl` warnings in real time. Logging all those warnings is what takes time. Once in production page load is way faster.
 
-If you run the docker container locally we aknowelage that the loading time is getting out of hand.
+If you run the docker container locally we acknowledge that the loading time is getting out of hand.
 We are [in the process](https://github.com/InseeFrLab/keycloakify/pull/63) of resolving this issue.
 
-In the meantime we recommend to run the docker container as a background task.
+In the meantime we recommend [to run the docker container as a background task](https://youtu.be/F29Z1GaH-jk).
 
 # Adding custom message (to `i18n/useKcMessage.tsx`)
 

package.json

@@ -1,6 +1,6 @@
 {
     "name": "keycloakify",
-    "version": "4.2.12",
+    "version": "4.2.13",
     "description": "Keycloak theme generator for Reacts app",
     "repository": {
         "type": "git",

src/bin/build-keycloak-theme/build-keycloak-theme.ts

@@ -121,13 +121,14 @@ export function main() {
             "",
             `👉 $ ./${pathRelative(reactProjectDirPath, pathJoin(keycloakThemeBuildingDirPath, containerLaunchScriptBasename))} 👈`,
             "",
-            "To test your theme: ",
+            "Once your container is up and running: ",
             "- Log into the admin console 👉 http://localhost:8080 username: admin, password: admin 👈",
             '- Create a realm named "myrealm"',
             '- Create a client with id "myclient" and root url: "https://www.keycloak.org/app/"',
             `- Select Login Theme: ${themeName} (don't forget to save at the bottom of the page)`,
-            `- Go to 👉 https://www.keycloak.org/app/ 👈 Click "Save" then "Sign in"`,
-            `You should see your login page, More details: https://www.keycloak.org/getting-started/getting-started-docker`,
+            `- Go to 👉 https://www.keycloak.org/app/ 👈 Click "Save" then "Sign in". You should see your login page`,
+            "",
+            "Video demoing this process: https://youtu.be/N3wlBoH4hKg",
             "",
         ].join("\n"),
     );