Jellyfin hosted on my primary PC with access to my GPU (NVIDIA GeForce RTX 4060) for transcoding. The Jellyfin libraries instance SMB shares on my NAS. Stream everything with Jellyfin for Chromecast right from the TV.

Works amazingly well. Great transcoding times. No lag despite only having 10/100/1000 NIC on NAS and streaming WiFi with Chromecast.

I manage the media library with TMM (tinymediamanager).

Super happy with it, particularly considering the only thing it cost me was the NAS (because I game on my PC anyways) which I was also going to get, anyways.

I’m coming to appreciate Hyper-V more and more to be honest. It’s a very mature virtualization environment. The only issue I have with it is the inability to do GPU-passthrough. Once they figure that one out, I probably won’t bother with anything else.

Because developers use cross-compilable languages to pump out Windows executables without knowing or understanding or caring about the Windows environment. I mean, ~/.whatever still works under Windows.

I guess it depends on what you mean by “edited content.”

Docker is so bad. I don’t think a lot of you young bloods understand that. The system is so incredibly fragmented. Tools like Portainer are great, but they’re a super pain in the ass to use with tools/software that include a dockerfile vs a compose file. There’s no interoperability between the two which makes it insurmountably time-consuming and stupid to deal with certain projects because they’re made for a specific build environment which is just antithetical to good computing.

Like right now, I have Portainer up. I want to test out Coolify. I check out templates? Damn, not there. Now I gotta add my own template manually. Ok, cool. Half way done. Oops. It expects a docker-compose.yml. The Coolify repository only has a Dockerfile. Damn, now I have to make a custom template. Oh well, not a big deal. Plop in the Dockerfile from the repository, and click “deploy.” OOPS! ERROR: “failed to deploy a stack: service “soketi” has neither an image nor a build context specified: invalid compose project.” Well fuck… Ok, whatever. Not the biggest of deals. Let me search for an image of “soketi” using dockerhub. Well fuck. There are 3 images which haven’t been updated in several years. Awesome. Which one do I need? The echo-server? The network-watcher? PWS?

Like, do you see the issue here? There’s nothing about docker that’s straightforward at all. It fails in so many aspects it’s insane that its so popular.

This is why rack mounts were made. Hell, I’ve seen a lot of custom builds where people have mapped out the server on their wall and it takes up no floor space. Something like this: https://i.xno.dev/kG9Wx.jpg

I know you can’t see my face but I just threw up in my mouth a little bit.

His tech bubble is clearly going to keep growing so why not invest now versus buying a full size case and all these extra hard drives and then realizing in a year or two that you really wanted a rack amount to begin with so you can expand even more?

Check out MinIO. It’s S3 compatible, so generally any tool which works with S3 will work with your instance. You can pair it with other FOSS applications like rclone. It’s a great combo.

Probably just easier to nix the Prime subscription and just download scene releases… Most of them are h265 these days and are released same day as on Prime.

I just checked a list of “new to prime” and my tracker and they were all there. No reason to give money to Amazon.

Update came through this morning. 7.2.2-72806 Update 3.

The one thing I’ll never recommend anyone selfhost is email. It’s just plain not worth it.

You can do literally everything right and still get cucked by spam filters because you’re not a recognized email provider.

If you’re dealing with this much storage, it’s time to upgrade to a rack. Don’t deal with having to shove 10 drives into a packed full-size.

Start scouring 2nd hand auction sites and buy one used. They’re pretty cheap as far as solutions go if you can grab them used. Something like this would be ideal: https://www.silverstonetek.com/en/product/info/server-nas/RM22-312/

https://forums.lawrencesystems.com/t/freenas-truenas-zfs-pools-raidz-raidz2-raidz3-capacity-integrity-and-performance/3569

It’s pretty great. The only thing you have to remember is that the caddy instance and the container you’re proxifying have to be within the same docker network. So you’ll definitely want to use the caddy2 container if this is the setup you want to pursue.

If not then you can just use IP addresses inside or outside of a container it doesn’t matter.

Then I found out my services would work better with Caddy

Exceptional idea. Cloudflare is nice, but Caddy will always win IMO. Additionally, considering you were able to get Caddy working, that simply drives home that unfortunately your reverse_proxy didn’t work because it was somehow misconfigured. Caddy is also a reverse_proxy.

My comment is pretty much what I said. You have an extremely complex environment that you’re not fully making use of. For example, you’re having issues with a reverse_proxy, but you had Tailscale presumably the whole time. Why not just use your VPN to reverse_proxy your requests if you were having issues?

Also using Caddy + Cloudflare is fine if you want to use cloudflare for DNS, however, Caddy handles all certificates itself. So you have Caddy, which can handle all the SSL certs itself, but you put Cloudflare on top of it to manage SSL certs. It’s just convoluted.

It’s a good environment, but a little overkill.

As someone who’s set up and managed critical business applications I would say that it’s perfectly fine to host your own provided you have decent hardware that’s capable of doing what you need and as a dedicated business line to provide connection.

If you try to run mission critical business applications on a home internet connection you’re going to have a really bad fucking time. But hosting business critical applications on appropriate hardware and a 1Gb/s business connection with an SLA is going to meet 95-98%% of all business applications.

If something like that sounds expensive or too difficult to do then it’s too expensive or too difficult for you to host yourself. Just go with a provider and sidestep self-host.

Debian, baby.

Chest freezers are exceptionally energy efficient. It’s not a very good comparison.

I really love home labs but this sounds incredibly over engineered for its purpose… I would expect a set up like this for an enterprise environment…

I very highly recommend that you take the time and just switch. Caddy is simply fabulous. It’s designed to work (assuming it’s compiled with the module) with containers and use docker networks for routing. It makes it easy to spin up containers and directly reference the container names instead of remembering IP addresses and particularly comes in handy when your entire environment is containerized.

You can pull the caddy image and run it in docker and as long as your environment is configured correctly you can simply reverse_proxy @container and you’re done. Caddy pulls all the relevant port information directly from the container API.

I get such a nerd boner thinking about it.