Use a single port for http - queries and downloads

[gordonwatts]

CUrrently we have two webservers. Instead, do a single webserver/end point to serve everything. This will have the side-benifit of making it possible to run on binder

[gordonwatts]

Linsey suggested using nginx, which we are already using, as a reverse proxy:

location /backend1/ {
    proxy_pass http://backend:1000/;
}
location /backend2/ {
    proxy_pass http://backend:2000/;
}

[gordonwatts]

The raw config file:

root@test-func-adl-http-results-69d6758589-92w9g:/etc/nginx# cat conf.d/default.conf                 server {
    listen       80;
    server_name  localhost;

    #charset koi8-r;
    #access_log  /var/log/nginx/host.access.log  main;

    location / {
        root   /usr/share/nginx/html;
        index  index.html index.htm;
    }

    #error_page  404              /404.html;

    # redirect server error pages to the static page /50x.html
    #
    error_page   500 502 503 504  /50x.html;
    location = /50x.html {
        root   /usr/share/nginx/html;
    }

    # proxy the PHP scripts to Apache listening on 127.0.0.1:80
    #
    #location ~ \.php$ {
    #    proxy_pass   http://127.0.0.1;
    #}

    # pass the PHP scripts to FastCGI server listening on 127.0.0.1:9000
    #
    #location ~ \.php$ {
    #    root           html;
    #    fastcgi_pass   127.0.0.1:9000;
    #    fastcgi_index  index.php;
    #    fastcgi_param  SCRIPT_FILENAME  /scripts$fastcgi_script_name;
    #    include        fastcgi_params;
    #}

    # deny access to .htaccess files, if Apache's document root
    # concurs with nginx's one
    #
    #location ~ /\.ht {
    #    deny  all;
    #}
}