Programming

13368 readers

1 users here now

All things programming and coding related. Subcommunity of Technology.

This community's icon was made by Aaron Schneider, under the CC-BY-NC-SA 4.0 license.

founded 1 year ago

MODERATORS

[email protected]

Is hosting a git repository on a Windows network share a terrible idea? (latte.isnot.coffee)

submitted 1 year ago by [email protected] to c/[email protected]

25 comments fedilink hide all child comments

I just joined a new team (very small: four developers in total, with two of those leaving soon). The two original developers set up the git repo on a folder in a Windows network share.

Am I taking crazy pills, or is that a bad idea? Our organization does have github/gitlab/bitbucket available, so is there any good reason not to use those hosted solutions?

you are viewing a single comment's thread
view the rest of the comments

[–] [email protected] 3 points 1 year ago* (last edited 1 year ago)

The big difference there seems to be cloud, ie someone else's computer, and company internal network. That is a big and fundamental choice: Will you allow (leak) your data outside of your control.

Doing anything with Windows shares is a bad idea technically, of course. But with git, every workspace is generally a full copy of the repository. All you need a shared one for is syncing work. And backups are always a sensible thing to have no matter how you arrange files. With that, it seems to be a low risk thing to me.

A bundle might or might not be safer than a repo, but either will probably work.

Reading some of the comment responses, it does sound like there's an air of ineptitude or a long history of systems not working and devs not allowed to make them work, so they just try workarounds for everything.