Maybe poor image compression?

And it is 6 now, I should def be asleep

I have and I can whole heartedly say that using Windows 11 on the Deck is an awful experience no one should be attempting as a daily runner.

Where is this meme from?

Hjerteknuser by Kaizers Orchestra but it’s a lil’ cheat since I understand a little Norwegian.

Hoppípolla by Sigur Rós this one sounds so so beautiful.

Jumalan terve by Markus Krunegård when he expanded to Finnish music I was a bit surprised to learn he speaks Finnish natively. So when he then released this album I was very excited. It’s Swedish styled pop but in Finnish.

How about now?

I’ll come to your material science course

I doooo and I still love it! I haven’t had the time to update to the latest version yet but it’s running very very nicely and has been a big help in my day to day!

So I’m also using Beszel and Ntfy to track my systems because it’s lightweight and very very easy. Coming from having tried Grafana and Prometheus and different TSDBs I felt like I was way better off.

I’ve been following Beszels development closely because it was previously missing features like container monitoring and systemd monitoring which I’m very thankful for them having added recently and I use containers as my primary way of hosting all my applications. The “Healthy” or “Unhealthy” status is directly reported by Docker itself and not something Beszel monitors directly so it has to be configured, either by the configuration in the Dockerfile of the container image or afterwards using the healthcheck options when running a container.

As some other comments mentioned, some containers do come with a healthcheck built in which makes docker auto-configure and enable that healthcheck endpoint. Some containers don’t have a healthcheck built into the container build file and some have documentation for adding a healthcheck to the docker run command or compose file. Some examples are Beszel and Ntfy themselves.

For containers that do not have a healthcheck built into the build file it is either documented how to add it to the compose or you have to figure out a way to do it yourself. For docker images that are built using a more standard image like Alpine, Debian or others you usually have something like curl installed. If the service you are running has a webpage going you can use that. Some programs have a healthcheck command built into it that you can also use.

As an example, the postgresql program has a built in healthcheck command you can use of that’ll check if the database is ready. The easiest way to add it would be to do

    healthcheck:
      test: ["CMD", "pg_isready", "-U", "root",  "-d", "db_name"]
      interval: 30s
      retries: 5
      start_period: 60s

That’ll run the command inside the container pg_isready -U root -d db_name every 30 seconds but not before 60 seconds to get the container up and running. Options can be changed depending on the speed of the system.

Another example, for a container that has the curl program available inside it you can add something like

    healthcheck:
      test: ["CMD", "curl", "-f", "http://localhost:3000/"]
      interval: 1m
      retries: 3

This will run curl -f http://localhost:3000/ every 1 minute. If either of the above examples would exit with an exit code higher than 0 Docker would report the container has unhealthy. Beszel will then read that data and report back that the container is not healthy. Some web apps have something along the line of a /health endpoint you can use the curl command with as well.

Unless the developer has spent some extra time on the healthchecks it is often just a basic way to see that the program inside the container is running. However, usually the container itself exits if the program it is running crashes or quits. So a healthcheck isn’t always necessary as the healthcheck will be that the container has abruptly stopped. This is why things like Uptime Kuma is something to consider running alongside Beszel because it can monitor when a web address or similar is down as well even if a container exits which as of now Beszel is still sadly lacking.

I would recommend you read up on the Docker Compose spec for healthchecks since with the other options you can also do things like timeouts and what not, combining that with whatever program you’re running with the healthcheck you can get very creative with it if you must.

My personal recommendation would be to sticking with Uptime Kuma regarding proper service availability healthchecks since it’ll be easier to configure and get an overview of things like slow load times of web pages and containers that have stopped while using Beszel to monitor performance and resource usage.

Can I boop your nose?

https://www.youtube.com/watch?v=cl958H8i9M4

I see. I must’ve missed that while doing my skimming a bit too hastily. Good thing it has, I was worried it would be limited to securing it through a VPN.

