@xarvos@outerheaven.club cover
@xarvos@outerheaven.club avatar

xarvos

@xarvos@outerheaven.club

pun-loving procrastinating dev/conlanger

i don't think this does anything but #nobot

consider my post a joke if you find it too absurd, but then so is life

expect:

  • lowercase
  • bad jokes that probably don't make sense (expect this in your replies if we're mutuals)
  • project reports
  • life rambling

This profile is from a federated server and may be incomplete. For a complete list of posts, browse on the original instance.

futurebird , to random
@futurebird@sauropods.win avatar

Is there a good resource or book for learning about some of the details of how webservers work?

For example if I want an IP address on a intranet to be a webpage that people on that intranet can go to... how would I set that up from scratch. Let's say I have a machine with a static IP on the local net... (but what I really also need to understand is how a static IP is established locally, a DNS?)

Maybe the dream book or resource doesn't exist. But I ask anyway.

(it's macs if that matters)

xarvos ,
@xarvos@outerheaven.club avatar

@futurebird @GeePawHill

Or even is Django like a small basic version of Apache?

no, they are entirely different things. apache is a generic http server that serves static files (serving files as-is), forward connections to secondary servers, and is also a php runtime.

django is a web framework, and that means you have to write a program on top of it. this program can technically does what apache does, but there is no point to it—you're better off just using apache (or nginx).

a python's equivalent to apache would be python -m http.server, which is indeed a very basic web server, way more basic than apache and only serve static files from one directory without much configs.

I assume it is I had to turn off one to run the other or else put them on different sockets.

yes, apache and the server you implement using django have to run on different ports. otherwise, when you request, http://localhost:<the port> , how could it know which server handles the request? it is common, however, to run both apache (or nginx) and other servers, with the generic server being a gateway to forward requests to other servers. with this setup, the gateway server (apache/nginx) listens to http/https ports (80/443) and other servers listens to different port, or to their own sockets. we then declare in the apache's config file that if a request matches this pattern, then it should forward the request to that server

  • All
  • Subscribed
  • Moderated
  • Favorites
  • •
  • random
  • test
  • worldmews
  • mews
  • All magazines
    •