-
Notifications
You must be signed in to change notification settings - Fork 544
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
Demo not suitable for Windows, due to using uwsgi an django-dotenv #218
Comments
Hi @Meteor0id - I've now updated the virtualenv installation instructions to skip installing uwsgi, as that was only really needed for Heroku deployment. Afraid I don't have a Windows setup to hand, so I can't investigate what's failing with dotenv - happy to consider any suggestions for fixing this, though. |
I touched upon this issue also.
Later:
When running docker-compose run app /venv/bin/python manage.py load_initial_data:
Quite frustrating to not be able to see a demo of wagtail. |
I just ran into the same issue on windows. Up until the last issue with the missing directory, there were errors but the process continued. docker-compose run app /venv/bin/python manage.py load_initial_data I can tell part of the issue is when I look in the directory there is not "load_initial_data" file that I can see is available? Manage.py calls for a file that doesn't exist. |
It runs fine in my Windows 10 using the virtualenv method; just install the |
In Windows/Docker setup, I have found that "generated" images seem to disappear between down and up cycles, and even a load_initial_data won't recreate them. Here is an example from my app logs: [pid: 16|app: 0|req: 32/53] 172.19.0.6 () {44 vars in 888 bytes} [Sun Jun 21 14:26:47 2020] GET /media/images/bakingsoda.2e16d0ba.fill-430x254-c100_OImoI29.jpg => generated 6595 bytes in 87 msecs (HTTP/1.0 404) 5 headers in 158 bytes (1 switches on core 2) I am assuming these files (*Olmol29.jpg, e.g.) are generated by "collect_static" in django? Also, it is worth mentioning that I am running NGINX as a front end in my dev environment, but the above logs are coming from the upstream app docker container. |
For the above issue, the workaround for me was to run:
Then the "generated" images were recreated. But I'd be curious why? |
Following the virtualenv instructions, users will hit errors.
uwsig will fail to install, since os.uname() is not available in the Windows version of Phython.
Further more the module dotenv cant be loaded (even when installing djanog-dotenv or python-dotenv)
It would probably be a good idea to allow windows users to try out Wagtail, and make sure they dont hit errors before having tried Wagtail.
The text was updated successfully, but these errors were encountered: