4 Just put the plugin files in the rigth place:
5 /opt/gforge/plugins/scmhg
7 --> /opt/gforge/www/plugins must contain a symlink to /opt/gforge/plugins/scmhg/www
9 Make sure you have installed Mercurial correctly. The Plugin should work with almost any Version of it.
10 Now search the hgweb.cgi of your Mercurial install or download it from http://mercurial.selenic.com/ .
12 The file should contain some lines like:
13 application = hgweb("/path/to/repo", "repository name")
14 wsgicgi.launch(application)
15 This lines are needed to launch independend webpages for every mercurial project.
16 Put the hgweb.cgi into scmhg/www/cgi-bin and make sure that it is readable for the user running fusionforges-cronjobs.
18 Now copy the fflog.tmpl file available in etc directory into your central mercurial path for templates. It should be something like '/usr/lib/python2.6/site-packages/mercurial/templates/' .
19 The path was correct, when you can use 'hg log --style fflog.tmpl' from any hg repository. The template file is needed to gather statistics for the sourcecode history.
22 Your scmhg.ini (/etc/config.ini.d/) should contain the following entries:
23 default_server, repos_path, use_ssh, use_ssl, use_dav, anonhg_login, anonhg_password
27 Here is an example configuration for use with http and hgweb .
30 # Mercurial Repository
32 ScriptAliasMatch ^/hg/(.*) /opt/gforge/www/plugins/scmhg/www/cgi-bin/$1.cgi
33 <Directory "/opt/gforge/www/plugins/scmhg/www/cgi-bin">
34 Options +ExecCGI FollowSymLinks Multiviews
35 AddHandler cgi-script .cgi
37 RewriteRule .* - [E=REMOTE_USER:%{ENV:REDIRECT_REMOTE_USER}]
45 AuthName "Mercurial Access"
46 AuthUserFile /data_path/hgroot-authfile