Hello, I have attempted to use this on a rhel system (Scientific Linux 7.4). I am using Apache 2.4.6 and PHP 7.2.11. I have successfully loaded the basic php structure provided in the latest release (W34-WE(131018), however I am unable to resolve a few problems.
First, when I try to access the settings1.php through an internet browser, I get a permission error that Sean got. I have double checked that all permission in my html root are recursively 775 (/var/www/html), so I'm not sure why I get this error. I am able to directly edit the settings1.php file, and most of the changes I have made are reflected on the page. Second, a few changes I am making to the settings1.php do not seem to be working. The big one is the realtime.txt directory which I left as the default (/var/tmp/realtime.txt). I have checked both my weewx.conf and the settings1.php to be sure the path is correct, and it is. I have also verified that realtime.txt is updating every 2.5 seconds (tail -f /var/tmp/realtime.txt). Yet this does not seem to be working on the web page. Third, the API keys that I had generated do not seem to be changing anything (CheckWX & Dark Sky) Check out http://canyoneastweather.ddns.net:303/ to see what I mean. Thanks for your help. -Aaron On Tuesday, October 9, 2018 at 3:55:14 AM UTC-5, [email protected] wrote: > > I think that we can all agree that the real strengths of weeWX are what > goes on 'under the hood (or the bonnet for a Brit like me)', its sheer > adaptability and a huge community working out solutions together. > > I came to weeWX after years of being a Cumulus user (another excellent > software) but came to a grinding halt when changing to unsupported Weather > Station. It was weeWX to the rescue along with the HP1000 driver and I was > back up and running. In my Cumulus days I had been an early adopter of the > excellent weather34 template, designed and owned by Brian Underdown. This > was originally designed for use with Cumulus as a single dashboard concept > where everything is accessible from a single web page. So could I use the > template with weeWX, yes by deploying the CRT extension to generate a > realtime.txt file. > > Now I wanted it to do more, I am not a coder so it takes me a bit longer > to discover the snippets of code that I need to make things happen and this > is where this forum and others became a valuable resource for myself along > with contributions and technical support from others. A big thanks here to > David Marshall who has rescued me on more than one occasion. > > Recently Brian Underwood took the decision to only support the Meteobridge > version of his template going forward. However, he was very happy for the > other versions of the template to hosted and maintained by others. On this > basis, both the weeWX and Cumulus versions live on. I am now hosting the > weeWX version and actively maintaining it in the spirit of Brian's original > concept. You can find it here: - > > > https://github.com/steepleian/weather34-Home-Weatherstation-Template-weeWX-adapted > > The latest version is now using the weeWX archive database to generate the > pop-up CanvasJS charts instead of relying on Weather Underground. The setup > guides are provided for general guidance only due to the multitude of ways > weeWX can be setup by individual users. > > I would like to re-iterate that although Brian Underdown is very happy for > this version to exist and be maintained, he offers no support whatsoever > for this version. Any requests to do so will remain unanswered. Please > respect Brian's wishes in this respect. Any issues should be directed to > this forum. > > My own current version of the template shows additional features which may > be included in future updates if there is sufficient demand. It can found > here https://claydonsweather.org.uk > > When used with a smartphone or a narrow browser window, the page morphs > into a slimline mobile version. > -- 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.
