-
Notifications
You must be signed in to change notification settings - Fork 978
Description
Greetings. We have had NextCloud highly recommended to us for our LAN storage needs, and a calendar.
We are genuinely dazed by the multiple configuration requirements across multiple README.md instructions.
The basic docker run / docker compose setup launches an insecure https://{ip}:{port} setup.
This setup requires a public Internet DNS server pointing to our local network to receive its SSL certificates.
Why can we not use a local self-signed certificate? Why can we not disable https entirely for an internal LAN?
We know there are many, multiple instruction templates for reduced LAN or and behind nginx setups.
But most of them read much more complicated than should be necessary (e.g. that nginx config) or feel oddly restrictive. If you will do me the appetite of a conversation they simply "feel" unnecessarily complicated, and...?
We have multiple various services running across our local network and the NextCloud model feels... hmm...
Thanks in advance. We can see NextCloud put a lot of work into NextCloud.
