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.
31–40 of 169 posts
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.
Does someone know how it handles (if any) zero downtime deployments? Like, if your Python service is running in one machine on port 8080 behind nginx, how does piku switch to a fresh instance running in the same port?
One thing it already does (optionally) is to kill off unused instances and idle, lazily starting them when a new connection comes in.
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?
Is there support for secrets?
pikku means tiny or little in Finnish. Is it where the name came from?
Nice work. But why isn't Docker supported as a runtime? Or is it?
You can use docker run commands, but that’s not the main goal.
Isn't it better to create local docker repository and then use Podman Quadlet with autopull images to run apps?
Very happy to see this here - check out our freshly revamped docs at https://piku.github.io/
I 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.
thanks for that. I have no idea what heroku is or does.
Earlier quoted context omitted.
That depends on your tech stack. I have Perl CGI and Java apps that have been running unchanged for two decades. And the only thing I ever had to change on Debian over that time was adding HTTPS (Let's Encrypt) and SPF/DMARC for email.
Yeah, but my point is that you have to upgrade your OS. If you never change anything, obviously you don't need to worry.
IMO that quality should be the default, and I would choose my OS and tech stacks accordingly.