Selfhosted

I had to reboot my Proxmox server after applying powertop --auto-tune. All was fine with every advised tweak but touching the Lan interfaces was not a great idea

Finally installed jellyfin when I realized I could use rclone to mount 10G of free disk space from box (with client side encryption using rclone) on my server.

Very easy to install on Debian, but the plugins are a security nightmare. Jellyfin devs are kinda dumb.

I fixed DNS

(My DNS queries were blocked by my ISP's modem, I flashed OpenWRT on an old WiFi Repeater, and set up a DoH proxy)

I am currently arguing what to do with my gaming rig and home theater. Either get a long cable which would need a DP-to-HDMI adapter or get a used mini PC (which is currently cheaper than a Raspberry Pi?) and setup Sunshine and Moonlight (but over WiFi and not LAN) to be more flexible when I eventually move the two into separate rooms. Does anyone have some experience with that? Maybe also latency over wireless network?

Debatting with myself and to a lesser degree what to do in terms of our homeserver situation. While the proxmox node has more than enough CPU and RAM capacity left, the NAS, an older Synology, is full to the brim, EOL and needs replacement.And sadly being a mini PC the proxmox node is unable to get the HDs connected.

So something new is needed and I would rather have my setup streamlined and combine the two.

But that is... More difficult than anticipated. I really would like something power saving with ECC ram that can take at least two PCI-e (SFP+ and a potential graphic card for AI later on). That can take 4,better 6 HDs. And at least one,better two NVMe. ...that basically means self building which I am happy with, but all current builds I calculate come out somewhere south of 2000€ (including two new HDs, as two old ones need to go). And that's sadly out of the financial possibility at the moment.

If only the fucking Ugreen (DXP6800)would support ECC. While not ideal in terms of PCI-e it would be enough to do the trick.

More incus:

• mounting persistent storage into containers (cheating by exporting NFS from my proxmox zfs into the incus host.
• wrote a pruning backup script for containers, runs daily, keeps last 7 days and the first of the month
• passed through hardware (quicksync) into jellyfin container (it works!)
• launched an OCI container (docker home assistant) natively in incus (this is a game-changer!)

Next:

• build 2nd incus node
• move all containers from proxmox to incus
• decom proxmox
• setup Debian with NFS export

Finally got around to trying what @[email protected] recommended me to troubleshoot my scanner sending to FTP. And I got it working! Thanks chaospatterns!

Scrubbing a little demo project I made featuring a web app behind oauth2-proxy leveraging keycloak as local idp with social login. It also uses a devcontainer config for development. The demo app uses the Litestar framework (fka starlite, in Python) because I was interested, but it's hardly the focus. Still gotta put caddy in front of it all for easy SSL. Oh, and clean up all the default secrets I've strewn about with appropriate secret management.

All of it is via rootless podman and declarative configuration.

Think I might have to create my own Litestar RBAC plugin that leverages the oauth headers provided by the proxy.

It has been a minute since I worked daily in this space, so it has been good to dust off the cobwebs.

I have a self-hosted AI system that works pretty well. I can interact with it via my phone, the shell, my IRC server, and I can verbally talk to it.

But I want to get it to remember things, so I need to start working on RAG or something. Eventually I'd like to be able to have it draft emails for me, and schedule appointments.

A new homepage for the business of my wife.

I plan to use Hugo for it, I just wish the documentation would be better.

For the homepage I need a few additional "non-blog" pages and from the documentation I am not sure how to do that the best way.

But to be honest, I have not really looked deeper into that, so it is very possible that I just missed something.

This week I finally managed to route torrent traffic through a VPS that was sitting around gathering dust. I am behind CGNAT so was taking me 6 weeks to do the kind of traffic I do in a day now. I couldn't be more chuffed.

i run coolify and I have to make my own solutions so I'm learning a lot about docker.

I tried to update my lemmy instance and it all went so horribly wrong. DB never came up, errors everywhere, searching implied I updated to a dev branch sometime in the past (not a dev, don't think I did) and it'll be console and DB queries for a fix.

Ran out of time and overwhelmed, I restored backups and buried my head in the sand. Nope, not now. Future, yes, but oh not now.

Email... My wife really wants to further de-google, this means moving custom domains off gsute.

Do I move to proton/tuta or go back to self hosting email again like I did for years until about 2010?

If I self host, do I do it at home or on the server that runs my lemmy instance?

I've been testing out immutable distros, in this case openSUSE Aeon (laptop) and openSUSE MicroOS (server).

I set up Forgejo and runners are working, all in podman. I'm about to take the plunge and convert everything on my NAS to podman, which is in preparation for installing MicroOS on it (upgrade from Leap).

I also installed MicroOS on a VPS, which was a pain because my VPS provider doesn't have images for it, and I'd have to go through support to get it added. Instead, I found a workaround, which is pretty amazing that it works:

1. Install Alpine Linux (in my case I needed to provision something else first and mount an ISO to install Alpine, which was annoying)
2. Download MicroOS image on VPS (not ISO, qcow image)
3. Write image to the disk, overwriting the current OS (qemu-img command IIRC)
4. Reboot (first boot takes longer since it's expanding the disk and whatnot)

The nice thing is that cloud-init works, so my keys set up in step 1 still work with the new OS. It's not the most convenient way to set things up, but it's about the same amount of time as asking them for an ISO.

Anyway, now it's the relatively time consuming task of moving everything from my other VPS over, but I'll do it properly this time with podman containers. I had an ulterior motive here as well, I'm moving from x86 to ARM, which reduces cost somewhat and it can also function as a test bed of sorts for ARM versions of things I'm working on.

So far I'm liking it, especially since it forces me to use containers for everything. We'll see in a month or two how I like maintaining it. It's supposed to be super low effort, since updates are installed in the background and applied on reboot.

I've just moved and I'm setting up my machines. NIC died in my DIY router just before the move so I'm upgrading to 2.5/10 Gbps at the same time.