Running operational services

EDITO Service API (and its UI as part of the datalab) allows users to easily and intuitively design and build Digital Twin Ocean-related applications; such as tools, decision-making apps (What-If applications), or complex stacks for data-science and artificial intelligence studies.

While the definitions of “operational” and “operability” is use-case dependent, the EDITO Service API provides some capabilities to increase the quality of the services deployed by the users; such as custom permanent URLs and instance replication to increase the availability (crash resiliency, heavy load handling, continuity of service during upgrade, etc.).

Hence, a user can, on EDITO, achieve to deploy and operate an application for a community on a daily basis. In any case, the service cannot expect a higher availability than the EDITO platform itself which is limited by Cloudferro WAW3-1 region availability. At some point, and depending on the operational needs, the user would consider switching to another infrastructure that provides lower levels or deeper levels of configuration.

Integration in your custom domain

If you deployed a service permanently on EDITO at https://my-service.lab.dive.edito.eu, and you wish to reach it from a subdomain that you own, like https://my-service.my.domain, you can configure your ingress controller to enable a permanent redirection. Here is an example with nginx:

# /etc/nginx/sites-available/my-service.my.domain.conf

server {
    listen 80;
    server_name my-service.my.domain;
    # Redirect all HTTP requests to HTTPS with a 301 Moved Permanently response.
    return 301 https://my-service.my.domain$request_uri;
}

server {
    server_name my-service.my.domain;
    include snippets/ssl.conf;

    access_log /var/log/nginx/my-service.my.domain_access.log;
    error_log /var/log/nginx/my-service.my.domain_error.log;

    location / {
        proxy_pass 'https://my-service.lab.dive.edito.eu/';
    }
}