What about backups? Managing access to the repository? Making the repository eas...

acomjean · on Jan 6, 2023

Our nonprofit host provider has a git repo option on their control panel.

They use this for access:

(somewhat ironicaly code hosted on github. Not sure its still being updated..)

we currently don't use it, just because its on the same network as our site.. though because its git and it replicates the repo everywhere its less of an issue.

GrumpySloth · on Jan 7, 2023

> But why would the average developer want to?

As for myself, I don’t like GitHub UI, which is slow, has low information density, and is generally lollipop-like; and its social media aspect, which often turns the bug tracker into a Twitter equivalent with viral bugs, emojis to cheer and boo people.

So I set up a cgit instance for myself. Patches can be sent over mail as attachments generated with git format-patch (attaching files to mails isn’t hard). Issues can similarly be sent over mail and described in a BUGS file.

That’s sufficient for my single person projects. Probably also for n-person projects for small values of n (let’s say 7). Past that I’d set up a Gerrit instance, which IMO has the best UX of all code review tools available, free or not; and a Redmine for ticket tracking.

jrm4 · on Jan 6, 2023

Honestly -- if this is too much for the average developer then we have WAY too many underskilled, and perhaps useless, developers.

shepherdjerred · on Jan 7, 2023

I would consider myself pretty knowledgeable and I love going on tangents when setting up projects. I love tinkering and learning.

There is no situation in which I'd want to do all of the above work for every single repository I setup.

I have hundreds of repositories that I own on GitHub for things like school assignments and personal projects. If I start a weekend project as you describe then the first 4 hours are going to be setting my repository up.

Nobody wants to do this. Just because something is difficult or time consuming doesn't mean that it is good or useful. Doing this once would be a fun learning experience. Doing it more than once is a useless chore.

Dylan16807 · on Jan 7, 2023

> There is no situation in which I'd want to do all of the above work for every single repository I setup.

What the heck are you talking about?

The only work you'd have to do "for every single repository" is the single git command.

Getting a server, managing access and discoverability, setting it up for browser access, setting up backups, those are things you would do once.

If that's a waste of four hours, valid argument, but it's not a waste of four hundred hours. You're grossly exaggerating the cost.

Oh and you didn't mention keeping the server updated but that's probably ten minutes of effort once a month.

> Doing this once would be a fun learning experience. Doing it more than once is a useless chore.

Then there's no problem.