I think you should put the weewx.conf into /etc/apache2/sites-available/ The run sudo a2ensite (this will enable the site) Then run: sudo systemctl restart apache2.service
I don't know what system you are running apache on but the above should work with Ubuntu (debian) On Sunday, 22 November 2020 at 06:47:10 UTC+11 vince wrote: > You always want to look at your logs for both syslog and apache for the > gory details. > > There are a couple alternate ways to get there.... > > - edit weewx.conf to tell it where to write its html to > - at the top of the [[StandardReport]] section in weewx.conf, edit > HTML_ROOT to point to /var/www/html which is where Apache thinks the > web > root is (weewx restart required) > - or point the apache DOCROOT at weewx's tree > - rename /var/www/html and create a symlink pointing to > /home/weewx/public_html (no apache or weewx restarts needed) > - or point the weewx's HTML_ROOT at apache's tree > - rename /home/weewx/public_html and create a symlink pointing to > /var/www/html (weewx restart required) > > FWIW, I use the second method here but that's just how I chose to do it. > > -- You received this message because you are subscribed to the Google Groups "weewx-user" group. To unsubscribe from this group and stop receiving emails from it, send an email to [email protected]. To view this discussion on the web visit https://groups.google.com/d/msgid/weewx-user/bf9f08d5-0a2e-4a7e-b48b-78175bbaa3fcn%40googlegroups.com.
