Replies: 1 comment
-
|
Hi @DaniG2k, Kamal Proxy doesn't currently have a way to do this, so at the moment what you're doing is a good workaround. However, it does seem like something we could be handling at the proxy layer, so yes I'd consider this a potential feature. There is an open PR at the moment that would cover this on the proxy side (#153) so once we land that we'd have a feature that we can then expose in Kamal. |
Beta Was this translation helpful? Give feedback.
0 replies
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Uh oh!
There was an error while loading. Please reload this page.
Uh oh!
There was an error while loading. Please reload this page.
-
Hi all,
I’m unsure if this is the best place to ask (please let me know if I should post in
basecamp/kamalinstead), but I’m trying to set up a 301 redirect fromwww.myapp.comtomyapp.com(www to apex domain) for a Rails app deployed with Kamal. I noticed a related discussion in the main Kamal repo about redirecting the other way (apex to www, #1214), but my question is specific to www-to-apex and whetherkamal-proxycan handle it.Currently, I’m handling this in my Rails
routes.rbfile:This works, but I’m wondering if
kamal-proxycan manage this redirect at the proxy level for better performance (avoiding the app layer). Is there a way to configurekamal-proxy(e.g., viadeploy.ymlor command-line options) to handle www-to-apex redirects? If not, is this a potential feature, or should I stick with the Rails approach?Thanks for any guidance!
Beta Was this translation helpful? Give feedback.
All reactions