Lack of ssl routine

[oleua]

I have inspected nginx config file and found out that there's no ssl routine present there by now. There should be added templates of ds.conf.tmpl, ds-ssl.conf.tmpl which will build on the fly ds.conf file.

Of course, there should be added/generated certificates.

[juliusknorr]

Thanks for your feature request. I'm curious to hear about how you would deploy it. Would the document server container directly handle ssl? In most setups I've seen there was a reverse proxy that would handle SSL termination?

[oleua]

Normally, there should be a generated ssl certificate per each instance, which confirms its security, as the instance could be located remotely, as it can serve several platforms.

As you may know, even if it is in a docker, I cannot use eo on the non-secure port together with nextcloud on a secure port. There should be some proxy relaying the requests (apache or nginx), or to have self-generated or obtained certificates (eg Let's encrypt) which can be used to guarantee the secure connection (integration) between platforms.

What do you think of that?