Cedrick Lunven

Not at the moment it would have been part of v2. You can implement this behaviour with a custom CacheProxy and CacheManager using some messaging.

Hello Mojo, The files to edit are - https://github.com/ff4j/ff4j/blob/master/ff4j-web/src/main/resources/ff4j-embedded.css - https://github.com/ff4j/ff4j/tree/master/ff4j-web/src/main/resources/views From there build your version of ff4j-web and you are good to go

Merci Angélique ! Et de deux badges ! https://api.badgr.io/public/assertions/bd6591lHR9Ok6RphABWxBA?identity__email=roy_angee%40hotmail.com

Hi, Regarding configuring Stargate when you build it would make sense to edit the `application.conf` file with proper consistency level and reuse it, not hardcoding. As the consistency level is...

Personally a fresh install of STS + dropping the `.metadata` of the workspaces was the solution.

The error came because you are using a token that is not admin and cannot do the lookup dbid->dbname i think but the error needs to be more explicit.

The current file is working with postgres. You can update your settings to be not case sensitive at postgres side or edit the `sql` file to match your settings.

1.9 will be released `20/12/2022` (sorry for the wait). All tests are cleared, going over a last pass in the tickets. Sample `application.yml` ```yml server: port: ${PORT:8080} ff4j: api: context-path:...

haaaa `n+1` select issue. you are totally correct. Now `readALL()` will only be invoked in the administration console so the performance hit is limited. I will mark this as low...

I would close this for now the custom properties can be delete by clickng the bin icon.