wehub-resource-sync
cddb07a176
build container image / cpu (push) Waiting to run
build container image / cuda (push) Waiting to run
build container image / rocm (push) Waiting to run
frontend tests / frontend-tests (push) Waiting to run
openapi checks / openapi-checks (push) Waiting to run
python tests / py3.12: macos-default (push) Waiting to run
python tests / py3.11: windows-cpu (push) Waiting to run
python tests / py3.12: windows-cpu (push) Waiting to run
python tests / py3.11: linux-cpu (push) Waiting to run
python tests / py3.12: linux-cpu (push) Waiting to run
typegen checks / typegen-checks (push) Waiting to run
uv lock checks / uv-lock-checks (push) Waiting to run
frontend checks / frontend-checks (push) Waiting to run
lfs checks / lfs-check (push) Waiting to run
python checks / python-checks (push) Waiting to run
python tests / py3.11: macos-default (push) Waiting to run
docs / deploy (push) Has been cancelled
docs / changes (push) Has been cancelled
docs / check-and-build (push) Has been cancelled
32 lines
1.8 KiB
Bash
32 lines
1.8 KiB
Bash
## Make a copy of this file named `.env` and fill in the values below.
|
|
## Any environment variables supported by InvokeAI can be specified here,
|
|
## in addition to the examples below.
|
|
|
|
## INVOKEAI_ROOT is the path *on the host system* where Invoke will store its data.
|
|
## It is mounted into the container and allows both containerized and non-containerized usage of Invoke.
|
|
# Usually this is the only variable you need to set. It can be relative or absolute.
|
|
# INVOKEAI_ROOT=~/invokeai
|
|
|
|
## HOST_INVOKEAI_ROOT and CONTAINER_INVOKEAI_ROOT can be used to control the on-host
|
|
## and in-container paths separately, if needed.
|
|
## HOST_INVOKEAI_ROOT is the path on the docker host's filesystem where Invoke will store data.
|
|
## If relative, it will be relative to the docker directory in which the docker-compose.yml file is located
|
|
## CONTAINER_INVOKEAI_ROOT is the path within the container where Invoke will expect to find the runtime directory.
|
|
## It MUST be absolute. There is usually no need to change this.
|
|
# HOST_INVOKEAI_ROOT=../../invokeai-data
|
|
# CONTAINER_INVOKEAI_ROOT=/invokeai
|
|
|
|
## INVOKEAI_PORT is the port on which the InvokeAI web interface will be available
|
|
# INVOKEAI_PORT=9090
|
|
|
|
## GPU_DRIVER can be set to either `cuda` or `rocm` to enable GPU support in the container accordingly.
|
|
# GPU_DRIVER=cuda #| rocm
|
|
|
|
## If you are using ROCM, you will need to ensure that the render group within the container and the host system use the same group ID.
|
|
## To obtain the group ID of the render group on the host system, run `getent group render` and grab the number.
|
|
# RENDER_GROUP_ID=
|
|
|
|
## CONTAINER_UID can be set to the UID of the user on the host system that should own the files in the container.
|
|
## It is usually not necessary to change this. Use `id -u` on the host system to find the UID.
|
|
# CONTAINER_UID=1000
|