Generalized Nginx http template

[MitchellShiell]

We need a base nginx configuration that enables us to easily deploy prelude on a server (http). It should support the range of url parameters without issue.

[MitchellShiell]

Http Nginx templates and setup automation script

I've created some nginx configuration setup templates and automations, they can be found here https://github.com/overture-stack/prelude/tree/conductorRefactor/apps/conductor/configs/nginx makes updating configs much quicker

will be merged to main soon

[MitchellShiell]

Swagger Problem

When using the swagger endpoints all request urls get appended to the root url

http://pantrack.genomeinformatics.org/category

where it should point to the service url, in this case

http://pantrack.genomeinformatics.org/lyric/category

when using the url (http://pantrack.genomeinformatics.org/lyric/category
) in the browser it renders the appropriate response:

[
  {
    "id": 1,
    "name": "idmapping"
  },
  {
    "id": 2,
    "name": "sample"
  },
  {
    "id": 3,
    "name": "summary"
  }
]

So what we really need is to somehow make sure swagger uses the correct base url

[MitchellShiell]

Sub-domain update

Surj recommended using subdomains, which tracks with some of our previous implementations. I followed this article to set up lyric as follows (see bottom of nginx config codeblock)

server {
    listen 80;
    listen [::]:80;
    server_name {SITE_NAME};

    # Frontend
    location / {
        proxy_pass http://localhost:3000;
        include proxy_params;
    }

    # Endpoint required by the frontend
    location /api/dataset_1_arranger/ {
        proxy_pass http://localhost:5050/;
        include proxy_params;
    }

    location /api/dataset_2_arranger/ {
        proxy_pass http://localhost:5051/;
        include proxy_params;
    }

    location /api/dataset_3_arranger/ {
        proxy_pass http://localhost:5052/;
        include proxy_params;
    }
   ....
}


    server {
        listen 80;
        listen [::]:80;
        server_name lyric.pantrack.genomeinformatics.org;

            location / {
                proxy_pass http://localhost:3030/;
                include proxy_params;
        }
    
    }

However i may need to update the URL to the /etc/hosts file which i do not believe i have access too.

[MitchellShiell]

Speaking to Yelizar, he informed me that we need to create multiple DNS records within the genomeinformatics.org zone listing these below:

lyric.pantrack.genomeinformatics.org
idmapping-arranger.pantrack.genomeinformatics.org
sample-arranger.pantrack.genomeinformatics.org
summary-arranger.pantrack.genomeinformatics.org
lectern.pantrack.genomeinformatics.org
maestro.pantrack.genomeinformatics.org
es.pantrack.genomeinformatics.org

(upper case characters not accepted in host names)

the updated nginx config is as follows

# Main pantrack site
server {
    listen 80;
    listen [::]:80;
    server_name {SITE_NAME};

    # Frontend
    location / {
        proxy_pass http://localhost:3000;
        include proxy_params;
    }

    # Specific Arranger dataset endpoints that the frontend expects
    location /api/dataset_1_arranger/ {
        proxy_pass http://localhost:5050/;
        include proxy_params;
    }

    location /api/dataset_2_arranger/ {
        proxy_pass http://localhost:5051/;
        include proxy_params;
    }

    location /api/dataset_3_arranger/ {
        proxy_pass http://localhost:5052/;
        include proxy_params;
    }
}

# Lyric API service
server {
    listen 80;
    listen [::]:80;
    server_name lyric.pantrack.genomeinformatics.org;

    location / {
        proxy_pass http://localhost:3030/;
        include proxy_params;
    }
}

# ID Mapping Arranger service
server {
    listen 80;
    listen [::]:80;
    server_name idmappingArranger.pantrack.genomeinformatics.org;

    location / {
        proxy_pass http://localhost:5050/;
        include proxy_params;
    }
}

# Sample Arranger service
server {
    listen 80;
    listen [::]:80;
    server_name sampleArranger.pantrack.genomeinformatics.org;

    location / {
        proxy_pass http://localhost:5051/;
        include proxy_params;
    }
}

# Summary Arranger service
server {
    listen 80;
    listen [::]:80;
    server_name summaryArranger.pantrack.genomeinformatics.org;

    location / {
        proxy_pass http://localhost:5052/;
        include proxy_params;
    }
}

# Lectern service
server {
    listen 80;
    listen [::]:80;
    server_name lectern.pantrack.genomeinformatics.org;

    location / {
        proxy_pass http://localhost:3031/;
        include proxy_params;
    }
}

# Maestro service
server {
    listen 80;
    listen [::]:80;
    server_name maestro.pantrack.genomeinformatics.org;

    location / {
        proxy_pass http://localhost:11235/;
        include proxy_params;
    }
}

# Elasticsearch service
server {
    listen 80;
    listen [::]:80;
    server_name es.pantrack.genomeinformatics.org;

    location / {
        proxy_pass http://localhost:9200/;
        include proxy_params;
    }
}