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). >
That's a good practice, even more so if you're using Trac for this - though there's obviously a bootstrapping issue here ;-) > 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? > I don't think that such a diagram exists, but you can find all of the information you need in http://trac.edgewall.org/wiki/TracInstall (sort of). If you come up with some good synthetic documentation or diagram, don't hesitate to share it, it might even become the starting point for a clarified TracInstall. -- Christian --~--~---------~--~----~------------~-------~--~----~ 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 -~----------~----~----~----~------~----~------~--~---
