Installation and Configuration of TRAC - standalone-server-configuration

• See official site: ​http://trac.edgewall.org/wiki/TracStandalone

• Get packages (trac-admin + standalone-server tracd)
  • Install setuptools via your packaging system (python - addon)
  • Install trac (here trac 0.12):

    server$ easy_install Trac==0.12
    

  • easy_install should resolve all dependencies
  • see ​http://trac.edgewall.org/wiki/TracInstall#Usingeasy_install
• Create the trac-directory containing
  • the configuration-file of this project (i.e. trac.ini)
  • the user-information (passwords + permissions)
  • the database for the wiki, tickets etc.
  • Therefore:

1. Init trac-environment

   server$ trac-admin /path/to/trac_dir/ initenv
   

   Choose Project Name, and local sqlite-database (I think also SQL and others are possible)

2. Create .htpasswd file in /path/to/trac_dir/:

   server$ htpasswd2 -c /path/to/trac_dir/.htpasswd username
   

   You are prompted for a password. To use the svn-users with trac, a small script can update the trac-user-information from the svn-passwd-file (see below).
3. Add admin-permissions for username -- necessary for availability of Admin-tab in the web-interface (see ​http://trac.edgewall.org/wiki/TracPermissions#GraphicalAdminTab):

   server$ trac-admin /path/to/trac_dir permission add username TRAC_ADMIN
   

4. Start trac-deamon tracd on your machine on port 8000 with .htpasswd as authentication-file:

   server$ tracd --port 8000 --basic-auth=*,/path/to/trac_dir/.htpasswd,realm /path/to/trac_dir
   

   realm is an arbitrary name. To start tracd in background and append all output to a file:

   server$ nohup tracd --port 8000 --basic-auth=*,/path/to/trac_dir/.htpasswd,realm /path/to/trac_dir &
   

   The output is appended to nohup.out!

5. Run your web-browser and type the following location:

   server:8000
   

6. Log in as username and you should see the Admin-tab on the upper right corner

7. The administration via the web-interface is self-explanatory (Project-Description, Permissions, Plugins, Repositories...).

Update .htpasswd

• the svn-passwd-file is saved unencrypted. An example:

  [users]
  user1 passwd1
  user2 a_second_passwd
  user3 ...
  

• tracd needs an encrypted file created by htpasswd2. To not have to administrate two different user and password information files, there is a small bash-script, which encrypts the unencrypted svn-passwd file automatically. (Maybe some future solutions should only use encrypted password information.) Edit the attached script (mainly the paths) for your requirements and schedule it maybe to run automatically every hour...

Remark: Until now the script asks for a user input for confirmation.