Closed ClementVanPeuter closed 2 months ago
Because the aurora database is on the private subnets, which is not allowed to access from outside of the vpc. To test functionality related to aurora, we need to add bastion as a proxy.
@statefb Thank you for the explanation.
@ClementVanPeuter Your welcome, let me close the issue
Describe the bug
In local development the POST /conversation/related-documents route throw a 500 , in the local UI, ( like a timeout or so) even having filled in the env variables ( DB_NAME, DB_USER, DB_PASSWORD, DB_PORT). Am I missing something about this ?
To Reproduce
Set all the env var according to the local development backend and frontend Readme.
VITE_APP_API_ENDPOINT
pointing on the local python backend. And exporting all the env vars according to the backend local dev README + DB_NAME, DB_USER, DB_PASSWORD, DB_PORT.Backend is plug to AWS services and nothing in local ( Nor Docker, Postgres or anything) pointing straight out to AWS services.
1.Launch local UI. 2.Ask a question ( for a RAG answer) Network console show a 500 on the /conversation/related-documents route