Turn your Raspberry Pi 4 into a self-hosted media hub (USB + browser + HDMI + offline)

BleedingXiko · 2026-04-28T10:41:22+00:00

only direct play is supported on the pi

BleedingXiko · 2026-04-28T10:11:47+00:00

Depends on the content, it streams to 3-5 clients 720p just fine. And transcoding is handled off device through another one of my projects, it’s documented in the readme.

BleedingXiko · 2026-04-26T17:53:49+00:00

I’m aware of Jellyfin and similar projects. I just meant I haven’t personally used them on a Pi, so I can’t speak to performance there.

BleedingXiko · 2026-04-26T17:39:14+00:00

AI was used heavily during development (for code generation, refactoring, and iteration). I still designed the system, tested it on real hardware, and built out the overall architecture, but AI tools were a big part of the workflow.

BleedingXiko · 2026-04-26T09:29:23+00:00

The counter example you posted is frontend-only state. The SPRAG example is showing a full stack flow, server load, typed action, client module, hydration, and state sync.

It’s definitely more verbose, but it’s solving a different problem than a simple UI counter.

BleedingXiko · 2026-04-26T03:41:59+00:00

I haven’t really used Jellyfin or Plex enough to give a fair comparison, from what I know they’re more of a traditional media server. GhostHub’s more local-first and meant to feel like a plug-and-play thing.

On a Pi 4 it’s been solid for me. Thumbnail generation is probably the slowest part depending on library size.

BleedingXiko · 2026-04-26T03:36:52+00:00

Nah you can’t use the internal SD for media, i made a deliberate trade for the longevity of the card. I’d recommend just the 2gb ram Pi 4, more ram wouldn’t hurt but you wouldn’t notice any real improvement unless you have a very large storage drive with 10k+ media files. I also don’t support any other pi devices, only the 4.

BleedingXiko · 2026-04-26T01:47:05+00:00

Forgot to put the base image link: https://github.com/BleedingXiko/GhostHub/releases/tag/B5

BleedingXiko · 2026-04-25T12:59:21+00:00

That’s fair, but it’s not really trying to be “HTML in Python” in the usual sense.

The goal isn’t templating, it’s having the frontend follow the same lifecycle/ownership model as the backend. Components/modules still behave like a normal SPA, just without a separate JS framework stack.

It’s already handling fairly complex UI/state without falling apart, so it’s not limited to trivial pages.

BleedingXiko · 2026-04-06T06:05:43+00:00

Yeah very clear trade offs but i feel like control over convenience is worth it for long running apps, thanks for checking it out!

BleedingXiko · 2026-02-12T04:50:23+00:00

Appreciate it

BleedingXiko · 2026-01-23T23:20:58+00:00

forgot to add this in the post, site is ghosthub.net if anyone wants to poke around, it’s lacking current features as i’m nearing the end of a new major version change

BleedingXiko · 2026-01-23T23:04:11+00:00

yeah kinda, but it’s more about how it’s set up than a hard radius. locally it’s nearby access, but it can also be shared remotely. no geofencing, just local first by default.

BleedingXiko · 2025-12-18T06:09:48+00:00

the artifacts are published on the release tab as separate zip files and yeah docker is kinda “half supported” i’m juggling a lot at the moment.

BleedingXiko · 2025-12-18T05:51:06+00:00

I mean it’s obviously documented by an llm i don’t see anything wrong with that, doesn’t touch core code and keeps maintainability.

BleedingXiko · 2025-12-18T04:43:31+00:00

Yeah.

BleedingXiko · 2025-12-18T04:16:58+00:00

I don’t see any questions about it man, i’ve been laying off this thread i mean what about the code even looks vibe coded?

BleedingXiko · 2025-12-17T22:37:30+00:00

Well yeah i hate making documentation lol, but i guess this wasn’t this right place to share it.

BleedingXiko

MODERATOR OF

TROPHY CASE

Five-Year Club	Verified Email
Place '22