so this would require an “empty” vhost configuration, pointing to some random empty directory for port 80? But wouldnt the certbot automatically create a new 443 vhost config, as it was doing it for all other unsecured domains before, and overwrite the svn config during this process?
And stopping the svn for an SSL update every 2-3 months is not an option at all.
The config of apache svn is standard, like in that tutorial: https://help.talend.com/reader/5r9QMxelU5pRCZnPEI0VcQ/dgHq5LUSMajI3cp1~lp~IQ