New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

Sign up for GitHub

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Jump to bottom

Surface deployment metadata through our own API endpoint #853

Open

joverlee521 opened this issue May 7, 2024 · 0 comments

Labels

Contributor

joverlee521 commented May 7, 2024

First proposed by @tsibley in #841 (comment)

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.

joverlee521 added the enhancement label

joverlee521 mentioned this issue

Separate indexer #841

Merged

7 tasks

joverlee521 mentioned this issue

[RFC] Maintain different resource indexes #829

Closed

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment