django-tutorial | Django 4 tutorial projects | Learning library

Looks like you don't have the OpenSSL library or its header files installed.

The answer very simple, my server is using a programme name passenger, the official website for more information: https://www.phusionpassenger.com/

Now error very simply; passenger can't find my application, All I did was move my project and app folder on the same layer passenger_wsgi.py and it works like charm.

What does your settings.py look like? have you added polls into your INSTALLED_APPS?

After trying almost everything. I moved my os from windows to Linux with Ubuntu 18 (Udemy course to learn Ubuntu) through virtual box then simply did

sudo apt install geos sudo apt install prog4 sudo apt install gdal

installed postgres sql and pgadmin3 (pg admin 4 is not available easily for install as of today on ubuntu ) made the database on called 'geodjango' using pgadmin3 then sudo apt install postgis

then pip installed psycopg2 and dj-database-url

I would recommend to stay away from the make & make install methods they take too long and always throws errors. After this the GeoDjango tutorial was a breeze

As it turns out, I wasn't paying attention to the process in which the application was served.

So, riding on this answer, I figured out it breaks down like this:

1. nginx gets a URL, decides where to pull from - in our case, Gunicorn.
2. Gunicorn searches for the proper Python file to pull - in our case, Django.
3. Djnago gets executed and the app loads (including our admin panel).

In this case, after making the changes to the admin panel I've restarted nginx, but not Gunicorn. Restarting Gunicorn solved the problem, and if you looked at my last comment - nginx crashed because of a typo in my admin.py file (added well after writing this question, during my attempt to fix it, and thus does not appear in the OP).

This is deprecated from 1.10:

You've got a missing closing parenthesis in line 39:

Your input is using {{ songs.id }}. It should be {{ song.id }}.

Django's terminology isn't perfect. Both "static" and "media" files are static (and in production both should be served by the web server without involving Django). In addition, "media" files can be any kind of file, not just media. A better terminology might have been "app files" and "data files".

"Static files" are those that are permanent; they are part of your application. These are typically JavaScript, CSS, and images such as logos and icons.

"Media files" are application data. They are, in a way, part of your database, but Django prefers to store them outside the database. Typically these are the files that correspond to ImageField and FileField.

In development, Django automatically serves static files. The only configuration you need is STATIC_URL = '/static/'. If you have file my_app/static/my_app/js/myjsfile.js, Django will serve that at http://localhost:8000/static/my_app/js/myjsfile.js (the /static/ in the URL is actually specified by STATIC_URL). In templates, you typically use something like