<Opinion> Deploying a Django site to a live environment the first time is one of the most intricate (and likely painful) activities you’ll ever deal with when working with Django.</Opinion>
The advantage of working through this now is that when you want to add features / functionality to your platform, you’ve already got the fundamentals taken care of.
I will make a couple of quick recommentations.
Ditch Apache. Either use nginx or take a look at caddy
Don’t try to get too sophisticated at the beginning. I’d even try just deploying the first step from the Django tutorial to ensure that you can get the simplest-possible app running before adding the Django-related issues into the mix.
I’m biased, but I do recommend reading the guide Ken shared. In your case if you’re in “I just want the darn thing online” mode, I would favor a PaaS option like Heroku, or Render / fly.io (the latter two have free tiers that are workable for hobby projects, Heroku does not). Based on your strategy, I’m guessing you’re not familiar with Docker, so I’d probably go with Render by default.
These two (admittedly,opinionated) diagrams may help:
Thank you Ken and czue, I don’t feel so stupid or alone anymore. Great info, I’ll read the docs and keep trying, eventually I’ll get there…now I understand, at least, why they give credit bonus when you sign-in, lol