Le 21 oct. 05, à 14:50, Carsten Ziegeler a écrit :
Can someone update our Cocoon demo version in our cocoon zone to the
version of 2.1.x of today (or tonight)?...
Done, and I took the opportunity to activate all three demos that were
originally planned:
1) http://cocoon.zones.apache.org/demos/release/
stays at 2.1.7 for now, we can upgrade it when 2.1.8 is released
2) http://cocoon.zones.apache.org/demos/21branch/
updated twice a day with the latest BRANCH_2_1_X code from svn.
This is what we can advertise for people to test the release.
3) http://cocoon.zones.apache.org/demos/trunk/
updated twice a day with the latest trunk code from svn.
(there are links to these on http://cocoon.zones.apache.org/)
All three demos will be down for about 5 minutes (depending on system
load) twice a day when they restart, as they do an svn up (except demo
1) and a full build including clean. The current schedule is (crontab
of user "cdemos" which runs the demos):
# restart the release demo
12 3,15 * * * date ; /home/config/cocoon.zone/cdemos/cocoondemo.sh
start release...
# restart the 21branch demo
22 3,15 * * * date ; /home/config/cocoon.zone/cdemos/cocoondemo.sh
start 21branch ...
# restart the trunk demo
32 3,15 * * * date ; /home/config/cocoon.zone/cdemos/cocoondemo.sh
start trunk ...
IIUC the host runs on GMT time.
To find out how this works, zone admins should start by studying the
/home/config/cocoon.zone/cdemos/cocoondemo.sh script, it's fairly
self-explanatory. Any changes to stuff under /home/config should be
done with the "config" user ID (su - config).
-Bertrand
