Themata.AI
Themata.AI

Popular tags:

#developer-tools#ai-agents#discussion#trending#llms#ai-ethics#claude#code-generation#ai-safety#openai

AI is changing the world. Don't stay behind. Clear summaries, community insight, delivered without the noise. Subscribe to never miss a beat.

© 2026 Themata.AI • All Rights Reserved

Archive

|

Topics

|

Privacy

|

Cookies

|

Contact
🕒 Latest🔥 Top

Filtering by tag:

streaming-servicesClear
What I Self-Host
self-hostingdeveloper-toolsstreaming-servicesopen-source-software
Opinion

What I Self-Host

A self-hosted home server built around a Beelink S12 Pro mini PC runs 28 services on an Intel N100 processor, 16 GB of RAM, a 512 GB SSD and a 6 TB media drive. The machine, bought for €180 last year, uses about 7.5 GB of memory and 30% to 40% CPU according to htop. It does not run local AI inference. Services are accessible only on the local network or through VPN; VPN endpoints run on the router and are publicly routable only over IPv6. Jellyfin replaced commercial streaming subscriptions and supplies locally controlled movies, television and home videos without autoplay or recommendation feeds. The setup also includes Immich for photo storage, Home Assistant for automation, Frigate with eight IP cameras, Vaultwarden for passwords, Actual Budget, Forgejo, FreshRSS, Audiobookshelf, Syncthing, Samba and Uptime Kuma. Frigate uses lower-resolution camera streams to limit Wi-Fi, processing and storage demands, while Jellyfin generally uses 720p media to reduce resource use. Seventeen services run natively and 11 run in Podman containers, all managed through systemd. Native deployments are preferred when dependencies are limited, while Podman is used for more complex applications. The server avoids Docker, the *arr media-management stack, self-hosted email, Collabora Online and several database-heavy alternatives because of operational complexity or resource demands.

viceconsole.fyi

🔥🔥🔥🔥🔥

16 min

1d ago

What I Self-Host

A self-hosted home server built around a Beelink S12 Pro mini PC runs 28 services on an Intel N100 processor, 16 GB of RAM, a 512 GB SSD and a 6 TB media drive. The machine, bought for €180 last year, uses about 7.5 GB of memory and 30% to 40% CPU according to htop. It does not run local AI inference. Services are accessible only on the local network or through VPN; VPN endpoints run on the router and are publicly routable only over IPv6. Jellyfin replaced commercial streaming subscriptions and supplies locally controlled movies, television and home videos without autoplay or recommendation feeds. The setup also includes Immich for photo storage, Home Assistant for automation, Frigate with eight IP cameras, Vaultwarden for passwords, Actual Budget, Forgejo, FreshRSS, Audiobookshelf, Syncthing, Samba and Uptime Kuma. Frigate uses lower-resolution camera streams to limit Wi-Fi, processing and storage demands, while Jellyfin generally uses 720p media to reduce resource use. Seventeen services run natively and 11 run in Podman containers, all managed through systemd. Native deployments are preferred when dependencies are limited, while Podman is used for more complex applications. The server avoids Docker, the *arr media-management stack, self-hosted email, Collabora Online and several database-heavy alternatives because of operational complexity or resource demands.

viceconsole.fyi

🔥🔥🔥🔥🔥

16 min

1d ago

What I Self-Host

A self-hosted home server built around a Beelink S12 Pro mini PC runs 28 services on an Intel N100 processor, 16 GB of RAM, a 512 GB SSD and a 6 TB media drive. The machine, bought for €180 last year, uses about 7.5 GB of memory and 30% to 40% CPU according to htop. It does not run local AI inference. Services are accessible only on the local network or through VPN; VPN endpoints run on the router and are publicly routable only over IPv6. Jellyfin replaced commercial streaming subscriptions and supplies locally controlled movies, television and home videos without autoplay or recommendation feeds. The setup also includes Immich for photo storage, Home Assistant for automation, Frigate with eight IP cameras, Vaultwarden for passwords, Actual Budget, Forgejo, FreshRSS, Audiobookshelf, Syncthing, Samba and Uptime Kuma. Frigate uses lower-resolution camera streams to limit Wi-Fi, processing and storage demands, while Jellyfin generally uses 720p media to reduce resource use. Seventeen services run natively and 11 run in Podman containers, all managed through systemd. Native deployments are preferred when dependencies are limited, while Podman is used for more complex applications. The server avoids Docker, the *arr media-management stack, self-hosted email, Collabora Online and several database-heavy alternatives because of operational complexity or resource demands.

viceconsole.fyi

🔥🔥🔥🔥🔥

16 min

1d ago

No more articles to load