Thanks Erik. I tried that approach (multiple subdomains) but had trouble
getting Trac to work that way. I'll give it another go, as you're probably
right.

-- 
Chris Bloom
Internet Application Developer
http://www.csb7.com/blogs/whyblogwhy/

On 9/28/07, Erik Bray <[EMAIL PROTECTED]> wrote:
>
>
> On 9/28/07, Chris Bloom <[EMAIL PROTECTED]> wrote:
> > Wow, that was quick :)
> >
> > Here's the .htaccess content. There was nothing there prior to
> installing
> > Trac; It was just an empty dir. I think Dreamhost did some magic on
> their
> > end to link that URL to the SVN repo, which, prior to Trac, I could use
> to
> > simply browse the latest revision.
> >
> > ----------
> > DirectoryIndex index.fcgi
> >  Options ExecCGI FollowSymLinks
> > <IfModule mod_rewrite.c>
> > RewriteEngine On
> > RewriteCond %{REQUEST_FILENAME} !-f
> > RewriteCond %{REQUEST_FILENAME} !-d
> >  RewriteRule ^(.*)$ /index.fcgi/$1 [L]
> > </IfModule>
> >
>
> The problem, so far as I can tell, is that you have your SVN
> repository and your Trac site rooted at the same path on your web
> server.  This is going to be very, very confusing for SVN, and I don't
> think you can even make it work that way.
>
> You need to set up your trac site at something like trac.mydomain.com,
> or mydomain.com/trac, or whatever works for you.  But if your SVN
> repostitory's root is svn.mydomain.com/ then I would not try to put
> anything else there.
>
> Alternately, you can root your repository at something like
> svn.mydomain.com/repos, and then put whatever you like under
> svn.mydomain.com.  For Trac, I would still put it in its own path,
> such as svn.mydomain.com/trac.
>
> Erik
>
> >
>

--~--~---------~--~----~------------~-------~--~----~
You received this message because you are subscribed to the Google Groups "Trac 
Users" group.
To post to this group, send email to trac-users@googlegroups.com
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
-~----------~----~----~----~------~----~------~--~---

Reply via email to