Mercurial > cgi-bin > hgweb.cgi > tincan
comparison doc/deployment.rst @ 63:8867b3a5c4fa draft
Some minor fixes.
author | David Barts <n5jrn@me.com> |
---|---|
date | Thu, 20 Jun 2019 21:52:30 -0700 |
parents | 55828c01e38f |
children | 25fdd985d046 |
comparison
equal
deleted
inserted
replaced
62:fd8c558a89bb | 63:8867b3a5c4fa |
---|---|
4 | 4 |
5 ======================== | 5 ======================== |
6 Bottle's Built-In Server | 6 Bottle's Built-In Server |
7 ======================== | 7 ======================== |
8 | 8 |
9 The ``launch`` command will simply use the WSGI server built into Bottle (built into the Python standard library, actually) to serve the routes defined by the webapp. This is a multithreaded server (see the :ref:`multithreading-problem` section on the issues with multithreading), which is primarily intended for debugging and light-duty use. | 9 The ``launch`` command will simply use the WSGI server built into Bottle (built into the Python standard library, actually) to serve the routes defined by the webapp. This is a multithreaded server (see the :ref:`multithreading-problem`), which is primarily intended for debugging and light-duty use. |
10 | 10 |
11 Static and Dynamic Routes | 11 Static and Dynamic Routes |
12 ------------------------- | 12 ------------------------- |
13 | 13 |
14 If you're using the built-in server, one thing to be aware of is that *by default, only dynamic content is served*. That means, if you create pages that reference style sheet, image, or font files, all these resources will cause 404 errors when a user agent attempts to request them from the server, because no routes exist to serve such content. | 14 If you're using the built-in server, one thing to be aware of is that *by default, only dynamic content is served*. That means, if you create pages that reference style sheet, image, or font files, all these resources will cause 404 errors when a user agent attempts to request them from the server, because no routes exist to serve such content. |