Nginx sends the response as an application/octet-stream so browsers try
to download it.

Address the issue after shore.co.il was moved to ns4.

Reply with the client's public facing (internet) IP.

In line with the master branch.

Should be faster. Just static files anyway.

2 services, the registry under /v2/ and a browsable frontend under /.
Allow uploading only from a local IP address (from the host itself).
I think that this way I can avoid having authentication and instead just
build and upload on the host.

This reverts commit d4d48591 but not
completly, just the parts needed for the services moved to ns4.

This reverts commit 7885e91e.

So I can get the real client IP in the service.

If the acme challenge is in a location block but the default redirection
is not, the default always takes precedence (Nginx won't resolve the
order between the different directives, but it will between different
location blocks).

Snippet to redirect to https if Upgrade-Insecure-Requests is set in the
request.

How can I miss the opportunity to interfere with Google in any way?

Login every 4 hours isn't reasonable. A week seems better to me.