OneUptime Blog

They even have a scrolling 5-star reviews section, clearly generated: https://oneuptime.com/#reviews-title https://github.com/OneUptime/oneuptime/commit/538e40c4ae724e8e83c01a81… https://github.com/OneUptime/oneuptime/commit/2bc585df20e6bbdaf85f5fd8… You can fabricate a professional business image in a few days with AI now. It's going to be hard to build an honest brand when everyone is going to point and say "vibe coded slop" because of examples like this website. I'm already seeing such comments whenever someone posts an app on /r/macapps and it's really discouraging for beginners. If I would have met that resistance and amount of mean comments when I launched Lunar, I would have probably never put in that amount of effort.

OneUptime (https://oneuptime.com) | Remote | Full Time | Sr Full Stack Engineers + LLM/ML Engineer We're building an open-source alternative to Datadog. Tech Stack: TypeScript + React + Node + Clickhouse + Postgres

https://oneuptime.com/ also makes it a managed service to compete with datadog

https://github.com/oneuptime/oneuptime https://oneuptime.com/

I saw this the other day, though not likely as mature a product: https://oneuptime.com/

With multi-stage Dockerfiles, you only copy the final, built application artifacts from the earlier stage(s). Then, building a package as one signed file to copy is justified and easier anyway. There's always: RUN dnf remove -y ansible && dnf clean all I thought there was a native way to build container images with ansible that don't have ansible installed in the image though? ansible/ansible-builder: https://github.com/ansible/ansible-builder "How to Use ansible-builder to Create Execution Environments" https://oneuptime.com/blog/post/2026-02-21-how-to-use-ansible-builder-… : > The Build Process Explained: When you run ansible-builder build, it goes through these steps: > Reads your `execution-environment.yml` definition, Resolves collection dependencies (including transitive dependencies), Generates a `Containerfile` in a `context/` directory, Copies dependency files into the build context, Runs the container build using Podman or Docker How to Use Ansible to Build Podman Images > Building with Build Arguments, Multi-Stage Builds, Building with Buildah: https://oneuptime.com/#building-with-buildah : It's possible to build images using build a commands in an ansible playbook: buildah from buildah copy buildah run buildah config buildah commit . The CLI way to traverse an ansible playbook graph, for e.g. dagger: ansible-playbook --list-tags ansible-playbook --tags…

Another surprising security feature regarding docker is that it bypasses firewall rules. https://oneuptime.com/blog/post/2026-03-02-ufw-docker-fix-bypassing-uf…

have you tried to recover it with git reflog? https://oneuptime.com/blog/post/2026-01-24-git-reflog-recovery/view

https://oneuptime.com/blog Scroll down a little and you'll see a huge block of posts dated March 31st

Both Redis (finally) and Valkey addressed the multithreading scalability issues, see https://oneuptime.com/blog/post/2026-01-21-redis-vs-memcached/view and/or https://news.ycombinator.com/item?id=43860273...

I’m guessing https://oneuptime.com/blog

But it isn't portable, unless you stick to posix subset which kinda sucks. You'll use some feature that some dude using an ancient shell doesn't have then he'll complain to you. And that list of features is LONG: https://oneuptime.com/blog/post/2026-02-13-posix-shell-compatibility/v… If you're using shell specific features in a tightly controlled environment like a docker container then yeah, go wild. If you're writing a script for personal use, sure. If you're writing something for other people to run then your code will be working around all the missing features posix hasn't been updated to include. You can't use arrays, or arithmetic context, nothing. It sucks to use. Besides, if you're writing a script it is likely that it will grow, get more complicated, and you will soon bump up against the limitations of the language and have to do truly horrible workarounds. This is why if I need something for others to run then I just use python from the beginning. The code will be easier to read and more portable. At this point the vast majority of OS's and images have it available anyway so it's not as big a barrier as it used to be.