1.9 KiB
| title | date | emoji | publishDate | bookmarkOf | references | summary | tags | ||||||||||||||
|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|
| Self-hosting advice | 2024-03-28T16:17:01Z | 💼 | 2023-08-09T16:00:00Z | https://ergaster.org/posts/2023/08/09-i-dont-want-to-host-services-but-i-do/ |
|
A concise and smart article talking to those of us interested in offering hobby networked services to others. |
|
A concise and smart article talking to those of us interested in offering hobby networked services to others.
I’m still in the mindset that a form of fully decentralised systems could overcome many of the issues mentioned here. My current bet would be on client-side web applications (or just websites) served from content addressed stores (like §IPFS), storing data primarily on local machines (think fission.codes and the §LocalFirst movement), is going to be a fruitful route.
I’ll be looking forward to the next article on the challenges with end-to-end encryption (E2EE)!
Highlights
Good backups are:
- done regularly
- documented
- tested regularly
- stored at a different location than the computer powering your services, also called off-site backups
- not accessible from a compromised machine in your network
My recommendation to most people putting services online would be: either do it for yourself only, or do it as a team with proper structure and processes.
we need to figure out how to do decentralise services and data storage for individuals at scale