orbit-oss/flask
4
4
Fork 2
Code Issues Pull requests Projects Releases Packages Wiki Activity Actions

Updated docs for external server information.

Browse source 
This fixes #14.
This commit is contained in:
Armin Ronacher 2010-04-24 17:46:06 +02:00
parent a862ead5f2
commit ef34638f5d
2 changed files with 22 additions and 9 deletions
Download patch file Download diff file Expand all files Collapse all files

18
docs/quickstart.rst
View file

@ -54,6 +54,24 @@ So what did that code do?
To stop the server, hit control-C.
.. _public-server:
.. admonition:: Externally Visible Server
If you run the server you will notice that the server is only available
from your own computer, not from any other in the network. This is the
default because in debugging mode a user of the application can execute
arbitrary Python code on your computer. If you have `debug` disabled
or trust the users on your network, you can make the server publicly
available.
Just change the call of the :meth:`~flask.Flask.run` method to look
like this::
app.run(host='0.0.0.0')
This tells your operating system to listen on a public IP.
Debug Mode
----------

13
docs/tutorial/setup.rst
View file

@ -57,13 +57,8 @@ without problems. When you head over to the server you will get an 404
page not found error because we don't have any views yet. But we will
focus on that a little later. First we should get the database working.
.. admonition:: Troubleshooting
.. admonition:: Externally Visible Server
If you notice later that the browser cannot connect to the server
during development, you might want to try this line instead::
app.run(host='127.0.0.1')
In a nutshell: Werkzeug starts up as IPv6 on many operating systems by
default and not every browser is happy with that. This forces IPv4
usage.
Want your server to be publically available? Check out the
:ref:`externally visible server <public-server>` section for more
information.