Make single-instance Kamal deployments finally work after I realized all Traefik, Postgres and Rails containers need to be running in the same private Docker network – and learn a lot of Docker along the way #life

Automated deployment of blastbanners.com with Kamal (#screenshotone)

Deploy production with kamal #rubypilot

deploy app to DigitalOcean #simpleanalytics

Setup Github actions Kamal deployment #superforum

Deploy imgproxy via kamal

deploy app to Dokku on digital ocean #mediumlytics

deploy bot to digitalocean server

Manage to deploy my first Rails 8 app using Kamal 2 without errors after figuring out remote builders, good Docker hardening config, Postgresql adapter config, etc. #life

Kamal + Docker + caddy + Vue + fastify + PostgreSQL #research

deployed on digitalocean

build docker containers and ship them

ansible docker deploy

Have even more issues with Kamal where it refuses to deploy a new docker container (container fails to start), I think because the same port is being used by the old one? Works when I manually stop the old container and deploy again. Seems horribly broken and now need to move to a different deployment method to get #watchdog working for Build in Public !private

Configure Github Action to deploy via Kamal #til

Configure Github Action to deploy via Kamal #followup

setup docker

Kamal deploy, single server #superforum

Setup WordPress on Digital Ocean

Mess with kamal for hours and hours and FINALLY get the app deployed in prod (not working in CI yet, it just times out on SSH for some unknown reason). Kamal needs a lot of work to be production ready, not very happy with it so far. Now to make sure my app can talk to the chromium container which is also running on Kamal now #watchdog !private