Edgewall Software

Changes between Version 18 and Version 19 of TracOnRhel4


Ignore:
Timestamp:
Jun 29, 2006, 5:35:55 AM (18 years ago)
Author:
anonymous
Comment:

—

Legend:

Unmodified
Added
Removed
Modified

  • TracOnRhel4

    v18 v19  
    1212SELinux note: Please read TracWithSeLinux if you're using SELinux on RHEL4. Basically the default SELinux configuration only allows Apache to read certain directories, so you may need to add trac to the Apache context (`man chcon`) or turn off SELinux (`man setenforce`). For more information on SELinux, see http://fedora.redhat.com/docs/selinux-faq/. To turn off SELinux edit the /etc/selinux/config file and set SELINUX=disabled
    1313
    14 1) After configuring up2date to use the RPMforge repository, run the following command in a terminal window:
     14After configuring up2date to use the RPMforge repository, run the following command in a terminal window:
    1515
    1616{{{
    … …  
    2222== Configure Subversion ==
    2323
    24 Before we can create a new trac environment we must first have a working subversion repository if we are going to get the full use out of trac. Create a subversion repository if you don't already have one, for example in ''/srv/svn'':
     24Before we can create a new trac environment we must first have a working subversion repository if we are going to get the full use out of trac. Create a subversion repository if you don't already have one, for example in ''/opt/subversion/repos'':
    2525
    2626{{{
    27  $ mkdir -p /srv/svn
    28  $ svnadmin create  --fs-type fsfs /srv/svn
     27 $ mkdir -p /opt/subversion/repos
     28 $ svnadmin create  --fs-type fsfs /opt/subversion/repos
    2929}}}
    3030
    31 Next you need to decide where to store your trac project and create the directory, for example in the new directory ''/srv/trac'':
     31Next you need to decide where to store your trac project and create the directory, for example in the new directory ''/opt/trac/projectA'':
    3232
    3333{{{
    34  $ mkdir -p  /srv/trac
     34 $ mkdir -p  /opt/trac/projectA
    3535}}}
    3636
    … …  
    3939A new Trac environment is created using [wiki:TracAdmin trac-admin]:
    4040{{{
    41 $ trac-admin /path/to/projectenv initenv
     41$ trac-admin /opt/trac/projectA initenv
    4242}}}
    4343
    44 [wiki:TracAdmin trac-admin] will ask you for the name of the project, the database connection string (explained below), and the type and the path to your source code repository.
     44Trac will first ask a few questions about your environment in order to initalize and prepare the project database.
     45
     46 Please enter the name of your project.
     47 This name will be used in page titles and descriptions.
     48
     49Project Name [My Project]> projectA
     50
     51 Please specify the connection string for the database to use.
     52 By default, a local SQLite database is created in the environment
     53 directory. It is also possible to use an already existing
     54 PostgreSQL database (check the Trac documentation for the exact
     55 connection string syntax).
     56
     57Database connection string [sqlite:db/trac.db]>
     58
     59 Please specify the absolute path to the project Subversion repository.
     60 Repository must be local, and trac-admin requires read+write
     61 permission to initialize the Trac database.
     62
     63Path to repository [/var/svn/test]> /opt/subversion/repos
     64
     65 Please enter location of Trac page templates.
     66 Default is the location of the site-wide templates installed with Trac.
     67
     68Templates directory [/usr/share/trac/templates]>
     69
     70---------------------------------------------------------------------
     71Project environment for 'projectA' created.
    4572
    4673''Note: The web server user will require file system write permission to the environment directory and all the files inside. Please remember to set the appropriate permissions. The same applies to the Subversion repository Trac is eventually using, although Trac will only require read access as long as you're not using the BDB file system.''
    47 
    48 === Database Connection Strings ===
    49 
    50 Since version 0.9, Trac supports both [http://sqlite.org/ SQLite] and [http://www.postgresql.org/ PostgreSQL] as database backends.  The default is to use SQLite, which is probably sufficient for most projects. The database file is then stored in the environment directory, and can easily be [wiki:TracBackup backed up] together with the rest of the environment.
    51 
    52 The connection string for an embedded SQLite database is:
    53 {{{
    54 sqlite:db/trac.db
    55 }}}
    56 
    57 === Source Code Repository ===
    58 
    59 You'll first have to provide the ''type'' of your repository (e.g. `svn` for Subversion, which is the default), then the ''path'' where the repository is located.
    60 
    61 If you don't want to use Trac with a source code repository, simply leave the ''path'' empty (the ''type'' information doesn't matter, then).
    62 
    63 Example of a configuration for a Subversion repository:
    64 {{{
    65 [trac]
    66 repository_type = svn
    67 repository_dir = /path/to/your/repository
    68 }}}
    6974
    7075== Directory Structure of Trac Environment ==
    … …  
    8893  '''Note: don't confuse a Trac environment directory with the Source Code Repository directory. It happens that the above structure is loosely modelled after the Subversion repository directory structure, but they are not and ''must not'' be located at the same place.'''
    8994
    90 3) Next, you need to edit the file ''/etc/httpd/conf.d/trac.conf'' to point to your new project
     95== Apache Configuration ==
     96
     97Next, you need to edit the file ''/etc/httpd/conf.d/trac.conf'' to point to your new project
    9198environment, as in this example (using mod_python):
    9299