Buy a blinding stew

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.

I think they mean librarian? Or maybe the libyans

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.

There seems to be a lot of confusion regarding your question from users. If I understand it correctly, you’re wondering about when the human species became less of hunter-gatherers and more socially adept animals and when and why societal progress started suppressing aggressive behaviours in tribe-based expansion and control.

You referencing “protohuman traits” makes it a bit harder however since protohumans are before our own species of homo sapiens but I could imagine that a lot of those traits are closely related to early homo sapien society.

I don’t have a lot of answers for you but I think the answer maybe lies in sociological studies and things like Social Contract theory. Maybe it’s that slowly people got more rights to not be hurt by others because they could bring value to society as a whole in other ways and with the invention of agriculture, things like jobs became more viable and governments formed with laws then religion came along and what not too heavily influencing rights and wrongs.

Now translate: spring bil snö penna

Does this count? https://sopuli.xyz/post/1138547

Only FANGS.

Exactly, just run your magical new code in a minifier and problem solved! It’ll be just as speedy as the real deal!

Having run minor projects using PocketBase before and also seen what PocketBase itself can do and SQLite configured correctly in general, It’s great. I’ve gotten to be a big fan of it by the years and gladly opt for it over the bigger ones.

If this project got SQLite support it would be a great replacement for my own setup which requires about 3 or 4 accounts. Currently using a proprietary solution and been looking into moving to Authentik but it’s a bit too heavy resource wise for my current servers.

But wait, I’m only in my mid 20s! It’s too early! It shouldn’t be happening!

I think we should use “Rofles”

Hey it also me

You’re beloved too for being here with us. Thank you for your presence.

Not necessarily. Most plugins for Tauri support being configured on the JS side of things quite well. You can achieve a total HTML/CSS/JS or using a JS framewframework with very very minimal Rust code modifications.

I dabbled in creating a GUI for password-store with Tauri and SvelteKit and managed to create everything without barely having to touch the Rust code. Of course, if you want to optimize and make it more efficient you’d probably want to port the code over to Rust as it’d most likely be a bit speedier for some tasks but in general you can go all the way in skipping the Rust partion of things!

4