Devfile registry - storing contents of the public community, OCI-based, devfile registry hosted at https://registry.devfile.io.
The public registry is updated weekly, by 12pm EST Wednesdays, with any updated stacks in this repository.
The staging devfile registry, https://registry.stage.devfile.io is refreshed upon each commit to main in this repository. Production, https://registry.devfile.io, promoted manually and as mentioned above, is done each Wednesday, as needed.
If you are a stack owner and need to request an urgent refresh of https://registry.devfile.io before Wednesday (for example if a stack is broken), please open an issue in the devfile/api repository outlining the following:
- Stack name
- Why the refresh is needed
- Why the refresh cannot wait until the next regularly scheduled refresh
/area registrysomewhere in the issue description, so that thearea/registrylabel gets added.
- Docker 17.06 or later
- Git
To build this devfile registry into a container image run bash .ci/build.sh. A container image will be built using the devfile registry build tools.
From there, push the container image to a container registry of your choice and deploy using one of the methods outlined here.
For contributing Devfile stacks to this registry, please see CONTRIBUTING.md.
The Devfile Registry is configured with telemetry to collect only the necessary information to improve the value of our service. For further details, refer to the Telemetry Data Collection Notice
For issues relating to a specific devfile stack in this repository, please reach out to the devfile stack maintainer to determine where to open an issue.
For issues relating to the hosted devfile registry service (https://registry.devfile.io), or devfile registries in general, please use the devfile/api issue tracker for opening issues. Apply the area/registry label to registry issues for better visibility.