Replies: 1 comment
-
|
You should be able to use PostgreSQL with the docker-compose.yml in the deploy folder. The most common reason Langflow falls back to SQLite is if the LANGFLOW_DATABASE_URL environment variable isn't set to a PostgreSQL connection string. Double-check that your .env file (or environment variables) includes something like: and that your docker-compose.yml references this .env file. If this variable is missing or misconfigured, Langflow will default to SQLite instead of PostgreSQL reference. The docker-compose.yml in the deploy folder already defines a PostgreSQL service under the db section, so no changes should be needed there reference. Just make sure your environment variables are set up correctly. If you’re still seeing SQLite, check your logs for any warnings about missing database URLs. To reply, just mention @dosu. How did I do? Good | Irrelevant | Incorrect | Verbose | Hallucination | Report 🐛 | Other |
Beta Was this translation helpful? Give feedback.
Uh oh!
There was an error while loading. Please reload this page.
-
When I deploy from a docker-compose.yml file in the deploy folder, I can only use the sqlite service instead of PostgreSQL?
Beta Was this translation helpful? Give feedback.
All reactions