Isn't it better to create local docker repository and then use Podman Quadlet with autopull images to run apps?
Piku: Allows git push deployments to your own servers
11–20 of 169 posts
Re: Piku: Allows git push deployments to your own servers
#12Isn't it better to create local docker repository and then use Podman Quadlet with autopull images to run apps?
Better in what way?
Re: Piku: Allows git push deployments to your own servers
#13Isn't it better to create local docker repository and then use Podman Quadlet with autopull images to run apps?
Better in what way?
1. Less dependencies (only Podman and registry is needed)
2. Rock solid rootless systemd service management
3. Easy integration with systemd-proxyd
4. Easy manage dependencies between containers (with healthchecks)
5. Rollbacks
Re: Piku: Allows git push deployments to your own servers
#14pikku means tiny or little in Finnish. Is it where the name came from?
Re: Piku: Allows git push deployments to your own servers
#15Nice work. But why isn't Docker supported as a runtime? Or is it?
Re: Piku: Allows git push deployments to your own servers
#16I 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?
Re: Piku: Allows git push deployments to your own servers
#17pikku means tiny or little in Finnish. Is it where the name came from?
I don't know but my first association was "pico-dokku"
Re: Piku: Allows git push deployments to your own servers
#18Earlier quoted context omitted.
Better in what way?
1. Less dependencies (only Podman and registry is needed) 2. Rock solid rootless systemd service management 3. Easy integration with systemd-proxyd 4. Easy manage dependencies between containers (with healthchecks) 5. Rollbacks
Sounds interesting! Is there any support for multi-node systems? Let's say I want to have an ingress Caddy proxy on one node, which reverse proxies to several backed APIs on other nodes - can this be done simply with Podman Quadlet?
Also, what is the localdev UX like? With Docker Swarm I can easily run very similar setups in dev, test and prod, and it works with multi-node setups, has support for secrets etc. But the lack of work going into Docker Swarm becomes more concerning as the years pass by.
Also, had no idea systemd-proxy was a thing - is there anything systemd doesn't have its tentacles into? :)
Re: Piku: Allows git push deployments to your own servers
#19Cool project, but I’ll stick with Dokku, which is a wonder for managing single server deploys via Docker/Git.
Re: Piku: Allows git push deployments to your own servers
#20Earlier quoted context omitted.
1. Less dependencies (only Podman and registry is needed) 2. Rock solid rootless systemd service management 3. Easy integration with systemd-proxyd 4. Easy manage dependencies between containers (with healthchecks) 5. Rollbacks
Sounds interesting! Is there any support for multi-node systems? Let's say I want to have an ingress Caddy proxy on one node, which reverse proxies to several backed APIs on other nodes - can this be done simply with Podman Quadlet? Also, what is the localdev UX like? With Docker Swarm I can easily run very similar setups in dev, test and prod, and it works with multi-node setups, has support for secrets etc. But the…
If your VPS is wired with another one using VPC or any other internal network it'll just work. Just point Caddy to specified internal IPs of your other servers.
It's not designed to work on local envs. When I wanted to debug infra I used to run it on Vagrant though