KenSchae
/
wyrde-comfyui-workflows
1
0
Fork 0
Code Issues Pull Requests Projects Releases Wiki Activity
Browse Source

Update README.md 

more about custom nodes
wyrde-docs
wyrde 2 years ago committed by GitHub
parent
a8e910dc15
commit
265ef5b8cb
No known key found for this signature in database
GPG Key ID: 4AEE18F83AFDEB23
1 changed files with 7 additions and 0 deletions
Whitespace
Show all changes Ignore whitespace when comparing lines Ignore changes in amount of whitespace Ignore changes in whitespace at EOL
Unified View
Diff Options
Show Stats Download Patch File Download Diff File
  1. 7
      basics/README.md

7
basics/README.md
Unescape View File

@ -67,6 +67,7 @@ If comfyUI doesn't have something you expect, there's probably a custom node for
* It's generally a good idea to put the author's name/handle as a directory/folder, then the node(s) inside it. * It's generally a good idea to put the author's name/handle as a directory/folder, then the node(s) inside it.
* This can cause an warning when comfy loads the folder but it is harmless. * This can cause an warning when comfy loads the folder but it is harmless.
* an alternative is to keep the folders outside of comfy, and copy over the particular files. * an alternative is to keep the folders outside of comfy, and copy over the particular files.
* this may seem annoying at first, but one time spent trying to remember where a custom node came from makes it worth it. (:
* some nodes come as "suites" which will include their own directory, drop the whole thing inside custom_nodes * some nodes come as "suites" which will include their own directory, drop the whole thing inside custom_nodes
* if nodes come in a folder with an `__init__.py` file, the whole thing can be put in `custom_nodes` with no errors * if nodes come in a folder with an `__init__.py` file, the whole thing can be put in `custom_nodes` with no errors
* well, there might still be errors (: * well, there might still be errors (:
@ -75,6 +76,12 @@ Extensions are bits of javascript that extend the UI or some functions of comfyU
* Extensions are placed in the `web\extensions` folder/directory. * Extensions are placed in the `web\extensions` folder/directory.
* Make sure to follow the author's instructions. These can break things. Easy to fix by removing the files. * Make sure to follow the author's instructions. These can break things. Easy to fix by removing the files.
There is no central repository of nodes/extensions (ie: marketptlace). ComfyUI is considered prealpha and it is felt a centralized system isn't advisable at this time (Don't let pre alpha scare you. ComfyUI is robust, but under rapid development!)
* there are a couple lists, though:
* https://github.com/wyrde/ComfyResources
* https://github.com/wyrde/wyrde-comfyui-workflows#custom-nodes-and-extensions
* and many are released on [civitai.com](https://civitai.com/tag/comfyui)
## Embeddings ## Embeddings
Otherwise known as Textual Inversons, embeddings can help create specfiic results in an image. Place embeddings in the `embeddings` folder and use them in prompts with `embedding:<filename>`. The extension isn't required. Note the lack of space after the `:`. Embeddings don't have a GUI element or node because their placement in a prompt is important. An embedding is basically a "word" with special meaning. Otherwise known as Textual Inversons, embeddings can help create specfiic results in an image. Place embeddings in the `embeddings` folder and use them in prompts with `embedding:<filename>`. The extension isn't required. Note the lack of space after the `:`. Embeddings don't have a GUI element or node because their placement in a prompt is important. An embedding is basically a "word" with special meaning.

Write Preview
Loading…
Cancel
Save