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
Documentation has been mentioned already, what I'd add to that is planning.
Start with a list of high-level objectives, as in "Need a way to save notes, ideas, documents, between multiple systems, including mobile devices".
Then break that down to high-level requirements such as "Implement Joplin, and a sync solution".
Those high-level requirements then spawn system requirements, such as Joplin needs X disk space, user accounts, etc.
Each of those branches out to technical requirements, which are single-line, single-task descriptions (you can skip this, it's a nice-to-have):
"Create folder Joplin on server A"
"Set folder permissions XYZ on Joplin folder"
Think of it all as a tree, starting from your objectives. If you document it like this first, you won't go doing something as you build that you won't remember why you're doing it, or make decisions on the fly that conflict with other objectives.
This is really smart actually