> Here's a use case for multiple instances on same server: > > an individual developer would like to publish his code to the world. > He could create an account on github and put it there, and indeed > that's what many people do almost by default. > > But he might want to publish "his" code at "his" domain, with his own > color scheme, branding etc. just like he might have a blog at that own > domain, etc. This is not unlikely as many employers, for example, now > Google their prospective hires and try to look at code they wrote. > > Chances are blogs etc. of individual are run on shared servers, and it > would be nice if Gitorious could function in that environment. > > Scalability is not an issue because it's just the code of some single > individual.
To be clear: I don't disagree that there are good use cases. This is indeed one of them. My point was that multiple setups on the same server is not something I'd recommend for companies/larger organizations. > > Question: so if gitorious was set up to only speak http (not the git > protocol), shouldn't that work? Indeed. And that would be a very neat setup, easier to install etc. We've considered it for some time. The only part missing is push over HTTP, which I don't think is a lot of code to pull off. Maybe Marius wants to chip in, as he's done some exploratory work on that. Christian -- -- To post to this group, send email to [email protected] To unsubscribe from this group, send email to [email protected] --- 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 [email protected]. For more options, visit https://groups.google.com/groups/opt_out.
