3 ms·
I've tried this route and the problem is that my company wants some open-source stuff and some closed source stuff. So a private Gitorious setup isn't great bec
by sant0sk1 16y ago
I've tried this route and the problem is that my company wants some open-source stuff and some closed source stuff. So a private Gitorious setup isn't great because we can't put our open-source stuff there.
If self-hosted Gitorious allowed for private & public projects then I could let it face the internet and have the perfect solution. I've seen a few implementations of private projects with merge requests, but sadly the Gitorious team has largely ignored them.
- darklajid 16y agoDon't want to be the gitorious fanboy here. I'm using both and I'm not involved with either project (although I kind of run an internal gitorious instance here at work). I have to agree with you: Both on one server is not possible. The only way to make this work would be cumbersome: Install a public and a private instance of gitorious. For private projects: Works just as before. For public projects: Push to somewhere and make the post-receive hook propagate the change to public/private. Ugly? Hell, yes. It's nothing but a workaround. On the other hand: You can mix GitHub and Gitorious just fine. Your client (if you use one, or the git cli) doesn't care about the hosts, so having http://myPrivateGitorious http://myPrivateGitorious repositories next to http://github.com http://github.com repositories would work fine and you gain the best of both worlds. It's the same system. You can easily push/pull/merge from one to the other, it's not like the decision to use one or the other has to be an XOR.
- icefox 16y agoAfter getting fed up with Gitorious I made GitHaven (http://www.githaven.com/ http://www.githaven.com/) which allows you to have public and private repositories and comes with a much simpler installer to boot.