Skip to content

Fix PostgreSQL port exposure in docker-compose - #2530

Merged
abimaelmartell merged 2 commits into
mainfrom
docker-compose-db-port
Dec 10, 2025
Merged

abimaelmartell merged 2 commits into
mainfrom
docker-compose-db-port

Conversation

@abimaelmartell

@abimaelmartell abimaelmartell commented Dec 9, 2025

Copy link
Copy Markdown
Member
  • Fix PostgreSQL port exposure in docker-compose
  • fix defaults

Summary by cubic

Stop exposing PostgreSQL in docker-compose and align DB defaults. This reduces the attack surface and clarifies the self-hosting setup.

  • Migration
    • If you were connecting via localhost:5432, use docker compose exec nuq-postgres psql instead (or add a temporary, firewalled port mapping).
    • Ensure POSTGRES_USER, POSTGRES_PASSWORD, and POSTGRES_DB match between your .env and docker-compose; defaults are now firecrawl/firecrawl_password/firecrawl, and USE_DB_AUTHENTICATION defaults to false.

Written for commit e87a7a7. Summary will update automatically on new commits.

@cubic-dev-ai cubic-dev-ai Bot left a comment

Copy link
Copy Markdown
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

No issues found across 2 files

@abimaelmartell
abimaelmartell merged commit 8e5acd8 into main Dec 10, 2025
12 checks passed
jerbao pushed a commit to jerbao/firecrawl-custom that referenced this pull request Aug 22, 2026
* Fix PostgreSQL port exposure in docker-compose

* fix defaults
zeekay pushed a commit to Dream-AI-4444/firecrawl that referenced this pull request Sep 10, 2026
* Fix PostgreSQL port exposure in docker-compose

* fix defaults
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

2 participants