Hi,

I've been looking into the subject. Evaluated 2 projects

Trac
- Very active, 13 contributors (according to ohloh) in python
- One proecess per project. We can associate a realm to a several projects.
It is multi-tenanted.
- Apache license
- Good API


Bug Genie Notes (Sameera pointed this out)
- This is multi-tenant using the means of hostnames. The methodology is to
put host name in /etc/hosts and then in /etc/apache2/sites-enabled. So this
solution is not very scalable. Perhaps it will scale up to hundreds.
- MPL
-Does not have a good API
-Not very active, 1 contributor
-Agile dashboards are present

IMO trac has a more scalable MT story than Bug Genie. I am +1 for trac. So
going forward with track would mean having a service that spawning
processes as required and killing them after a certain idle time. I think
that system would scale well. I assume there is a better way to do
authentication password file - which I have been using so far.

thanks,
dimuthu


-- 
Dimuthu Leelarathne
Architect & Product Lead of App Factory

WSO2, Inc. (http://wso2.com)
email: [email protected]

Lean . Enterprise . Middleware
_______________________________________________
Architecture mailing list
[email protected]
https://mail.wso2.org/cgi-bin/mailman/listinfo/architecture

Reply via email to