| 1 |
<?xml version="1.0" encoding="UTF-8"?> |
|---|
| 2 |
<chapter xmlns:db="http://docbook.org/docbook-ng" xmlns:xi="http://www.w3.org/2001/XInclude" |
|---|
| 3 |
xmlns:xsl="http://www.w3.org/1999/XSL/Transform" xml:id="gettingstarted"> |
|---|
| 4 |
<title>Getting started</title> |
|---|
| 5 |
<section> |
|---|
| 6 |
<abstract> |
|---|
| 7 |
<para>Since CherryPy is pure Python and has no dependencies, obtaining and installing it |
|---|
| 8 |
is a snap. You can install using a release package, or by using Subversion.</para> |
|---|
| 9 |
</abstract> |
|---|
| 10 |
<title>Installing CherryPy from a release package</title> |
|---|
| 11 |
<section> |
|---|
| 12 |
<title>Obtaining a release package</title> |
|---|
| 13 |
<para>A "release package" is an official stable release of CherryPy. It means that the |
|---|
| 14 |
main features and issues that were decided to be integrated and fixed for a particular |
|---|
| 15 |
milestone, have been.</para> |
|---|
| 16 |
<para>The latest package is available from <ulink |
|---|
| 17 |
url="http://sourceforge.net/project/showfiles.php?group_id=56099">the sourceforge |
|---|
| 18 |
repository</ulink> of the CherryPy project. You need to pick up the latest version of the |
|---|
| 19 |
package.</para> |
|---|
| 20 |
</section> |
|---|
| 21 |
<section> |
|---|
| 22 |
<title>Installing from a release package</title> |
|---|
| 23 |
<para>Installing CherryPy from a release package will take three steps only. Type the |
|---|
| 24 |
following commands :</para> |
|---|
| 25 |
<cmdsynopsis> |
|---|
| 26 |
<command>tar</command> |
|---|
| 27 |
<arg choice="req">zxvf</arg> |
|---|
| 28 |
<arg choice="req">CherryPy-2.1.0.tar.gz</arg> |
|---|
| 29 |
</cmdsynopsis> |
|---|
| 30 |
<para>Which will create the CherryPy-2.1.0 directory.</para> |
|---|
| 31 |
<cmdsynopsis> |
|---|
| 32 |
<command>cd</command> |
|---|
| 33 |
<arg choice="req">CherryPy-2.1.0</arg> |
|---|
| 34 |
</cmdsynopsis> |
|---|
| 35 |
<para>Then issue the following command (if you are under Unix or Linux, you should be |
|---|
| 36 |
root):</para> |
|---|
| 37 |
<cmdsynopsis> |
|---|
| 38 |
<command>python</command> |
|---|
| 39 |
<arg choice="req">setup.py</arg> |
|---|
| 40 |
<arg choice="req">install</arg> |
|---|
| 41 |
</cmdsynopsis> |
|---|
| 42 |
</section> |
|---|
| 43 |
</section> |
|---|
| 44 |
<section> |
|---|
| 45 |
<title>Installing CherryPy from the Subversion repository</title> |
|---|
| 46 |
<section> |
|---|
| 47 |
<title>Obtaining the package from the Subversion repository</title> |
|---|
| 48 |
<para>The CherryPy project uses Subversion to control access to its source code. Getting |
|---|
| 49 |
CherryPy from the latest changeset is sometimes required because a bugfix or a feature is |
|---|
| 50 |
only available from it. Keep in mind that subversion code is subject to change on a |
|---|
| 51 |
regular basis; therefore, only use it if you know what you are doing.</para> |
|---|
| 52 |
<para>To get the latest source code from the subversion repository, you first need to |
|---|
| 53 |
install a SVN client. On Microsoft Windows, <ulink |
|---|
| 54 |
url="http://tortoisesvn.tigris.org/">TortoiseSVN</ulink> is a good choice. Under Linux, |
|---|
| 55 |
you can either use the <ulink url="http://subversion.tigris.org/">svn</ulink> command |
|---|
| 56 |
line tools or use a graphical user interface such as <ulink |
|---|
| 57 |
url="http://esvn.umputun.com/">eSVN</ulink>.</para> |
|---|
| 58 |
<para>Once you have installed a svn client, you need to type the following command |
|---|
| 59 |
:</para> |
|---|
| 60 |
<cmdsynopsis> |
|---|
| 61 |
<command>svn</command> |
|---|
| 62 |
<arg choice="req">co</arg> |
|---|
| 63 |
<arg choice="req">http://svn.cherrypy.org</arg> |
|---|
| 64 |
</cmdsynopsis> |
|---|
| 65 |
<para>This will download the complete source code to your computer.</para> |
|---|
| 66 |
</section> |
|---|
| 67 |
<section> |
|---|
| 68 |
<title>Installing the package from the Subversion repository</title> |
|---|
| 69 |
<para>If you have downloaded the source code from the CherryPy subversion repository, |
|---|
| 70 |
then you should have a directory called svn.cherrypy.org. Then type the following |
|---|
| 71 |
commands:</para> |
|---|
| 72 |
<cmdsynopsis> |
|---|
| 73 |
<command>cd</command> |
|---|
| 74 |
<arg choice="req">svn.cherrypy.org/trunk</arg> |
|---|
| 75 |
</cmdsynopsis> |
|---|
| 76 |
<para>Then issue the following command (as root if you are under Unix/Linux):</para> |
|---|
| 77 |
<cmdsynopsis> |
|---|
| 78 |
<command>python</command> |
|---|
| 79 |
<arg choice="req">setup.py</arg> |
|---|
| 80 |
<arg choice="req">install</arg> |
|---|
| 81 |
</cmdsynopsis> |
|---|
| 82 |
<para>Alternately, since CherryPy has no dependencies, you don't have to run setup.py. |
|---|
| 83 |
Instead, checkout <code>/trunk/cherrypy</code> into a directory which is on your Python |
|---|
| 84 |
path, such as <code>site-packages/cherrypy</code>.</para> |
|---|
| 85 |
</section> |
|---|
| 86 |
</section> |
|---|
| 87 |
<section> |
|---|
| 88 |
<title>Running the test programs</title> |
|---|
| 89 |
<para>If you have installed CherryPy from the source code downloaded from the subversion |
|---|
| 90 |
repository, you can run the test suite to check if everything is fine on your system. Type |
|---|
| 91 |
the following commands:</para> |
|---|
| 92 |
<cmdsynopsis> |
|---|
| 93 |
<command>cd</command> |
|---|
| 94 |
<arg choice="req">svn.cherrypy.org/trunk/cherrypy/test</arg> |
|---|
| 95 |
</cmdsynopsis> |
|---|
| 96 |
<cmdsynopsis> |
|---|
| 97 |
<command>python</command> |
|---|
| 98 |
<arg choice="req">test.py</arg> |
|---|
| 99 |
</cmdsynopsis> |
|---|
| 100 |
<para>If all tests pass, then they will be flagged as <code>ok</code>. If an error occurs, |
|---|
| 101 |
please visit the main CherryPy website to report the issue.</para> |
|---|
| 102 |
</section> |
|---|
| 103 |
</chapter> |
|---|