Yeah - just ran into the CSS problem. :/ Considering just running this out of a vhost rather than a subdir - although it'd be interesting to see how much work would really be needed to make this happen.
On Jun 3, 10:31 am, Thomas <[email protected]> wrote: > The fork still exists as a merge request [1]. > > We have gitorious running on our private server using a sub base uri > (e.g.http://someserver.com/gitorious/), but we hardcoded almost every > existance of '/' to '/gitorious/'. I have a clone of the new > gitorious, which runs with these modifications. See [2] for more the > changes made to mainline. > > Greets, Thomas > > [1]:http://gitorious.org/~dcrec1/gitorious/dcrec1s-clone/commit/c37d420f8... > [2]:http://gitorious.org/~tschamm/gitorious/tschamms-clone > > On Jun 3, 7:14 pm, "Per Christian B. Viken" <[email protected]> > wrote: > > > On Jun 3, 2009, at 7:06 PM, Steve Hajducko wrote: > > > > We installed gitorious on a system where we have several other rails > > > apps running and I've got it running in a mongrel+apache setup with > > > mod_proxy. > > > > The problem we're running into is that we run the app > > > ashttp://host.example.com/git/ > > > - We've found is that there are certain times when gitorious redirects > > > the user back to /, which ends up being some other site rather than > > > the app. > > > > I've gone through the code and found a few instances where this > > > happens - mostly in session_controller, users_controller and > > > merge_requests_controller. Would it be possible to change this to be > > > a configurable value via gitorious.yml? I didn't want to post a patch > > > because I'm not sure if there are other instances yet where gitorious > > > assumes that it's running out of '/' on the site - I only really did > > > this to the obvious instances and then added a 'gitorious_url' to the > > > gitorious.yml file. > > > > If those really are the *only* places, I can submit the patches up - > > > wasn't sure on the name of the config variable either but I couldn't > > > think of anything better to call it. :) Maybe gitorious_urlroot > > > One problem is that the CSS-files contains tons of references to > > images found in "/images". Not sure what the best way to deal with > > those are, but I'm sure it could be done. > > > There was a fork of Gitorious that did something similar, I can't > > remember the exact name right now. That was for the old version of > > Gitorious however, and might not work very well anymore. But maybe you > > could get some ideas. --~--~---------~--~----~------------~-------~--~----~ You received this message because you are subscribed to the Google Groups "Gitorious" 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/gitorious?hl=en -~----------~----~----~----~------~----~------~--~---
