4 ms·
I am sorry for sounding naive, but I have never used a reverse proxy before, I'll work on it though and add a chapter as soon as possible. It'd be great if you
by thewhitetulip 10y ago
I am sorry for sounding naive, but I have never used a reverse proxy before, I'll work on it though and add a chapter as soon as possible. It'd be great if you can provide me some pointers :)
- nkozyra 10y agoNot many pointers needed, a simple reverse proxy to your local Go app will provide all of the good, mature stuff that NGINX provides, most noteworthy good, simple plug-and-play logging: location / { proxy_pass http://127.0.0.1:8088; } This of course proxies everything to your Go app; you'd probably want to let NGINX handle static assets as well.
- brightball 10y agoJust think of it as a load balancer. Just something that sits in front of your application and gives you the opportunity to determine how to handle things before they get to your application. Usually things like serving images, css, automatically compressing them, automatically compressing other traffic, domain redirects, ssl, etc. Helps keep your application focused although I realize it can be tempting to just do all that inside of go since it's somewhat good at it.
- deleted 10y ago[deleted]