Programming

13376 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

alyaza@beehaw.org

Hexorg@beehaw.org

remington@beehaw.org

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@beehaw.org

26 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

[–] ActuallyRuben@actuallyruben.nl 4 points 1 year ago (1 children)

Do they have an agreement with GitHub/gitlab/bitbucket? Using their consumer targeted services as a business is just asking for trouble.

Storing a headless repository on a shared filesystem is a perfectly valid solution, and something git was designed to do, if you don't mind the lack of online interface. Although I'd personally prefer using an ssh connection.

[–] Zargontapel@latte.isnot.coffee 1 points 1 year ago

This is actually a very large government agency, with many internal as well as external projects hosted on those services, in the public instances as well as our own internal hosted instances of those services. But as long as there's no glaring issues with it, and it's a generally acceptable practice, then I'm fine with it as it doesn't really affect my day to day use via command line.