Been thinking about nginx for some time. If I could get an easy Mono/F# implementation working with it, I'd jump on it in a heartbeat.
Nginx for Developers: An Introduction
21–30 of 142 posts
Re: Nginx for Developers: An Introduction
#22> The default port for the internet is 80, so if there’s no port in a url, that means it’s 80.
The Internet has no default port; 80 is for HTTP. If the port is omitted, then the default for the scheme[1] is assumed.
Re: Nginx for Developers: An Introduction
#23> The default port for the internet is 80, so if there’s no port in a url, that means it’s 80. The Internet has no default port; 80 is for HTTP. If the port is omitted, then the default for the scheme[1] is assumed. [1]: https://en.wikipedia.org/wiki/URI_scheme
haha fair enough, if I changed "the internet" to "http" would that satisfy you?
Re: Nginx for Developers: An Introduction
#24If you are interested in running NGINX on Heroku, checkout my buildpack: https://github.com/ryandotsmith/nginx-buildpack
Re: Nginx for Developers: An Introduction
#25I like this article because it reaffirms the demand for competent devops who've taken an afternoon to read all of http://wiki.nginx.org/DirectiveIndex.
Re: Nginx for Developers: An Introduction
#26Been thinking about nginx for some time. If I could get an easy Mono/F# implementation working with it, I'd jump on it in a heartbeat.
If it can talk to a socket, nginx can talk to it. Is there something I'm missing?
Re: Nginx for Developers: An Introduction
#27Been thinking about nginx for some time. If I could get an easy Mono/F# implementation working with it, I'd jump on it in a heartbeat.
I haven't tried it myself but the mono guys have an article on getting nginx up and running with fastcgi-mono-server2
Re: Nginx for Developers: An Introduction
#28I am a little hesitant on restarting nginx. When you do that, it drops the connections that are currently attached. Instead, you may want to do `nginx reload`
I can't imagine there are many connections to worry about if you're configuring a new server.
Right but if you are modifying and existing server, then this needs to be taken into account. We have several servers who are constantly serving connections and we can't have any of them drop otherwise it will result in a poor user experience.
I just wish the article talked about using reload as well as restart and when to use them.
Re: Nginx for Developers: An Introduction
#29I am a little hesitant on restarting nginx. When you do that, it drops the connections that are currently attached. Instead, you may want to do `nginx reload`
I can't imagine there are many connections to worry about if you're configuring a new server.
It's not a problem on a new server of cause, but on a live server it makes a difference, so you might as well learn the "correct" approach initially, so you won't hurt yourself in the future.