On Sep 15, 2017 13:15, wrote:
Hey! That worked! Thank you, Shawn. Much appreciated.
You're welcome! Kudos to you for not just being lazy and running as root.
--
You received this message because you are subscribed to the Google Groups
"golang-nuts" group.
To
Hey! That worked! Thank you, Shawn. Much appreciated.
On Friday, September 15, 2017 at 7:24:16 AM UTC-7, Shawn Milochik wrote:
>
> You don't need to use nginx. You *can* if you want to serve multiple
> domains from the same IP, or terminate TLS there, or have nginx handle
> static data from
You don't need to use nginx. You *can* if you want to serve multiple
domains from the same IP, or terminate TLS there, or have nginx handle
static data from disk.
You can listen on port 80 if you do this: sudo /sbin/setcap
cap_net_bind_service=+ep yourBinary
--
You received this message because
Do you have to use Nginx or apache with your go web app? I know web apps run on
port 80 but I'm unable to run my app on port 80. Currently I'm using port 8000
and to access my website I'm putting in the IP address and port number in the
browser.
I thought a plus of using go was that you