Or even better, perhaps, what if we exposed this deployment/version metadata via our own API endpoint? e.g. https://nextstrain.org/-/deployment-metadata. This would also address the edge case of config.RESOURCE_INDEX in the live server process not being equivalent to RESOURCE_INDEX in the on-disk config.json.
First proposed by @tsibley in https://github.com/nextstrain/nextstrain.org/pull/841#discussion_r1588227761