Overview
Introduction
The Registry is a public collection of custom nodes. Developers can publish, version, deprecate, and track metrics related to their custom nodes. ComfyUI users can discover, install, and rate custom nodes from the registry.
Why use the Registry?
The Comfy Registry helps the community by standardizing the development of custom nodes:
Automated Testing: Authors can continuously test new versions of their custom nodes against workflows that use their nodes. Our CI/CD Dashboard automatically checks for regressions in image quality, runtime, or if a workflow stops running completely. Node Versioning: Developers frequently publish new versions of their custom nodes which often break workflows that rely on them. With registry nodes being semantically versioned, users can now choose to safely upgrade, deprecate, or lock their node versions in place, knowing in advance how their actions will impact their workflows. Node Integrity: The registry will serve as a backend for the UI-manager. All nodes will be scanned for malicious behaviour such as custom pip wheels, arbitrary system calls, etc. Nodes that pass these checks will have a verification flag () beside their name on the UI-manager.Set up a Registry Account
Watch a Tutorial
Create a Publisher
A publisher is an identity that can publish custom nodes to the registry. Every custom node needs to include a publisher identifier in the pyproject.toml file.
Go to Comfy Registry, and create a publisher account. Your publisher id is globally unique, and cannot be changed later because it is used in the URL of your custom node.
Your publisher id is found after the @
symbol on your profile page.
Create an API Key for publishing
Go here and click on the publisher you want to create an API key for. This will be used to publish a custom node via the CLI.
Name the API key and save it somewhere safe. If you lose it, you’ll have to create a new key.
Add Metadata
This command will generate the following metadata:
Add this file to your repository. Check the specifications for more information on the pyproject.toml file.
Publish to the Registry
Option 1: Comfy CLI
Run the command below to manually publish your node to the registry.
You’ll be prompted for the API key.
Keep in mind that the API key is hidden by default.
When copy-pasting, your API key might have an additional \x16 at the back when using CTRL+V (for Windows), eg: ************************************************\x16.
It is recommended to copy-paste your API key via right-clicking instead.
Option 2: Github Actions
Automatically publish your node through github actions.
Set up a Github Secret
Go to Settings -> Secrets and Variables -> Actions -> New Repository Secret.
Create a secret called REGISTRY_ACCESS_TOKEN
and store your API key as the value.
Create a Github Action
Copy the code below and paste it here /.github/workflows/publish_action.yml
main
, such as master
, add the name under the branches section.Test the Github Action
Push an update to your pyproject.toml
’s version number. You should see your updated node on the registry.
pyproject.toml
fileFrequently Asked Questions
Was this page helpful?