Opened 18 years ago
Closed 11 years ago
#68 closed task (invalid)
Cron Job for Static HTML File Updates
Reported by: | robertbray | Owned by: | warmerdam |
---|---|---|---|
Priority: | major | Milestone: | |
Component: | SysAdmin | Keywords: | |
Cc: | gregboone tomfunkushima |
Description
Projects need a way to update static HTML page content on the OSGeo site. This request is for a cron job to update the following directories based on the corresponding SVN folders:
../files/mapguide/docs <= http://svn.osgeo.org/mapguide/trunk/docs ../files/fdo/docs <= http://svn.osgeo.org/fdo/trunk/docs
Change History (7)
comment:1 by , 18 years ago
Status: | new → assigned |
---|
comment:2 by , 18 years ago
Resolution: | → fixed |
---|---|
Status: | assigned → closed |
comment:3 by , 18 years ago
I'd add that the cronjob runs the script:
/root/scripts/web_svn_refresh.sh
#!/bin/sh
# The following two refreshes take quite a bit of time, so don't run this # script too often!
cd /var/www/html/files/fdo/docs svn update -q --non-interactive chown -R apache.apache .
cd /var/www/html/files/mapguide/docs svn update -q --non-interactive chown -R apache.apache .
comment:4 by , 18 years ago
Resolution: | fixed |
---|---|
Status: | closed → reopened |
I uploaded new HTML context to the fdo.osgeo.org site on 03/26/07 18:25:37.
Changeset 2718-2719
Timestamp: 03/26/07 18:25:37 (17 hours ago)
Author: gregboone
Message: Ticket #26: Update FDO web documentation
I believe the changes should have been updated at ~4am this morning. At this time I do not see the changes.
comment:5 by , 18 years ago
Greg,
I found that the checkouted out tree had orphaned locks, and I had to run svn cleanup on it.
I have done that manually, and updated things (well the update is still running).
We have to remove these doxygen docs from svn though - they are just killing the server. Just too many files and too much churn. My current theory is that most of our server problems relates to getting hammered on checkouts and other subversion activity around the fdo and mapguide repositories.
comment:6 by , 18 years ago
Frank,
How about we start by moving the automatic update at 4am to an on-demand update? We would just need a backup resource who could invoke the update other than yourself. We can discuss other options at a later date.
I have put in place a job to refresh these two directories from svn once per day (4:19am PST).
I had to recheckout the trees, so please verify the results are correct.
Note that the doxygen output is frighteningly large. Over 1GB counting all the .svn directory overhead. For this reason it takes over 5 minutes for the svn update jobs to run. I'd suggest we try to generate these documents locally from the source, and perhaps even tune down the doxygen parameters to reduce the volume produced.