Edgewall Software

Changes between Version 7 and Version 8 of TracOnRHEL


Ignore:
Timestamp:
Feb 27, 2015, 2:55:27 PM (9 years ago)
Author:
figaro
Comment:

Cosmetic changes

Legend:

Unmodified
Added
Removed
Modified

  • TracOnRHEL

    v7 v8  
    1 = Trac on RHEL =
     1= Trac on RHEL
    22
    3 Installing Trac On RHEL 4 (and higher), is easy with Yum.
     3Installing Trac on [http://www.redhat.com/en/technologies/linux-platforms/enterprise-linux RHEL 4+] is easy with the Yum package manager.
    44
    551. If you haven't already installed Yum, do so as appropriate for your operating system.
    … …  
    99  $ sudo yum install trac
    1010}}}
    11  Yum will take care of all dependencies on which the Trac package depends (including the python-clearsilver package) and will fetch and install them for you automatically.
    12  Note: With the current (0.11.5) version in RPMforge the mod_python dependency is missing, so if you haven't already installed mod_python you also need to do:
     11 Yum will take care of all dependencies on which the Trac package depends (including the python-clearsilver package) and install them for you automatically.
     12 '''Note''': the mod_python dependency may be missing in RPMforge, so if you haven't already installed mod_python, you also need to do:
    1313{{{
    1414  $ sudo yum install mod_python
    1515}}}
    16161. Create a new project environment. An environment is basically a directory that contains a human-readable configuration file and various other files and directories.
    17  a. Create a subversion repository if you don't already have one, for example in ''/srv/svn'':
     17 a. Create a Subversion repository if you don't already have one, for example in `/srv/svn`:
    1818{{{
    1919 $ sudo mkdir -p /var/www/svn/foobar
    2020 $ sudo svnadmin create  --fs-type fsfs /var/www/svn/foobar
    2121}}}
    22  a. Next you need to decide where to store your trac project and create the directory, for example in the new directory /srv/trac:
     22 a. Next you need to decide where to store your Trac project and create the directory, for example in the new directory `/srv/trac`:
    2323{{{
    2424 $ sudo mkdir -p  /var/www/trac
    2525}}}
    26  a. Then create a new environment using [wiki:TracAdmin trac-admin], as in this example for project ''foobar''
     26 a. Then create a new environment using [wiki:TracAdmin trac-admin], as in this example for project `foobar`:
    2727{{{
    2828 $ sudo trac-admin /var/www/trac/foobar initenv
    2929}}}
    30  a. Now make it owned by apache:
     30 a. Now make it owned by Apache:
    3131{{{
    3232 $ sudo chown -R apache:apache /var/www/trac/foobar
    3333 $ sudo chown -R apache:apache /var/www/svn/foobar
    3434}}}
    35 1. Next, you need to edit the file ''/etc/httpd/conf.d/trac.conf'' to point to your new project environment, as in this example (using mod_python):
     351. Next, you need to edit the file `/etc/httpd/conf.d/trac.conf` to point to your new project environment, as in this example (using mod_python):
    3636{{{
    3737# The Location is the part after the host (http://example.com<Location>) that
    … …  
    5858}}}
    5959
    60 = Apache Authentication =
     60== Apache Authentication
    6161
    62 The example above assumes you have a trac project environment setup in ''/var/www/trac/foobar/'' directory, described in step 2 and an htpasswd file at /var/www/trac/foobar/conf/trac.htpasswd for authentication purposes (see also wiki:TracModPython (too generic)).
     62The example above assumes you have a Trac project environment setup in `/var/www/trac/foobar/` directory, described in step 2 and an htpasswd file at `/var/www/trac/foobar/conf/trac.htpasswd` for authentication purposes. See also a generic guide at TracModPython.
    6363
    64 There are numerous other ways to authenticate users, but if you care about security ''do not'' use the same authentication for comand line Subversion clients as you do for Trac. This is because Subversion keeps its passwords for command lines locally, in your home directory, in clear text.
     64There are other ways to authenticate users, but if you care about security '''do not''' use the same authentication for comand line Subversion clients as you do for Trac. This is because Subversion keeps its passwords for command lines locally, in your home directory, in clear text.
    6565
    66 = Activating the web server =
     66== Activating the web server
    6767
    6868You will need to tell Apache to reload configuration after editing trac.conf:
    … …  
    7272}}}
    7373
    74 Verify your Trac installation by pointing your browser at the correct URL for your Trac server (e.g. http://localhost/trac).
     74Verify your Trac installation by pointing your browser at the correct URL for your Trac server, eg `http://localhost/trac`.
    7575
    7676Notes on the RHEL package:
    7777
    78  * trac.cgi and trac.fcgi are installed in /var/www/cgi-bin/ (actually, //usr/share/trac/cgi-bin/trac.fcgi for RHEL).
    79  * apache webserver config file is installed in /etc/httpd/conf.d/trac.conf
     78 * trac.cgi and trac.fcgi are installed in `/var/www/cgi-bin/`, or `//usr/share/trac/cgi-bin/trac.fcgi` for RHEL.
     79 * Apache webserver config file is installed in `/etc/httpd/conf.d/trac.conf`.
    8080
    81 If you happen to come across any packaging issues, feature requests or problems on RHEL, you can submit a bugzilla bug for the Trac package at [https://bugzilla.redhat.com/bugzilla/easy_enter_bug.cgi].
     81If you happen to come across any packaging issues, feature requests or problems on RHEL, you can [https://bugzilla.redhat.com/bugzilla/easy_enter_bug.cgi submit a Bugzilla bug] for the Trac package.
    8282
    83 Be sure to check out the generic installation instructions in the [wiki:TracGuide TracGuide]
     83Also check the generic installation instructions in the TracGuide.
    8484
    85 == SELinux ==
     85== SELinux
    8686
    8787RHEL now ships with SELinux enabled by default. This means you need to make the Trac and Subversion directory accessible to the webserver. If you keep these contents under {{{/var/www/trac}}} and {{{/var/www/svn}}}, you don't need to do anything else.
    8888
    89 If you want an alternative location such as {{{/srv}}} or {{{opt}}}, and many installers have their own ideas about where these should go, follow thiese guidelines and read the notes at [http://fedora.redhat.com/docs/selinux-apache-fc3/] for details.
     89If you want an alternative location, such as {{{/srv}}} or {{{opt}}}, and many installers have their own ideas about where these should go, follow these guidelines and read the notes at [http://fedora.redhat.com/docs/selinux-apache-fc3/] for details.
    9090
    9191{{{
    … …  
    9494}}}
    9595
    96 If you put these under {{{/srv/www/trac}}} and {{{/srv/www/svn}}} instead, the {{{restorecon}}} command will know that these attributes should be preserved. Alternatively, you can teach {{{restorecon}}} about these two directories by adding these lines to the file {{{/etc/selinux/targeted/contexts/files/filecontexts.local}}}
     96If you put these under {{{/srv/www/trac}}} and {{{/srv/www/svn}}} instead, the {{{restorecon}}} command will know that these attributes should be preserved. Alternatively, you can teach {{{restorecon}}} about these two directories by adding these lines to the file {{{/etc/selinux/targeted/contexts/files/filecontexts.local}}}:
    9797
    9898{{{
    … …  
    101101}}}
    102102
    103 You may need to create this file if it is not already present: it's not present by default.
     103You may need to create this file, because it is not present by default.