On Sat, Apr 24, 2010 at 02:51:42AM -0400, Jeremy wrote: > David wrote: > > 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. :-) > > > 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.
Nice idea. This would also be a natural extension to Aegir. All our documentation is kept in Trac, but everyone complains about wikiformatting. > PS: Angie you rock! All the Montreal Drupalistas rock, but Angie especially! -- Mark http://www.lambic.co.uk
signature.asc
Description: Digital signature
_______________________________________________ mlug mailing list [email protected] https://listes.koumbit.net/cgi-bin/mailman/listinfo/mlug-listserv.mlug.ca
