Donal McBreen
Donal McBreen
@Towerthousand - if the deployment is not a web app, you can set `proxy: false` which will then skip running the proxy. Then Kamal will either wait for the container...
Thanks @karls! I've raised https://github.com/basecamp/kamal/pull/1018 to fix the buffering arguments. I guess it may be that disabling the buffering is what's needed to fix your issue with SSE?
Yes, definitely something it should support - I've raised https://github.com/basecamp/kamal-proxy/issues/34 to track 👍
I think you'd need to run `kamal app remove` with the old config, then change it and then run `kamal deploy`. Is that what you did?
I'm not sure why this is happening then. The error suggests that kamal-proxy still has a deployment registered under the old role. You should be able to remove it manually...
I'm not 100% sure but this may be a limitation of net-ssh (see https://github.com/net-ssh/net-ssh/issues/954https://github.com/net-ssh/net-ssh/issues/954). Can you ssh directly with the ssh command using the ed25519-sk key?
I think then we are stuck until net-ssh adds support.
cc @jorgemanrubia @duduribeiro - this is an alternative to https://github.com/rails/rails/pull/50920 which you spotted some issues with last week. If you had time to confirm if it works for you I...
Are you using Kamal 1 or Kamal 2? Kamal 2 does not use .env anymore. In any case what results do you get? Have you tried specifying the env variable...
Going to close this as it is for Kamal 1.0