Skip to main content
InfraGap.com Logo
Home
Getting Started
Core Concept What is a CDE? How It Works Benefits CDE Assessment Getting Started Guide
Implementation
Architecture Patterns DevContainers Language Quickstarts IDE Integration AI/ML Workloads Advanced DevContainers
Operations
Performance Optimization High Availability & DR Monitoring Capacity Planning Troubleshooting Runbooks
Security
Security Deep Dive Secrets Management Vulnerability Management Network Security IAM Guide Compliance Guide
Planning
Pilot Program Design Stakeholder Communication Risk Management Migration Guide Cost Analysis Vendor Evaluation Training Resources Team Structure Industry Guides
Resources
Tools Comparison CDE vs Alternatives Case Studies Lessons Learned Glossary FAQ

Getting Started with CDEs

Your complete quickstart guide to cloud development environments - from zero to productive in minutes

Before You Start

Any Computer

CDEs work from any machine with a browser or SSH client - even a Chromebook or tablet.

Internet Connection

A stable internet connection is required. Most CDEs work well on connections 10Mbps+.

Git Repository

Your code hosted on GitHub, GitLab, Bitbucket, or any Git provider.

New to Cloud Development?

No worries - you don't need to change how you code. CDEs feel like local development but run in the cloud. Your favorite IDE, keybindings, and extensions all work the same way.

5-Minute Quickstart (GitHub Codespaces)

GitHub Codespaces is the fastest way to try CDEs. Free tier includes 60 hours/month.

1

Go to Your Repository

Navigate to any GitHub repository you want to work on.

https://github.com/your-org/your-repo
2

Press the Period Key

On any GitHub repo page, press . (period) to open github.dev instantly.

Or click the green "Code" button and select "Codespaces" tab.

3

Create a Codespace

Click "Create codespace on main" - your environment will be ready in ~30 seconds.

That's it! You're now coding in the cloud.
4

Start Coding

You're now in a full VS Code environment. Run commands in the terminal, install extensions, and commit changes.

# Example: Run your project
npm install
npm run dev

Choose Your Platform

Different platforms suit different needs. Here's how to get started with each major CDE provider.

GitHub Codespaces

Best for GitHub-centric teams wanting zero-config cloud development.

  • 60 free hours/month
  • Deep GitHub integration
  • No infrastructure needed
Get Started

Gitpod

Container-based environments with powerful prebuilds for instant startup.

  • 50 free hours/month
  • Works with any Git host
  • SaaS or self-hosted
Get Started

Coder

Self-hosted with Terraform - ultimate flexibility and control.

  • Open source core
  • Any cloud or on-prem
  • Enterprise compliance
Get Started

DevPod

Open-source desktop app for running DevContainers anywhere.

  • 100% free and open source
  • Works with any provider
  • Desktop + CLI
Get Started

Daytona

Open-source platform focusing on developer experience.

  • Apache 2.0 license
  • Multi-IDE support
  • Enterprise features
Get Started

VS Code Remote SSH

Connect VS Code to any Linux machine via SSH - DIY approach.

  • Free (your infra costs)
  • Full VS Code experience
  • Maximum flexibility
Get Started

Connect Your Favorite IDE

VS Code

Most popular choice

1

Install the "Remote - SSH" extension from the marketplace

2

Press F1 and select "Remote-SSH: Connect to Host"

3

Enter your workspace SSH connection string

# Example SSH config
Host my-workspace
  HostName workspace.example.com
  User developer

JetBrains IDEs

IntelliJ, PyCharm, GoLand, etc.

1

Download JetBrains Gateway (free)

2

Select your CDE provider (Coder, Gitpod, etc.) or SSH

3

Gateway installs the IDE backend and connects you

Pro tip: Gateway only runs the frontend locally - the IDE runs on your CDE for maximum performance.

Browser-Based (No Install)

Access from any device

Most CDEs include a web-based VS Code (code-server) that runs directly in your browser. Just click a link and start coding - no installation required.

Chrome Firefox Safari Edge

Setting Up DevContainers

DevContainers define your development environment as code. Add one to your repo and everyone gets the same setup.

Create .devcontainer/devcontainer.json

{
  "name": "My Project",
  "image": "mcr.microsoft.com/devcontainers/base:ubuntu",

  // Install Node.js and Python
  "features": {
    "ghcr.io/devcontainers/features/node:1": {},
    "ghcr.io/devcontainers/features/python:1": {}
  },

  // VS Code extensions to install
  "customizations": {
    "vscode": {
      "extensions": [
        "esbenp.prettier-vscode",
        "dbaeumer.vscode-eslint"
      ]
    }
  },

  // Commands to run after container starts
  "postCreateCommand": "npm install",

  // Ports to forward
  "forwardPorts": [3000, 8080]
}
image - Base container image (Ubuntu, Debian, Alpine, etc.)
features - Reusable components (languages, tools, CLIs)
customizations - IDE extensions and settings
postCreateCommand - Setup scripts (install dependencies)

Common First Tasks

Set Up Git Credentials

git config --global user.name "Your Name"
git config --global user.email "[email protected]"

Most CDEs inherit credentials from your SSO login.

Forward Ports

# In VS Code, open the Ports panel
# Or use the terminal:
npm run dev -- --port 3000

CDEs auto-detect and forward ports to your browser.

Install Extensions

Your extensions install on the remote machine, not locally. Add them to devcontainer.json to share with your team.

"extensions": ["esbenp.prettier-vscode"]

Configure Secrets

Never put secrets in devcontainer.json. Use your CDE's secret management:

  • - Codespaces: Repository secrets
  • - Coder: Workspace parameters
  • - Gitpod: Environment variables

Common Issues & Solutions

Connection drops or is slow
  • - Check your internet connection stability
  • - Try a wired connection instead of WiFi
  • - Reduce the workspace machine type if not needed
  • - Contact your IT team about firewall settings for port 22 (SSH)
Extensions not working
  • - Extensions run remotely, not locally - reinstall them in the workspace
  • - Some extensions require specific dependencies - check extension docs
  • - UI extensions need to be installed locally, workspace extensions remotely
Git authentication issues
  • - Use SSH keys instead of HTTPS for Git operations
  • - Enable credential forwarding in your CDE settings
  • - For Codespaces: GitHub credentials are automatic
  • - For others: Add your SSH key to the workspace or use SSH agent forwarding
Workspace won't start
  • - Check if you've exceeded your quota (Codespaces: 60 hours free)
  • - Try rebuilding the container (may fix corrupted state)
  • - Check for syntax errors in devcontainer.json
  • - Review the creation logs for specific error messages