Re:Running servers and services well is not trivial (2018)
by marginalia_nu on Sunday March 27, 2022 @09:48AM
(#30820204)
From any machine who has checked out the code? That's sort of the point of git. Any cloned version of a repository is a "git server" in itself.
Re:Running servers and services well is not trivial (2018)
by 0ldskool on Monday March 28, 2022 @07:19PM
(#30836798)
So the solution is to individually track down each cloned git repo on developers workstations. Then have each developer open up SSH access for others to clone using SSH or run an HTTP server? Also keep in mind not all repo's may have been cloned, up-to-date, etc...
DVCS is designed to propagate code to many people and allow them to easily modify and share with others who also have a copy. If people don't have a copy they can get a copy of a copy (which at some point may have been modified). In a large company you need a Single source of centralized truth. You cannot build a company on the concept of "it works on my dev workstation" or the worse suggestion here "all the company's IP source code is on only on my dev workstation".
You’re responsible for 1000 Git repositories used by developers all over your department. Some (or even all) of those have just been wiped in a ransomware attack.
Whom are you going to tell to `git clone` what from where?