There is a huge webpage devoted to the subject: *The WeeWX Customizing Guide* <http://weewx.com/docs/customizing.htm>.
Be sure to see the webpage on documentation <http://weewx.com/docs.html> to see what else you might be missing. -tk On Tue, Jan 2, 2018 at 1:44 AM, Cycle London <[email protected]> wrote: > I thought of that - rsyncing the data over to my production box, but I'm > pretty paranoid about having anything experimental on that. I snapshot the > hell out of it if I so much as update a Horde module. > > Anyway, I've done the proxy thang, so technically, the Pi is now invisible > from the outside world - and runs over https, so bonus. > > Can someone now point me to how to change the appearance of the site, and > I'll stop bothering you all? :) > > On 2 January 2018 at 09:07, Andrew Milner <[email protected]> > wrote: > >> You could always have the web server somewhere other than on the rpi and >> then just use weewx/rpi to build pages in public_html (using SQLite as the >> database perhaps), and ftp the buil;t pages to your real protected >> webserver wherever it may be - on your lan or maybe even on external >> servers. This would mean you did not need to protect/open ports/firewall >> etc the rpi as it would only ever output to elsewhere and never have to >> handle incoming connections. >> >> >> >> >> >> On Tuesday, 2 January 2018 10:58:59 UTC+2, Cycle London wrote: >> >>> This is incredible - it works. Thank you. Forgetting the soft link >>> from the public_html directory. Duh! >>> >>> Priorities now are : >>> >>> 1. customization. I want dials rather than a table. Is this in the >>> customization guide? >>> 2. running proxy so that I don't need to have port number after the URL >>> 3. adding my SSL certificates >>> 4. securing the installation. The Pi sits on a LAN that also has my >>> production Atlassian, MX and horde.org servers on it. So getting >>> iptables up and running is a priority. Oh, wait. It's firewalld isn't it? >>> Sigh. Something else to learn. Can't wait to retire. :-P >>> >>> Thank you for all of your help. >>> >>> On 2 January 2018 at 00:13, Les Niles <[email protected]> wrote: >>> >>>> BTW, I run on mysql but I think there’s also a permission issue in >>>> creating the sqlite database file when running non-root, solved by >>>> pre-creating the file and setting its ownership. >>>> >>>> -Les >>>> >>>> On 1 Jan 2018, at 16:05, Les Niles <[email protected]> wrote: >>>> >>>> Under what user ID are you running weewx? I install from the debian >>>> package on a Raspberry Pi, and have to work around some permission issues >>>> related to running non-root. IIRC, there are two: >>>> * weewx can’t create the PID file in /var/run, causing it to exit >>>> almost immediately. My hack is putting lines in the startup script >>>> (actually in /etc/defaults/weewx) to touch /var/run/weewx.pid and to chown >>>> that file to the weewx user ID. >>>> * weewx can’t create the html, etc. files because it can’t write to >>>> /var/www/html. Solution is to manually create weewx's html directory and >>>> make that directory owned by the weewx user ID. >>>> >>>> -Les >>>> >>>> >>>> On 1 Jan 2018, at 9:25, Cycle London <[email protected]> wrote: >>>> >>>> Yeah, I'm a friend of UNIX. 30 years of administering first Solaris, >>>> then RHEL and Slackware, FreeBSD, HP-UX and SCO UNIX. But zero knowledge >>>> of Python, so completely unable to troubleshoot this. And most of my days >>>> now are taken up with CentOS and RHEL, and I don't use apache2. >>>> >>>> Anyway, the system now appears to be running. >>>> >>>> root@weather:~# ps -ef | grep weather >>>> avahi 322 1 0 2017 ? 00:00:17 avahi-daemon: running >>>> [weather.local] >>>> >>>> Still nothing in the HTML_ROOT however. That's fine I guess since it's >>>> aliasing to /home/weewx/public_html but what should the permissions be on >>>> that directory? >>>> >>>> drwxr-xr-x 6 root root 4096 Jan 1 17:20 public_html >>>> >>>> And lynx localhost/weewx` still returns a 404 (with nothing in the >>>> httpd log but just that: 404). >>>> >>>> Trying to hit the Pi on http from my Mac also returns a 404, which >>>> isn't anything to do with name resolution as the Pi is in DNS and I can >>>> ping it on its FQDN. >>>> >>>> Stumped, now. >>>> >>>> >>>> On 1 January 2018 at 15:45, mwall <[email protected]> wrote: >>>> >>>>> On Monday, January 1, 2018 at 9:33:55 AM UTC-5, Cycle London wrote: >>>>>> >>>>>> Now I seem to have broken the entire thing. I decided to try the >>>>>> python installation method, so ran `apt-get remove weewx` and then >>>>>> downloaded the tarball to try a manual installation. >>>>>> >>>>>> This time, there is content in /var/www/html but hardly anything >>>>>> (except user) under /usr/share/weewx. Everything is under /home but even >>>>>> when I place the new driver into /usr/share/weewx/user and modify the >>>>>> configuration file, I still get... >>>>>> >>>>> >>>>> welcome to "unix is user-friendly, it is just picky about who its >>>>> friends are" >>>>> >>>>> there are a few things you should understand about debian linux and >>>>> about python. >>>>> >>>>> 1) setup.py and apt-get are not compatible >>>>> >>>>> you really should use one or the other. the weewx wiki has >>>>> instructions about how to change from one to the other. >>>>> >>>>> https://github.com/weewx/weewx/wiki/How%20to%20convert%20fro >>>>> m%20setup.py%20install%20to%20debian%20install >>>>> >>>>> 2) how to use apt-get >>>>> >>>>> apt-get install weewx >>>>> apt-get remove weewx >>>>> apt-get purge weewx >>>>> >>>>> install does both initial installation as well as updates (but not >>>>> upgrades) >>>>> >>>>> three different commands which do three different things. remove does >>>>> not destroy any configuration files, especially not any that you have >>>>> modified. it also does not remove any debconf values. >>>>> >>>>> purge deletes all configuration files and debconf values. it does not >>>>> touch any weewx data (nominally /var/lib/weewx/weewx.sdb) >>>>> >>>>> for the state diagrams, see: >>>>> >>>>> https://www.debian.org/doc/debian-policy/#maintainer-script-flowcharts >>>>> >>>>> we try to test installer stuff, but as you can see the surface area >>>>> for testing is massive. so if you can clarify any procedures you make >>>>> that >>>>> result in unexpected results, that makes it more likely that someone will >>>>> fix it. >>>>> >>>>> 3) python coders are lazy, and that is a good thing >>>>> >>>>> weewx does not create a database until it has to use it >>>>> >>>>> weewx does not create the html directory or any files in that >>>>> directory until it has something to write. in a default installation, >>>>> that >>>>> means you will not see anything until after the first archive interval >>>>> (nominally 5 minutes, but it depends on your configuration). >>>>> >>>>> 4) you almost never need to reinstall the operating system. linux is >>>>> not windows, no matter how much certain redhat employees would like to >>>>> make >>>>> it so. >>>>> >>>>> hope that helps! >>>>> >>>>> m >>>>> >>>>> >>>>> -- >>>>> You received this message because you are subscribed to a topic in the >>>>> Google Groups "weewx-user" group. >>>>> To unsubscribe from this topic, visit https://groups.google.co >>>>> m/d/topic/weewx-user/iGXSDG5XsOQ/unsubscribe. >>>>> To unsubscribe from this group and all its topics, send an email to >>>>> [email protected]. >>>>> For more options, visit https://groups.google.com/d/optout. >>>>> >>>> >>>> >>>> -- >>>> 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]. >>>> For more options, visit https://groups.google.com/d/optout. >>>> >>>> >>>> >>>> -- >>>> 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]. >>>> For more options, visit https://groups.google.com/d/optout. >>>> >>>> >>>> -- >>>> You received this message because you are subscribed to a topic in the >>>> Google Groups "weewx-user" group. >>>> To unsubscribe from this topic, visit https://groups.google.com/d/to >>>> pic/weewx-user/iGXSDG5XsOQ/unsubscribe. >>>> To unsubscribe from this group and all its topics, send an email to >>>> [email protected]. >>>> For more options, visit https://groups.google.com/d/optout. >>>> >>> >>> -- >> You received this message because you are subscribed to a topic in the >> Google Groups "weewx-user" group. >> To unsubscribe from this topic, visit https://groups.google.com/d/to >> pic/weewx-user/iGXSDG5XsOQ/unsubscribe. >> To unsubscribe from this group and all its topics, send an email to >> [email protected]. >> For more options, visit https://groups.google.com/d/optout. >> > > -- > 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]. > For more options, visit https://groups.google.com/d/optout. > -- 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]. For more options, visit https://groups.google.com/d/optout.
