Tom, Will do. Thanks for the reply. Your time and work on Weewx is appreciated.
Regards, Anthony On Friday, January 13, 2017 at 1:25:35 PM UTC-5, Tom Keffer wrote: > > If you're just experimenting, you need not install it at all. Just go into > the directory where you cloned weewx, and run it directly from there, > giving a path to your weewx.conf file. For example, > > cd ~/git/weewx > ./bin/weewxd /etc/weewx.conf > > -tk > > On Fri, Jan 13, 2017 at 9:58 AM, wxwatching <[email protected] > <javascript:>> wrote: > >> Ok, I installed git and cloned a copy of Weewx to my RPi2. Do I install >> it using the setup.py method? >> >> Thanks, >> Anthony >> >> On Friday, January 13, 2017 at 9:00:05 AM UTC-5, mwall wrote: >> >>> On Friday, January 13, 2017 at 8:12:22 AM UTC-5, wxwatching wrote: >>>> >>>> mwall, >>>> >>>> Thanks for the info. I don't suppose there is a date set yet for that >>>> release? If it is still sometime away, I am not adverse to install a >>>> development version, although I have never installed from github and am >>>> not >>>> quite sure how to go about that. >>>>> >>>>> >>>>> >>> usually it is pretty safe to use what is on the master branch. we try >>> to never 'break' the master, but sometimes bugs happen. >>> >>> really disruptive changes happen on a branch so they can be tested >>> first. for example, there is a lot of activity right now on the >>> 'development' branch. >>> >>> there is not yet a date set for the 3.7 release. there will probably be >>> a lengthy public testing period before 3.7 is ready to replace 3.6. >>> >>> if you want to run from code directly from master, download the zip file >>> from github (click the green 'clone or download' button and select >>> 'Download ZIP'). unzip it, then install using the setup.py approach. deb >>> and rpm packages are only available once we get into the last stages of >>> testing a release. >>> >>> if you want to keep updated with the latest changes from master, then >>> use 'git' to clone the repository and to update your copy over time. >>> details for doing that would take more than a couple of sentences. >>> >>> if you are playing with unstable code (yours or that of someone else), >>> be sure to backup your database, and keep a copy of your working weewx >>> around in case you want to roll back. >>> >>> its pretty easy to switch back and forth from one version of weewx to >>> another, but probably not something you want to do on a production system. >>> >>> 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] <javascript:>. >> 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.
