So that user@shore.co.il chats are done by the Synapse instance.

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.

I'm getting nowhere. I still got an A+, but now I'm marked down because
I don't support TLS 1.2.

Marked as weak in SSL Labs' test.

SSL Labs' test complains that it doesn't offer forward secrecy.

Prettier editing.

Up to now I supported older browsers by supporting older versions of TLS
and cipher suites. I still think it makes sense for my blog, etc. but
not for Nextcloud or GitLab. So here's the first step, make the previous
default SSL configuration be ssl-legacy (split out the common parts to
ssl-common) and next is ssl-modern.

Use the git skeleton file. Apply changes from the new hooks.

It has a hard-coded server name, it should be in the that server's
config.