-
Notifications
You must be signed in to change notification settings - Fork 3
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
No module named 'production_settings' #5
Comments
I am not really sure, what this might be caused by... I'll have a look at it and try to figure it out. Also, paging @raphaelm, the almighty pretix-god, for further insights, as the only place I could find production_settings is in https://github.com/pretix/pretix/blob/master/deployment/docker/production_settings.py ;-) |
My wild guess would be that you need to
Haven't tested it, though. |
I tried as @raphaelm suggested to cd into /pretix/src via Dockerfile and also tried to add it to PATH but the situation remains. I will try around some more as it seems PATH is not modified permanently in the docker build env. current Dockerfile:
|
Please try this:
|
PYTHONPATH did the trick, the following Dockerfile actually worked for me to build the plugin:
|
@pc-coholic just now saw your answer. tried it and it works as well. Thx guys, your fast input made this horrible problem dissolve in a flash :) 👍 |
I ran into this issue. I think the root cause is lack of DJANGO_SETTINGS_MODULE. I specified it as in the docs and it worked.
|
Hi,
I'm trying to deploy this plugin inside a docker installation via the official instructions but it fails with 'No module named 'production_settings'. I'm not sure whats the root cause of this problem as I did not find any import directive for 'production_settings'.
So far this seems only to affect the cashpayment plugin (tried with pretix-pages, pretix-passbook - could build both of them without this problem)
Maybe I'm just missing something here...
Any help would be great. Thanks in advance!
my Dockerfile looks like this:
build output as follows:
The text was updated successfully, but these errors were encountered: