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
plumber 1.2.2 overrides the swagger api url with 127.0.0.1 which causes swagger to become unavailable inside docker containers, even if the api works.
I'm aware this problem has been reported and fixed in the past, but it seems it reappeared. After looking through the plumber code, options(plumber.apiURL = paste0('http://0.0.0.0:1234')) is a serviceable workaround. please note it only works when setting apiURL, apiHOST, apiPORT, etc are NOT enough to fix this.
edit: overriding plumber.apiURL seems to break the url generation inside swagger (e.g. you can no longer execute the examples), so it's not a serviceable workaround.
The text was updated successfully, but these errors were encountered:
plumber 1.2.2 overrides the swagger api url with
127.0.0.1
which causes swagger to become unavailable inside docker containers, even if the api works.I'm aware this problem has been reported and fixed in the past, but it seems it reappeared.
After looking through the plumber code,options(plumber.apiURL = paste0('http://0.0.0.0:1234'))
is a serviceable workaround. please note it only works when setting apiURL, apiHOST, apiPORT, etc are NOT enough to fix this.edit: overriding
plumber.apiURL
seems to break the url generation inside swagger (e.g. you can no longer execute the examples), so it's not a serviceable workaround.The text was updated successfully, but these errors were encountered: