Restrict image access

Thanks for your quick answer, I’m starting to suspect ChatGPT being a cheap copy of you. But OpenAI will have hard times to reach your level of professionalism. I really appreciate that you take the time to elevate hobby projects like mine.

Anyways, I can imagine that after reaching a certain level of expertiese it’s getting harder and harder to think into the very beginner problems. So I want to give it a try to document my approach to a solution in the hope being able to give something back to the inspirational free-open-source-computer-science-community.

So, after spending hours on that topic I learned about Nginx and Apache.
I learned that Apache is the server utilized by my web hosting service STRATO (closely connected to this topic here). Similar to them it seems i have no access to “mod_wsgi” and it is unlikely (though I have not yet checked) there is a way to add a module to the apache installation like they state as an alternative installation of mod_wsgi in their documentation here.

I came to the conclusion that my hope (restricting certain files) may be the right configuration within a “.htaccess” file, as discussed here.

Do you think I’m on the right track?

Interesting that you say a server should have access to the files, but not the project. I would have expected it to be exactly the other way around, since my django apps access the frameworks SQLite database and their static and media files. What you’re saying means that Apache (in my case) would serve the media and static files to clients, whereas the django project shouldn’t.
And still I would expect Apache to communicate with my Django project somehow?

Since this is the first time i want to make a project kind of production ready, I put a lot into question what seemed fine so far. So all the static file handling i utilized when building my django project is only for development, but i should get rid of it in production?

Again, thanks in advance for any help to stay on track reaching my goal!