Repository navigation
Replies: 1 comment
|
We are glad someone is still out there looking to keep this going; in Ai life we guess it consider old, but eventhough we find it better than forge version and comfyui. We have since been working on the memory leak issues and other tweaks and performance with both intel AMD and M4 silicon which is ARM version OS. Even today we are finding and working with the hidden gems of lack of realworld docs to make great generations. We have created custom extensions and scripts to make a great webui experience, including now how to save the conltrnet image file to our meta so it to is available for recal of what file was used in controlnet. |
0 replies
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Uh oh!
There was an error while loading. Please reload this page.
Hi @AUTOMATIC1111 and maintainers,
I’ve been developing and maintaining a Raspberry Pi–focused installer for AUTOMATIC1111’s Stable Diffusion WebUI, with the goal of making local image generation practical on Raspberry Pi 5 hardware.
Repository:
https://github.com/comp6062/rpi-automatic1111
The project handles the Raspberry Pi–specific dependencies, installation requirements, compatibility fixes, model setup, and launch process needed to run AUTOMATIC1111 on ARM64 Raspberry Pi hardware.
The initial installation and first successful WebUI launch must be completed in LAN mode. This allows the required dependencies, components, models, and other files needed by the WebUI to be installed and initialized correctly.
After the WebUI has been successfully run in LAN mode at least once and the required files are present locally, the installer also provides an offline mode, allowing the Raspberry Pi to run the WebUI and generate images locally without requiring an active Internet connection.
The project currently maintains compatibility with a pinned upstream AUTOMATIC1111 revision while keeping the Raspberry Pi–specific changes isolated to the installation, dependency handling, configuration, and launch process, rather than attempting to replace or fork the WebUI itself.
My intention is to maintain a Raspberry Pi compatibility and installation layer around the upstream AUTOMATIC1111 project while keeping the actual WebUI as close to upstream as possible.
Would you be open to reviewing the repository and potentially linking to it in your documentation as a community-maintained Raspberry Pi installation option?
I would continue maintaining the Raspberry Pi–specific setup, tracking relevant upstream changes, testing compatibility, and providing fixes as needed.
I’d also welcome any feedback on the implementation, repository structure, or requirements you would want addressed before considering linking to the project.
Thank you for your work on Stable Diffusion WebUI.
All reactions