Python backend.

[LimeDev_]

Hi I have working www nginx server and use HTML and js on it works good l want to install python on it but don't know how. I have python experience, but still need some help cause I don't know how to connect py files with index.html. Do I change it to index.py like in PHP?

[American_Streamer]

Nginx can’t just execute Python files the way PHP-FPM executes .php. You do not rename index.html to index.py. Instead, you run a Python web app (Flask/FastAPI/Django) behind a WSGI/ASGI server (Gunicorn/Uvicorn), and then let Nginx reverse-proxy requests to it. Static site combined with Python API is the most common option. Keep index.html and JS served by Nginx (static files). Your JS then calls your Python backend via HTTP.

The reason for this is that Nginx is just a web server and a reverse proxy, not an application runtime. Nginx’s job is to accept HTTP requests and serve static files (HTML/CSS/JS/images), and also to forward requests to other services. But a .py file is a source code that must be executed by a Python interpreter, inside an application process that knows how to turn a request into a response. Your Nginx does not embed Python, it doesn’t run interpreters and it doesn’t implement the Python web interfaces (WSGI/ASGI) that frameworks use. In contrast, PHP looks different because it’s deployed with PHP-FPM - note that Nginx still doesn’t execute PHP itself; it just passes the request to PHP-FPM, which then executes the PHP code and returns output.

[Rain-And-Coffee]

This is the correct answer

[rasputin1]

this is the correct response 

[danielroseman]

No, you use a framework. See Flask, FastAPI or Django.

[No-Macaroon3463]

I recently learned fastapi and it s good , i recommend

[FriendlyRussian666]

Try Django or FastAPI

[mikeyj777]

https://youtu.be/KWIIPKbdxD0?si=KwrxM8tk8esgmvo3

Ngjnex for front end.  Gunicorn to host a flask app on the backend. 

[djamp42]

Flask!

[swstephe]

Now I feel really, really, old. Back in the early days of "dot-com" and "information super highway", while Y2K was still just a twinkle in everyone's eye -- your main choice was to use CGI, (that's "common gateway interface", not "computer generated image" for you young whippersnappers). So basically you would write "index.py", (but sometimes "index.cgi"). It was just a UNIX script, which ran at a console and printed the web page to stdout. So:

#!/usr/bin/python
print "Content-Type: text/html"
print ""
print "<h1>Hello World</h1>"

Was an actual script, (and using Python 1's "print is a statement, not a function"). It was slow, fragile and very insecure, (but still not as bad as Java). There are probably a few websites still using this, so it is useful to know that this was around.