SVN + Trac module for ISPConfig3

[quentusrex]

I'm interested in making a module that will allow the ISPConfig3 admin to allow clients to build svn and trac projects. Is anyone else interested in this module? Also, could someone send me links to ISPConfig3 module documentation? I'm considering setting something up along the lines of the way phpmyadmin is setup. One install, but have the client specific files in their web folders. and the client apache configuration in their vhost file.

[till]

The Link to the developer documentation is in the sticky post of this forum named "ISPConfig 3 Developer documentation".

[till]

One note. If you are searching for documentation of the software installation function, there is no documentation available yet. The software packages are .zip files containing at least a setup.sh script which is executed when the package gets installed plus the files that shall be installed.

I attached a package named test.zip

[quentusrex]

Is it better for ISPConfig3 modules to use a web directory such as www.mydomain.com/webmail/ ? or use a subdomain such as: webmail.mydomain.com ?

[quentusrex]

Is there a way to manually upload a module into ISPConfig3? to install a custom module?

[quentusrex]

Would there be a problem with adding a folder in the client's /var/clients/clientX/webY/svn and /var/clients/clientX/webY/trac ???

This way they aren't viewable from the web, but they are managed in the client's web folder, and thus subject to the clients web space restrictions. Would this also be tracked by webalizer and subject to the clients bandwidth restrictions? That would be useful.

[till]

Would there be a problem with adding a folder in the client's /var/clients/clientX/webY/svn and /var/clients/clientX/webY/trac ???

I dont see any problems with that.

Would this also be tracked by webalizer and subject to the clients bandwidth restrictions?

+
That depends on how you access them. If they were accessed like www.domain.com/trac/, then yes. If you access them like trac.domain.com, they will not be part of the webalizer stats.

[quentusrex]

Awesome. We'll see how it goes. here is my initial tutorial/build of the system. It allows for one install of trac and svn on the server, then allows easy install for each individual client. Thus it will be easy to add into a module to allow a user to have access to. :-D

This install is still rough. I need to test it a few more times, but it seems to work. It is initially designed to host a single project, but can easily be changed to host multiple projects.



1. sudo apt-get install apache2 libapache2-mod-python subversion-tools libapache2-svn python-setuptools subversion python-subversion

2. sudo easy_install Trac

3. sudo mkdir /var/clients/client1/web1/trac

4. sudo chown web1:client1 /var/clients/client1/web1/trac

5. vim /etc/apache2/sites-enabled/mydomain.vhost

Add the following near the end, but above the </VirtualHost>
================================

<Location /trac>
SetHandler mod_python
PythonInterpreter main_interpreter
PythonHandler trac.web.modpython_frontend
PythonOption TracEnv /var/clients/client1/web1/trac/testproject
PythonOption TracUriRoot /trac/testproject
PythonOption PYTHON_EGG_CACHE /tmp
</Location>

<Location /trac/login>
AuthType Basic
AuthName "myproject"
AuthUserFile /var/clients/client1/web1/trac/.passwd
Require valid-user
</Location>


<Location /svn>
DAV svn
AuthType Basic
AuthName "My Trac"
AuthUserFile /var/clients/client1/web1/svn/.passwd
AuthzSVNAccessFile /var/local/svn/svn.example.com/conf/authz
SVNPath /var/local/svn/svn.example.com
Require valid-user
</Location>

================================

6. sudo mkdir /var/clients/client1/web1/svn

7. sudo chown web1:client1 /var/clients/client1/web1/svn

8. sudo svnadmin create /var/clients/client1/web1/svn/<YourProjectNameHere>

9. sudo chown -R web1:client1 /var/clients/client1/web1/svn

10. sudo /etc/init.d/apache2 reload

11. sudo trac-admin /var/clients/client1/web1/trac/<YourProjectNameHere> initenv <projectname> sqlite:db/trac.db svn /var/clients/client1/web1/svn/<YourProjectNameHere>

12. sudo chown -R web1:client1 /var/clients/client1/web1/trac

13. sudo apt-get install build-essential graphviz htmldoc enscript

14. sudo rm /var/clients/client1/web1/svn/.passwd

15. sudo touch /var/clients/client1/web1/svn/.passwd

14. sudo rm /var/clients/client1/web1/trac/.passwd

15. sudo touch /var/clients/client1/web1/trac/.passwd

(so that trac can manage it's own users)
16. sudo chown web1:client1 /var/clients/client1/web1/trac/.passwd

17. Now some trac plugins:
sudo easy_install http://svn.edgewall.org/repos/genshi/trunk/
sudo easy_install http://trac-hacks.org/svn/accountmanagerplugin/trunk
sudo easy_install http://trac-hacks.org/svn/customfieldadminplugin/0.11
sudo easy_install http://trac-hacks.org/svn/eclipsetra...racrpcext/0.10
sudo easy_install http://trac-hacks.org/svn/iniadminplugin/0.11
sudo easy_install http://trac-hacks.org/svn/masterticketsplugin/0.11
sudo easy_install http://trac-hacks.org/svn/pagetopdfplugin/0.10/
sudo easy_install http://trac-hacks.org/svn/progressmetermacro/0.11
sudo easy_install http://trac-hacks.org/svn/ticketdeleteplugin/0.11
sudo easy_install http://trac-hacks.org/svn/tracwysiwygplugin/0.11
sudo easy_install http://wikinotification.ufsoft.org/svn/trunk

18. htpasswd /var/clients/client1/web1/svn/.passwd <username>

19. htpasswd /var/clients/client1/web1/trac/.passwd <username>

20. trac-admin /var/clients/client1/web1/trac/<YourProjectNameHere> permission add <username> TRAC_ADMIN

21. /etc/init.d/apache2 restart

[quentusrex]

TracError: The user www-data requires read _and_ write permission to the database file /var/clients/client1/web1/trac/testproject/db/trac.db and the directory it is located in.


Should I change the ownership of these files to www-data???

[till]

Originally Posted by quentusrex

TracError: The user www-data requires read _and_ write permission to the database file /var/clients/client1/web1/trac/testproject/db/trac.db and the directory it is located in.


Should I change the ownership of these files to www-data???

Either that or make it world redable.

Another solution might be to use python as cgi (if thats possible) instead of mod_python together with suexec so the file can be owned by the web user and nobody else needs permissions to this file.