On Feb 21, 2009, at 5:25 AM, ray wrote:
> > > > On Feb 20, 1:31 pm, "Noah Kantrowitz" <[email protected]> wrote: >> You want to use all the defaults for the most part. Just use tracd >> as the >> server, it is easier. As of 0.11.3 we should be compatible with >> Python 2.6, >> so either the latest 2.5 or 2.6 is fine. >> > Noah, > > Thank you for the concise directions. They will help me be more > focused for planning the installation (I am logging my activities so I > can have a reproducible path to follow when I need to do this again to > actually implement the system). > > I would like to learn more about how Trac works and it seems that > knowing what the system looks like might help. This is why I would > like to see come type of architectural diagram. Does one exist? Not sure what you are asking for. Trac is a webapp, not some kind of large server install. It touches a DB for storage (though in the case of sqlite you wouldn't notice) and the svn repo to display data about it (read-only access is fine for FSFS-based repos). The only other "architecture" concern I can think of is needing an SMTP server to send emails. --Noah --~--~---------~--~----~------------~-------~--~----~ You received this message because you are subscribed to the Google Groups "Trac Development" group. To post to this group, send email to [email protected] To unsubscribe from this group, send email to [email protected] For more options, visit this group at http://groups.google.com/group/trac-dev?hl=en -~----------~----~----~----~------~----~------~--~---
