Wojciech Wnętrzak
Wojciech Wnętrzak
Thank you for checking
Hey, just a mention that we see similar issue on production k8s. The jobs where in "in_progress" and assigned to the worker that didn't exist. Manual `release` worked in this...
@Talha345 does it solve your issue? Can it be closed?
Just in case GH notification miss - @tiegz FYI
@zhuravel Rails 8.0 is just around the corner. Are you able to loosen rails version restriction or maybe create separate PR for it?
FYI: Code from this PR works fine for us on Rails 8.0.0.rc1 in production.
@binarylogic The tests have passed. Ready for a release
I'm experiencing the same issue. @djmb What was the rational behind this? Is there an easy way to have this output without passing --verbose option to deploy command, as this...
Yes, I had the same issue. When added a new database configuration and running `bin/rails db:prepare` the database was created and the seeds were run. I made my seed file...
@cosminonea You can use "files" config, something like: ``` accessories: db: files: - path-to-file-in-your-repo:/.gcloud/sql-proxy-key.json:ro ``` See https://kamal-deploy.org/docs/configuration/accessories/#copying-files BTW, the better place for asking such questions is https://github.com/basecamp/kamal/discussions