johnke.me

Project Idea no. 5629

Another idea for a project I may or may never get around to completing (or in this case, starting):

This would allow an admin quick and easy access to view any changes made to the configuration structure of their machine.

Advantages over using CVS for monitoring

update

I’ve been doing some more thinking about this. Here’s one proposed database structure and what each column should store:

db_machinename

  • file_name (name of the config file we’re backing up)
  • config_orig (config file as it was originally)
  • date_orig (date the config file was read in)
  • config_cur (config file as it is today)

db_machinename_diffs

  • file_id (id of the config file we’re dealing with)
  • diff_date (date we took the diff)
  • diff_text (text of the actual diff)