-
-
Notifications
You must be signed in to change notification settings - Fork 959
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
import_demo management command doesn't work in dockerized dev environment #4414
Comments
@nijel I'm guessing cloning the following repo needs to be done somehow: https://github.com/WeblateOrg/demo |
Maybe networking doesn't work in your Docker? There is often issue with DNS resolving. |
To me looks like something else, but I need to debug it, until now I couldn't find an easy way with Docker, here the stacktrace in case it helps:
|
The repository access error should raise a validation error as well. The file path seems correct:
The file is there: https://github.com/WeblateOrg/demo/blob/master/weblate/langdata/locale/django.pot Most importantly it runs fine for me and it runs fine during the CI tests. What is content of the /app/data/vcs/demo/gettext? Is there valid checkout of the demo repository? |
This issue looks like a support question. We try to answer these reasonably fast, but in case you are looking for faster resolution, please consider purchasing support subscription and make Weblate stronger. |
This issue has been automatically marked as stale because it has not had recent activity. It will be closed if no further activity occurs. Thank you for your contributions. |
Describe the bug
When running
docker-compose exec --user weblate weblate weblate import_demo
the following error is produced:WARNING File parse error: FileNotFoundError: [Errno 2] No such file or directory: '/app/data/vcs/demo/gettext/weblate/langdata/locale/django.pot'
To Reproduce
Steps to reproduce the behavior:
cd dev-docker
from project rootdocker-compose exec --user weblate weblate weblate import_demo
Expected behavior
As described in the documentation here a demo translation is loaded in the DB
The text was updated successfully, but these errors were encountered: