sequencer VS epinio

I really love this idea in theory, and I believe that for some system, specially mature ones, it may work well. I see good documentation as a super power; it empowers readers and motivate people to understand more about the system without being caught in the weeds of reading the source.

The source has baggages, and the intent of every single function calls is not always evident. Writing documentation up-front can help direct the source, but this is a tug-of-war environment. Each affect the other in its own ways.

And for that reason, documentation driven development can be a real drag. You start writing documentation with the best intentions, everything works great for this first release. But 2 months down the road you need to modify something and it has a ripple effect on many of the things you documented. It's a non-negligible cost.

I've been working on this open-source tool(https://github.com/pier-oliviert/sequencer) and I've spent a lot of time on the documentation. And what I described above happened. I wanted to make a not-too-big change, and it required me to rewrite 30% of the documentation. I still love the documentation aspect of it, but it definitively has a cost.

First time I read about piku. I have no idea why, but the feeling of `git push` to initiate a deployment like piku does always felt magical to me. There's nothing simpler than that.

This is timely for me as well as I just open sourced (yesterday!) a project that is in the same space, but for Kubernetes (https://github.com/pier-oliviert/sequencer).

All of this to say, congrats! It looks great.

I like Epinio which does the same but on top of kubernetes. It is backed by Suse and lightweight compared to KNative (which is the basis of GCP CloudRun for example), but being kubernetes based still requires more Resources than dokku or Piku. I still prefer k8s due to the vast ecosystem of mature solutions. And I can still run everything on a single box, it just needs to be a bit bigger. The new Hetzner CX42 with 8 vCPUs, 16 GB of RAM, and 160 GB of disk space for € 16.40 a month (€ 0.0273 per hour) is sufficient, and with the Kube Hetzner Project I can set up a kubernetes cluster with auto updating microos in 5 minutes.

https://github.com/epinio/epinio/

https://github.com/kube-hetzner/terraform-hcloud-kube-hetzne...

You could have a look to https://epinio.io/. It is a PAAS that leverage build pack to deploy app on k8s cluster. Disclaimer: my team is working on it

Epinion

Would have helped if I spent it right 😂 - https://github.com/epinio/epinio

Epinio can be installed using Helm onto any compliant Kubernetes Cluster. The latest CLI release can be found at [][https://github.com/epinio/epinio/releases]

We are building a product (Epinio) to avoid this. The idea is that devs don't need to access the cluster and to know the Kubernetes internals to deploy something. It's still in alpha/beta, with a lot of development ongoing. 🙂

For the Apache/php container portion and building the app itself, I'd suggest looking at buildpacks (Paketo buildpacks are easy). This can let you standardize on the code->container pipeline. (I'm biased since I'm working on Epinio which uses them to simplify the code->running application pipeline)

For dev work, we also are working on a project called Epinio which takes a bit of a different approach to developing on top of Kubernetes. (https://epinio.io)