Details
-
Type:
Bug
-
Status:
Closed
-
Priority:
Major
-
Resolution: Not a bug
-
Component/s: demo.moodle.net
-
Labels:None
Description
According to alexa.com, 4% of all moodle.org traffic goes to the demo site. I assume that others go there for the same reason I do: to try out new features.
I recently got burned by a serious discrepancy between the demo site and the latest stable release (see MDLSITE-234). The problem was fixed quickly, but it left me wondering about the process by which demo.moodle.org is maintained, and what guarantees users have when using this site.
Suggestion: set up cron to put demo.moodle.org into maintenance mode and do a cvs update to the latest stable release at least once every 24h. Then advertise the site as the latest stable release with a 24h guarantee.
If this can't be done, the front page should warn users that the release may be different from latest stable release.
Issue Links
| This issue is duplicated by: | ||||
| MDLSITE-222 | Demo site is not running the latest stable release |
|
|
|
(copy of a comment from
MDLSITE-234because it's more appropriate here)John, it's a demo site I provide for convenience. It's not meant to be a reference implementation of the code.
The current latest source code is always available via CVS if you want the very latest, plus there are daily builds on the download page.
Automatically upgrading Moodle as you describe is not easy and probably not advisable if things go wrong. It will be easier when we have command line upgrading (Google SOC student is working on it) but even then possibly a problem every now and then. I'll look into it though.
MDLSITE-234because it's more appropriate here) John, it's a demo site I provide for convenience. It's not meant to be a reference implementation of the code. The current latest source code is always available via CVS if you want the very latest, plus there are daily builds on the download page. Automatically upgrading Moodle as you describe is not easy and probably not advisable if things go wrong. It will be easier when we have command line upgrading (Google SOC student is working on it) but even then possibly a problem every now and then. I'll look into it though.