| 170 | | Now trac-admin, apache and tracd should all find the necessary bindings |
| 171 | | and run without any further ado. |
| 172 | | |
| 173 | | 8. At this point everything is wired up and ready to go with tracd as the |
| 174 | | server and SQLite3 as the backend database. You can create your first |
| 175 | | trac environment by issuing the following command: |
| | 170 | We can see that /usr/local/lib/svn-python has been added to python's search path. The only thing to note is that a version upgrade of python will require that we move trac_svn.pth to the new site-packages directory. Now trac-admin, apache and tracd should all find the necessary bindings and run without any further ado. |
| | 171 | |
| | 172 | 8. At this point everything is wired up and ready to go with tracd as the server and SQLite3 as the backend database. You can create your first trac environment by issuing the following command: |
| 185 | | and answering the questions regarding the database connection and |
| 186 | | subversion repository. To use a different DB backend you must first |
| 187 | | initialize the alternative database environment before runing trac-admin initenv. |
| 188 | | |
| 189 | | 9. To use postgresql as the backend one must first setup a target |
| 190 | | database user and a database instance to pass to trac-admin when it asks for a connection string. The postgresql command line utilities for this are createuser(1) and createdb(1). |
| | 182 | You must answer the questions regarding the database connection and subversion repository. To use a different DB backend you must first initialize the alternative database environment before runing "trac-admin /path/to/trac_project_env initenv". |
| | 183 | |
| | 184 | 9. To use postgresql as the backend one must first setup a target database user and a database instance to pass to trac-admin when it asks for a connection string. The postgresql command line utilities for this are createuser(1) and createdb(1). |
| 246 | | You have to provide the connection password again as above, but this time |
| 247 | | you use the password for trac_db_admin since this was used to establish |
| 248 | | the connection. You can of course use any established postgresql |
| 249 | | user/role that has CREATEDB priviliges instead. |
| 250 | | |
| 251 | | 10. With trac and postgresql all set up you must now determine the |
| 252 | | absolute path to the subversion repostor(y/ies) that you wish to use with trac. This is a manual task. A typical repository path might look |
| 253 | | like "/var/data/svn" or "/var/svn". |
| 254 | | |
| 255 | | 11. With the information obtained above, the postgresql database name, |
| 256 | | the path to the trac directory, and the path to the subversion repository, |
| 257 | | we now invoke trac-admin to create the environment. |
| 258 | | |
| 259 | | # |
| 260 | | {{{ |
| 261 | | |
| | 238 | You have to provide the connection password again as above, but this time you use the password for trac_db_admin since this was used to establish the connection. You can of course use any established postgresql user/role that has CREATEDB priviliges instead. |
| | 239 | |
| | 240 | 10. With trac and postgresql all set up you must now determine the absolute path to the subversion repostor(y/ies) that you wish to use with trac. This is a manual task. A typical repository path might look like "/var/data/svn" or "/var/svn". |
| | 241 | |
| | 242 | 11. With the information obtained above, the postgresql database name, the path to the trac directory, and the path to the subversion repository, we now invoke trac-admin to create the environment. |
| | 243 | |
| | 244 | |
| | 245 | {{{ |
| | 246 | # |
| 427 | | 12. You will now need to customize your trac installation to suite your |
| 428 | | project needs. Configuration is carried out either through the |
| 429 | | trac-admin command line interface (adding and removing trac users, adding, |
| 430 | | changing or removing priority and severity codes, adding and removing |
| 431 | | milestones, etc.) or by directly editing the .trac/conf/trac.ini file (setting email, and default values for the web interface. See [wiki:TracIni] |
| | 412 | 12. You will now need to customize your trac installation to suite your project needs. Configuration is carried out through both the trac-admin command line interface (adding and removing trac users, adding, changing or removing priority and severity codes, adding and removing milestones, etc.) and by directly editing the .trac/conf/trac.ini file (setting email and default values for the web interface). See [wiki:TracIni] |
| 446 | | More advanced customatization can be accomplished by modifying or |
| 447 | | replacing the stylesheets in .trac/templates. |
| 448 | | |
| 449 | | 13. You WILL, at some point, wish to use trac plugins. To employ plugins |
| 450 | | you must install or upgrade setuptools for python. The easiest way to do |
| 451 | | this is to obtain ez_setup.py from |
| 452 | | [http://peak.telecommunity.com/DevCenter/setuptools] and run it as root |
| 453 | | "#python ez_setup.py". You can get more information about plugins for |
| 454 | | trac at [wiki:TracPlugins]. |
| 455 | | |
| 456 | | This completes our broadcast day. For information on configuring Apache to run trac see [wiki:TracModPython]. For alternative methods for installing on Red Hat type systems, particularly Fedora Core see [wiki:TracOnFedoraCore]. |
| | 427 | More advanced customization is accomplished by modifying or replacing the stylesheets in .trac/templates. |
| | 428 | |
| | 429 | 13. You WILL, at some point, wish to use trac plugins. To employ plugins you must install or upgrade setuptools for python. The easiest way to do this is to obtain ez_setup.py from [http://peak.telecommunity.com/DevCenter/setuptools] and run it as root "#python ez_setup.py". You can get more information about plugins for trac at [wiki:TracPlugins]. |
| | 430 | |
| | 431 | This completes our broadcast day. For information on configuring Apache to run trac see [wiki:TracModPython] or for my specific [wiki:TracApacheRecipe]. For alternative methods for installing on Red Hat type systems, particularly Fedora Core see [wiki:TracOnFedoraCore]. |
