WebStack

docs/deploying.html

400:5b276bbcbbb5
2005-07-16 paulb [project @ 2005-07-16 20:32:38 by paulb] Changed virtual path info in sub-resources so that it may be an empty string.
     1 <!DOCTYPE html PUBLIC "-//W3C//DTD XHTML 1.0 Transitional//EN" "http://www.w3.org/TR/xhtml1/DTD/xhtml1-transitional.dtd">     2 <html xmlns="http://www.w3.org/1999/xhtml">     3 <head>     4   <title>Deploying a WebStack Application</title>     5   <meta name="generator"     6  content="amaya 8.1a, see http://www.w3.org/Amaya/" />     7   <link href="styles.css" rel="stylesheet" type="text/css" />     8 </head>     9 <body>    10 <h1>Deploying a WebStack Application</h1>    11 <p>The process of deploying a WebStack application should be as    12 straightforward as taking some adapter or "glue" code and either    13 running it    14 or using the deployment processes of the server environment or    15 framework in    16 which the application will be living.</p>    17 <h2>The Adapter Code</h2>    18 <p>What adapter or "glue" code does is to set up your applications main    19 resource object and to hook that object up with the underlying server    20 environment. For the&nbsp;<code>MyApplication</code> <a    21  href="resources.html">example</a>, together with a simple environment,    22 looks something like    23 this:</p>    24 <pre>from WebStack.Adapters.BaseHTTPRequestHandler import deploy    # import the support for the server environment<br />from MyApplication import MyResource                           # import the main resource class<br />print "Serving..."<br />deploy(MyResource())                                           # connect a resource object to the server environment</pre>    25 <p>In the case of BaseHTTPRequestHandler, which is a module in the    26 Python standard library, you can just run this code, making sure that    27 the <code>MyApplication</code> module or package is on your <code>PYTHONPATH</code>.    28 Then, you can visit&nbsp;<code>http://localhost:8080</code> in your    29 browser and see the result.</p>    30 <h3>More Demanding Adapter Code</h3>    31 <p>Unfortunately, not all server environments can be connected up with    32 applications this easily. Some environments require special classes and    33 functions to be defined in the adapter code in order for    34 applications to    35 be properly integrated into those environments. A summary of the    36 requirements of each environment can be found in <a    37  href="writing-adapters.html">"Writing Adapters"</a>.</p>    38 <h2>The Deployment Process</h2>    39 <ul>    40   <li><a href="writing-adapters.html">Writing Adapters</a></li>    41   <li><a href="pythonpath.html">Getting PYTHONPATH Right</a></li>    42   <li><a href="deploying-applications.html">Deploying an Application</a></li>    43 </ul>    44 </body>    45 </html>