how nginx works i think, by holly:
so you have programs on your server that think they're talking to the internet. like my mastodon tihnks it's talking to the internet directly. but it's not because that would be bad. instead you have nginx sitting between them. the internet talks to nginx and then nginx tells mastodon what it said, and then whatever mastodon says back nginxs says to the internet
@monorail why would that be bad
-F
@Felthry in general? ¯\_(ツ)_/¯
in my case, in addition to whatever other benefits it has: mastodon wants to be the only thing talking to the internet, but nginx knows how to talk to more than one thing, and it knows how to tell which thing any given request is for
@monorail oh so it's kind of like using an rs232 to rs485 conversion thingy
-F
@Felthry yeah
only one thing can actually talk to the internet at a time, so you have to have nginx in the middle telling everything "oh yeah don't worry, i'm the internet, you're the only one talking to me"
but it says that to both my mastodon instance and to my phpbb board
also nginx knows how to serve files, too, so it itself is one of the things that the internet might be talking to
@monorail @Felthry also most of the first few hundred ports are reserved for services/programs or have been used by services/programs enough that everyone else just acknowledges that
port 666 is Doom's port, for example, they never formally requested that port but even Windows just labels it doom
there's a benefit to not running stuff on the default port, moving ssh to a different port than 22 means that your login service won't get attacked with dictionaries all the time
