Thomas Many thanks for that very lucid explanation! Just one more thing though - FTP only tries to FTP files in public_html which have a timestamp newer than when FTP last ran and so does not upload css, js, icons etc again - is that correct, and there is no connection between copy generator section and files which are uploaded via FTP?
On Wednesday, 12 September 2018 15:53:17 UTC+3, Thomas Keffer wrote: > > It is a little confusing. Let's walk through the process. > > The set of skins to be run is given in the [StdReport] section of > weewx.conf. > > Skins use *generators* to do their work. The list of generators to be run > for a given skin is given in the [Generators] section of its respective > skin configuration file, skin.conf. > > So, first the [[StandardReport]] skin gets run. In its [Generators] > section, in addition to the CheetahGenerator and the ImageGenerator, it > specifies that the CopyGenerator should be run. The job of the copy > generator is just to move files locally from the skin subdirectory to the > HTML subdirectory. It takes care of simple files, like CSS and JPG, that > don't need to be run through a complicated engine. It just copies them. > Which files to be copied are specified in the [CopyGenerator] section of > the skin configuration file. > > Next, the [[FTP]] skin gets run. In its [Generators] section it specifies > that the FtpGenerator be run. Its job is to copy files *remotely*: from > the HTML directory to your remote webserver. > > Order matters. The Cheetah, Image, and Copy generators must be run first > so the files are in hand in the HTML directory, *then* they can get > copied to the webserver. This is why the FtpGenerator does not appear in > the list of generators to be run in StandardReport --- there may be other > reports to be run, and you want FTP to do its job *after* everything else > is finished. > > So, if you are running multiple skins, each should have its own > CopyGenerator configuration in each skin.conf, specifying which files of > the skin need to be copied over to the HTML directory. > > In weewx.conf, the skins should be listed in their own [[ ... ]] stanza, > followed by the [[FTP]] section. This way the skins will have finished > their job when the FTP section gets run. > > Hope this helps. > > -tk > > On Wed, Sep 12, 2018 at 5:13 AM Andrew Milner <[email protected] > <javascript:>> wrote: > >> I know I should either know the answer, or be able to find it in the docs >> - but I can't. I have been generating my pages and serving them from a >> local apache server on my RPi for a few years using two skins - the >> original Standard skin and a highly modified Bootstrap skin. >> >> I have just decided to upload the public_html directory to an external >> host. >> >> Now my problem: What is the relationship between copyGenerator section >> of weewx.conf and skin.conf and the [[FTP]] section of reports?? >> the FTP section specifies the FTP connection options - does this appear >> just in weewx.conf or in the skins or both places?? >> >> the Copy generator section allows me to copy once or force copy - but >> from where, to where?? Does this section have to appear in all skins for >> which one wishes to FTP files? Does the FTP section have to also appear in >> that skin - or only on weewx.conf or only in Standard/skin.conf?? >> >> I'm totally confused and am sure there is a simple explanation. If I >> was only using one skin I think I could do it - but with two skins (so that >> I can keep things separated) I'm ,lost >> >> >> -- >> 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.
