- Introduction
- Getting started
- Configuration
- Dev Container
- Automations
- Editors
- VS Code
- Cursor
- JetBrains
- Zed
- Gitpod Desktop
- Self-Hosted Runner
- AWS
- Azure
Coming soon
- GCP
Coming soon
- Linux
Coming soon
- Source Control
- GitHub
- GitLab
Coming soon
- Bitbucket
Coming soon
- Integrations
- Port sharing
- Personal access tokens
- Administration
- Organizations
- Projects
- Billing
- Reference
- CLI
Ingress Handling
Runner SCM OAuth
The Gitpod Gateway manages OAuth flow for source control management (SCM) systems as follows:
A Runner that uses a Gateway exposes a unique OAuth callback URL for each configured SCM (please check Runners—SCM integrations).
Users are redirected to the SCM provider’s authorization page when they initiate an OAuth flow.
After authorization, the SCM provider redirects to the Gateway’s callback URL.
The Runner Server verifies the OAuth state and exchanges the code for an access token.
Environment Logs Ingress
Each environment runs a process that orchestrates the lifecycle, including the devcontainer build/run/rebuild.
The environment exposes logs on a local port (22999) and automatically exposes them over the Nebula network.
Only Proxy nodes can reach this port in the Nebula network using the group “proxy” in the Nebula Certificate.