Comfyui side automatic update SD-PPP
The ComfyUI-side half of the sd-ppp auto-update pair
- Status
The Photoshop half of sd-ppp gets updated by CCXManager and CCXManagerCopy. This node is the other half: it keeps the ComfyUI-side sd-ppp custom node itself current, straight from its git repo. Two updaters, one workflow, zero manual git pulls. That's the whole pitch of WWWEN8's ComfyUI-CCXManager pack, and this is the piece that closes the loop.
How it works
Point it at a GitHub repo and it does the git dance for you: fetch the remote, compare against your local checkout, and if there's a newer commit, pull it. It's not sd-ppp-specific - the input is just a repo URL - but the pack's default setup watches zombieyang/sd-ppp, and the pack also ships an updater_config.json that lets the same updater run automatically on startup in the background (it fires a check about five seconds after ComfyUI boots). The node is the on-demand, in-workflow version of that background check.
Because it's shelling out to git, it only works cleanly on nodes that were installed by git clone. A ZIP-installed node has no .git directory and nothing to pull.
The inputs
repo_url- the git repo to watch (e.g.https://github.com/zombieyang/sd-ppp.git). Empty string errors out, so this is the one you actually set.auto_update- whentrue(default), it pulls automatically when an update is found. Turn it off and it just reports "update available" and leaves your checkout alone.force_override- whentrue, it forces the update even if the repo doesn't look updatable or the local state is dirty. Handle with care; this is the "just do it" switch.
It returns a single string, Status, that tells you what happened - updated, already latest, or "update found but auto-update disabled". Wire it into a Show Text node to read it without fishing through the console.
Setup
Same shared pack install as everything else:
cd ComfyUI/custom_nodes
git clone https://github.com/WWWEN8/ComfyUI-CCXManager.git
or search "ComfyUI-CCXManager" in ComfyUI Manager, then restart. The only Python dependency is requests; the real requirement is git on your PATH, which you already have if you've been cloning custom nodes by hand.
Gotchas
Three things bite people here. First, this node pulls the whole repo, so any local edits you made to the sd-ppp node get overwritten or conflict - if your checkout is dirty, the pull can fail, which is exactly when force_override is tempting (and exactly when you should stash your changes instead). Second, it needs network access to GitHub; behind a proxy or in an offline setup it can't check, and you'll get a check-failure message rather than an update. Third, there's a subtle ordering thing in the pack's workflow: update the ComfyUI side first, then the Photoshop side, because a newer sd-ppp node usually wants a newer ccx to match. Run it in that order and the two halves stay in sync.
Inputs (3)
| Name | Type | Default | Description |
|---|---|---|---|
| repo_url | STRING | — | |
| auto_update | BOOLEAN | true | — |
| force_override | BOOLEAN | false | — |
Outputs (1)
| Name | Type | Description |
|---|---|---|
| Status | STRING | — |