Kushan

It’s self hosting by the literal definition that you host the server yourself.

That it’s closed source and sends all kinds of data to another server is an entirely separate (and valid) concern.

As much as I agree with the concerns around Plex, I would rather we didn’t start gatekeeping the self hosting community with arbitrary requirements and grey lines around what is and isn’t “true self hosting” or whatever. I would far rather we inform people and let them make their own choices about what they want to host on their private devices and networks.

If that’s the case, then it should be trivial to prove and the EFF can force them to open source it.

Let’s not make baseless accusations, let’s get proof and hold them to it.

That’s not strictly accurate.

The slicer is Open Source yes, but not the printer firmware or software. That’s closed source and proprietary to Bambu.

Now there’s some contention there because a lot of the features and ideas that make modern 3D printing as reliable and great were developed in the open, under open source licenses and Bambu has definitely implemented many of them in their printer firmware, but they don’t infringe any licenses in the printer software itself (as far as anyone is aware).

This whole debacle centres around the slicing software, which is separate from the printer itself (though is necessary to actually use the printer) and it’s AGPL.

You’ve done the hard work building the compose file. Push that file to a private GitHub repository, set up renovate bot and it’ll create PR’s to update those containers on whatever cadence and rules you want (such as auto updating bug fixes from certain registries).

Then you just need to set up SSH access to your VM running the containers and a simple GitHub action to push the updated compose file and run docker compose up. That’s what I do and it means updates are just a case of merging in a PR when it suits me.

Also I would suggest ditching the VM and just running the docker commands directly on the TrueNAS host - far less overheads, one less OS to maintain and makes shares resources (like a GPU) easier to manage.

You should look at restic or Kopia for backups, they are super efficient and encrypted. All my docker data is backed up hourly and thanks to the way out handles snapshots, I have backups going back literally years that don’t actually take up much space.

Fuck, I love ntfy, it’s one of the best self hosted push notification systems I’ve used. It has been flawless so far.

Don’t like this.

It was a couple of weeks ago for me but I managed to get my docker compose script for all my infrastructure cleaned up and all versions of containers are now pinned.

I have renovate set up to open PR’s when a new version is available so I can handle updates by just accepting the PR and it’s automatically deployed to my server.

Nice and easy to keep apps up to date without them randomly breaking because I didn’t know if a breaking change when blindly pulling from latest.

Absolutely! Here’s my CI pipeline, it’s actually super basic: https://gist.github.com/neoKushan/bd92031bb9c8db3320e8c19d5dae3194

Happy to answer questions if you like.

I just added my compose files to the repo, that CI file and set up renovate https://github.com/renovatebot/renovate to create my PR’s for me.

I generally agree with the sentiment but don’t pull by latest, or at the very least don’t expect every new version to work without issue.

Most projects are very well behaved as you say but they still need to upgrade major versions now and again that contains breaking charges.

I spebt an afternoon putting my compose files into git, setting up a simple CI pipeline and use renovate to automatically create PR’s when things update. Now all my services are pinned to specific versions and when there’s an update, I get a PR to make the change along with a nice change log telling me what’s actually changed.

It’s a little more effort but things don’t suddenly break any more. Highly recommend this approach.

In your compose file, make sure you’ve added runtime: nvidia.

You also don’t need to deploy the resources and reserve the GPU, you can remove the entire deploy section when using the nvidia runtime.

I just changed my compose reference to update the volume and base image. Worked a treat.

Jellyfin is a fork of emby (from when it went closed source), so that makes sense. They have diverged quite a bit but seems the Auth hasn’t changed enough.

I’m running a TrueNAS build which has just grown in time. Started off at 5x8TB drives, then added 5x16TB drives and just last week added another 5x26TB drives (that was costly ☠️). It’s all running in a very cheap case using an old threadripper machine I had (2950x), which thankfully supports ECC (128GB purchased years ago before the sillyness).

It’s about the storage I have in my server right now - using 15 drives ☠️

Start off simple, use something like uptime-kuma just to check your services are available - takes minutes to set up and can send you notifications when something goes down. It can plug into docker directly to check if a container is up, as well as perform HTTP checks that the service is responding, plus some other cool stuff.

(Side note, I set up ntfy to handle notifications and it’s great! Another solid recommendation but you can use discord web hooks or whatever as well)

The other options described here are good for gathering and visualising data, but it takes quite a bit to set them up and even more to configure the right kinds of alerts to notify you when something is wrong. A simple “is this docker container running” check or a “does this respond with a http 200” check gets you like 95% the way there.

It’s entirely hypothetical. Jellyfin could also close source tomorrow, hypothetically (It happened with Emby so there’s precedent).

This is a "slippery slope’ argument and thus a fallacy.

Let users decide how they want to run their own stuff. Right now if you have Plex pass this isn’t an issue. If it becomes an issue, then you’re in the exact same position you’d be in today if you decided to move away from Plex now.

I moved away from Plex years ago, but I don’t blame users for sticking with it, it still has a lot of advantages over jellyfin.

EDIT: Y’all are trippin’ over yourselves to complain about what other people choose to deploy on their own hardware.

You know exactly what I’m referring to

Yeah this sucks but honestly it never really worked well for me, ebooks are horribly underserved in the media world.

Op please don’t ignore the above.

Learn docker once and you’ll be able to install almost anything, rather than having to learn every individual app and how it installs on specific operating systems.

Yeah I think your problem was trying to use ~ in a path. That’s a bash thing, not a linux thing - slightly pedantic distinction for many but worth knowing about in case future applications give you a similar problem.