Skip to content

Host your app

Host for local use


You can run your app locally on your computer as follows:
In the directory: Open the folder where you installed your bokeh app.
This folder contains the file: "serve_bokeh.bat". Run this file from the command line: 

serve_bokeh.bat

Your comandline will show a Bokeh HydroDashboard is started:

2022-10-19 17:19:59,297 Starting Bokeh server version 2.4.3 (running on Tornado 6.1)
2022-10-19 17:19:59,312 User authentication hooks NOT provided (default user enabled)
2022-10-19 17:19:59,322 Bokeh app running at: http://localhost:5003/bokeh
2022-10-19 17:19:59,322 Starting Bokeh server with process id: 25148

Open your web browser and copy the http adress to the browser. In this example: http://localhost:5003/bokeh
If everything went right, the bokeh dashboard is shown in your browser.

The commandline will continue logging. If all goes well without errors:

2022-10-19 17:24:16,445 Qualifiers request in 2.299 sec
2022-10-19 17:24:17,634 Qualifiers parsed in 1.188 sec
2022-10-19 17:24:18,048 Parameters request in 0.391 sec
2022-10-19 17:24:18,064 Parameters parsed in 0.015 sec
2022-10-19 17:24:20,064 Locations request in 1.998 sec
2022-10-19 17:24:20,694 Locations parsed in 0.629 sec
2022-10-19 17:24:20,983 Filters request in 0.280 sec
2022-10-19 17:24:20,985 Filters parsed in 0.000 sec
2022-10-19 17:24:23,179 WebSocket connection opened
2022-10-19 17:24:23,182 ServerConnection created

And your app should then be loaded in the browser:

Host as Web Service (Windows IIS)

Never expose the Bokeh HydroDashboard to the web directly.

Here you can find info on how to route your Bokeh HydroDashboard via Application Request Rerouting (ARR) in a Windows IIS web server.

Installation

  • Install the URL Rewrite package from the downloads section on the IIS website or Microsoft Web Platform Installer.

  • Install the ARR (application request routing) 3.0 module from the downloads section on the IIS website or Microsoft Web Platform Installer.

    Note (!) web-socket routing is only possible from ARR 3.0.

Configuration of IIS

From the left pane, double-click on the main tree node with your server name on it, and from the modules, double-click on Application Request Routing Cache. In the right pane, choose Enable proxy, and set HTTP version to Pass through:

In the left pane, right-click on the website you created and select Explore. Windows explorer will open in inetpub\your_website. Open, or create a new web.config file at this location, so inetpub\your_website\web.config:

You can copy-paste this section:

<?xml version="1.0" encoding="UTF-8"?>
<configuration>
    <system.webServer>
        <rewrite>
            <rules>
                <rule name="Bokeh proxy" enabled="true" stopProcessing="true">
                    <match url="(.*)" />
                    <action type="Rewrite" url="http://127.0.0.1:5003/{R:1}" />
                </rule>
            </rules>
        </rewrite>
    </system.webServer>
</configuration>

Allow web-socket routing

After restarting your IIS the backend-app should be re-routed to the root-adress of your website. If your app runs with content you're done.

If not, you will only see an empty html page without content. In this case you have to enable the WebSocket Protocol in the Add Roles and Features Wizard of your server:

Host for production (NGiNX load balancer)

Bokeh HydroDashboards are scalable. Here we show how we can distribute Bokeh HydroDashboards over multiple proesses using a NGiNX load balancer. With a similar setup you can distribute Bokeh HydroDashboards over (even more) multiple backend servers.

For more background on load-balancing with NGiNX: http://nginx.org/en/docs/http/load_balancing.html

Installation

Download the stable version of nginx for windows, unzip it and put this in a chosen folder.

Configuration of the load balancer

The folder conf contains the configuration file: nginx.conf. We need to change this file to enable load balancing. The example below shows the required configuration if we want to distribute the bokeh app traffic over 4 local hosts (5004, 5005, 5006 and 5007) via the least connection method. The NGiNX server is listening on port 5003. 

events {}

http {
    upstream bokeh {
    least_conn;
    server 127.0.0.1:5004;      # Bokeh Server 0
    server 127.0.0.1:5005;      # Bokeh Server 1
    server 127.0.0.1:5006;      # Bokeh Server 2
    server 127.0.0.1:5007;      # Bokeh Server 3
    }
    server{
    listen: 5003;
    location / {
        proxy_pass http://bokeh;
        proxy_set_header Upgrade $http_upgrade;
        proxy_set_header Connection "upgrade";
        proxy_http_version 1.1;
        proxy_set_header X-Forwarded-Proto $scheme;
        proxy_set_header X-Forwarded-For $proxy_add_x_forwarded_for;
        proxy_set_header Host $host:$server_port;
        proxy_buffering off;
        }
    }
}

Start Bokeh HydroDashboards

Your nginx configuration is now ready. Open the bokeh app folder, here you find the file: "serve_bokeh-loadbalancer.bat". If you view this file, you will see it serves the bokeh application from Run this file from the 4 local hosts (5004,5005,5006 and 5007): 

start bokeh serve bokeh --port 5004 --allow-websocket-origin *   
start bokeh serve bokeh --port 5005 --allow-websocket-origin *   
start bokeh serve bokeh --port 5006 --allow-websocket-origin *   
start bokeh serve bokeh --port 5007 --allow-websocket-origin *

Run this file from the command-line as follows:

serve_bokeh-loadbalancer.bat

Start the NGiNX load balancer

Start the nginx.exe (go to the folder where you installed nginx)

If you open the listening port: 5003 (see nginx conf file) in your web browser (http://localhost:5003/bokeh), you have your local load balanced website. Because port: 5003 is redirected to the root-adress of your website (see the last section "(Behind web service (Windows IIS)"), your root website is also load balanced.