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
Usually, we avoid any references to IP addresses and ports anywhere in the code.
The exception is for the webapp, which as far as I can tell has no way of magically working out the IP/Domain and Port of the API gateway. Remember the webapp is Angular and therefore 100% client side.
The way I'm implementing this is: (there may be a better way, will learn about this over time)
Angular client will get the IP address/domain of where it was served from (simple Javascript)
We will standardise on port 8080 in production, and port 30000 for local-microservice.
This keeps things simple.
(there must be a better way!)
The text was updated successfully, but these errors were encountered:
Usually, we avoid any references to IP addresses and ports anywhere in the code.
The exception is for the webapp, which as far as I can tell has no way of magically working out the IP/Domain and Port of the API gateway. Remember the webapp is Angular and therefore 100% client side.
The way I'm implementing this is: (there may be a better way, will learn about this over time)
This keeps things simple.
(there must be a better way!)
The text was updated successfully, but these errors were encountered: