Add Reload The nginx Configuration as a devops til.

README.md

@@ -20,6 +20,7 @@ smart people at [Hashrocket](http://hashrocket.com/).
 
 - [Check The Status of All Services](devops/check-the-status-of-all-services.md)
 - [Push Non-master Branch To Heroku](devops/push-non-master-branch-to-heroku.md)
+- [Reload The nginx Configuration](devops/reload-the-nginx-configuration.md)
 - [Wipe A Heroku Postgres Database](devops/wipe-a-heroku-postgres-database.md)
 
 ### git

devops/reload-the-nginx-configuration.md

@@ -0,0 +1,17 @@
+# Reload The nginx Configuration
+
+The nginx service won't immediately start using a modified or replaced nginx
+configuration. Once a `restart` or `reload` signal is received by nginx, it
+will apply the changes. The `reload` signal
+
+```
+$ service nginx reload
+```
+
+tells nginx to reload the configuration. It will check the validity of the
+configuration file and then spawn new worker processes for the latest
+configuration. It then sends requests to shut down the old worker processes.
+This means that during a *reload* nginx is always up and processing
+requests.
+
+[source](http://nginx.org/en/docs/beginners_guide.html)