conda-forge.github.io
conda-forge.github.io copied to clipboard
better story on which container registry we use?
Right now we upload some of our images to quay and docker, others to docker only. Further, we don't make use of github's packages (due to permissions issues IIRC).
It'd be nice to fix this up so we
- push all images everywhere?
- make use of github if we can
- have our CI + feedstock jobs use only one source?
Thoughts?
Consistency would help, yes :) If we are going to push everywhere, it would be nice if the backend was configurable through a quick setting somewhere too. For example, in feedstocks folks could rerender via conda-forge.yml edits if Quay.io is down, and in our infra we could leverage Action variables at the org or repo level to control that.