As the configuration for the web hook service is part of the repository, and as the information in there is private so that others can't trigger the hook, the config was modified on the server before starting up the web hook service.
However, when the hook runs, the repo does a git reset --hard. That nixed all the configs. Then, when the server rebooted some days ago due to DigitalOcean maintenance, the web hook came back up, but with the wrong config (the default data).
This PR moves the config into a sample so that the actual config is a 'untracked' file.
As the configuration for the web hook service is part of the repository, and as the information in there is private so that others can't trigger the hook, the config was modified on the server before starting up the web hook service. However, when the hook runs, the repo does a
git reset --hard. That nixed all the configs. Then, when the server rebooted some days ago due to DigitalOcean maintenance, the web hook came back up, but with the wrong config (the default data).This PR moves the config into a sample so that the actual config is a 'untracked' file.