I’m glad it exists and hope of develops further. It has gotten some well deserved growth and exposure in general.

I’ve been a Joplin user as well for some time and decided to switch to something different too. I looked at Trilium as a possible alternative but decided it wasn’t for me. Seems like their self hosted sync server doesn’t have much in terms of proper authentication at all? At least from what I’ve seen from the setup and when I skimmed through the docs. However there does seem to be encryption available which at least seems to be something. The interface also seems very cluttered and has a wild amount of features I’ll never even dream of using extensively. I needed something more simple and streamlined.

With that in mind and as I use Authentik for authentication and user management I decided to look elsewhere. I’m currently testing Jotty/Jotty.page, however they want to format it, and it has everything I need. But it lacks encryption and a proper mobile app. It does however have PWA support which is at least something. I do also enjoy that it is pretty much completely directory based. Even the users and user sessions and shared notes are just JSON files. This makes active backups a breeze and disaster recovery is going into a users directory and making a copy of their directories and .md files. It’s growing on me to say the least.

Mines an LCD. So I don’t really worry about burn in on it. However my portable monitor is an OLED which I do worry about burn in on so I have my screen off time quite low.

My Steam Deck has been my primary and only PC for almost 2 years. My laptop that I had broke and instead of buying a new one I decided to buy adapters and a portable monitor. I rarely game on it but manage my homelab and do web development.

I’ve been trying some different distros over time and currently I’ve been sticking with NixOS, however it’s been giving me some minor inconveniences here and there so I’ve been thinking of moving back to Nobara again.

When I do game I never really leave desktop mode and just play it normally. Lately I’ve been playing Peak, No Man’s Sky, Stardew Valley and occasionally some VRChat.

Overall, it’s great, my steam deck works well as a secondary screen while plugged into my monitor. I place my chats and stuff there and then I do whatever else on the main screen.

I’ve always found the installation process of Debian unintuitive for people not used to linux. But I could imagine that it’s probably abreally good contender once the packages are installed and the DE setup with any necessary extensions for file browsers and other programs, for example preview of files in Nautilus for GNOME. Unsure if that is automatically installed or not in Debian but could be a good idea to check.

I’d suggest trying a test install in a VM if you can to check how well Debian will hold after configuration. Package updates for my Debian servers happens every once or so week and with a DEs GUI package manager it could simplify the process of the user actually hitting the update button.

“Nevermet”?

I’d want this as my first tattoo.

I once bought these chocolates that had a outer coating making them look like decorative rocks.

My mum loves to have little rocks as decoration so I bought a pack and decided to surprise her with it. Out of nowhere in front of her I decided to bite through one and she was in shock looking at me as she slowly realised they were edible. They looked extremely convincing.

They were pretty damn hard tho. Nothing too bad however.

It’s an interesting topic me and my friends have discussed for a long time. On one hand, putting ease of use and user experience behind a paywall is terrible but on the other developers deserve compensation. Not everyone can donate and others doesn’t even figure that it’s an option.

Pangolin I think does it very kindly by having a button on the lower left of the interface that you can click on and then also dismiss to hide that button for a week which I find a good common ground. But at the same time I also think it’s hard to justify hate towards projects that lock things behind a paywall.

Of course if you lock security features like OIDC/LDAP like some do or self-hosting to “Local Infrastructure” it’s pure BS. I think there’s a lot of nuance to what should and shouldn’t be done in the matter but as long as it’s still open source it’s good in my book. Like self hosting Bitwarden gives you access to the paid features or you can pay them the small fee to not self host it and get some extra QoL features.

People do in the end have to juggle software maintenance, community maintenance, organizing issues, planning features and implementations, keeping wiki and docs up to date, etc. On top of, I’m assuming in most cases, having to do a regular job too. I know for a fact I wouldn’t be able to do that at all so if they can get some motivation through either code contribution or monetarily it would potentially ease up things.

“I was also on the team that helped create covid!”