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.
-
No low-effort posts. This is subjective and will largely be determined by the community member reports.
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 actually wrote a blog about this a few months back. It was after a 12 day war (Israel+USA attacking Iran) and 40 day internet blackout, and then we got into another war (Israel+USA attacking Iran) and a 90-100 day(lost track) internet blackout.
It isn't exactly "how to survive the apocalypse" guide but it was a really helpful guide for myself and my friends and helped me keep working in those blackout days.
It's isn't focused on hardware, just software, since I'm a software engineer.
https://alavi.me/blog/we-need-apocalypse-proof-software/
@somegeek @jobbies This is a good read. I was rather amused by your "TODO: How to use Git offline? Offline merge requests?" section, though. Git was written by people who literally email each other patches. It's offline-first, with online stuff tacked on there. You can copy a cloned git repo to a usb stick and give it to someone, and now they have the entire history. Of course merge requests and bug tracking are separate (I understand what you meant w/ the TODO), but git itself is already there.
Thank you! I actually got that figured at during the second war but didn't got the time to update the post. I put what I learnt in my knowledge base linked below. I will uodate the post. Thank you for pointing that out!
I tried to push it at work but most of my team members didn't felt like learning this whole new workflow (they're "normies" you could say. Using windows, outlook, etc.)
http://kb.alavi.me/#/page/git%20email%20workflow
Grate share, thank you!