-
|
Why do we have the {profile} placeholder in the route endpoint when the profile is statically decided during the extract phase? Was there (or is there) a plan to support multiple profiles and switch dynamically, or is there another reason for this? |
Beta Was this translation helpful? Give feedback.
Replies: 1 comment 1 reply
-
|
The placeholder is mostly here for historical reasons. I can't tell whether there was a plan to allow for using it originally but this never has been the case. You can use that though if you're running some kind of proxying to route requests based on profile, there is a sample nginx config example for that somewhere in the closed issues. |
Beta Was this translation helpful? Give feedback.
-
|
Okey, thank you for your answer. |
Beta Was this translation helpful? Give feedback.
The placeholder is mostly here for historical reasons. I can't tell whether there was a plan to allow for using it originally but this never has been the case. You can use that though if you're running some kind of proxying to route requests based on profile, there is a sample nginx config example for that somewhere in the closed issues.