Skip to content

WEB_PORT seems hardcoded #2239

@kudkudak

Description

@kudkudak

Problem

It seems to me that passing --web-port to ./docker/run.sh doesn't have any effect. Instead, using port 3000 is hardcoded in web/setupProxy.js.

Solution

Use WEB_PORT env variable in web/setupProxy.js.

Metadata

Metadata

Assignees

No one assigned

    Labels

    No labels
    No labels

    Type

    No type
    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