trac_on_sdf
Differences
This shows you the differences between two versions of the page.
Both sides previous revisionPrevious revisionNext revision | Previous revision | ||
trac_on_sdf [2021/03/17 22:02] – fix file location of trac.cgi peteyboy | trac_on_sdf [2025/07/05 06:58] (current) – void hc9 | ||
---|---|---|---|
Line 1: | Line 1: | ||
+ | ====== Trac on SDF ====== | ||
+ | |||
+ | :!: //**This is currently NOT UP-TO-DATE info at SDF as Trac is not currently installed properly **// | ||
+ | |||
+ | This tutorial discusses how to install [[http:// | ||
+ | |||
+ | ===== Introduction ===== | ||
+ | |||
+ | Trac includes wiki, bug tracker, milestone plan and an interface to Subversion or Git. It is installed on SDF, so you can setup your own instance and manage your projects. | ||
+ | |||
+ | ===== Installing a Trac instance on SDF ===== | ||
+ | |||
+ | ==== Setting up an SVN repository ==== | ||
+ | |||
+ | Skip this step if you want to use Trac //without// a repository. Otherwise run the commands | ||
+ | |||
+ | $ mkdir .svn_repos | ||
+ | $ svnadmin create .svn_repos/ | ||
+ | |||
+ | to setup a repository named " | ||
+ | |||
+ | === Setting up a Git Repository === | ||
+ | |||
+ | :FIXME: TBD, but Trac supports git, which is more modern as source control. Details are [[https:// | ||
+ | |||
+ | ==== Setting up Trac ==== | ||
+ | |||
+ | Get started with | ||
+ | |||
+ | trac-admin / | ||
+ | |||
+ | where /// | ||
+ | |||
+ | If the output finally reads Project environment for 'My cool project' | ||
+ | |||
+ | ===== Running Trac ===== | ||
+ | |||
+ | There are currently two ways to run Trac on SDF: with the standalone server " | ||
+ | |||
+ | ==== Using the standalone server " | ||
+ | |||
+ | This is by far the least painful, but requires the MetaARPA membership because //tracd// opens a port on the machine. After you determine your [[meta port allocation]], | ||
+ | |||
+ | Next, run the command | ||
+ | |||
+ | tracd --port < | ||
+ | |||
+ | You will now be able to connect to your Trac instance with your Browser of Choice™ at '' | ||
+ | |||
+ | ==== Running Trac as CGI within Apache ==== | ||
+ | |||
+ | With this setup, you will be able to run Trac under your own domain. The tradeoff is performance – //tracd// is considerably faster. | ||
+ | |||
+ | Copy '' | ||
+ | |||
+ | cp / | ||
+ | |||
+ | and fix the permissions using '' | ||
+ | |||
+ | import os os.environ[' | ||
+ | |||
+ | Now Trac can locate the directory containing your instance. | ||
+ | |||
+ | If you rename the CGI to // | ||
+ | |||
+ | Point your browser to '' | ||
+ | |||
+ | **Note:** If you want to use Trac in your VHOSTed domain at SDF, be sure to put // | ||
+ | |||
+ | ===== Further reading ===== | ||
+ | |||
+ | To use prettier URLs, please refer to [[http:// | ||
+ | |||
+ | Most basic information (tickets, milestones, etc.) can be changed through the web interface. However, administrative tasks must be done on the command line using the '' | ||
+ | |||
+ | Lastly, [[http:// | ||
+ | |||
+ | ---- | ||
+ | |||
+ | Traditional link (using [[wp> | ||