- Configure Your Project
- Docker Configuration
- Start Tasks
- VS Code Extensions
- Exposing Ports
- Prebuilt Workspaces
- Environment Variables
- Workspace Location
- Editor Configuration
- Gitpod Self-Hosted
- Install on Google Cloud Platform
- Install on Amazon Web Services
- Install on self-managed Kubernetes
- Configure OAuth
- Configure a Domain
- Configure HTTPS Certificates
- Configure a Database
- Configure a Docker Registry
- Configure Storage
- Configure Nodes
- Configure Workspaces
- Languages & Frameworks
If you want to access services running in your workspace, e.g. a development HTTP server on port
you need to expose that port first. Gitpod has two means of doing that:
- On-the-fly: when you start a process which listens on a port in your workspace, Gitpod will ask you if you want to expose that port to the internet.
- In your configuration: if you already know that you want a particular port exposed, you can configure
it in the
.gitpod.ymlfile and skip the extra click later on. For example:
ports: - port: 8080
Ports are mapped to their own URLs. In a workspace you can get the URL mapped to a port using
gp url <port>. At the moment you can only expose
You can configure entire ranges and tell Gitpod how it should behave when a service in such a range is opened.
For instance, the following configs will stop notifying the user when a service opens on a port between 3000 and 8999:
ports: - port: 3000-8999 onOpen: ignore
When a newly started service gets detected, you usually get a notification telling you about it.
If it is not yet exposed, because it is not listed in the
.gitpod.yml, the notification will allow you to expose the port.
If it is already exposed, either through the
.gitpod.yml or by manually exposing it, the notification asks
whether and how to open it.
To change this behavior you can provide the property
It has four possible values:
notify(default) - Show the notification.
open-preview- Open in the preview on the right.
open-browser- Open in a browser tab.
ignore- Don’t do anything.
Any changes to the
.gitpod.yml will have effect immediately.
Still Have Questions?
Please reach out. We’re happy to answer them.