Selfhosted

40329 readers

419 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:

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!

founded 1 year ago

MODERATORS

HybridSarcasm@lemmy.world

HybridSarcasm@lemmy.hybridsarcasm.xyz

HDD or SSD for a home server? (lemdro.id)

submitted 4 months ago by Xylight@lemdro.id to c/selfhosted@lemmy.world

32 comments fedilink hide all child comments

I'm new to this stuff so go easy on me.

So I want to get into selfhosting, and I've decided to get a Raspberry Pi 5. I plan to attach drives to it, from about 500GB-1TB. I'm on a budget, preferably under $100.

I want to host these things:

A personal lemmy instance
A samba server, to store files and backups
A mail server
A few other light docker containers

I was wondering whether I should get an SSD or an HDD for these. Lemmy would probably like an SSD because it uses Postgres, but an HDD would be better for storage since I get more GB per dollar.

What should I go with?

you are viewing a single comment's thread
view the rest of the comments

[–] scrubbles@poptalk.scrubbles.tech 77 points 4 months ago (2 children)

While I run my own Lemmy instance, I can say with 100% certainty - do not host a Lemmy instance on your own hardware.

It's tempting, and I did, but don't. The reason? CSAM. Your hosting stuff for other people, and if someone uploads something horrible to another instance, that is federated with you. That means now you are hosting that content.

The feds then have full rights to kick down your door and seize your hardware. On the cloud however, they'll seize your VM , but your home stuff is okay.

Hosting Lemmy is great - but it's something you really have to think about. Hosting your content is awesome, fun, and rewarding. I've learned hosting other people's content is.... Not as fun.

[–] Ebby@lemmy.ssba.com 15 points 4 months ago (1 children)

Didn't the Lemmy teams sort of fix that CSAM thing ages ago?

I remember a wave of lockdowns and hush hush related to that, soon followed by an update to Pictrs with a bunch of new docker compose settings.

My server got pooched in the update and it took me almost a month to fix partly because I had little free time.

[–] scrubbles@poptalk.scrubbles.tech 15 points 4 months ago (1 children)

There were some automod things built by 3rd larties, and they help, but it's still a worry. There's also image proxying now, so at least I'm not directly hosting it, but I'm not 100% that the feds will see it that way immediately

[–] Ebby@lemmy.ssba.com 5 points 4 months ago

Ah, thanks for the info!

[–] CrimeDad@lemmy.crimedad.work 15 points 4 months ago

Is this really still true about images federating in Lemmy? In any case, I think the problem can be avoided by disabling pict-rs.