Selfhosted

39987 readers

963 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

First steps to self hosting (aussie.zone)

submitted 1 year ago by tuff_wizard@aussie.zone to c/selfhosted@lemmy.world

16 comments fedilink hide all child comments

Hey all

Been playing around with plex and the *arr's for a while on my main desktop.

Now looking to set up a server to run plex, downloads, pi hole and eventually some other backup's.

Unfortunately the PC I had laying around is 32bit and it seems like most things are removing support for that architecture if they haven't already. Now I'm faced with the problem/opportunity of getting something new (to me).

But I'm struggling with the absolute sea of options out there and also don't want to spend on brand new gear.

There's quite a bit of server grade hardware floating around (like a Dell Poweredge server T410, 32GB ram, Intel Xeon E5645 2.13GHz Quad-core for $100AUD) or even rackmount gear (probably overkill but a boy can dream).

Or should I just get a consumer case with the most drive bays I can find and build from there?

Lowish power consumption is a priority, planning on running ubuntu or similar.

Any and all tips welcome! Thanks.

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

[–] thisNotMyName@lemmy.world 5 points 1 year ago (1 children)

You'll have to keep in mind, that the pi is not really suitable for RAID and not at all for transcoding. The latter means if you have all your media in codecs your devices support, it's direct play only, it will work, but as soon as you need to transcode, you will have a hard time

[–] canitendtherabbits@lemmy.world 1 points 1 year ago (1 children)

Thanks for the information. Being completely honest, I had to look up what transcoding even was. But hey, that's the point of this current project I'm working. To learn all this stuff! I have a pi4 and really only plan to use that to run the server. Then i was going to use my PC (Linux) and macbook for coding project, etc. and building the front end(s). Does any of that make sense?

[–] thisNotMyName@lemmy.world 1 points 1 year ago

Don't worry, most of this is about learning :) You could also put Docker on the Linux, install Jellyfin as a Docker container, and only fore it up when you are using Jellyfin. It's a little less convenient, than having it available all the time, but storing all media in H264 AC3 (most common video and audio codecs) costs a lot of storage (H265 and AV1 are far more efficient). Another pro of Docker is, when you decide to move your server, you just shut down the container, copy it's data and start the container on the new device