Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

[Question]: How to actually access the UI? #43

Open
magJ opened this issue Jun 28, 2024 · 1 comment
Open

[Question]: How to actually access the UI? #43

magJ opened this issue Jun 28, 2024 · 1 comment
Assignees
Labels
question Further information is requested

Comments

@magJ
Copy link

magJ commented Jun 28, 2024

I'm a bit unclear about what the expected UX is for this application.

There isn't any way to actually access runpod deployed UI via a browser right?
Is the methodology described in "How to get the workflow from ComfyUI?" the only current supported method?
When is says "Open ComfyUI in the browser", it's implied that you are running a separate ComfyUI server somewhere(locally perhaps).

Can I run the UI locally, and have it render images on the runpod worker automatically when I press the queue button?
Or do I need to copy paste the workflow json each time I change something?

Related: #26

@TimPietrusky
Copy link
Member

TimPietrusky commented Jul 29, 2024

@magJ thanks for these questions.

There isn't any way to actually access runpod deployed UI via a browser right?

Yes exactly. The purpose of this project is to have a headless ComfyUI API, that you can use via an API to run your workflows. What we have described via Local API is only something that should be used during development. But you could also use that with the deployed API on RunPod. If you just want to run ComfyUI on RunPod, it might be a better idea to use a Pod and use one of the templates.

Is the methodology described in "How to get the workflow from ComfyUI?" the only current supported method?

Yes exactly. There might also be an API in ComfyUI that provides a way to get the workflow, but I couldn't find any info about this. But maybe there is something, but we are just not aware of this.

When is says "Open ComfyUI in the browser", it's implied that you are running a separate ComfyUI server somewhere(locally perhaps).

When do you see this? When usingg the method described in Local API?

Can I run the UI locally, and have it render images on the runpod worker automatically when I press the queue button?
Or do I need to copy paste the workflow json each time I change something?

When you do Local API, you can run ComfyUI locally and also access the WebUI. When you use the WebUI, you don't have to send the workflow via the API yourself, the WebUI will already handle this for you. Both the WebUI and the runpod-worker-comfy are using the API provided by ComfyUI.

@TimPietrusky TimPietrusky self-assigned this Jul 29, 2024
@TimPietrusky TimPietrusky added the question Further information is requested label Jul 29, 2024
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
question Further information is requested
Projects
None yet
Development

No branches or pull requests

2 participants