Repository: bokeh/bokeh

Issue:
Need to use different sintaxis when using command "bokeh serve" in Windows command line.
This issue was originally commented and resolved [here](http://stackoverflow.com/questions/41936031/bokeh-server-not-working-when-deployed-from-windows-server/41980870#41980870). One of the possible arguments to use is `--host='*'` to allow any host. The use of this argument appears somewhere in the documentation I do not find right now, anyway in Linux it works properly. But when used in Windows Command Prompt, not any host is allowed to connect as it is supposed to be. After making some tests with the sintaxis in Windows, the conclussion is that correct way to use arguments is `--host '*'` or `--host=*`. 
Using `--host='*'` is literally interpreted in Windows, hence no wildcard is applied. This issue is probaly obvious for advanced users, but for beginners as me may be not so clear. Thanks to @bryevdv for the help.

![bokeh2 1](https://cloud.githubusercontent.com/assets/20949300/22511196/27ec39ba-e895-11e6-9bb7-acc544614119.JPG)
![bokeh4](https://cloud.githubusercontent.com/assets/20949300/22511197/2800feae-e895-11e6-86f6-0e64fdb2b3e2.JPG)




Discussion:
@bokeh/dev I have labeled this as a documentation task, I think that pointing out the difference between platforms is the minimum that is necessary. If there are better ways to handle things on Windows, that would be good to know and perhaps try as well. 

@fraserpal I don't think it is obvious at all, so thanks for raising the issue so we can make it clearer for everyone

Resolving patch:
diff --git a/bokeh/command/subcommands/serve.py b/bokeh/command/subcommands/serve.py
--- a/bokeh/command/subcommands/serve.py
+++ b/bokeh/command/subcommands/serve.py
@@ -85,7 +85,7 @@
 
 .. code-block:: sh
 
-    bokeh serve app_script.py --port=8080
+    bokeh serve app_script.py --port 8080
 
 To listen on an arbitrary port, pass ``0`` as the port number.  The actual
 port number will be logged at startup.
@@ -95,7 +95,7 @@
 
 .. code-block:: sh
 
-    bokeh serve app_script.py --address=0.0.0.0
+    bokeh serve app_script.py --address 0.0.0.0
 
 will have the Bokeh server listen all available network addresses.
 
@@ -120,7 +120,7 @@
 
 .. code-block:: sh
 
-    bokeh serve app_script.py --address=0.0.0.0 --host='*'
+    bokeh serve app_script.py --address 0.0.0.0 --host '*'
 
 Using the wildcard can be helpful when testing applications that are deployed
 with cloud orchestration tools and when the public endpoint is not known ahead
@@ -163,7 +163,7 @@
 
 .. code-block:: sh
 
-    bokeh serve app_script.py --prefix=foobar
+    bokeh serve app_script.py --prefix foobar
 
 Then the application will be served under the following URL:
 
@@ -222,7 +222,7 @@
 
 .. code-block:: sh
 
-    bokeh serve app_script.py --session-ids=signed
+    bokeh serve app_script.py --session-ids signed
 
 The available modes are: {SESSION_ID_MODES}
 
@@ -305,7 +305,7 @@
 
 .. code-block:: sh
 
-    bokeh serve app_script.py --log-level=debug
+    bokeh serve app_script.py --log-level debug
 
 The available log levels are: {LOGLEVELS}
 
@@ -313,7 +313,7 @@
 
 .. code-block:: sh
 
-    bokeh serve app_script.py --log-format="%(levelname)s: %(message)s"
+    bokeh serve app_script.py --log-format "%(levelname)s: %(message)s"
 
 The default log format is ``"{DEFAULT_LOG_FORMAT}"``
 


Test patch: