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

Various documentation fixups

Browse source
This commit is contained in:
Armin Ronacher 2014-02-08 22:10:08 +00:00
parent 9074bc46af
commit a8a98bc6b6
3 changed files with 15 additions and 13 deletions
Download patch file Download diff file Expand all files Collapse all files

25
docs/deploying/fastcgi.rst
View file

@ -54,14 +54,14 @@ can execute it:
Configuring Apache
------------------
The example above is good enough for a basic Apache deployment but your `.fcgi`
file will appear in your application URL e.g.
example.com/yourapplication.fcgi/news/. There are few ways to configure your
application so that yourapplication.fcgi does not appear in the URL. A
preferable way is to use the ScriptAlias and SetHandler configuration directives
to route requests to the FastCGI server. The following example uses
FastCgiServer to start 5 instances of the application which will handle all
incoming requests:
The example above is good enough for a basic Apache deployment but your
`.fcgi` file will appear in your application URL e.g.
example.com/yourapplication.fcgi/news/. There are few ways to configure
your application so that yourapplication.fcgi does not appear in the URL.
A preferable way is to use the ScriptAlias and SetHandler configuration
directives to route requests to the FastCGI server. The following example
uses FastCgiServer to start 5 instances of the application which will
handle all incoming requests::
LoadModule fastcgi_module /usr/lib64/httpd/modules/mod_fastcgi.so
@ -79,10 +79,11 @@ incoming requests:
</Location>
</VirtualHost>
These processes will be managed by Apache. If you're using an standalone FastCGI
server, you can use the FastCgiExternalServer directive instead. Note that in
the following the path is not real, it's simply used as an identifier to other
directives such as AliasMatch:
These processes will be managed by Apache. If you're using an standalone
FastCGI server, you can use the FastCgiExternalServer directive instead.
Note that in the following the path is not real, it's simply used as an
identifier to other
directives such as AliasMatch::
FastCgiServer /var/www/html/yourapplication -host 127.0.0.1:3000

1
docs/signals.rst
View file

@ -322,6 +322,7 @@ The following signals exist in Flask:
.. versionadded:: 0.10
.. data:: flask.appcontext_popped
:noindex:
This signal is sent when an application context is popped. The sender
is the application. This usually falls in line with the

2
docs/tutorial/dbinit.rst
View file

@ -38,7 +38,7 @@ hand. Without an application context the :data:`~flask.g` object does not
know yet to which application it becomes as there could be more than one!
The ``with app.app_context()`` statement establishes the application
context for us. In the body of the with statement the :flask:`~flask.g`
context for us. In the body of the with statement the :data:`~flask.g`
object will be associated with ``app``. At the end of the with statement
the association is released and all teardown functions are executed. This
means that our database connection is disconnected after the commit.