8 ms·
This looks great. But if you don’t need containers or are using tiny hardware, consider trying out Piku: https://github.com/piku https://github.com/piku (You
by rcarmo 5y ago
This looks great. But if you don’t need containers or are using tiny hardware, consider trying out Piku:
https://github.com/piku https://github.com/piku
(You can use docker-compose with it as well, but as a deployment step — I might bake in something nicer if there is enough interest)
- uniqueuid 5y ago+1 for pikku which is one of my favorite examples of "right abstraction, simple, just works, doesn't re-invent the architecture every 6 months". Thanks for that, Rui!
- rcarmo 5y agoWell, I am thinking of reinveinting around 12 lines of it to add explicit Docker/Compose support, but it’s been a year or so since any major changes other than minor tweaks :) It has also been deployed on all top 5 cloud providers via could-init (and I’m going back to AWS plain non-Ubuntu AMIs whenever I can figure out the right packages).
- stavros 5y agoThat looks nice, isn't it kind of like Dokku? It's a nice option but not a very good fit if you don't need ingress/aren't running web services (most of my services were daemons that connect to MQTT).
- rcarmo 5y agoYou can have services without any kind of ingress. It’s completely optional to use nginx, it just gets set up automatically if you want to expose a website. My original use case was _exactly_ that (MQTT services).
- stavros 5y agoOh huh, that's interesting, thanks! Is it geared towards worker/DB too, like Dokku? Unfortunately with Dokku it's a bit hard to run multiple containers together (I remember having to hack stuff to enable app deployments where one app was the frontend and another was the API).