Y
Y
Yakov Kravtsov2015-12-06 02:04:29
git
Yakov Kravtsov, 2015-12-06 02:04:29

What is the correct way to migrate a GIT repository?

Greetings!
There is a working copy of the repository with branches, changes. Uploaded to a local GIT server at work. But the problem is that it is only available locally. You can take the work home, and you are already tired of copying back and forth on a flash drive. Raised the home server. Set up. Works. But now how to move the whole thing there?
1) Tried to add one more source (in SourceTree which I use) - it is not flooded.
2) I tried to make a repository on the server, and upload everything that was in the .git folder there - it seems to be flooded, the web face shows files, changes, etc. --- but not cloned, error again.
What am I doing wrong? And what is the right way to organize it all? After all, it’s probably somehow possible, because Git is essentially a decentralized system, and each working copy can also become a repository.
Thank you very much in advance!
PS
Server: Windows Server 2012 R2 + IIS 8.5 + BONOBO GIT SERVER 5.0.1.0

Answer the question

In order to leave comments, you need to log in

2 answer(s)
M
Maxim Moseychuk, 2015-12-06
@fshp

git daemon
But my advice to you is to raise GitLab better. It is set in 2 clicks, it is also configured in 2.

A
abcd0x00, 2015-12-06
@abcd0x00

The simplest thing is to make a bare repository (bare) and put it on a server accessible to both clients. And then clone it for each of the clients and push it on the client after the changes. (When cloning, the source address will be set automatically.)

Didn't find what you were looking for?

Ask your question

Ask a Question

731 491 924 answers to any question