Selfhosted
A place to share alternatives to popular online services that can be self-hosted without giving up privacy or locking you into a service you don't control.
Rules:
-
Be civil: we're here to support and learn from one another. Insults won't be tolerated. Flame wars are frowned upon.
-
No spam posting.
-
Posts have to be centered around self-hosting. There are other communities for discussing hardware or home computing. If it's not obvious why your post topic revolves around selfhosting, please include details to make it clear.
-
Don't duplicate the full text of your blog or github here. Just post the link for folks to click.
-
Submission headline should match the article title (don’t cherry-pick information from the title to fit your agenda).
-
No trolling.
Resources:
- selfh.st Newsletter and index of selfhosted software and apps
- awesome-selfhosted software
- awesome-sysadmin resources
- Self-Hosted Podcast from Jupiter Broadcasting
Any issues on the community? Report it using the report flag.
Questions? DM the mods!
view the rest of the comments
I'm going to be honest, I have no idea how open source works. I can't imagine maintaining anything more than a tiny library that I can ignore six days of the week.
Also: open source relies on good jobs. You can only do it if you have a well paid low stress job with good hours. Those have been in short supply recently.
I think the free time covid gave, followed by the free time the layoffs gave, and AI have been patching / hiding the fact that the core model of open source is completely unsustainable in its current state.
I have a job like that, but I also have kids, so...
The part that confuses me is: How can multiple people work on overlapping bits of code at the same time, and the Git manager (or whatever you call it) just handles it all without breaking everything?
Roughly equal parts "git is clever" and "once in a while, someone has to take some time to figure it out".
Say the code is split into two files. You and I both make changes, but you're working on file A and I'm in file B. No problem!
Now we both make changes in file A. Sometimes Git can just "figure it out", like if all your changes are in the beginning of the file, and all my changes are at the end.
But sometimes we both change the same section. Git can't figure that part out, so one of us has to sit down and reconcile the changes. Sometimes this is pretty simple, other times...not so much.
Put it all together, and it works out pretty well most of the time.
Okay, so the answer basically is that you can't have multiple people working on overlapping bits of code, not without someone sorting it out first.
Being able to have two different people work on different parts of the same file without causing any issues makes sense, but I also thought there was some magic formula that fixes everything if two people try to upload the file with the same part of the code modified in two different ways at the same time.
Git is not as magical as I thought it was now that you've explained it.
Yeah, it's fairly clever but not actually magical. Sometimes you have to go in and take a look.
Actually, the real magic is that it works out mostly ok most of the time. Much better than older systems where you would have to "check out" a file to work on it which would lock others out. I've heard older programmers talk about needing to go find someone who had a file checked out and have them check it back in to enable them to do some work.