From: Jesse op d. B. <ht...@op...> - 2004-02-20 13:46:13
|
Hi all, when accessing the htdig main website, file main©shtml does not contain the included news©txt file, allthough the string is definitely in the file itself© Can anyone verify this? BTW: a few mirror do not use Server Side Includes, so the news isn't shown at all on theire pages© Can we change this? --jesse |
From: Gilles D. <gr...@sc...> - 2004-02-20 21:28:40
|
According to Jesse op den Brouw: > when accessing the htdig main website, file main=A9shtml does not > contain the included news=A9txt file, allthough the string is > definitely in the file itself=A9 > Can anyone verify this? Yes, there seems to have been a hiccup in the news update script (/home/groups/h/ht/htdig/scripts/news-get.sh) which runs at 3:42 PST every morning. It uses a wget query to fetch the URL http://sourceforge.net/export/projnews.php?group_id=3D4593&limit=3D4&flat= =3D0&show_summaries=3D1 and then checks that the file it got is not empty. If it's not, it copies it to maindocs/news.txt and cvs commits it. Well, this morning, the commited file was empty, so I can only assume the copy had failed. Assuming it was either a temporary disk full condition (in which case there's not much we can do - it's not full now) or a quota exceeding (which I didn't hear about, and which I can't seem to find out about righ= t on their shell.sf.net server), I deleted some old database backup files to cut down on our disk usage, in the hope that the problem will be less likely to recur. I also manually regenerated the news.txt file for today. Not much else I can do. Geoff, did you get any error messages from this morning's script run? > BTW: a few mirror do not use Server Side Includes, so the > news isn't shown at all on theire pages=A9 Can we change this? We could probably change the news-get.sh script to build a mail.html file from the main.shtml and news.txt files, and commit that. We'd also need to change contents.html to point back to news.html. This would actually make the maindocs files a bit more like the htdig3/htdoc files, only news.html would be regenerated on a daily basis. The potential problem I see with this is the Last modified date will keep changing every day, even if there's no new news, and news.html will get copied to all cvs users who get daily updates of maindocs. Can anyone suggest a way around this, without losing the Last modified date altogether? I suppose the script could compare the regenerated news.txt against the previous one, and only regenerate main.html if news.txt's content changes, or main.shtml has been changed since the last time. Another way might be to do away with main.shtml and news.txt from the maindocs tree altogether, and just have a main.html file, as before the SourceForge days. Only difference is this time, the news section in main.html would be between clear delimiters, and the news-get.sh script would use these to automatically strip out and reinsert updated news items from the one file. It would recommit it only if it was different from yesterday's file. The script should also have proper tests to ensure the newly generated file is indeed complete, to prevent the whole thing from getting clobbered in the event of a disk space crunch, but with that, it may be the best option from a maintenance point of view. I'm leaning towards this latter approach. Any ideas, concerns, other thoughts from the developers about this? --=20 Gilles R. Detillieux E-mail: <gr...@sc...> Spinal Cord Research Centre WWW: http://www.scrc.umanitoba.ca/ Dept. Physiology, U. of Manitoba Winnipeg, MB R3E 3J7 (Canada) |
From: Gilles D. <gr...@sc...> - 2004-02-20 22:32:48
|
According to me: > Another way might be to do away with main.shtml and news.txt from the > maindocs tree altogether, and just have a main.html file, as before the > SourceForge days. Only difference is this time, the news section in > main.html would be between clear delimiters, and the news-get.sh script > would use these to automatically strip out and reinsert updated news > items from the one file. It would recommit it only if it was different > from yesterday's file. The script should also have proper tests to > ensure the newly generated file is indeed complete, to prevent the whole > thing from getting clobbered in the event of a disk space crunch, but > with that, it may be the best option from a maintenance point of view. > I'm leaning towards this latter approach. OK, I've implemented this on a trial basis. index.html and contents.html still point to main.shtml, with still includes news.txt. However, I've updated the news-get.sh script to maintain both news.txt and main.html, so we'll see how it goes in the coming days/weeks. If it seems solid, we can switch index.html and contents.html over to using main.html, and we can then get rid of main.shtml and news.txt (and take out the part in news-get.sh that maintains the latter). Please have a look and comment. I'd appreciate the extra eyeballs. -- Gilles R. Detillieux E-mail: <gr...@sc...> Spinal Cord Research Centre WWW: http://www.scrc.umanitoba.ca/ Dept. Physiology, U. of Manitoba Winnipeg, MB R3E 3J7 (Canada) |
From: Gilles D. <gr...@sc...> - 2004-06-18 16:29:36
|
All right, after about 4 months and a few news updates, I'm satisfied that my script for regenerating main.html is working satisfactorily, so I've switched the index.html and contents.html files over to using this, rather than the main.shtml file. This should help out our mirrors who don't support SSI. The next step, as I see it, is to automate updates to dev/htdig-3.2/main.html the same way. I can see 3 ways of doing this. The main difference between the maindocs/dev/htdig-3.2 version and the maindocs version, is the latter has been using the maindocs/css/htdig.css style sheet for quite some time, but the former hasn't been. So we can... 1) make a copy of css/htdig.css in dev/htdig-3.2, and then the script that updates main.html can just copy it to dev/htdig-3.2, and check in both copies as needed, or 2) copy and check in the 2nd main.html as above, but use sed to strip out the css-dependent stuff, or 3) fully regenerate dev/htdig-3.2/main.html, independently of the one in maindocs (though using the same technique). What do you folks think? If we plan to introduce the style sheet into the 3.2 on-line docs soon, as well as into the htdoc subdirectory of the source tree, then maybe option 1 is the way to go. It's easiest. If we don't plan to do this soon, then option 2 might be better, so the look of main.html is consistent with the other 3.2 on-line docs. However, both 1 and 2 assume that the information in main.html (i.e. the Introduction and Recent News frame when you first go to the site) will remain the same for both. If we want the option to have different content (e.g. a different intro for 3.2), then option 3 is the only real viable one, whether we add style sheets soon or not. I'm planning for now to copy the main.html (minus the css stuff) to dev/htdig-3.2 manually and check it in, for now, but I wouldn't mind some feedback on this before I change the update script. The style sheet was added to maindocs around the time 3.1.6 went out, as an experiment, but we haven't really followed up in terms of deciding if we want to stick to this format or not. Cheers, Gilles Back in February, I wrote... > According to me: > > Another way might be to do away with main.shtml and news.txt from the > > maindocs tree altogether, and just have a main.html file, as before the > > SourceForge days. Only difference is this time, the news section in > > main.html would be between clear delimiters, and the news-get.sh script > > would use these to automatically strip out and reinsert updated news > > items from the one file. It would recommit it only if it was different > > from yesterday's file. The script should also have proper tests to > > ensure the newly generated file is indeed complete, to prevent the whole > > thing from getting clobbered in the event of a disk space crunch, but > > with that, it may be the best option from a maintenance point of view. > > I'm leaning towards this latter approach. > > OK, I've implemented this on a trial basis. index.html and contents.html > still point to main.shtml, with still includes news.txt. However, I've > updated the news-get.sh script to maintain both news.txt and main.html, > so we'll see how it goes in the coming days/weeks. If it seems solid, > we can switch index.html and contents.html over to using main.html, > and we can then get rid of main.shtml and news.txt (and take out the > part in news-get.sh that maintains the latter). > > Please have a look and comment. I'd appreciate the extra eyeballs. -- Gilles R. Detillieux E-mail: <gr...@sc...> Spinal Cord Research Centre WWW: http://www.scrc.umanitoba.ca/ Dept. Physiology, U. of Manitoba Winnipeg, MB R3E 3J7 (Canada) |