Documenting Working Codes - Django Setup
Spent the whole day stuck on starting up a freaking django app
I ran this same shit yesterday and everything went well in the end.
Today was a different story
Up till now, even after getting the set up working, I can't tell exactly what I did or didnt do wrong.
Either way, posting this for the rainy day I might get stuck again.
It's not like programming is super hard
It's just demanding
And the older you get, the harder it is to sit your ass down for 10 hours a day without having it dragged by one thing or the other.
PostScript: one noticeable thing is that although I thought not running the script as an administrator made the server not to run, running a second server from from the normal Command Line showed that was not the cause. So, in effect, I still don't know jack about the shit that was staining this code all day.
Will report back when I figure it out hopefully
Leave Documenting Working Codes - Django Setup to:
Best Posts From HolyBranches
We have not curated any of holybranches's posts yet. But you can encourage our curation team to review posts by visiting them regularly and by referring other readers. Because we give priority to frequently read content.
More Posts From HolyBranches
- Trying to Manually set up a virtual environment with pipenv
- Documenting Working Codes: Re-Establishing The Fact That We Must Pipenv-Install Django Everytime We Create A New Project Inside The Directory Containing That New Project
- Documenting Working Codes: Must we pipenv-install django everytime we start a new project?
- Documenting Working Codes: Path and PipEnv
- Documenting Working Codes - A Django Setup Routine that actually Works
- Documenting Working Codes - Windows Powershell Trash?
- Documenting Working Codes - Django Setup
- A Hermit's Opinion - 3
- A Hermit's Opinion - 2
- A Hermit's Opinion - 1