I have a very similar question as this one.
I do have an Angular application that collects data which are then processed via a REST Api. I can happily dockerize both
Your baseURL is hardcoded to localhost. For "global" deployment you would need to change the baseURL to point to the global endpoint of your REST api. That will require you to know the global endpoint and it would need to be static.
Another option would be to set baseURL to /api for prod and configure the angular nginx to proxy /api to your REST api. You would need to link the containers for that to work but wouldn't need to expose the public port on the REST api container, it will only be proxied through nginx.
I use the nginx proxy option for my projects and use docker-compose to handle all linking and inter-container communication stuff.
Example docker-compose.yml and nginx.conf files. This is taken from what I'm currently using, think it should work for you.
docker-compose.yml
version: '3.4'
services:
nginx:
container_name: nginx
image: form_angular
build:
context: .
dockerfile:
ports:
- 8088:80
networks:
- my-network
restapi:
container_name: restapi
image: form_rest
build:
context: .
dockerfile:
networks:
- my-network
networks:
my-network:
driver: bridge
nginx.conf:
events {
worker_connections 1024;
}
http {
upstream api {
server restapi:3000;
}
server {
server_name nginx;
root /usr/share/nginx/html;
index index.html;
include /etc/nginx/mime.types;
location /api/ {
proxy_pass http://api;
proxy_http_version 1.1;
proxy_set_header Upgrade $http_upgrade;
proxy_set_header Connection 'upgrade';
proxy_set_header Host $host;
proxy_set_header X-Real-IP $remote_addr;
proxy_set_header X-Forwarded-For $proxy_add_x_forwarded_for;
proxy_set_header X-NginX-Proxy true;
proxy_cache_bypass $http_upgrade;
}
location /assets/ {
access_log off;
expires 1d;
}
location ~ \.(css|js|svg|ico)$ {
access_log off;
expires 1d;
}
location / {
try_files $uri /index.html;
}
}
}