-
Notifications
You must be signed in to change notification settings - Fork 162
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
installation flow in setup.rst #67
Comments
ok, that one (no attribute user) is fixed, one has to change MIDDLEWARE to MIDDLEWARE_CLASSES... i do not know why that is not generated correctly. the warning persistst and i get another warning:
|
and i've overseen this one:
could be corrected in the doc as well. |
Are you using Django 1.10, right? |
i installed via pip, looking into what is the desired django version for puput? isn't it 1.9 and if so why is 1.9 installed? |
i was asked to issue a finally the link "Continue reading »" points to a wrong location (i have a setup where django is in a sub-path "/PATH_PREFIX/blog/..." only so i have |
@emdete could you open a new issue for each issue that you have? Is easy for me to track which issues are resolved or not. thanks |
i followed the docs/setup.rst (after a
virtualenv -p /usr/bin/python3 env; source ./env/bin/activate; pip install django; django-admin.py startproject demo
) line by line. when doing thedemo/manage.py migrate
(and setting PROJECT_ROOT as requested) (and fixing the errordjango.core.exceptions.ImproperlyConfigured: COMPRESS_ROOT defaults to STATIC_ROOT, please define either
) i get a:when requesting i get an error:
is the setup document uptodate and meant to work out of the box?
The text was updated successfully, but these errors were encountered: