Optimization exercise: how would we turn the output of tools/wwwdocs.rb get_annotated_scan(...) into a nightly generated /public/whimsy-tools.json? Side effect: learning more about whimsy architecture.
* Inputs (all public files): - /www/**/*.cgi where line =~ ... PAGETITLE = ... - whimsy-vm4.apache.org.yaml['vhosts_whimsy::vhosts::vhosts']['whimsy-vm-443']['authldap'] * Output (which would be sucked in by /www/committers/tools.cgi): - /www/public/whimsy-tools.json * Questions: - Why are the scripts that generate /public inside /www/roster, instead of being in /tools? Mere history, or a specific reason? - Does one *need* an ASF::module to wrap the data model, or can the existing generation code in wwwdocs.rb just be used as-is, wrapped in sufficient calls to public_json_common.rb to handle the 'write file only if json data changed' bits? - Better suggestions to do this? I know writing the .json to /public maybe premature optimization, but I'm also thinking there might be other uses of this data as well, meaning having a URL with the data is useful. -- - Shane https://www.apache.org/foundation/marks/resources
