> I like Epinio which does the same but on top of kubernetes
So basically not at all the same? :D
The point of piku seems to be: Heroku experience without requiring docker, and with a really simple architecture, and that it works on ARM.
Kubernetes works on ARM, I give you that. But AFAIK, Kubernetes requires you to use some sort of containers (Docker or otherwise) and its architecture is anything but simple (for obvious reasons).
Besides that, I don't see how epinion enables the "git push" workflow, the quick start tutorial seems to tell you to run "epinio push manifest.yaml" or similar to deploy the application, so it doesn't fit with the "Heroku-like experience" either.
So really, the only things they have in common is that they handle deployments?
You are right it needs docker but so does Dokku and I see this more as an implementation detail (even a plus in my book for the flexibility). Epinio does admittedly not support git push but for me „epinio push --name myapp“ feels similar enough. In the end, I can just push my Django or next.js or rails or node.js code to the server.
I should have said „I like Epinio, as well“ because I also like Piku, especially for its minimalistic approach and readable code, but when it comes to actually using it for deployments, I prefer Kubernetes.
So basically not at all the same? :D
The point of piku seems to be: Heroku experience without requiring docker, and with a really simple architecture, and that it works on ARM.
Kubernetes works on ARM, I give you that. But AFAIK, Kubernetes requires you to use some sort of containers (Docker or otherwise) and its architecture is anything but simple (for obvious reasons).
Besides that, I don't see how epinion enables the "git push" workflow, the quick start tutorial seems to tell you to run "epinio push manifest.yaml" or similar to deploy the application, so it doesn't fit with the "Heroku-like experience" either.
So really, the only things they have in common is that they handle deployments?