top button
Flag Notify
    Connect to us
      Site Registration

Site Registration

Git Multi Server Setup

0 votes

I want to set up Git so that when I commit to BitBucket my web server automatically fetches those commits.
How can I do that?

posted Jun 16, 2013 by anonymous

Looking for an answer?  Promote on:
Facebook Share Button Twitter Share Button LinkedIn Share Button

Similar Questions
+3 votes

I'm looking to setup a git server under CentOS 6.5 x64 that will serve 2-5 .NET developers using Visual Studio Pro 2013. I've been reading that Visual Studio 2013 now has 'native git support', but as I've been reading into this more and more, it appears to me that the 'native git support' is really the fact that Team Foundation Server has git support on it and that I'd need to setup TFS in order to use the Visual Studio 2013's native git support. Can anyone either confirm and/or deny this for me? My personal suspicion is that I will need to implement TortiseGIT to do what I want to do, but wanted to throw this question.

If, in actuality, I can use a CentOS git server with Visual Studio 2013, can anyone point me in the direction of an FAQ/directions/YouTube video/book/anything for how to setup something like this? I have the resources to setup a CentOS git server (which will also host some DreamWeaver CC users as well on other projects), but setting up a dedicated TFS server isn't an option, hence why I'm looking into this.

+2 votes

Cloning huge repositories like Linux kernel takes considerable amount of time. Is it possible to incorporate a multi-threaded simultaneous connections functionality for cloning? To what extent do we need to change the architecture of the current code and how large would be the scope of the work? That just seems an interesting idea to me and would liked to share it with the community.

+1 vote

I would like to implement a multi-workspace version of git. The main goal is to have several independent workspaces using only one and single repository (without their own cloned repos). All these things will run on one host, or probably will be located on nfs and will be available on more hosts. Yes, I know there should be some restrictions, for example push and pull will work on the repo (probably there can be something like my-push). Branches will be somehow tied to the workspaces, also all workspaces will have its own HEAD. I would like to discuss here how can it be implemented, what will (or will not) work.

+3 votes

I was hoping that somebody could give me advice since I'm new to git.

I'll be installing a couple of projects from github on our servers, and adding some features.

Should I create a repository on our server (e.g. in /opt/git/), add the github project as a remote, and create a branch? Then on my local machine add our server as the remote and then pull / push with that?

On the server there will be two web directories: stable and dev. I was planning for these to be branches, and then just pull from the server repository using the local protocol.

I think it would mean sorting out merge actions on the server. I'm hoping to be able to fetch and integrate updates from the developer's github repository, but without making things more complicated than they need to be.

Does anyone have any suggestions?