tools.html 2.75 KB
Newer Older
Mariano Montone's avatar
Mariano Montone committed
<h1><i class="fa fa-wrench"></i> Tools</h1>
<h2 id="trac">Trac</h2>

<p><a href="">Click here to access Trac.</a>

6 7 8 9 10 11 12
  <p>We are running Trac for projects who request it.  It's a
    fairly vanilla installation which resides in
    <code>/project/&lt;project&gt;/trac</code> (on the filesystem)
    and is writeable by the project administrator only.  He/she may
    choose to use <code>trac-admin</code> as per the documentation
    to add milestones, components, etc.  It's accessible through the web

14 15 16 17
    <p>The first thing you'll want to do after having logged in to your Trac
      instance is to go to <em>Settings</em> and add your email address and
      name.  This will make your username show up in the Assign-To dropdown
      list for tickets.
18 19 20 21

      <h3 id="permissions">Permissions</h3>

      <p>Everyone with a account has a Trac user and password,
22 23
      it is stored in $HOME/trac-info.txt.  Please see it for your username
      and password.
24 25

      <p>Trac is configured such that anonymous users may not create or modify
26 27 28 29 30 31 32 33 34 35 36 37 38 39 40 41 42 43 44 45 46 47 48 49 50 51 52 53 54 55 56 57 58 59
        the wiki (but may submit tickets) and authenticated users (ie. all users) can create or modify the wiki and submit tickets.
        If you need to restrict this you can argue your case at <a href="">
        the clo-devel mailinglist</a> or use <code>trac-admin</code> to change
        it for your project.

        <h3 id="notifications">Notifications</h3>

        <p>Notifications are automatically sent to the &lt;project&gt;
          mailinglist and Reply-To is set to the &lt;project&gt; list.
          If you want to change this you may change <code>/project/&lt;project&gt;/trac/conf/trac.ini</code>
          to suit your needs.

               <h2 id="rsync">rsync service</h2>
               All projects are available through rsync.  This makes syncing
               webpages, source code or binaries to mirrors easy to manage for project members.
               To see all projects available use <code>rsync</code>.

          <!--            <h2 id="viewcvs">Repository access</h2>

               <p>Here at we offer git, Subversion, darcs and CVS to our
               projects.  To view their repositories, use the following links:</p>

               <li><a href="/viewvc">ViewVC</a> [CVS and Subversion]</li>
               <li><a href="/darcsweb.cgi">darcsweb</a></li>
               <li><a href="/gitweb">GitWeb</a></li>