Kushan

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.

The main argument against bsky is that they’re still holding all of your data, unless you self host your own server.

I don’t actually see how Lemmy is much different. Most users are not self hosting on Lemmy either, you’re trusting your data to a 3rd party. The main difference seems to be that there’s much more centralisation on bsky.

I think it’s entirely reasonable to be wary of any service, be ready to delete your account if it goes to shit or whatever it is you need to do to feel safe.

But right now, I like blue sky. I’ve had far more positive interactions on there than I ever had on twitter (even before musk took it over), the lists feature that lets you pre-emptively block entire swathes of dickheads is a game changer (I just block one group, anyone Maga) and I’m having a good time.

I expect I’ll get downvoted for this but honestly I don’t care, the world has gone to shit far too much for me to give a crap about what internet strangers think over my own health and wellbeing and right now I’m having a good time and will not apologise for it.

The second that stops, I’ll be leaving bsky.

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.

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.

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.

Don’t set it to your home path, set the path explicitly. That’ll be what it’s complaining about, the ~.

It shouldn’t really matter where you’ve got your files as long as they’re mounted on a standard path. Maybe try creating a symlink from where your media is to a standard path like /mnt/media or something?

Hmm sorry not sure why it would be complaining about an invalid path. Is it all paths that are invalid, or just the ones to your media?

I don’t think you should be getting downvotes for having an opinion and I appreciate your reply.

However I do love a good debate - what’s the advantages for you for installing apps on “bare metal” (I’m assuming you mean a base OS install rather than actual bare metal). What about virtualisation?

I’m also on emby and it works well for me. My main grievance is setting up a new device is a chore, “emby connect” is far too clunky to use so I end up configuring via URL every time - and on some devices that’s a real chore.