search

AppFlowy-IO / AppFlowy-Cloud

AppFlowy is an open-source alternative to Notion. You are in charge of your data and customizations. Built with Flutter and Rust.
GNU Affero General Public License v3.0
1.05k stars 220 forks source link

[Bug] Possible variable naming error in deploy.env or docker-compose.yml #802

Closed IgniKSJ closed 1 month ago

IgniKSJ commented 2 months ago

I found this problem following the self-host documentation. It advices to use "deploy.env" as a template to create the ".env" file. Everything works but for the "APPFLOWY_AI_OPENAI_API_KEY", i had to change its name to "APPFLOWY_OPENAI_API_KEY" in order for it to work. Since the previous variable name follows the naming conventions in the rest of the file, guess the problem is in line 117 of docker-compose.yml "APPFLOWY_OPENAI_API_KEY=${APPFLOWY_OPENAI_API_KEY}" should be changed to "APPFLOWY_OPENAI_API_KEY=${APPFLOWY_AI_OPENAI_API_KEY}"

To Reproduce Steps to reproduce the behavior: Follow the lastest selh-hosting tutorial. The problem emerges when trying to compose with the said variable, since it is badly named, the compose script warns you that you haven't set up the openai api key and it will use a blank string by default. I have done this in a clean ubuntu installation, using docker desktop.

khorshuheng commented 2 months ago

Actually, line 117 should be removed entirely - AppFlowy cloud service actually doesn't communicate directly with OpenAI, it is the other service, appflowy AI, that does this.

Thanks for raising this, we will fix the docker compose file.

almereyda commented 1 month ago

Related to