That's a good question. One of my scripts gracefully restarts Apache, so that command line might have to change. Otherwise I can't think of anything that wouldn't work without maybe some minor changes. I'm hoping to have the scripts uploaded to trac-hacks soon.
I'm sorry I don't know anything about Windows authentication with Apache/Trac. Maybe someone else could answer this? On Feb 19, 11:27 pm, ray <[email protected]> wrote: > Stodge, > > Thank you for responding to my concerns in the google trac goup. I > read the page about the Apache configure your message linked to. Of > course, now I have more questions. I really appreciate your efforts. > > I have done no programming in Python, yet. Reading the examples is > giving me a feeling for the methods. > > Your examples brought up two major questions: > > You stated that your scripts were designed for Linux. Does this go > anyu further than the 'typical' file system symbols and naming > conventions? > > I found the access control you presented to be quite fine grained. I > was planning (for SVN) on using Windows authentication with Apache. > Is this possible with Trac? What are the ramifications? > > Thanks, > Ray > > On Feb 10, 6:50 am, Stodge <[email protected]> wrote: > > > I updated my page on Trac hacks with the Apache configuration files > > for Trac & Subversion. Hope this helps: > > >http://trac-hacks.org/wiki/AdminToolkitScript > > > On Feb 9, 9:44 pm, Stodge <[email protected]> wrote: > > > > We use Apache to access Trac and Subversion. I also wrote some scripts > > > that make it easier to create and manage multiple projects (one > > > project per Trac environment). I'm in the slow process of open > > > sourcing the scripts ontohttp://track-hacks.org. I will also include > > > two Apache configuration files; one for Trac and one for Subversion. > > > So if you can wait a wee while I'll try to get those up. Currently the > > > scripts assume global rights - that is, everyone can access all > > > projects. I also plan on changing the scripts to provide per project > > > authentication, so you can define which users can read/write each > > > project (assuming one project is one Trac environment and one > > > Subversion repository, both on the same server). But this will take > > > time. Drop me an email and I'll try to walk you through it. > > > > Cheers > > > Mike > > > > On Feb 9, 11:29 am, ray <[email protected]> wrote: > > > > > I am experimenting with TSVN to manage content in an engineering > > > > company. Additionally, I would like to have an issue tracker for > > > > office operations. I have found reading about Trac. I have seen in > > > > this discussion group that Trac uses SVN as a repository. I would > > > > like to keep the two repositories separate in physical location and > > > > ACLs. > > > > > I see that Trac can us Apache as an http server. Since this is > > > > similar to what I have setup (TSVN and > > > > Appache), I would like to consider using both TSVN and Trac with one > > > > Apache server. > > > > > I would like to learn about other people that may have experience > > > > with > > > > this combination. Moreover, I am concerned with how to setup Apache > > > > for both TSVN and Trac. Is there any problem with serving both from > > > > one Apache instance and how do I configure Apache for both? > > > > > Thanks, > > > > Ray- Hide quoted text - > > > - Show quoted text - --~--~---------~--~----~------------~-------~--~----~ You received this message because you are subscribed to the Google Groups "Trac Users" 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-users?hl=en -~----------~----~----~----~------~----~------~--~---
