mirror of
https://github.com/Comfy-Org/ComfyUI-Manager.git
synced 2026-11-05 07:47:25 +00:00
[GH-ISSUE #928] Use git submodules for installation/management #405
Labels
No milestone
No project
No assignees
1 participant
Notifications
Due date
No due date set.
Dependencies
No dependencies set.
Reference
Comfy-Org/ComfyUI-Manager#405
Loading…
Add table
Add a link
Reference in a new issue
No description provided.
Delete branch "%!s()"
Deleting a branch is permanent. Although the deleted branch may continue to exist for a short time before it actually gets removed, it CANNOT be undone in most cases. Continue?
Originally created by @Xyem on GitHub (Aug 4, 2024).
Original GitHub issue: https://github.com/Comfy-Org/ComfyUI-Manager/issues/928
For my own ComfyUI installation, I add custom nodes as git submodules, as this allows me to manage custom nodes as part of how I manage ComfyUI (on a
personalbranch).Would this installation method be considered for CUI-Manager? I have it installed as it helps with some other things, but would really like to use it for managing custom nodes as well.
@ltdrdata commented on GitHub (Aug 5, 2024):
Actually, using git submodules is not recommended.
At one point, Impact Pack also used a git submodule structure, but I found that git submodules are not supported in several systems depending on the environment.
Also, when updating the submodule parts, problems frequently occurred.
I am currently considering how to handle additional installations using submodules or similar methods.
@Xyem commented on GitHub (Aug 11, 2024):
I'd certainly be interested in hearing about these issues you experienced as I haven't had any (though I am using them to manage an installation, not a codebase).
Perhaps I have overlooked something, but submodules are, to my knowledge, the only way to manage compatible versions between ComfyUI and the custom nodes. If you just check out the latest of either of them, they could be incompatible.
@ltdrdata commented on GitHub (Aug 11, 2024):
On systems with older Git installations, the submodule functionality doesn't work at all. Furthermore, when updating, there were frequent issues where changes that should have been applied to submodules weren't properly implemented.
If I make a mistake, I might need to reorganize the branch history. This often led to divergent branch issues. (This situation prevents me from delivering further updates, causing many problems.)
After encountering these issues several times, I reverted to using independent modules instead.