Skip to content

Stat server port conflicts with user's application's port #108

Description

@joshuatshaffer

The stat collector port is read from an env variable in the server, but in the client it is defined as a constant.

// TODO
// It is better to find an available/free port automatically and use it.
// Then the post script (`post.ts`) needs to know the selected port.
const SERVER_PORT: number =
parseInt(process.env.WORKFLOW_TELEMETRY_SERVER_PORT || '') || 7777

const STAT_SERVER_PORT = 7777

This conflicts with one of the ports my application is already using. If both places read from a environment variable I could change this to a different port. I could change my application's port but it would be better if I could configure this action's port.

Metadata

Metadata

Assignees

No one assigned

    Labels

    No labels
    No labels

    Type

    No type

    Projects

    No projects

    Milestone

    No milestone

    Relationships

    None yet

    Development

    No branches or pull requests

    Issue actions