Programming

13391 readers

2 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

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

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

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

Do you mean a bare repo you use as a remote and push/pull from or using the workdir straight from the share. The first would be strange, but kinda usable (don’t do this though), the latter is oh my god, get an other job category.

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

Yes, it's definitely the former case, thankfully. Agreed that it's strange, but it's hard to put a technical reason behind it if I decide to push for hosting it somewhere better.

[–] Los@beehaw.org 2 points 1 year ago

Why not just host a server in house?

[–] alsciaucat@lemmy.cafe 4 points 1 year ago

Working from the network share - I've worked on a project like this before, it was awful for developer experience. It took seconds to run a git status, it was so slow. Occasionally git would lock itself out of being able to update files, since the network read/write times were so slow. Large merges were impossible.

The reason it was set up like this was that the CEO had the network share we were working off of set up to serve to a subdomain (so like, Bob's work would be at bob.example.com), and it would update live as most hot-reloads will do. He wanted to be able to spy on developers and see what they were doing at any given time.

I have a lot of programming horror stories from that job. The title of this thread brought up a lot of repressed memories.