Question: does this version also expose the REST api on port 5000?

[abdbarho]

Question: does this version also expose the REST api on port 5000?

[AbdBarho]

I am not sure since this depends on the underlying UI, you can add the port to the docker compose file and try it

    ports:
      - "7860:7860"
      - "5000:5000"

[StefH]

I think that the api is not running on port 5000.

When clicking the api-link in the bottom page, I get redirected to this:

[AbdBarho]

well, I guess the api is running on the same port as the ui

[rgriffogoes]

Which UI are you using @StefH ? did you add something somewhere to enable api?

When I use auto1111, clicking in the api link shows a page informing me it is off, and I would like to have it on.

[StefH]

I cloned this project, followed the readme, and started:

docker compose --profile auto-cpu up --build

Then the UI is running at : http://localhost:7860/

[rgriffogoes]

Getting the UI to work is fine on my side, I'm curious about the API. Regardless if I run auto-cpu or auto clicking on the api-link at the bottom gives me:

With my superficial understanding of the code, I would need to either use a parameter (if auto1111 code is prepared for it) or change the code in auto1111 to start gradio with API server.

[AbdBarho]

maybe the discussion in #92 could be of some use

[github-actions]

This issue is stale because it has been open 14 days with no activity. Remove stale label or comment or this will be closed in 7 days.

[github-actions]

This issue is stale because it has been open 14 days with no activity. Remove stale label or comment or this will be closed in 7 days.

[github-actions]

This issue was closed because it has been stalled for 7 days with no activity.