Running as https, under nginx or custom domain

[AlessioGr]

Hey,

how can I run this with https enabled, either via nginx or a custom domain? I found no information regarding this in the readme.

Do I need to change the Dockerfile to use the nginx alpine image? And what would I do next?

[VincentSC]

Via nginx-proxy.

Here's the docker-compose:

version: "3"

services:
  languagetool:
    image: erikvl87/languagetool
    container_name: languagetool
#    ports:
#      - 8010:8010
    environment:
      - VIRTUAL_HOST=${DOMAIN}
      - VIRTUAL_PORT=8010
      - LETSENCRYPT_HOST=${DOMAIN}
      - langtool_languageModel=/ngrams
      - Java_Xms=512m
      - Java_Xmx=1g
    volumes:
      - ./volumes/ngrams:/ngrams
    networks:
      - nginx-proxy

networks:
  nginx-proxy:
    external:
      name: nginx-proxy

Set the domain in .env. Be sure to have nginx-proxy set up correctly, including the nginx-proxy network

[leerobert]

@VincentSC any chance you could be a little more specific with the full docker-compose.yml including the nginx-proxy configuration? Or maybe some kind of step by step?

Did you not use https://github.com/nginx-proxy/acme-companion to get SSL support?

[Erikvl87]

Closed due to inactivity.

[VincentSC]

@leerobert Totally missed this.

Correct. I've been using nginx for over a decade, hence my preference. There are multiple solutions (using Nginx, Apache, Lighttpd), but they all work the same:

• the public facing docker is connected to an external network
• a reverse proxy detects a new docker on the network via the variables, and self-configures the internal IP to the given domain name. Some reverse proxies require the config to be centralized, though.
• let's encrypt kicks in. Regularly it's updated.

In .env I set DOMAIN=lt.domain.com - I tend to make generic dockers, so I can more easily test without editing docker-compose.yml.