[GH-ISSUE #11] Quickstart's compose.yaml: external postgres port mapping not needed and can cause problems #1

Closed
opened 2026-02-17 17:12:19 -05:00 by yindo · 1 comment
Owner

Originally created by @errorb0t on GitHub (Sep 25, 2025).
Original GitHub issue: https://github.com/Drop-OSS/drop-docs/issues/11

It seems to be a recurring issue for people with little experience with Docker that they are not aware whether they already have a postgres instance listening on port 5432. This is not uncommon (e.g. postgres is running there by default on Synology NAS devices). Since Drop's postgres instance is only needed for Drop itself, why not just remove the external port mapping? Should make the quickstart process go even smoother, regardless of the client's environment.

Originally created by @errorb0t on GitHub (Sep 25, 2025). Original GitHub issue: https://github.com/Drop-OSS/drop-docs/issues/11 It seems to be a recurring issue for people with little experience with Docker that they are not aware whether they already have a postgres instance listening on port 5432. This is not uncommon (e.g. postgres is running there by default on Synology NAS devices). Since Drop's postgres instance is only needed for Drop itself, why not just remove the external port mapping? Should make the quickstart process go even smoother, regardless of the client's environment.
yindo closed this issue 2026-02-17 17:12:19 -05:00
Author
Owner

@DecDuck commented on GitHub (Sep 25, 2025):

Fixed, should be visible when it rebuilds.

@DecDuck commented on GitHub (Sep 25, 2025): Fixed, should be visible when it rebuilds.
yindo changed title from Quickstart's compose.yaml: external postgres port mapping not needed and can cause problems to [GH-ISSUE #11] Quickstart's compose.yaml: external postgres port mapping not needed and can cause problems 2026-06-05 14:25:14 -04:00
Sign in to join this conversation.
1 Participants
Notifications
Due Date
No due date set.
Dependencies

No dependencies set.

Reference: Drop-OSS/drop-docs#1