Hacker News Board Hacker News, browsed like a classic message board
Live data from Hacker News

Piku: Allows git push deployments to your own servers

github.com

Post reply on HN
Print view View original

161–169 of 169 posts

Re: Piku: Allows git push deployments to your own servers

#161

Post by mitjam »

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...

Re: Piku: Allows git push deployments to your own servers

#162

Post by chr15m »

rcarmo wrote: post #81
foxhop wrote: post #55

Earlier quoted context omitted.

are there docs for this setup?

It’s just a 10-line script, I’ll see if I can sanitize it and add to the docs (one of the samples already does something similar, you can peek at the repos to get ideas)

That script sounds super useful!

Re: Piku: Allows git push deployments to your own servers

#163

Post by CaptainOfCoit »

mitjam wrote: post #161

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…

> 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?

Re: Piku: Allows git push deployments to your own servers

#165

Post by withinboredom »

llIIllIIllIIl wrote: post #151

I use dokku for my side gigs and it works best. The performance issue I’ve experienced was when the container with my app was being built and it dramatically increased the load on a $20 vm. Then I migrated to use container registry to utilize GitHub actions for building and pushing containers to the registry and then deploying the container directly on the dokku host. Does piku support that flow? Another question is…

> Those two problems make me think that my side gig has grown up enough to switch to ArgoCD/K8s

If you have to think about it, it isn't worth it. You'll know when it is time to refactor your infra.

Re: Piku: Allows git push deployments to your own servers

#166

Post by dizhn »

rozhok wrote: post #144
tiffanyh wrote: post #59

With PHP, 1-line (no new tools): sftp user@host remoteFile localFile Joking aside, I’m a bit surprised such a tool would be developed in Python given its dependency’s and runtime (which is not easy on the user).

You still need to install nginx, php-fpm an configure certs, so php is not that easy unfortunately.

That's two lines in Caddy : ) (I do get your point of course )

Re: Piku: Allows git push deployments to your own servers

#167

Post by mitjam »

CaptainOfCoit wrote: post #163
mitjam wrote: post #161

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…

> 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 obv…

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.

Re: Piku: Allows git push deployments to your own servers

#169

Post by lakomen »

This, but on a per user basis would be great.

But uwsgi performance overhead is a concern. Altough last time I've done anything with uwsgi that was probably over a decade ago.

And last time I checked, Go required to import the uwsgi package, maybe not anymore? Or is uwsgi used only for Python here?

Also I wonder how to define nginx routes aka locations?

Post reply on HN