A FAQ-O-Matic installation can be configured as a mirror of another FAQ-O-Matic. During the "Define Configuration Parameters" step of the installation, set $mirrorURL equal to the URL of the CGI of the source FAQ. For example, to mirror this FAQ, set your $mirrorURL to http://faqomatic.sourceforge.net/cgi-bin/fom.

The mirror will generate its own cache, and will handle [Search], [Appearance], and [Show This Entire Category] requests locally. However, the [Show Edit Commands] link will direct the user to the original site. This avoids the tricky issue of maintaining distributed write consistency. Your mirror will be automatically updated daily as a part of the maintenance cron job.

The advantage to pull mirroring is that you set it up using the same easy web interface you used to install your master FAQ.

The second approach is to use a one-line cron job to "push" a mirror of a master FOM's fom-serve/cache directory to a mirror site. The rsync program is an excellent way to transfer the directory intact. The cached HTML that FOM generates contains local (relative) links for browsing content, and absolute (i.e. back to the master site) links for anything requiring the CGI, so this sort of mirror behaves identically to the pull mirror: browsing is handled locally; searching, special appearance features, and editing are handled at the master site.

Push mirroring is useful when you can't even run the slave CGI on the mirror site, and/or the mirror site cannot make an outgoing web connection to the master site to pull down the content. I use this to deal with sourceforge, which disallows outgoing web connections needed for "pull" mirroring.