Barnabé

I don't know if this is possible, or even if it's a good idea, but I was thinking about it and it seems to me that rails helpers are tested....

@Towerthousand, @krasylnikov : I don't think you can bypass. But you can use Docker's healthcheck, or simply add a non-https route which responds 200 You should find more information in...

I've also encountered this problem. The problem comes from the “/up” route which must remain reachable without SSL. You just need to add a configuration line in `production.rb`. I actually...

@guilhermecaixeta maybe it's a port 80 error. Thruster expose the port 80 and I think it's the new default port in kamal 2. But you can try to specify port...

@guilhermecaixeta or you can also add thruster. You will need some change in the entrypoint file.

@guilhermecaixeta It looks like you have a new error message : `host settings conflict`. I'm not sure, but maybe you have many deployments with similar configuration and between some trying,...

@kishaningithub I think the app boot sequence needs a health check anyway, event with `kamal-proxy` off. https://github.com/basecamp/kamal/blob/main/lib/kamal/cli/app/boot.rb#L54C7-L 60C9 I think the health check is mandatory to release the deployment's lock....

> @BarnabeD But the problem is they have removed the health check from the global config in kamal 2 and made it to be part of "proxy". When we set...