I actually had a fun time learning by "doing," as it's the way that I learn things the best, for better or worse. This is a good project for me as I know what "sudo" does and knew enough to be able to get leafpad (text editor) to edit the config file as an admin. I thought I was doing something wrong by having to do it this way. I didn't see it anywhere in the Wiki that this was the only way to edit the config file. The command in the wiki only would edit the first few generic items like elevation and model/brand. In fact, the default package installed in the GUI for the latest Raspbian Jessie never asked me to configure anything like I expected from reading the Wiki. It just installed and didn't ask me a thing. This entire time, I thought I installed it in the wrong place. Will I need to whitelist anything?
Still not showing up, though... Added my WU URL to the [StdRESTful] [[Station Registry]] section and it is set to "true" Added my LAN IP 192.168.x.x:weewx to the Station_url in [Station] On Saturday, October 8, 2016 at 9:27:29 PM UTC-7, mwall wrote: > > On Sunday, October 9, 2016 at 12:18:29 AM UTC-4, Tim Phillips wrote: >> >> I spent the day trying to get this to work at all am quite proud of it >> "just" working with WU's site. >> > > nice! hopefully most of that time was general learning about pi and linux > rather than fighting weewx. if you were battling weewx, please let us know > so we can fix the sharp edges so the next person does not get as many scars. > > >> So what you're saying is that I should set the "Station" for my personal >> use, using my WU site and I can use the "StdRESTful" for my private use, >> using my WAN IP address? >> > > make the Station.station_url your lan-accessible url, and make > StdRESTful.StationRegistry.station_url your publicly-accessible WU url. > > >> **I had a hard enough time trying to edit the conf. file since the >> package got installed to my "etc" folder on my RPi3 and I ended up using >> "sudo leafpad /etc/weewx/weewx.conf" to edit my config file. I'm sure I >> went wrong somewhere but that's the workaround I eventually found. Does >> that seem right? >> > > you got it. > > there are many editors, including nano, vim, vi, emacs, or even ed. none > of them can edit the system configuration files (the files in /etc) unless > you run them as root. and as you figured out, that is what sudo does. > > m > -- 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.
