A lot of people are looking to provide the most dynamic, user friendly websites these days. They can be great or horrible, but either way the drive is all about user experience and hopefully retaining said users.
Static websites can actually provide the same functionality too, however.
The problem with this is the overhead it requires on the servers to generate this content. Even though typical servers don’t have an issue handling 1,000′s of connections for dynamic content, there’s nothing saying the overhead that Apache or PHP give can’t push the envelope either.
Static sites are simple HTML pages. You can’t magically create it when a visitor gets to your site. A major benefit to it though is that you don’t need 5 different servers to provide content, you just need one: a web server. This is where Nginx is primarily used (or as a caching/proxy server).
I’m sure I’m not the only one that experiences the oh so wonderful moments of my remote SSH sessions hanging and not responding to any input. While I’m not really sure why this happens it seems to mostly be due a period of no interactivity (i.e.: no key presses).
Before I used to close out the local terminal screen then start up another and SSH into it again. However, I did recently find a way to make this process a lot easier. Note to any and all readers: man pages can really save you time and effort.
When you run into this issue again just hit enter then ~ and . (tilde and period) and SSH will terminate itself.
This works because SSH basically creates a session within itself, so you have the master/main SSH program that listens to events and a child SSH program that remotely connects and lets you do all your stuff.