On Saturday, 10 December 2016 10:58:35 UTC, Bill Morrow wrote: > > On Wednesday, 7 December 2016 09:47:58 UTC-4, mwall wrote: >> >> standard practice is to put a new driver in the user folder (not the >> weewx/drivers folder) so that you can update weewx without losing your >> modifications. unless you're working on core weewx code, this approach >> tends to be easier than maintaining a separate fork or branch. >> >> you could make it easier to manage (for yourself) and share (for others) >> if you put the mqtt driver into its own repository (i.e., just the >> wxMesh.py file). that way you don't have to duplicate the entire weewx >> codebase. >> >> even better, package the mqtt driver as a weewx extension so it can be >> easily applied to any weewx installation. packaging should be pretty easy >> - see the fileparse driver as one example, and the customization guide for >> details: >> >> http://weewx.com/docs/customizing.htm#extensions >> > >> if any of that is unclear or difficult to understand, please let us know >> so we can make it better! >> >> m >> > > Thank you Matthew. I thought it was a mistake to fork all of weewx on > github. I'll work on making it an extension instead. > > I need to understand git and github better. I come from the close shop > industrial world, where we've used everything from sccs to Mercurial. > > To start with, should I delete that entire weewxMQTT repository, and start > over with only my new file(s)? >
Hi Bill, I have just found this thread, it seems to be exactly what I need to feed my esp8266 sensors into weewx via MQTT. Please..... Have you put your work on github again?, if so where? many thanks regards Patrick -- 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.
