Skip to content

Expose workspace ports on external IP #459

Open
@geropl

Description

@geropl

Currently the model we use for accessing workspace ports is different to 'real' machines our users are used to.

Problems with this approach:

  • limited to https
  • a lot of frontends try to connect to backends using the pattern ${window.location.hostname}:${port}, which does not work with Gitpod (example: trying to get hot loader working #435 (comment) f). Only solution: patch the respective code or put proxy in front

A solution would be to expose workspaces under a IP6 address. Then each workspace would be accessible under: :
Optionally, we could add a (customizable) DNS entry for that as well (see #329)

This would allow other usecases:

  • ssh access into workspaces to integrate with local environment
  • none-https traffic

Metadata

Metadata

Assignees

No one assigned

    Labels

    Type

    No type

    Projects

    Milestone

    No milestone

    Relationships

    None yet

    Development

    No branches or pull requests

    Issue actions