cookiecutter/cookiecutter-django
1
1
Fork 0
mirror of https://github.com/cookiecutter/cookiecutter-django.git synced 2025-08-14 00:44:53 +03:00
Code Issues Packages Projects Releases Wiki Activity

Update instructions for Docker

Browse Source
This commit is contained in:
Bruno Alla 2023-05-31 20:28:37 +01:00
parent bf1bab516a
commit d46ff405bf
No known key found for this signature in database
1 changed files with 4 additions and 2 deletions
Show Stats Download Patch File Download Diff File Expand all files Collapse all files

6
{{cookiecutter.project_slug}}/locale/README.rst
View File

@ -3,7 +3,7 @@ Translations
Translations strings will be placed in this folder when running::
python manage.py makemessages -all
{% if cookiecutter.use_docker == 'y' %}docker-compose -f local.yml run --rm django {% endif %}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::
@ -12,6 +12,8 @@ This should generate ``django.po`` (stands for Portable Object) files under each
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::
python manage.py compilemessages
{% if cookiecutter.use_docker == 'y' %}docker-compose -f local.yml run --rm django {% endif %}python manage.py compilemessages
Note that the ``.po`` files are NOT used by the application directly, so if the ``.mo`` files are out of dates, the content won't appear as translated even if the ``.po`` files are up to date.
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.