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

Moving the --theme dark flag from Dockerfile to docker-compose.yml #204

Closed
Keavon opened this issue Nov 6, 2022 · 2 comments · Fixed by #205
Closed

Moving the --theme dark flag from Dockerfile to docker-compose.yml #204

Keavon opened this issue Nov 6, 2022 · 2 comments · Fixed by #205

Comments

@Keavon
Copy link

Keavon commented Nov 6, 2022

Since not everyone wants the dark theme in the AUTOMATIC1111 web UI, wouldn't it make more sense to move the --theme dark flag into the environment variables set in docker-compose.yml? I currently track your repository but I have one commit that I rebase which just changes those environment variables in docker-compose.yml (removing --allow-code --medvram and adding --api for my purposees). Not having to rebase two files would make it slightly easier to maintain. Thanks for considering.

@AbdBarho AbdBarho mentioned this issue Nov 7, 2022
@AbdBarho
Copy link
Owner

AbdBarho commented Nov 7, 2022

@Keavon I removed it in #205

that being said, you don't need an extra commit that you have to always rebase for this, you can leave the original docker compose file as is, and create a docker-compose.override.yml and put this in it:

services:
  auto:
    environment:
      - CLI_ARGS=--api # your args here
    # you can even override the entire command if you want to
    command: [python3, -u, ../../webui.py, --listen, --port, 1111, --beep, --beep, --iamasheep]

@Keavon
Copy link
Author

Keavon commented Nov 7, 2022

Awesome, that's very helpful. Thank you for that tip! And I see that that override also .gitignored, handy.

cloudaxes pushed a commit to cloudaxes/stable-diffusion-webui-docker that referenced this issue Sep 6, 2023
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging a pull request may close this issue.

2 participants