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

docs: `.html, .py`

Browse source
This commit is contained in:
defuz 2014-11-05 07:46:58 +03:00
parent d4b9b9854c
commit d338dc8a13
8 changed files with 16 additions and 16 deletions
Download patch file Download diff file Expand all files Collapse all files

4
docs/patterns/fabric.rst
View file

@ -86,7 +86,7 @@ this command::
However this requires that our server already has the
:file:`/var/www/yourapplication` folder created and
:file:`/var/www/yourapplication/env` to be a virtual environment. Furthermore
are we not creating the configuration or `.wsgi` file on the server. So
are we not creating the configuration or ``.wsgi`` file on the server. So
how do we bootstrap a new server into our infrastructure?
This now depends on the number of servers we want to set up. If we just
@ -110,7 +110,7 @@ To setup a new server you would roughly do these steps:
configuration file for the application (eg: :file:`application.cfg`)
3. Create a new Apache config for ``yourapplication`` and activate it.
Make sure to activate watching for changes of the `.wsgi` file so
Make sure to activate watching for changes of the ``.wsgi`` file so
that we can automatically reload the application by touching it.
(See :ref:`mod_wsgi-deployment` for more information)

2
docs/patterns/fileuploads.rst
View file

@ -43,7 +43,7 @@ Why do we limit the extensions that are allowed? You probably don't want
your users to be able to upload everything there if the server is directly
sending out the data to the client. That way you can make sure that users
are not able to upload HTML files that would cause XSS problems (see
:ref:`xss`). Also make sure to disallow `.php` files if the server
:ref:`xss`). Also make sure to disallow ``.php`` files if the server
executes them, but who has PHP installed on his server, right? :)
Next the functions that check if an extension is valid and that uploads

2
docs/patterns/packages.rst
View file

@ -23,7 +23,7 @@ Simple Packages
To convert that into a larger one, just create a new folder
:file:`yourapplication` inside the existing one and move everything below it.
Then rename :file:`yourapplication.py` to :file:`__init__.py`. (Make sure to delete
all `.pyc` files first, otherwise things would most likely break)
all ``.pyc`` files first, otherwise things would most likely break)
You should then end up with something like that::