My description was wrong.
the steps generating a clientraw file are as follows:
1) by pressing "save" on the "WD live" page templates named "/home/meteohub/clientraw*.conf" are generated.
2) when cron schedule starts generation of a clientraw file, the template gets filled with real data (according the standard HTML template replacement mechanisms in Meteohub) and stored at "/public/graphs/clientraw*.out"
3) immediately after that this file is copied to "/public/myweb/uploads/clientraw*.txt" to have it permanent for local use (the WD-Live applet integrated in Meteohub for example). The name of the file is predefined, to make sure that the WD-live applet can make use of it.
4) then the "clientraw*.out" file is moved from the "/public/graphs/" folder to "/public/uploads/" folder and renamed as specified in the file name section of the "graph upload" page.
5) Next time the ftp upload is starting, all files from "/public/uploads/" folder are transferred to the web server via FTP and are deleted in the /public/uploads/" folder.
puhhh... done.
WD-live and VP2 bugs ** solved **
Moderator: Mattk
-
- Platinum Boarder
- Posts: 873
- Joined: Fri Jan 25, 2008 6:27 pm
- Location: Isle of Skye, Scotland
Re:WD-live and VP2 bugs ** solved **
Thanks for outlining the process. :)admin wrote:the steps generating a clientraw file are as follows:
<SNIP>
puhhh... done.