cd /www/perl.apache.org/preview/modperl-docs cvs up bin/build -f bin/makeindex (for search)
since a complete site rebuild including pdf generation is a very heavy operation, for efficiency we need to extend the update mechanism to do:
* build + makeindex only if cvs up indicated that things were changed. That means that we need something like VCS::CVS to get the control over cvs.
futher optimizations:
* rerun makeindex only if things under src/ have changed
* run build -df only if things under tmpl/, src/images or lib/ have changed
* otherwise run build -d (without -f), the code will figure out what should be updated by itself.
If we do this, no one will need to ssh to the site and manually update the site.
One thing to think about: what if something goes broken, e.g. someone has committed code to lib/ and didn't manually verify that everything builds properly. Then on the next automatic update, things go kaboom and the site could become unusable. Any ideas how to prevent this? Currently I haven't planned using cvs for the autogenerated site.
Anybody can help me to replace the 4-liner update script with a more elaborate one?
__________________________________________________________________ Stas Bekman JAm_pH ------> Just Another mod_perl Hacker http://stason.org/ mod_perl Guide ---> http://perl.apache.org mailto:[EMAIL PROTECTED] http://use.perl.org http://apacheweek.com http://modperlbook.org http://apache.org http://ticketmaster.com
--------------------------------------------------------------------- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
