Skip to content

Hardcoded servers definition makes swagger UI usage not possible, when using a load balancer #2

@Ocramius

Description

@Ocramius

I'm aware that StraightMail was designed to stay within its own VPC network (not exposed to the outside), but in a dev environment, it is not uncommon to make the HTTP traffic available to the host, either via:

  • port forwarding
  • ngrok-alike tunnel
  • traefik and Host header routing
  • path routing
  • etc...

The current API location (according to swagger UI) is hardcoded:

Perhaps that can be dropped, letting swagger use the current host as server URI?

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