There have been a couple of discussions about the community demo/test
servers that are available and required ones that are missing. This is a
summary of what has been suggested/planned; how the servers should be
setup, maintained, etc.
Thoughts, suggestions, glaring issues with the current plans? Please
feel free to respond. Cheers
Current plans/suggestions:
1. Mike Peters will be maintaining a master demo server while Brian
Feifarek will maintain a current stable release demo server and EC2 image.
2. Weekly (or twice a week) refresh of data, clearly stated on demo
server page. Mike Peters provided a rudimentary script[1] to auto
refresh the data.
3. Provide a list of cronjobs/services (targeting scripts, reporter,
etc) that are running on the demo servers and try to have all of them
running the same set.
4. The sample data provided by Mike Peters[2] will be used on all
demos/images so we will have some consistency across servers.
5. Standardize http://foo.com/democlient.exe as a location for all demos
and on versions that can do remote client updates use
http://foo.com/updates/manualupdate.html That way, everyone always knows
where to look on each demo server for the version specific staff client.
[1] http://paste.lisp.org/display/124819
[2] http://help.evergreen.lib.in.us/generate-demodata.tar.gz
--
Anoop Atre
IS Developer & Integrator, PALS
PH: 507.389.5060
OF: 3022 Memorial Library (Office-ML 3022)
--
"Mit der Dummheit kämpfen Götter selbst vergebens"
~ Johann Christoph Friedrich von Schiller
