engine VS piku

Qovery: Qovery simplifies the deployment process for Kubernetes by letting you declare your project's structure and dependencies, making it an excellent choice for startups looking to focus on development without worrying about infrastructure.

Enter Qovery - an Internal Developer Platform that can be installed on any Kubernetes cluster to bring a delightful and simplified developer experience. But don't take my word for granted. In this quick step-by-step article, I will show you how to deploy one of my GitHub apps and a Postgres database on my Kubernetes cluster running on GCP. And what's really really cool is that I don't even need to understand how Kubernetes work!

Qovery is a comprehensive PaaS tool that offers a range of features to simplify the deployment and management of applications. With Qovery, you can easily deploy your applications in various cloud environments, eliminating the complexities of infrastructure setup. Its intuitive and developer-friendly interface, Git integration, and automatic scaling capabilities make it a powerful choice for building a custom PaaS. Qovery's seamless integration with popular frameworks and databases further enhances its appeal.

Qovery https://www.qovery.com

I have one of my customers who want to use Qovery to deploy their apps on AWS China. Technically speaking, Qovery runs on Kubernetes and on all the usual AWS regions. But AWS China (Beijing) is a bit different (cf here)

Combining GitLab (CI) with Qovery (CD) sounds what you need.

I am eager to get your feedback on Qovery - an open-source CD platform that helps thousands of developers and DevOps to build and scale on AWS.

Qovery - an open-source platform that makes AWS easier and there is a Terraform provider available

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?