We read every piece of feedback, and take your input very seriously.
To see all available qualifiers, see our documentation.
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
We currently have two settings:
WAGTAIL_VECTOR_INDEX, where configuration for AI backends is managed. WAGTAIL_VECTOR_INDEX_VECTOR_BACKENDS, where storage backends are managed.
WAGTAIL_VECTOR_INDEX
WAGTAIL_VECTOR_INDEX_VECTOR_BACKENDS
It probably makes sense to simplify these and move the vector backend config to be a key in the more general WAGTAIL_VECTOR_INDEX setting.
As part of this, we can also correct the example on https://wagtail-vector-index.readthedocs.io/en/latest/vector-backends/ which implies that setting is used to configure OpenAI as a backend.
The text was updated successfully, but these errors were encountered:
No branches or pull requests
We currently have two settings:
WAGTAIL_VECTOR_INDEX
, where configuration for AI backends is managed.WAGTAIL_VECTOR_INDEX_VECTOR_BACKENDS
, where storage backends are managed.It probably makes sense to simplify these and move the vector backend config to be a key in the more general
WAGTAIL_VECTOR_INDEX
setting.As part of this, we can also correct the example on https://wagtail-vector-index.readthedocs.io/en/latest/vector-backends/ which implies that setting is used to configure OpenAI as a backend.
The text was updated successfully, but these errors were encountered: