Skip to content

Port inconsistency: Dockerfile exposes 3000 but CLI defaults to 9090 #273

Description

@ajianaz

Problem

Dockerfile and CLI binary disagree on the default listen port:

Source Port File
Dockerfile EXPOSE / ENV TRAPFALL_LISTEN 3000 Dockerfile L54, L59
CLI default_value 9090 crates/trapfalld/src/main.rs L37
README docker example 3000 README.md L30
Marketing copy (all slides, docs) Mixed 3000/9090 codecoradev/marketing

This causes confusion for users: the published Docker image listens on 3000, but if someone builds from source or runs the binary directly, it listens on 9090.

Suggested Fix

Standardize on one port across all surfaces:

  1. Dockerfile — update ENV TRAPFALL_LISTEN + EXPOSE to match CLI default
  2. README — update all docker run -p examples
  3. README — update localhost:3000 references
  4. Marketing repo — update carousel slides + per-product-copy (we'll handle this side)

Trade-off: 3000 vs 9090

Factor 3000 9090
Convention Common dev server port (Grafana, etc.) Sentry-compatible (Sentry default is 9000, adjacent)
Collision risk Higher (many apps use 3000) Lower
Current Docker ✅ Active ❌ CLI only
Current README ✅ Active ❌ Not used

Recommendation: Pick one and stick with it. If Sentry compatibility matters (users coming from Sentry expect ports near 9000), go 9090. If simplicity matters, go 3000 since Dockerfile + README already use it.

Discovered By

Cora AI code review (cora review) on codecoradev/marketing commit 1ef8af6 — flagged 3 MAJOR issues for port mismatch between carousel slides and copy pack.

Metadata

Metadata

Assignees

No one assigned

    Labels

    No labels
    No labels

    Type

    No type

    Fields

    No fields configured for issues without a type.

    Projects

    No projects

    Milestone

    No milestone

    Relationships

    None yet

    Development

    No branches or pull requests

    Issue actions