http://qs321.pair.com?node_id=662300


in reply to Re: a question on case/software engineering
in thread a question on case/software engineering

hi, i really liked your idea of using trac. now here is my situation. i am basically a single programmer. i dont have any employees (as of yet). but i have a server, on which i will install trac. is that the right thing to do? but will it handle only a single project or multiple projects? on my computer i have apache group\apache\cgi-bin and some projects in apache group\apache\modperl where i store some of my cgi scripts for different projects. now how to use trac? is there a guide/tutorial of trac for newbies? if you could show me some screenshots of your trac page like how it is organised and stuff then i can get a good idea on how to use it properly. i have been programming for quite some time now. but now i want to stream line my operations a bit more. so that i can keep track as well as analyse my data later. what about keep track of emails and payments made? which software to use for that? thank you for all your help.
  • Comment on Re^2: a question on case/software engineering

Replies are listed 'Best First'.
Re^3: a question on case/software engineering
by olus (Curate) on Jan 14, 2008 at 16:33 UTC
    On trac's homepage they have a few links for the documentation that will help you get started as well as getting into some more advanced features.
    I have trac installed on a virtual machine, and manage several projects from the same installation.
    You must get acquainted with trac's command line tool that allows the initial setup and configuration for each project.

    You start by creating an svn repository for each project.
    My installation is at /servers/work/...
    sudo svnadmin create /servers/work/svn/repo/<PROJECT>
    Having created the repository, you can now initialize your trac environment for the PROJECT
    sudo trac-admin /servers/work/trac/env/<PROJECT> initenv
    Also, typing help on trac-admin's prompt will display a list of available commands and how you can set different levels of permissions.

    Do read the TracGuide. They have good documentation.

    I have trac online and work with the permissions in order to grant access to different kinds of information.
    Everyone can see the wiki and the ticket reports, but wiki and ticket creation are granted only to the developers and 'project owners'.