* fix: pin postgres image to bookworm in docker_example to prevent collation mismatch
The postgres:16 tag silently moved its base from Debian Bookworm
(glibc 2.36) to Trixie (glibc 2.41), causing a recurring collation
version mismatch warning on existing langflow-postgres volumes.
Pin to postgres:16-bookworm in both docker-compose files and update
the README so existing data volumes keep matching the OS locale data.
Refs: https://github.com/langflow-ai/langflow/issues/9608
* docs: pin postgres image to bookworm in current docs compose snippets
Mirror the docker_example pin in the four current docs that publish
copyable Compose snippets pairing postgres:16 with a persistent
langflow-postgres volume. Prevents the same Bookworm-to-Trixie
collation version mismatch warning when users follow docs instead
of docker_example.
Versioned historical docs are left as-is.
Refs: https://github.com/langflow-ai/langflow/issues/9608
* fix: switch postgres pin from bookworm to trixie for OS consistency
Aligns the pinned postgres base with the langflow runtime image, which
moved to Debian Trixie in #12990. Keeping postgres on bookworm would
have diverged the stack and locked the database to an aging glibc that
will receive fewer security backports as bookworm ages into oldstable.
The pin itself still solves the original bug — postgres:16 cannot
silently roll its OS underneath an existing volume.
Document the one-time REFRESH COLLATION VERSION step for users
upgrading from a bookworm-initialized volume in docker_example/README.md.
Refs: https://github.com/langflow-ai/langflow/issues/9608
* fix: Resolve relative paths to absolute in Settings class
Added functionality to resolve relative paths to absolute paths in the Settings class to ensure correct handling of directory creation. This change improves robustness when dealing with user-defined paths.
* fix: Update LANGFLOW_CONFIG_DIR path in docker-compose.yml
Changed the LANGFLOW_CONFIG_DIR environment variable from a relative path to an absolute path to ensure correct directory resolution in the Docker setup. This improves the reliability of the configuration in various deployment environments.
This makes the postgres instance only reachable from the langflow container and allows it to spin up even if another process (e.g. another postgres instance) is running on the host and binds to the same port.
* chore: Update docker-build.yml to disable pre-release by default
* chore: Update Dockerfiles to set LANGFLOW_HOST and LANGFLOW_PORT
The Dockerfiles have been updated to set the environment variables LANGFLOW_HOST and LANGFLOW_PORT. This ensures that the correct host and port are used when running the langflow application.
* 🔧 (build_and_push_backend.Dockerfile): remove unnecessary host and port configuration to simplify the Dockerfile and focus on backend-only functionality
* chore: Update LANGFLOW_CONFIG_DIR in docker-compose.yml
The LANGFLOW_CONFIG_DIR environment variable in docker-compose.yml has been updated to /app/langflow. This change ensures that the correct directory is used for storing logs, file storage, monitor data, and secret keys.
* Update Dockerfile to use logspace/langflow:latest image
* Update docker-compose.yml with new version and add PostgreSQL service
* Add langflow 1.0-alpha tag
feat(Dockerfile): add gcc, g++, git, and make to apt-get install
feat(Dockerfile): add user and set environment variables
feat(Dockerfile): add WORKDIR and COPY
feat(Dockerfile): update langflow to version 0.0.71
feat(Dockerfile): add --port flag to CMD
