FRESH

Hacker News

Show HN: Mist – a lightweight, self-hosted PaaS

13 points by notcalc

by mappu

1 subcomments

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?

by Reubend

1 subcomments

This looks cool. I see under the "current limitations" section that it only supports a single node. Are there plans to change that? I'd imagine that database instances which got started on a single node deployment would be hard to migrate to a multi-node setup later on if they weren't originally spun up in that configuration (though ofc not impossible, just tricky).

by nullpilot

0 subcomment

Gratz on shipping! I've been eyeing Canine for my next Hetzner setup, but the database support on Mist is a nice feature.
Looks like I have some experiments to run soon.

by swrobel

1 subcomments

Dokku = steep learning curve according to your comparison chart? As a longtime Heroku user, I’d have to disagree.