i have a nice reverse proxy i forked

it also has nip-05 and #golang  vanity redirects... i had meant to get to adding URL rewrites so i could use it to make a single-user git repo without using the gay git thing that is impossible to set up https://github.com/mleku/lerproxy

import is actually lerproxy.mleku.dev because i run it

will is not advanced level sysadmin

not like our man nostr:nprofile1qyghwumn8ghj7mn0wd68ytnhd9hx2tcpz4mhxue69uhhyetvv9ujuerpd46hxtnfduhszrnhwden5te0dehhxtnvdakz7qgkwaehxw309a3x2an09ehx7um5wgcjucm0d5hszynhwden5te0dehhxarjxgcjucm0d5hsz8thwden5te0dphhgunfva58gmn0wuhxummnw3erztnrdakj7qg6waehxw309ac8ymmxd9kx2uewdehhxarjxyhxxmmd9uqzqlxr9zsgmke2lhuln0nhhml5eq6gnluhjuscyltz3f2z7v4zglqwf4fpr9  

or he would know that using reverse proxies have actual uses other than logging 

 I don't run nginx on my relay therefore I don't know what nginx is for? wut. I don't want a reverse proxy in front of my relay, the entire server is dedicated to a single program. I have no need for reverse proxying there. 

 Load balancing, "ip forwarding", ssl termination, transport upgrades (h3 and such with h11 backends) caching/acceleration. Reverse proxies are a requirement. (Yes I understand not all apply to websockets)

Maturity in edge servers matters imo.  

 the actual code used in my reverse proxy is battle hardened since 2009, the app itself is tiny