David wrote: > Hi everyone, > > At work we're in the process of updating our server infrastructure. So > I figured it would be a good time to pull knowledge out of peoples head > and put in a common location. I'm looking to document server hardware > specs, what the server is used for, procedures, how-tos, rebuild > procedures, etc. At the moment a wiki jumps to to mind. Any other > suggestions for how to store the info or what info to store? Open > Source solutions preferred. :-) > > > David Drupal6 default install with no extra modules (fine, pathauto module to have nice urls easily if you care).
Start a new "book" for each server. Nodes are added by user/admin and attached to certain books. This segments servers and has documentation under each. Table of contents and pager etc is auto. Taxonomy is predefined by you and is a general category you wish to segment (ie: dns, web, mail, files, doc) types of server. You can then (with pathauto) call up domain.com/dns and see all documents pertaining to all dns servers, and can drill down further to specific servers, or just get a general overview. Permit advanced search to allow users to search in a way that can bring up both taxonomy and book topics in one query. You can give WYSIWYG and image upload capabilities easily to users, define editors, have pretty good acls, etc. Wikis are great, but in the end they are all content management systems, and I like drupal. The bonus is you get all the extra horsepower of drupal and addons to go wherever you want without having to write much code if any. Perfect lazy yet pro sysadmin stuff. Estimated setup time: 87 mins with no experience but willing to read (get _Using Drupal_ book), 9 mins with experience. Theme extra. Jeremy PS: Angie you rock! _______________________________________________ mlug mailing list [email protected] https://listes.koumbit.net/cgi-bin/mailman/listinfo/mlug-listserv.mlug.ca
