Description of the enhancement

Support base href and config path variables in the environment for better docker deployment (same as SKOSMOS_SPARQL_ENDPOINT) .

Who are the users that would benefit from the enhancement and how?

Sysadmins and devops

What new functionalities would the enhancement make possible?

This would allow admins to defined config path and base href in the container environment. This way it would be easier to deploy a skosmos server and make it match the base href of the reverse proxy.

Example docker-compose.yml snippet

  ...

  skosmos:
    image: quay.io/natlibfi/skosmos:latest
    networks:
      - default
      - traefik
    environment:
      - SKOSMOS_SPARQL_ENDPOINT=http://varnish:80/skosmos/sparql
      - SKOSMOS_BASE_HREF=https://${SKOSMOS_BASE_URL}
      - SKOSMOS_CONFIG_NAME=/etc/skosmos/config.ttl
    volumes:
      - ./config.ttl:/etc/skosmos/config.ttl:ro
    labels:
      - traefik.enable=true
      - traefik.http.routers.skosmos.rule=Host(`${SKOSMOS_BASE_URL}`)
      - traefik.http.services.skosmos.loadbalancer.server.port=80
...

Why is the enhancement important?

Easier docker setup.