From 1162e14e795f95bb1145aa6a47d9a7f039679733 Mon Sep 17 00:00:00 2001
From: saidimu apale <saidimu@gmail.com>
Date: Wed, 1 Oct 2014 13:46:37 -0400
Subject: [PATCH] Websockets support in README

---
 README.md | 6 ++++++
 1 file changed, 6 insertions(+)

diff --git a/README.md b/README.md
index 7d3e26d..b965360 100644
--- a/README.md
+++ b/README.md
@@ -14,6 +14,12 @@ Then start any containers you want proxied with an env var VIRTUAL_HOST=subdomai
 
 Provided your DNS is setup to forward foo.bar.com to the a host running nginx-proxy, the request will be routed to a container with the VIRTUAL_HOST env var set.
 
+### Websockets support
+
+To proxy a websockets container, add an env var WEBSOCKETS=1
+
+    $ docker run -e VIRTUAL_HOST=foo.bar.com -e WEBSOCKETS=1  ...
+
 ### Multiple Ports
 
 If your container exposes multiple ports, nginx-proxy will default to the service running on port 80.  If you need to specify a different port, you can set a VIRTUAL_PORT env var to select a different one.  If your container only exposes one port and it has a VIRTUAL_HOST env var set, that port will be selected.