2e111364a2
This commit includes: - Django backend with multi-tenancy (django-tenants) - React + TypeScript frontend with Vite - Platform administration API with role-based access control - Authentication system with token-based auth - Quick login dev tools for testing different user roles - CORS and CSRF configuration for local development - Docker development environment setup 🤖 Generated with [Claude Code](https://claude.com/claude-code) Co-Authored-By: Claude <noreply@anthropic.com>
Translations
Start by configuring the LANGUAGES settings in base.py, by uncommenting languages you are willing to support. Then, translation strings will be placed in this folder when running:
docker compose -f docker-compose.local.yml run --rm django python manage.py makemessages --all --no-location
This should generate django.po (stands for Portable Object) files under each locale <locale name>/LC_MESSAGES/django.po. Each translatable string in the codebase is collected with its msgid and need to be translated as msgstr, for example:
msgid "users"
msgstr "utilisateurs"
Once all translations are done, they need to be compiled into .mo files (stands for Machine Object), which are the actual binary files used by the application:
docker compose -f docker-compose.local.yml run --rm django python manage.py compilemessages
Note that the .po files are NOT used by the application directly, so if the .mo files are out of date, the content won't appear as translated even if the .po files are up-to-date.
Production
The production image runs compilemessages automatically at build time, so as long as your translated source files (PO) are up-to-date, you're good to go.
Add a new language
- Update the
LANGUAGESsetting to your project's base settings. - Create the locale folder for the language next to this file, e.g.
fr_FRfor French. Make sure the case is correct. - Run
makemessages(as instructed above) to generate the PO files for the new language.