jbpenrath f2c407f6a0 🌐(frontend) manage translation keys through i18next-cli ...

Rework totally the way to manage frontend translation keys. Currently we were
managing manually all those keys but now we want to use crowdin to manage our
languages so first we need to be able to extract frontend translation keys in
dedicated files.

Furthermore, we allow to setup frontend application languages and default
language through environment variables
(NEXT_PUBLIC_DEFAULT_LANGUAGE and NEXT_PUBLIC_LANGUAGES)

2025-10-06 10:06:14 +02:00

..

backend.defaults

✨(smtp) implement smtp_tls_security_level, follow RFC more closely (#336)

2025-09-19 12:28:38 +02:00

crowdin.defaults

✨(all) refactor several areas before 0.1 release (#265)

2025-07-15 10:41:55 +02:00

frontend.defaults

🌐(frontend) manage translation keys through i18next-cli

2025-10-06 10:06:14 +02:00

keycloak.defaults

✨(all) refactor several areas before 0.1 release (#265)

2025-07-15 10:41:55 +02:00

mta-in.defaults

🐛(mta-in) change MDA_API_BASE_URL default value

2025-09-29 10:57:55 +02:00

mta-out.defaults

✨(all) refactor several areas before 0.1 release (#265)

2025-07-15 10:41:55 +02:00

postgresql.defaults

✨(all) refactor several areas before 0.1 release (#265)

2025-07-15 10:41:55 +02:00

socks-proxy.defaults

✨(mta) add Direct mode for MTA out (#285)

2025-09-04 15:48:46 +02:00

widgets.defaults

✨(channels) add feedback widget and multiple inbound channels support (#301)

2025-09-24 14:30:40 +02:00