Hi all, trying to deploy dagster behind a multi-purpose load balancer that forwards to different services depending on the path (e.g. example.com/dagster, example.com/app2) makes it inaccessible, dagit logs a

Warning: Invalid HTTP request

whenever I try to open the website. Am I missing some more configuration or is it just not supported? Deploying it under dagster.example.com works fine. And in case it’s not supported, are you planning on supporting it in the future?

theres a flag to

dagit

you can set if you are hosting it on a fixed path prefix,

--path-prefix

Oh sweet, completely missed that 🙂

@alex - Does that mean that this comment is now outdated? https://github.com/dagster-io/dagster/blob/master/helm/dagster/values.yaml#L857

yea the original blame on that line was from before the dagit flag got added but in the context of helm it appears we don’t a helm value to set the

--path-prefix

flag

Ahh, okay, I did start poking around to see if that was set anywhere but didn’t notice it either. I assume it would want to live in this block somewhere? https://github.com/dagster-io/dagster/blob/master/helm/dagster/templates/helpers/_helpers.tpl#L42-L49