[mappu]

Dokku user for a decade here, congrats on shipping, love to see more self-hosted PaaS options like this.

Why are binaries checked into the bin/ directory in the repo?

Compared to Dokku, I like how your LE support is builtin instead of a plugin. Is your main www ingress server an nginx that gets externally configured (like Dokku) or are you using net/http or libcaddy directly?

Dokku has a history of trying to compete with Heroku buildpacks - as a non Heroku/non Ruby developer this never resonated with me and there are a lot of vestigal parts (e.g. .web.1) that i would just put in my own Dockerfile directly. So focusing solely on Dockerfiles i personally feel is a good move.

One issue i faced with Dokku is eventually the build process for my Dockerized app was too memory-intensive to run on the VPS. I switched to running docker build locally, sending the container via `docker export | ssh | docker import`, and having a single `FROM myapp` dockerfile in Dokku. This was not particularly ergonomic to set up. Is it possible you can improve the UX of client-side built containers, or will you focus solely on the GitOps deploy?

[notcalc]

Thank you so much for your feedback.

The binaries are for local testing for now, the actual binaries are built on the server/VPS on installation, we are planning to distribute single binaries in future.

The reverse proxy + TLS is Handled by traefik running in a docker container itself, we chose traefik because of the automatic docker label based dynamic routing, I hope we don't need to switch to something else anytime soon .

We have plans for remote/local builds using a small docker registry instance on the server/VPS to eliminate the need of any external registry