Question

@SergK (I'm also @samrocketman) do you mind if I propose a change which dual purposes the domain SERVER_NAME to also be used as a docker registry?

Background

This would effectively get rid of DOCKER_DEV_NAME, DOCKER_VIRTUAL_NAME, and UPSTREAM_DOCKER_REPO from env.config.

Example nginx config:

upstream nexus {
  server nexus:8081;
}
upstream docker-hosted {
  #port of the hosted docker registry
  server nexus:8082;
}
...
server {
  ...
  location / {
    #proxypass docker registry if docker client is used
    if ($http_user_agent ~ docker) {
      proxy_pass http://docker-hosted;
    }
    #fall back to the web browser (because first proxy_pass wins)
    proxy_pass http://nexus;
    ...
  }
}

Let's say for example, your nexus frontend is hosted at https://nexus.sandbox.example.com/ (per the env.config SERVER_NAME). The above pseudo code nginx.config.tpl would essentially allow the Nexus frontend to be visited by a browser but also allow docker commands with it. It would be pretty seamless.

docker login nexus.sandbox.example.com
docker push nexus.sandbox.example.com/my_docker_image:latest

I got the idea from the Nexus blog on configuring nginx with Nexus.

Regarding the configuration JSON in https://github.com/SergK/nexus3-ssl/tree/master/nexus/json

Is there any easy way to get JSON from my current configuration? How did you build out and write those JSON files? I have been reading Nexus documentation on scripting but it's not really clear to me.

Thanks in advance!