You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Remove GENERATOR_HOST and pull scheme/host/port from request details.
GENERATOR_HOST itself adds some other complexity, for example if a single nginx configuration is used to proxy multiple addresses to the same instance of the service (e.g. api.example.com, example.com, and latest.example.com could point to the same service via single nginx configuration, but would all require separate processes due to GENERATOR_HOST.
The text was updated successfully, but these errors were encountered:
I found that this condition is really only a problem when running from within a docker container. Setting the default value to an empty string appears to fix the bug. Running the service from command line or other means without the GENERATOR_HOST variable also works as expected. I opened #3289 to fix and add some documentation around the usage of the variable.
Bug Report Checklist
Description
The
GENERATOR_HOST
environment variable in openapi-generator-online isn't necessary and can't accurately be set in some cases.openapi-generator version
all?
OpenAPI declaration file content or url
Command line used for generation
n/a
Steps to reproduce
GENERATOR_HOST
would need to be passed atdocker run
, which isn't possible when docker randomizes port assignments.See
Related issues/PRs
#3287
Suggest a fix
Remove
GENERATOR_HOST
and pull scheme/host/port from request details.GENERATOR_HOST
itself adds some other complexity, for example if a single nginx configuration is used to proxy multiple addresses to the same instance of the service (e.g.api.example.com
,example.com
, andlatest.example.com
could point to the same service via single nginx configuration, but would all require separate processes due toGENERATOR_HOST
.The text was updated successfully, but these errors were encountered: