otomi-core VS piku

An example of a self-hosted Kubernetes-based PaaS is Otomi. Install Otomi on your Kubernetes cluster, compose your platform (by activating the required capabilities) and build, deploy and expose apps in just a couple of minutes. Heroku, but Kubernetes native and running on your own cluster.

This video shows some of the new features of Otomi version 0.19.0 that will be released in Week 11 2023. Follow us on GitHub and be the first to try it out: https://github.com/redkubes/otomi-core

Otomi

Kubernetes is 'only' a multi-node cluster kernel. Some call it the Linux of the cloud.

And because K8s is only a kernel, there are now over 2000+ (open source) projects, all adding some extra functionality to it. Be it for observability, security, or networking. But all of these projects don't really collaborate and end-users don't ask for maturity of individual projects, they want sets/stacks of projects that integrate well.

Now every company has created some Stack with applications and configurations for Kubernetes, all trying to reinvent the wheel and spending an often shocking $ in doing so.

So here is my take:

- Let's create a new category in the Cloud Native Computing Foundation (CNCF) landscape and call it Integrated Stacks for K8s

- To be accepted, a stack needs to provide an open integration framework for other projects to add/integrate their apps

- Just like aLinux distro, each stack is ideal for some specific use case(s)

- A stack can be installed in one run, contains integrated apps that work out-of-the-box, has a (web) UI that acts as a desktop environment to provide easy and secure access to all features. Call it a new user experience for Kubernetes

Wouldn't it be great to have a list of all Kubernetes stacks available that everyone can use (and contribute to)? Just like (in the Linux analogy) you can choose between Linux Mint, Fedora, or Ubuntu.

We already created the first: https://github.com/redkubes/otomi-core

I should add one to https://piku.github.io (spoiler - this doesn't use Docker at all)

I like it. I wrote Piku (https://github.com/piku/piku) with much the same interest in fixing some of my pains, so I get where you're coming from with this. Will drop it into one of my current projects to build ESP32 binaries :)

I never had any serious issue with SD cards since the Pi 2B (and I've kept Pis running for years).

Anyway, for those wanting to deploy more generic apps, that is why I initially wrote https://github.com/piku/piku - you still have to flash the OS (and rpi-imager does that with sane defaults these days), but once you're done you have Heroku-like deployments for any language runtime you install on the Pi.

I also have https://github.com/rcarmo/ground-init, a cloud-init like shim that simplifies setting up machines (I'm a big fan of cloud-init, but since Raspbian doesn't support it and Ubuntu on ARM requires some fiddling to make it work I decided it wasn't too hard to roll my own).

(I probably should look into glueing that into rpi-imager, but there is are only so many hours in the day...)

I automated that away a long time ago: https://github.com/piku/piku/blob/master/piku.py#L814

Piku https://github.com/piku/piku

So, stupid question: why couldn't I just use the 'baremetal' OS provided by Hetzner, install Postgres, Redis & node, create a separate db for each app, and run each app with https://github.com/piku/piku on a different port? For backups, I'll setup crontab to dump dbs locally and to S3.

piku?