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

51–60 of 169 posts

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

#51

Post by vault »

szundi wrote: post #23
lathiat wrote: post #22

Earlier quoted context omitted.

At -some- point you actually need to update things. If you're using a 2008 docker container you have all manner of bugs and security issues.

But at least the attack vectors are limited

yes, limited to those that work 100%!

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

#52

Post by vault »

cfiggers wrote: post #44

The initial commit was eight years ago?? I wish I had known about this project ~18 months ago. I was specifically looking for a way to have a Heroku-like dev experience deploying to my Raspberry Pi, and this looks like it's trying to be exactly that.

Exactly. There's a visibility problem. I've just setup a new VPS with CapRover and never found any mention of piku in the hour I've spent checking for comparisons between "Heroku-style self-hosted PaaS" dokku, CapRover, coolify, and dokploy.

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

#53

Post by CaptainOfCoit »

p-o wrote: post #50

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.

Maybe I'm missing something obvious, but how does sequencer use git to do deploys, if it's similar to Heroku/dokku/piku? Seems like you're dealing with kubernetes templates and kubectl rather than `git push` to deploy, which would put the project is a completely difference space.

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

#54

Post by vault »

adeptima wrote: post #27
sneak wrote: post #16

I think a more common use case than doing deploys by pushing to a different remote is to send git repo webhooks on PR merges to main to an API that has a deploy key and can fetch the repo itself. This afaik is missing from most PaaS tools (CapRover excluded, but it has been illegally relicensed to non-open-source). Perhaps watchtower or something could replace the functionality?

Didnt know ... "CapRover has built in anonymous usage analytics starting v1.11" https://github.com/caprover/caprover/blob/master/TERMS_AND_C... https://github.com/caprover/caprover/issues/1852 Was looking at CapRover to see if it has REST API Looks shaddy

You scared me for a moment, as I've just setup a new VPS with CapRover and migrated all my projects from heroku. Doesn't look too shady for me, there's a oneliner to disable analytics, it seems enough for me.

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

#55

Post by foxhop »

rcarmo wrote: post #33
sneak wrote: post #16

I think a more common use case than doing deploys by pushing to a different remote is to send git repo webhooks on PR merges to main to an API that has a deploy key and can fetch the repo itself. This afaik is missing from most PaaS tools (CapRover excluded, but it has been illegally relicensed to non-open-source). Perhaps watchtower or something could replace the functionality?

Actually, this is how I deploy my static websites: piku in lazy mode handles GitHub hooks, pulls the source and renders them out to cloud storage, then kills all workers and idles again.

are there docs for this setup?

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

#56

Post by zeroq »

15 years ago it was common to deploy web applications as live SVN repositories with a hidden path executing 'svn update' on manual http request.

Not quite the 'push deploy', but that was the way apps were developed back in the days, and for some reason I still prefer that approach. Commit, test, and at one point manually nominate and deploy stable version.

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

#57

Post by snitty »

1oooqooq wrote: post #47

[flagged]

> set -e

> echo "Downloading piku-bootstrap here."

> curl -s bootstrap" rel="nofollow">https://raw.githubusercontent.com/piku/piku-bootstrap/master... > piku-bootstrap

> chmod 755 piku-bootstrap

> echo "Now you can install Piku on `hostname` like this:"

> echo "./piku-bootstrap install"

Did you look at the script?

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

#60

Post by layer8 »

stavros wrote: post #41
layer8 wrote: post #40

Earlier quoted context omitted.

My point is that OS upgrades don’t have to break tech stacks, and don’t tend to with runtimes that care a lot about backwards compatibility like Perl and Java. I did regularly upgrade Debian across those two decades. IMO that quality should be the default, and I would choose my OS and tech stacks accordingly.

Don't they link against static libraries? How do they do that?

The runtimes are part of the Linux distribution and get upgraded along with it (and receive continuous security updates along with it), while maintaining backwards compatibility for the application code (Perl scripts or Java bytecode). Tools like needrestart will notify when a process needs to be restarted to take advantage of the update.
Post reply on HN