Skip to content

Include port information in status messages #633

Open

Description

@fubarhouse

Changing the port breaks the urls in the status command when testing and printing them, this would be a nice quick win to solve.

Activity

  1. fubarhouse commented on May 21, 2025

    @fubarhouse
    CollaboratorAuthor

    Looks like the cleanest way to get around this consistently and reliably is to set an environment variable which will manually associate a port number to all the URLs.

    Containers/services themselves are extremely customizable, can have multiple ports and getting the right information at the right time for every use-case is simply going to create more problems than it would solve.

    For now I'm working on something which uses PYGMY_WEB_PORT and injects it into the list of endpoints.

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

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