-
Notifications
You must be signed in to change notification settings - Fork 6
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
[Bug]: Poor install instructions #32
Comments
Thank you for your suggestion, I will improve the documentation. By the way, your question is actually very simple. You can install FooocusAPI just like you install Fooocus, and the startup is the same. For example, using |
Can I just grab a release from this project and extract the zip overwriting the same files in my already working Fooocus directory? |
I did a simple test, and it's okay. But I still recommend that you back up your existing Fooocus before proceeding |
I was able to install FooocusAPI on Windows but the Fooocus documentation is not complete for Windows users : it gives a "handy" 7z file, but doesn't explain how to achieve an installation with pip+virtualenv. |
how do you use the API in docker? 7866 isn't enabled, and the web server doesn't respond to api calls only displasy the webui. |
Try this; docker pull ghcr.io/mrhan1993/fooocusapi:2.5.3
cd FooocusAPI
docker run --rm --gpus all --name fooocusapi -v $(pwd):/content/app -p 7865:7865 -p 7866:7866 ghcr.io/mrhan1993/fooocusapi:2.5.3 |
Checklist
What happened?
Why are the install instructions so vague? How to install this alongside an existing Fooocus instance?
Steps to reproduce the problem
read the Install instructions, https://github.com/mrhan1993/FooocusAPI#install
What should have happened?
The install instructions should be clearer on how to add the FooocusAPI alongside an existing Fooocus instance.
What browsers do you use to access Fooocus?
Google Chrome
Where are you running Fooocus?
Locally
What operating system are you using?
Windows 11
Console logs
Additional information
N/A
The text was updated successfully, but these errors were encountered: