Programming

13373 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

remington

alyaza

Hexorg

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

submitted 1 year ago by Zargontapel@latte.isnot.coffee to c/programming

32 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

[–] Los 6 points 1 year ago (4 children)

Are you concerned about corruption due to multiple users? Are you using the repo in the intended way? Then it's fine. Git has locking mechanisms. Pull, work, commit, push.

[–] Zargontapel@latte.isnot.coffee 2 points 1 year ago (3 children)

I can't exactly put my finger on it, but something feels off. For example, on my first day, I wasn't able to view the files in Windows Explorer (or clone the repo, actually), so the other dev just gave me a zip file of the repo. There's something fishy going on, and I'm trying to figure it out.

[–] Los 6 points 1 year ago (2 children)

Since it's on a network share, there's the extra overhead of managing the file system permissions. And you probably hadn't received access at the point.

[–] Zargontapel@latte.isnot.coffee 4 points 1 year ago (1 children)

That probably is the case, but in my mind I'm also questioning if they're backing it up regularly, what prevents someone from going in and deleting the files, etc.

[–] Los 8 points 1 year ago

Sure, let's hope they have a backup policy in place for best practice. But also it is kinda decentralized anyway. Every dev is going to have their local repo, and that is essentially a backup.