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
Currently whenever I deploy to AWS, it will destroy the old container, and form a new one. This means a new IP address will need to be assigned to the new container and this will need to be updated manually in code.
The usual solution is to implement a load balancer, but this is a lot of tech and expense for a small problem.
There may be other solutions available, e.g. something called CloudMAP, or JV said maybe using a domain name
Needs research
The text was updated successfully, but these errors were encountered:
Currently whenever I deploy to AWS, it will destroy the old container, and form a new one. This means a new IP address will need to be assigned to the new container and this will need to be updated manually in code.
The usual solution is to implement a load balancer, but this is a lot of tech and expense for a small problem.
There may be other solutions available, e.g. something called CloudMAP, or JV said maybe using a domain name
Needs research
The text was updated successfully, but these errors were encountered: