

I was wrong in my previous comment, because I accidentally used a calculator that did percentages wrong (it converted percentages of a circle, but in measuring grade, percent is rise over run (or height over width, if you imagine it as a right-angled triangle—you can take the tangent of the angle to get the grade). So 100% would be 45°.
So 15° is actually just under 27%.
The steepest hill in my city is 31%, so that’s not outside the realm of possibility. But it is very, very extreme. Heck, even 15% is an extremely steep climb. An extremely steep popular climb near me averages out to less than 9%. It gets decent stretches which probably average to 12%, and those are exhausting to get up.














@non_burglar@lemmy.world is correct, but is perhaps not explaining it perfectly for the practical questions you seem to be asking.
If you have, say, two Docker containers for two different web servers (maybe one’s for your Wiki, and the other is for your portfolio site), you can have both listening on ports 80 and 443 of their container, but a third Docker container running a reverse proxy which has access to your machine’s ports 80 and 443. It then looks at the incoming request and decides which container to route the request to (e.g., http://192.168.1.2/wiki/%s requests go to the Wiki container, and all other requests go to portfolio site).
Now, reverse proxies can be run without Docker, but the isolation Docker adds makes it all a lot easier to manage, in part because you don’t need to configure loads of different ports.