I just want to say that I am extremely irritated that the question of which webserver to use to serve static files inside a docker container has become political.

Look, if you want to program in React Native and contribute to Zucherberg and the decay of democracy globally that's on you.

I'm sorry if your college professors all had their heads up their asses for front end frameworks for the duration you went to college but out here in the trenches react is a niche toy for prototyping powering about 0.3% of the web and sucking at it.

Side note: Proud boys can suck my balls.

@HiFiWiFiSciFi what.

@M3m35terJ05h Oh, um hi I'll have a Bacon Double and a Frosty.

@HiFiWiFiSciFi dafuq you smoking bro, what does react have to do with this?

Use nginx.

- trust me I'm an Apache kind of guy.

@C0D4 Fuck I totally misread the OP post... nevermind about all of that.

Fuck react tho

@HiFiWiFiSciFi all my homies use angular

@C0D4 Yeah that's what I did. And someone on another team is losing their mind. The twist: the server they prefer isn't apache

@M3m35terJ05h what do they want to use instead. Please don't say IIS 😬

@C0D4 For static files, Nginx would be a plausible choice, at least as reverse proxy.

Nginx should be the obvious answer here.

But also, what? What's the context for this? Is there some war going on again?

NGINX, Caddy or Lighttpd depending what on your use cases.
I haven't used those much except for Lighttpd, Apache for production/staging environments and serve for development.

Imagine if your boss called you on the way to work to ask when you'll be in. For some reason you mention the brand of car you're driving and they freak out. They say what are you doing in a Toyota, get yourself to an airfield right now and grab a Cessna. What kind of idiot drives a Toyota to work when the British could invade at any moment.

I'm sorry I can't go into more detail.