Programming

13383 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 2 years 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

[–] preciouspupp@sopuli.xyz 6 points 1 year ago (2 children)

I don’t see how would this be compliant with literally anything.

[–] ricecake 1 points 1 year ago

It's actually fine, as long as you coordinate with them.
They offer services that cater to just about any compliance need, including things as annoying as fedramp.

[–] TheTrueLinuxDev 1 points 1 year ago

I would have to agree on this, it seems rather odd if the code repo is confidential or classified to be shared on a Windows Share. The reason why we would use Git services (self-hosted) is so that we have multitude of security services/layers maintained by dedicated team of system administrators such as firewall, service update, data redundancy, backup, active directory and so forth.

I can see a scenario where people accidentally put classified repos or information that aren't supposed to be shared on Windows Share where unauthorized users could view that repos.