Custom domain for the IDE

[JeremyJaydan]

Ability to add a CNAME which is somehow directed to your current active workspace's open ports would be cool.

[svenefftinge]

We'd rather integrate well with services that do these things better, such as now.sh, netlify, platform.sh etc. Would that be good enough in your case?

[JeremyJaydan]

Yeah those make sense for deployment although I'm thinking in terms of sharing a custom URL with friends which shows the live development version (which would stop working when I close a workspace).

Something like https://dev.example.com would show the live development version of https://example.com

[JeremyJaydan]

I'm not 100% on the idea though, I understand how complex this can be for the actual returned benefit. More of a "nice to have".

[meysholdt]

I'd also prefer to integrate with other platform such as now.sh, netlify, platform.sh... they're optimised to have services running continuously at high density.

But to discuss your request, I think there are two possibilities:
a) allow custom subdomains, e.g. jeremys-app.apps-eu.gitpod.io, with you having it named jeremys-app.
b) allow custom top-level domains, e.g. jeremys-app.com

While (a) could be doable, (b) brings more challenges:

• request ssl certs on-demand
• you, as the owner of your domain, would need to configure one of Gitpod's IPs in your DNS

[JeremyJaydan]

(a) sounds like a great idea, maybe it could be part of the configuration:

# The Docker image to run your workspace in. Defaults to gitpod/workspace-full
image: "<your-workspace-image>"
# Command to start on workspace startup (optional)
tasks:
  - command: "yarn install && yarn build"
# Ports to expose on workspace startup (optional)
ports:
  - port: 8000
# Sub domain
domain: "jeremys-app"

[meysholdt]

what would be the behaviour when multiple workspaces on the same git-repo (and therefore with the same config) are launched?

[JeremyJaydan]

That's a tricky one, which made me also think.. custom sub domains would need to only work on per-account basis since snapshots could also cause a similar conflict. I think to get to the root of the "issue", it's the long url. Maybe a gitpod url shortener would do the trick.

[svenefftinge]

One reason I'd consider such a feature is to allow an easy way to show and share your work, without additional tools. I.e. I'd love to see gitpod having a similar feature than the online playgrounds or glitch and repl.it, in that you can embed the website you built in a small widget and from the open the IDE (based on a snapshot) or open the website in a new tab.
But still, ideally we integrate/collaborate with a third party that does this stuff already well so we can keep our focus.

[JeremyJaydan]

Regarding embedding widgets & playgrounds, sounds like adding support for GitHub gists would be make that idea come to life. You could pull in a gist repo, edit files, push back. From there, gitpod could have a sibling service for gist rendering (similar to my gistpage project) to render certain kinds of previews & include a button to launch the IDE.

[csweichel]

related: #70

Hello,

I'd also like to have a custom subdomain for accessing the workspace. Then I can seperate the workspaces for frontend and backend development and access the backend from the frontend while developing. This would be much faster than deploying my development snapshot to the dev stage of the cloud.

Best regards,
Thomas

[stale]

This issue has been automatically marked as stale because it has not had recent activity. It will be closed if no further activity occurs. Thank you for your contributions.