You are implicitly assuming a lot about my server, you definitely do not understand anything about it, and I think this is part of the reason for your concern. Allow me to explain --

To your first point, I understand that it is convention for /var/www to often serve static files. However, this is not the case on my server, you are assuming it is, but it isn't. This is not the case every time this directory is used, either. It is not like your system suddenly chowns everything to a public group whenever you put files into /var/www.

Secondly, as you said, I have a proxy pass -- therefore, the only time that port 80 is listened to is whenever it is to be redirected to a different port, I believe in the case of the article this is port 8000. Also, it really does not make a difference what directory I put files in. /var/www on my machine is owned by route. There are NO static files served on this server at all, so I do not know why this keeps coming up.

To your second point, this project is containerized with Docker. Just because I am using a proxy pass and serving files out of /var/www should not give you the impression that this whole thing is not on a Docker image in the first place. Also, git branching helps a lot with the rollback issue, I don't push updates to main that aren't stable and ready to go.

To your third point, once again I wiill say there are no static files being served on this server, at all. Not a single directory on this server is being served, at all. Even if one was, it would be served at a particular route point with NGINX to begin with.

Also how could you possibly simultaneously acknowledge that the server is being served via a proxy pass, but then proceed to say that I am serving static files.

That repository is not serving static files, it is literally a Julia web-server. I do not even know what you mean by " git objects become heavy upon teams of development," what? Git has so little to do with this other than pulling repository updates from main at a predetermined time. Why would I need to save API-keys in this instance?? If I needed to save an API key, I would just put it into my supervisor configuration.

Lastly, the LOGS are not Supervisor, NGINX, or Docker logs, they are JULIA LOGS from the Julia web-server. They are stored within the project because it is a self-contained Julia module.

I thank you for your response man, but I really do not understand why there is an argument to this if you do not even understand that all of my directories are private in the first place. If EmsComputer is a static site, then where is the HTML man. The only static files in there is a couple of different images, and all of those files, and all of the routes on my server, as well, are served through Julia Strings. Nothing leaves the server without going through Julia first, at all.