Deploy Bold BI as a Sub-Application in Docker Environment
This section explains how to install Bold BI as a Sub-Application in a Docker environment using the docker advance command.
-
Follow this document to deploy the Bold BI application on a Docker environment using the advanced command.
-
After successfully deploying the Bold BI container, edit the
boldbi-nginx-config
file present in the Nginx mount persistent volume path (Example: /var/www/boldbi/nginx ) and change the Bold BI configuration as shown below.Note: You are going to set the subpath as /dashboard.
Example: http://example.com/dashboard
#server { #listen 80; #server_name example.com; #return 301 https://example.com$request_uri; #} server { listen 80; #server_name example.com; #listen 443 ssl; #ssl on; #ssl_certificate /etc/nginx/sites-available/domain.crt; #ssl_certificate_key /etc/nginx/sites-available/domain.key; proxy_buffer_size 128k; proxy_buffers 4 256k; proxy_busy_buffers_size 256k; large_client_header_buffers 4 16k; proxy_read_timeout 300; proxy_connect_timeout 300; proxy_send_timeout 300; send_timeout 300; client_max_body_size 200M; location /dashboard/ { root /application/idp/web/wwwroot; proxy_pass http://localhost:6500/dashboard/; proxy_http_version 1.1; proxy_set_header Upgrade $http_upgrade; proxy_set_header Connection keep-alive; proxy_set_header Host $http_host; proxy_cache_bypass $http_upgrade; proxy_set_header X-Forwarded-For $proxy_add_x_forwarded_for; proxy_set_header X-Forwarded-Proto $scheme; fastcgi_buffers 16 16k; fastcgi_buffer_size 32k; } location /dashboard/api { proxy_pass http://localhost:6501/dashboard/api; proxy_http_version 1.1; proxy_set_header Upgrade $http_upgrade; proxy_set_header Connection keep-alive; proxy_set_header Host $http_host; proxy_cache_bypass $http_upgrade; proxy_set_header X-Forwarded-For $proxy_add_x_forwarded_for; proxy_set_header X-Forwarded-Proto $scheme; } location /dashboard/ums { root /application/idp/ums/wwwroot; proxy_pass http://localhost:6502/dashboard/ums; proxy_http_version 1.1; proxy_set_header Upgrade $http_upgrade; proxy_set_header Connection keep-alive; proxy_set_header Host $http_host; proxy_cache_bypass $http_upgrade; proxy_set_header X-Forwarded-For $proxy_add_x_forwarded_for; proxy_set_header X-Forwarded-Proto $scheme; } location /dashboard/bi { root /application/bi/web/wwwroot; proxy_pass http://localhost:6504/dashboard/bi; proxy_http_version 1.1; proxy_set_header Upgrade $http_upgrade; proxy_set_header Connection keep-alive; proxy_set_header Host $http_host; proxy_cache_bypass $http_upgrade; proxy_set_header X-Forwarded-For $proxy_add_x_forwarded_for; proxy_set_header X-Forwarded-Proto $scheme; } location /dashboard/bi/api { proxy_pass http://localhost:6505/dashboard/bi/api; proxy_http_version 1.1; proxy_set_header Upgrade $http_upgrade; proxy_set_header Connection keep-alive; proxy_set_header Host $http_host; proxy_cache_bypass $http_upgrade; proxy_set_header X-Forwarded-For $proxy_add_x_forwarded_for; proxy_set_header X-Forwarded-Proto $scheme; } location /dashboard/bi/jobs { proxy_pass http://localhost:6506/dashboard/bi/jobs; proxy_http_version 1.1; proxy_set_header Upgrade $http_upgrade; proxy_set_header Connection keep-alive; proxy_set_header Host $http_host; proxy_cache_bypass $http_upgrade; proxy_set_header X-Forwarded-For $proxy_add_x_forwarded_for; proxy_set_header X-Forwarded-Proto $scheme; } location /dashboard/bi/designer { root /application/bi/designer/wwwroot; proxy_pass http://localhost:6507/dashboard/bi/designer; proxy_http_version 1.1; proxy_set_header Upgrade $http_upgrade; proxy_set_header Connection keep-alive; proxy_set_header Host $http_host; proxy_cache_bypass $http_upgrade; proxy_set_header X-Forwarded-For $proxy_add_x_forwarded_for; proxy_set_header X-Forwarded-Proto $scheme; } location /dashboard/bi/designer/helper { proxy_pass http://localhost:6507/dashboard/bi/designer/helper; proxy_http_version 1.1; proxy_set_header Upgrade $http_upgrade; proxy_set_header Connection "upgrade"; proxy_set_header Host $http_host; proxy_cache_bypass $http_upgrade; proxy_set_header X-Forwarded-For $proxy_add_x_forwarded_for; proxy_set_header X-Forwarded-Proto $scheme; } }
-
Modify the InternalAppUrls with the
/dashboard
subpath in both config.json and product.json files present in the Bold BI application persistent volume path location </var/www/boldbi/boldbi_data/configuration> as shown in the following screenshot:product.json
config.json
Note: From version 6.19.14, use the config.json and the config.xml for versions prior to this.
-
Restart the container using the following command.
docker restart <container ID/ container name>
Example: docker restart Bold BI
-
After restarting the application, you can access the Bold BI using the
http://domain-name/dashboard
. -
Refer to the link for application startup.