Skip to content
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.

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

Client-side access to anaconda.org-provided .conda metadata in conda-forge.org/packages #51

Open
jaimergp opened this issue Feb 22, 2024 · 1 comment

Comments

@jaimergp
Copy link
Contributor

Quansight-Labs/conda-metadata-app#7 shows a snippet where a Docusaurus page could access Anaconda.org to query the .conda metadata live. Sadly this is not possible for .tar.bz2 artifacts, so those would need to be retrieved from either OCI or an intermediate API server (e.g. https://condametadata-1-n5494491.deta.app/).

It would use URLs like the current /status dashboard does for migrations (see https://deploy-preview-12--cf-infra-docs.netlify.app/status/).

@jaimergp
Copy link
Contributor Author

@afshin, this is the client-side idea we talked about with range-requests and so on.

If a standalone library needs to be created, the reference JSON payload format is "documented" at https://github.com/regro/conda-forge-metadata/blob/d6e4378f94566bafa2e7e28239633c142a93b105/conda_forge_metadata/artifact_info/info_json.py#L85C7-L96

@jaimergp jaimergp moved this to 📬 TODO in czi-conda-forge 📦 Feb 27, 2024
@jaimergp jaimergp moved this from 📬 TODO to 📋 Backlog in czi-conda-forge 📦 Mar 6, 2024
@jaimergp jaimergp modified the milestones: 18 months, 24 months Mar 26, 2024
@jaimergp jaimergp modified the milestones: 24 months, Stretch goals May 21, 2024
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
Status: 📋 Backlog
Development

No branches or pull requests

1 participant