-
Notifications
You must be signed in to change notification settings - Fork 423
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
"Running in production" doesn't point to the app.wsgi file #543
Labels
Comments
good catch! I believe we can add it to the MANIFEST.in at least. But you're right the paths can be tedious to find within the pip site-packages folders... Mentionning the file URL online also makes sense. As a stretch goal, we could also run uwsgi in the Dockerfile to make sure the app.wsgi runs properly there |
leplatrem
added a commit
that referenced
this issue
May 24, 2016
leplatrem
added a commit
that referenced
this issue
May 24, 2016
lavish205
pushed a commit
to lavish205/kinto
that referenced
this issue
Jun 20, 2016
lavish205
pushed a commit
to lavish205/kinto
that referenced
this issue
Jun 20, 2016
…sions-documentation First round of improving permissions documentation (fixes Kinto#543)
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
The running in production with uwsgi doc talks about an
app.wsgi
which is provided, but1/ it's not "there" in the project folder if kinto was installed using pip
2/ it's not in the pip package I think (it's not in https://github.com/Kinto/kinto/blob/master/MANIFEST.in)
So maybe the documentation should be modified to link to the app.wsgi in the repository? (like https://github.com/Kinto/kinto/blob/master/app.wsgi)
The text was updated successfully, but these errors were encountered: