Nethserver uses a template system for the config files.
In your case, you’ll need to create a file in /etc/e-smith/templates-custom/etc/httpd/conf.d/zz_nextcloud.conf/90customvhost and put your additions there.
With signal-event nethserver-nextcloud-update you can write config files and restart the relevant services.
Developer documentation for additional information:
http://docs.nethserver.org/projects/nethserver-devel/en/latest/index.html
Feel free to ask if you have questions…
Thanks Markus. Perfect. This was the missing link!
I’ll report in another howto.
Cheers, Axel
Of course, but there’s no reason it needs to have its own certificate. Nothing prevents you from having a single cert that includes both your main domain and your virtual host name–up to 100 names on a cert. Make that your default cert, the Nextcloud vhost uses it (because it uses the default cert), and you’re good to go without messing with template fragments and the like.
That isn’t to say I disagree with you; I’d also prefer to have a separate cert for each virtual host. But there’s an easy and secure workaround to your problem.
I’d disagree here; I’d say to copy 10base into templates-custom and make the relevant edits there
You’re right. It may not work with appending the same virtualhost to the conf file.
But copying a fragment should be an exception as you miss future updates of the copied template fragments.