I just added a magic URL in my app that GitHub calls whenever a commit is pushed and the server does `git pull` which in turn causes pm2 to reload the app. So committing anything shows up in production in seconds. Great for smaller projects.
Piku: Allows git push deployments to your own servers
131–140 of 169 posts
Re: Piku: Allows git push deployments to your own servers
#132interesting project! what are the advantages of this over pushing to a normal ssh server with a server side git hook?
Re: Piku: Allows git push deployments to your own servers
#133I just "git push" using nixos-rebuild
Re: Piku: Allows git push deployments to your own servers
#134I just added a magic URL in my app that GitHub calls whenever a commit is pushed and the server does `git pull` which in turn causes pm2 to reload the app. So committing anything shows up in production in seconds. Great for smaller projects.
I have a similar setup, using snare to handle the webhook endpoint: https://github.com/softdevteam/snare
GitHub will call the webhook after a push to main and a successful test suite run. Snare runs a shell script on my server to git pull, build, deploy, and call a cronitor.io hook for monitoring deploy success.
I've been pretty happy with how relatively simple it is and how well it works.
Re: Piku: Allows git push deployments to your own servers
#13515 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.
You can do that in the git push by having a separate "stable" branch and linking deployment to it.
Re: Piku: Allows git push deployments to your own servers
#136Maintainer and co-author here. If you like simple, minimalist deployment tools, check out https://github.com/rcarmo/ground-init for a very much down to earth take on cloud-init…
Your readme doesn't really answer the question of why not cloud-init?
Re: Piku: Allows git push deployments to your own servers
#137I love piku. I wrote a webapp tutorial for piku which got turned into a repo as part of the official GitHub piku org. You can find that here: https://github.com/piku/webapp-tutorial?tab=readme-ov-file#b... It explains how piku works under the hood, as well as showing a minimalistic Python web app example from a user standpoint.
"What is a Heroku-style deploy?" thanks for that. I have no idea what heroku is or does.
Short version:
Git push deployment where it detects your stack and automatically builds, then deploys with zero downtime.
Re: Piku: Allows git push deployments to your own servers
#138Earlier quoted context omitted.
Oh yes, I definitely use LTS distros, but my longest-running apps are from 2008, so even LTS won't cover that.
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.
I agree. But 2008 is old enough that exploits may be lost in time.
I recently pentested a client, and had great problems connecting to an old service still using SSL (i think it was 2.0). Every modern tool straight up refused to connect, there was no method to override that, oldest static curl binaries i could find were still too new, I couldn't easily compile curl from source because dependencies also changed in the meantime. Finally I've found sn acient docker image that worked.
The service was ironically so old that no modern vulnerability scanner or programming language would be able to connect!
This made me seeiously ponder the fleeting nature of modern world - SSL support was everywhere 15 years ago, and now I, as an expert, had great problems using it. What chance do we have in 100 years?
Re: Piku: Allows git push deployments to your own servers
#139[dead]