Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
Closes issue #35
This code is not complete, I am opening a PR so we can discuss structure and things like compose context.
You seem to know your way around compose way better than me, so should we add a new dir for auto-mq or just link store two dockerfiles in
./services/AUTOMATIC1111
and provide context in the compose?:Right now, the
./services/AUTOMATIC1111/Dockerfile
works and if you spin up with the following command, it will run on mac m1:That said, the Dockerfile needs to be cleaned (something I'm in the process of with the file
Dockerfilemerged
) and what are your thoughts on the added*.py
and*.sh
files -- should we keep them, as they contain edits needed for running on mac m1, or should we try to parse the changes tosed
commands and modify existing files in place?Note: the non-m1 Dockerfile has been preserved, just currently named
./services/AUTOMATIC1111/Dockerfile.x86
, on this branch.(Then, deff need to squash commit history haha)
Update versions