CODEWITHSUNDEEP
git
usr-local-ΕΨΗΕΛΩΝ
usr-local-ΕΨΗΕΛΩΝ

Reputation: 26874

Using a Git manager against existing private Git repositories

This question is tied to my other one, but it's a different question in the specific.

Suppose I have already set up private Git repositories in Apache 2 within an organization. Later we decide to implement a Git management tool such as Stash or just any other. AFAIK these tools come with their own Git server, or at least I haven't performed research yet.

The question is very simple: can Stash, or another tool, be set up in order to work on existing URLs instead of relocating the repositories? I'm asking now because my organization is planning to use Git and we must decide our strategy in advance. Stash is current candidate because we use other Atlassian products.

The scenarios are two: either we start our own "manual" Gitting on our Apache "monstre" (using the same approach I'm going to use for my personal private repositories) and then buy Stash when we like, or we must buy Stash first.

The distributed nature of Git suggests that repositories might be migrated to another URL easily

Upvotes: 0

Views: 40

Answers (3)

drRobertz
drRobertz

Reputation: 3638

Gitolite is great if you want centralized control of users, permissions, etc. For a bit more flexibility, delegating management of individual (groups of) projects to users, via a web interface, I recommend gitlab (https://about.gitlab.com), basically an open source altrnative to github written in ruby/rails.

Upvotes: 2

sschuberth
sschuberth

Reputation: 29821

According to this answer, unfortunately Stash cannot be used to just put access control on top of an existing Git repository. You have to import your "vanilla" Git repository to Stash.

Regarding other tools, Gitolite (which I highly recommend) can put access control on top of an existing Git repository. It works with both HTTP or SSH access to the repository.

Upvotes: 2

Matthieu
Matthieu

Reputation: 16407

I am not sure what you mean by setting up a Git repository in Apache 2. Git is a server by itself and does not need Apache to run. Looking at your other question, maybe Apache is only to get a view of the repository and navigate it remotely? Or is it to be able to clone through http? Or more than that?

Stash will be hosting your git repositories by itself. You can use it to manage permissions, code reviews...etc...

As you mention in your last line, it is easy enough to "move" (clone) a git repository from one place to another, so if you have a system that works now and you just decide to use Stash, gitolite, github or anything else later, that should not be a problem. It's more about the services you want or use around that git server that you may have to change.

Upvotes: 2

Related Questions