-1👍
✅
I’ve managed to resolve the issue. Turns out since in this Django version I would need to separate the wsgi file for development and production use. therefore wsgi_prod.py and wsgi.py . This action was not needed in previous versions of Django.
0👍
There’s no need to upgrade or degrade your Django version for an OSError [Error123].
I got this error for weeks and I thought about the actual reason behind this error because my code and files were all perfect! But then, after weeks of observation of my code, I figured out the hell of that mistake!
ANSWER – Please create your APPS, STATIC-FOLDER, TEMPLATE-FOLDER, and further things within your PROJECT!!
DEMONSTRATION -> { ‘>>’ indicates next step}
OPEN POWERSHELL >> mkdir DIRECTORY_NAME >> cd DIRECTORY_NAME >> code .
this will open visual studio code within the directory named (DIRECTORY_NAME)
OPEN TERMINAL >> install django >> django startproject PROJECT_NAME >>
cd PROJECT_NAME >> python manage.py runserver >> COME OUT OF THE SERVER >> django startapp APP_NAME >> CONTINUE YOUR WORK IN THE VS CODE AND ONLY COM TO TERMINAL TO RUN SERVER.
- [Django]-Django auto logout and page redirection
- [Django]-Passing context from child to parent template in Django
- [Django]-Filtering by calculated (extra()) fields
- [Django]-How to config apache to run Django (mod_WSGI) and Rails (Passenger)
Source:stackexchange.com