It may not be so easy to run more than one installation of Gitorious on the same server.
Creating a GITORIOUS_HOME env var that points in the direction of the correct config file(s) is one step. That's straightforward (and in fact I have it working -- will make available shortly) Different "context" paths (example.com/foo vs. example.com/bar) work partially, as discussed earlier, and could probably get fixed with a bit of diligence digging through the code looking for where URLs are generated. But what about ssh? It seems that gitorious wants a system user, which is set up in a way that when ssh logs into that user, the "gitorious" command is executed. That command doesn't have any context in terms of which installation to talk to. One could create different system users for each installation, e.g. example.com/foo goes with git1, example.com/bar goes with git2, and example.net with git3. That'd be really messy, and hard to administer. Alternatively there could be one git system user, but the gitorious usernames would have to be unique across all Gitorious installations (so the .ssh/authorized_keys file could invoke gitorious with the correct context) Same for the git daemon? But if installations only supported http, would that work? Cheers, Johannes. -- -- To post to this group, send email to gitorious@googlegroups.com To unsubscribe from this group, send email to gitorious+unsubscr...@googlegroups.com --- You received this message because you are subscribed to the Google Groups "Gitorious" group. To unsubscribe from this group and stop receiving emails from it, send an email to gitorious+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/groups/opt_out.
