34 | | == Installing Trac on Ubuntu |
35 | | This is a short recipe to install and configure virtual `Apache2` host with `Trac` |
36 | | === Which Ubuntu packages are needed |
37 | | Typical procedure to install Trac under Ubuntu with its default dependencies (default - choosed by apt) is |
| 34 | == Installing Trac on Ubuntu == |
| 35 | This is a short recipe to install and configure a virtual `Apache2` host with `Trac` |
| 36 | |
| 37 | === Which Ubuntu packages are needed === |
| 38 | The typical procedure to install Trac under Ubuntu with its default dependencies (default - chosen by apt) is: |
42 | | Ensure that python version matches Trac latest, otherwise apt will install older Trac version which matches your old python package installed. Also take into account that `python-babel` should be always installed before `trac` if you wish to see it internationalized. |
43 | | ==== Upgrade python packages |
44 | | Ubuntu pre-packaged python resources are not always newest, and you may consider to upgrade them with `easy_install` or `pip` |
| 43 | Ensure that the python version matches the Trac latest, otherwise apt will install an older Trac version which matches the older version of python that you have installed. Also take into account that `python-babel` should be always installed before `trac` if you wish to later configure internationalisation. |
| 44 | |
| 45 | ==== Upgrade python packages ==== |
| 46 | Ubuntu pre-packaged python resources are not always the newest; you may consider to upgrade them with `easy_install` or `pip` |
56 | | === Configuring virtual host |
57 | | Here is shown sample virtual host configuration running under `apache2` (one file) with minimal, "entry level" settings. |
58 | | Config file created at `apache2` known place for site configs (see below), and then configured site can be "enabled" to run. |
| 58 | |
| 59 | === Configuring a virtual host === |
| 60 | Here is a sample virtual host configuration running under `apache2` (one file) with minimal, "entry level" settings. |
| 61 | The config file should be created at the `apache2` known place for site configs (see below), and then the configured site can be "enabled" to run. |