mirror of
https://github.com/invoke-ai/InvokeAI
synced 2024-08-30 20:32:17 +00:00
27 lines
1.4 KiB
Plaintext
27 lines
1.4 KiB
Plaintext
## 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 `nvidia` or `rocm` to enable GPU support in the container accordingly.
|
|
# GPU_DRIVER=nvidia #| rocm
|
|
|
|
## CONTAINER_UID can be set to the UID of the user on the host system that should own the files in the container.
|
|
# CONTAINER_UID=1000
|