No place for UNSTRUCTURED_API_KEY
JSemc2 opened this issue · comments
Self Checks
- This is only for bug report, if you would like to ask a question, please head to Discussions.
- I have searched for existing issues search for existing issues, including closed ones.
- I confirm that I am using English to submit this report (我已阅读并同意 Language Policy).
- 请务必使用英文提交 Issue,否则会被关闭。谢谢!:)
- Please do not modify this template :) and fill in all the required fields.
Dify version
0.6.12-fix1
Cloud or Self Hosted
Self Hosted (Docker)
Steps to reproduce
✔️ Expected Behavior
There is no place to write a API key for UNSTRUCTURED.
❌ Actual Behavior
No response
@JSemc2 Hello there! I'm here to help you with any bugs, questions, or contributions. Let's work together to solve the issue you're facing.
You can write the API key for UNSTRUCTURED_API_KEY
in the .env
file under the UNSTRUCTURED_API_KEY
variable.
Here is the relevant section from the .env.example
file:
UNSTRUCTURED_API_URL=
UNSTRUCTURED_API_KEY=
You should set the UNSTRUCTURED_API_KEY
variable to your API key. For example:
UNSTRUCTURED_API_KEY=your-api-key-here
Make sure to also set the ETL_TYPE
to Unstructured
and configure the UNSTRUCTURED_API_URL
with the appropriate API path if you are using the Unstructured.io file extraction scheme:
ETL_TYPE=Unstructured
UNSTRUCTURED_API_URL=http://unstructured:8000/general/v0/general
This will enable the use of the UNSTRUCTURED_API_KEY
in the Dify application [1][2].
In docker/.env
ETL_TYPE=
UNSTRUCTURED_API_URL=
UNSTRUCTURED_API_KEY=
Thanks.