6 ms·

Excuse my ignorance, since I don't work in the corporate world. But isn't one of the central points of a distributed version control system like git that you do

by kleiba 14y ago

Excuse my ignorance, since I don't work in the corporate world. But isn't one of the central points of a distributed version control system like git that you don't have to host it at all? (Of course, you still need a network that you're in control of.)

hp50g 14y ago
Well we need a master as an integration point for building deployment packages, which means that you need a central host anyway. Github is usually just this thing for people.
- jiggy2011 14y ago
  You can have a master branch without necessarily having a central server.
  - hp50g 14y ago
    Yes but how does our integration server know which one of our 180 dev workstations has the latest tip of the master branch?
    - jiggy2011 14y ago
      Add the integration server as a remote.
    - khromov 14y ago
      This needs an answer.
    - querulous 14y ago
      the integration server has it's own repo that you push 'latest tip' to
      - deleted 14y ago
        [deleted]
      - hp50g 14y ago
        That's a poor solution as there is no way to know how much of the product is actually on that repo...
        jiggy2011 14y ago
        Not quite sure what you mean, you will have whatever branches you assign to it.
jiggy2011 14y ago
Sort of. You have "remotes" which you copy your own repo to. So in theory you could just have everyone push code to everyone elses workstations. It is probably prudent to have some central location to push code to though, especially if you want people to work on it outside of your company LAN. Best solution is probably to have a server you control and have a copy on somewhere like github and keep them in sync. That way you don't have to worry about DDOS of github and you don't have to worry about what happens if a drive dies on your server etc.