| 16 | | WIP. Should be completed by 21st July 2007. In the meantime see ["TracOnRhel4"] |
| | 16 | This guide will result in the following configuration: |
| | 17 | * HTTP requests will be handled by Apache HTTP Server ("Apache"): |
| | 18 | * Trac will be run within its own separate and limited user account: |
| | 19 | * No Trac code will be executed inside Apache HTTPD processes; |
| | 20 | * Trac data will be stored within a SQLLite database; |
| | 21 | * All data files are owned/readable/writable only by the dedicated Trac user account; |
| | 22 | * HTTP requests will be proxied from Apache to Trac via mod_proxy_ajp. |
| | 23 | |
| | 24 | |
| | 25 | The rationale for this configuration is: |
| | 26 | * We can take advantage of Apache's features such as SSL, and advanced authentication (eg LDAP); |
| | 27 | * No extra code or modules that could effect the security or stability of the Apache server are introduced; |
| | 28 | * Individual instances of Trac are isolated and can have their resource usage easily measured; |
| | 29 | * Multiple versions of Trac could be run if so desired. |
| | 30 | |
| | 31 | If you are dedicating an entire machine to Trac and don't require such high levels of |
| | 32 | security and stability, you may wish to simply embed Trac in Apache. See ["TracOnRHEL"] for |
| | 33 | an alternative installation guide. |
| | 34 | |
| | 35 | It is assumed that Subversion is already installed/configured and in a working state. |
| | 36 | |
| | 37 | WIP. Should be completed by 23st July 2007. |
