Currently, the aphlict configuration used by Phab/Phorge is stored in the DB as a hidden & locked config. The configuration doesn't contain any sensitive data and it would be better to have it committed in a repo somewhere so it can be added to the local Phorge disk config files.
It seems like the config did live in Puppet at some point when aphlict was collocated on the same machine with Phorge, but it's currently disabled. Then it was presumably moved to the DB manually when aphlict was moved to its own separate host.
We can add the configuration to Puppet, so it becomes part of the standard process of bootstrapping a Phorge target or alternatively, the configuration could live in the Scap3 deployment repository, where it would be part of our deployments.