help early reader to debug and fix a Kamal deploy

Get multiple Rails app deployed in the same single-instance server with Kamal

Play around with deploying own lightweight registry for Kamal deploys

Dockerize #submit and deploy it with Kamal to Digital Ocean

Dockerize #pushmore and deploy it with Kamal to Digital Ocean

Dockerize #storyai and deploy it with Kamal to Digital Ocean

Dockerize #image and deploy it with Kamal to Digital Ocean

Dockerize #traits and deploy it with Kamal to Digital Ocean

Dockerize #marcbot and deploy it with Kamal to Digital Ocean

Dockerize #emoji and deploy it with Kamal to Digital Ocean

Dockerize #buildinpublic and deploy it with Kamal to Digital Ocean

Dockerize #highscore and deploy it with Kamal to Digital Ocean

Replace sidekiq with solid_queue #danceai

Published a post about how to deploy Next.js with SQLite to Hetzner with a help of Kamal 2 and GitHub actions 👉 scalabledeveloper.com/posts/d…

Finally get GitHub Actions to deploy via Kamal after a few hours of debugging #wip

Dockerize names.marc.io and deploy it with Kamal to Digital Ocean

change sidekiq configuration for big senders #botletter

Set up CI workflow with Github Actions and Kamal #submit #domains #emojidomains #highscore #traits #pushmore #til #followup

Kamal + Docker + caddy #research

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