Skip to content

Conversation

ltdrdata
Copy link
Collaborator

@ltdrdata ltdrdata commented Apr 9, 2025

Manual setup required, yet.

Comfy-Org/ComfyUI-Manager#1737

@christian-byrne
Copy link
Collaborator

christian-byrne commented Apr 10, 2025

Can we also ensure the comfyui manager custom node is not imported, except if --disable-manager?

And add to requirements.txt?

It's still in the development stage, so the version is not pinned yet.
…hen `--disable-all-custom-nodes` is used.

feat: Disable specific custom nodes according to the policy of `comfyui_manager`.
@christian-byrne
Copy link
Collaborator

I think if --disable-manager is set, we should not import the package at all.

@ltdrdata
Copy link
Collaborator Author

My intention was that --disable-manager should only disable the Manager web service, while keeping other auxiliary features intact.
This includes components like the security scanner, and also allows the Manager to be used as a library.

@ltdrdata
Copy link
Collaborator Author

ltdrdata commented Apr 28, 2025

--disable-manager-ui has been added.
And --disable-manager will prevent importing ComfyUI-Manager.

Now, it is possible to distinguish between disabling ComfyUI-Manager entirely and disabling only the UI of ComfyUI-Manager.

@christian-byrne If the endpoint is blocked using --disable-manager-ui, is it also possible to block ui from the frontend?

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

Core Core team dependency Core-Important

Projects

None yet

Development

Successfully merging this pull request may close these issues.

6 participants