wesgarrison.us

Never used Trac before. I like the way it’s laid out, so I definitely want to try it out. Having never set it up, I want to set it up for a new project.

First, you need a port to put your tracd daemon on, so put in a TextDrive Support Ticket first because it’ll take a little while to get it (my response time was 3 hours and 6 minutes.)
I started with the TextDrive manual for installing trac.

I’ve already got a subversion repository that I’ve been using for several months, so that part is ready to go.

I made my directory as ~/trac

Since my project is not on my primary domain, I had to write out the path to it so I didn’t forget. There’s not auto-tab-path-completion inside the trac prompts, and I just can’t type all that path stuff out by memory.
On chilco, I had to modify the trac-admin command by adding ‘/users’ to the beginning of the path:

trac-admin /users/home/wesgarrison/trac/sampletrac initenv

The same caveat about /users applies when running tracd, too.

I chose to put my trac start in a file and put it in ~/etc/rc.d/trac_start , just like my lighttpd and rails start scripts.

After running my startup script, I could see trac wonderfully on its port.

I logged into webmin and made my cron job, using the script as the job to be run on system boot.  Next, I turned my attention to setting up a rewrite rule to proxy to tracd from Apache.
Now, I need to add some tickets and start getting them done!