this post was submitted on 07 Dec 2023
82 points (97.7% liked)

Selfhosted

39964 readers
339 users here now

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:

  1. Be civil: we're here to support and learn from one another. Insults won't be tolerated. Flame wars are frowned upon.

  2. No spam posting.

  3. 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.

  4. Don't duplicate the full text of your blog or github here. Just post the link for folks to click.

  5. Submission headline should match the article title (don’t cherry-pick information from the title to fit your agenda).

  6. No trolling.

Resources:

Any issues on the community? Report it using the report flag.

Questions? DM the mods!

founded 1 year ago
MODERATORS
 

Hey guys, I'm new to self-hosting; I'm trying to set up cloud storage to store pics and other content. However, I’m unsure whether to use my old computer, Buy NAS or ResberryPie to set up a home server.

Also, what is the best privacy-friendly OS to use with the home server?

Lastly, do’s and don’ts.

Any help would be appreciated (:

you are viewing a single comment's thread
view the rest of the comments
[–] juli@programming.dev 31 points 11 months ago (1 children)

Use docker compose . Like "everyone" uses it. If the service doesn't have a compose file, request it, or write it yourself as son as you are knowledgable enough.

Use podman as soon as people and services switch to it (you'll know when the latest tutorials talk about podman instead of docker).

Use ngingx proxy manager or another easy to use reverse proxy.

Don't think it's production ready after it was working 2 days. It may be, but it's unlikely you have enough knowledge how to fix things.

Automatic updates.

Don't install crap on the system.

[–] scrubbles@poptalk.scrubbles.tech 8 points 11 months ago

This is a good way to get started.

Docker and Docker compose on whatever hardware you want to start on.

Don’t think it’s production ready after it was working 2 days. It may be, but it’s unlikely you have enough knowledge how to fix things.

Most important there. You aren't building a production system for corporate clients, you're doing this for fun. Focus on one thing, try to get that one thing running. Toy with it, make it work. Then start on your next thing. Slowly you'll build up a large system, but it won't be immediate.

I personally have been working on switching from compose to kubernetes, which is way more advanced than a starter needs - but I've been slowly migrating for about 4 weeks now, one service at a time. Just how homelabs are done