-
Notifications
You must be signed in to change notification settings - Fork 1.3k
Open
Labels
meta: never-staleThis issue can never become staleThis issue can never become staleteam: workspaceIssue belongs to the Workspace teamIssue belongs to the Workspace teamtype: feature requestNew feature or requestNew feature or request
Description
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
Shynixn, jankeromnes, axonasif, trumbitta and mapsiwilmarques
Metadata
Metadata
Assignees
Labels
meta: never-staleThis issue can never become staleThis issue can never become staleteam: workspaceIssue belongs to the Workspace teamIssue belongs to the Workspace teamtype: feature requestNew feature or requestNew feature or request