You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Feature for display information about LORA - primarily key trigger words (but showing other info also useful - like example_prompt).
For example, we can receive information from CivitAI or a similar resources.
Because when there is a lot of Lora, which also have strange names (the names of files do not correspond to the names of webpages where it is hosted) or been renamed - you forget where from downloaded files. But it is important to use keywords so that the Lora is applied correctly
get JSON from open API CivitAI (/api/v1/model-versions/by-hash/{sha256})
and extract trainedWords (and examplePrompt) section from JSON
Reply from API sometimes not so fast, and because of it - will be good use api request in async mode; even may be will be useful store this information about Lora model in DB.
Additional Content
No response
The text was updated successfully, but these errors were encountered:
Is there an existing issue for this?
Contact Details
No response
What should this feature add?
Feature for display information about LORA - primarily key trigger words (but showing other info also useful - like example_prompt).
For example, we can receive information from CivitAI or a similar resources.
Because when there is a lot of Lora, which also have strange names (the names of files do not correspond to the names of webpages where it is hosted) or been renamed - you forget where from downloaded files. But it is important to use keywords so that the Lora is applied correctly
Alternatives
As example: node for Comfy UI - Lora Info (https://github.com/jitcoder/lora-info)
You can find in code it is quite easy:
Reply from API sometimes not so fast, and because of it - will be good use api request in async mode; even may be will be useful store this information about Lora model in DB.
Additional Content
No response
The text was updated successfully, but these errors were encountered: