- Introduction
- Getting Started
- Gitpod Tutorial
- Use Cases
- Languages
- Configure
- Workspaces
- User settings
- Repositories
- Organizations
- Authentication
- Billing
- References
- .gitpod.yml
- IDEs & editors
- Integrations
- Gitpod CLI
- Gitpod API
- Gitpod URL
- Compatibility
- Enterprise
- Overview
- Setup and Preparation
- Deploying
- Configure your Gitpod Instance
- Administration
- Upgrading
- Background
- Reference
- Archive
- Help
- Contribute
- Troubleshooting
Step 1: Start your first workspace
Gitpod workspaces are based on repositories. To open a workspace based on the EventHub repo. Click the button below to open a workspace.
Note: Opening workspaces based on repositories without commit rights—like the example above—is useful for exploring. However, when using gitpod day-to-day, you would typically use a repo you own (or have forked).
Fork the EventHub repository
Let’s fork the EventHub repository to continue. Go to the repository on GitHub and click “Fork”. This will create a copy of the code in your own Organization.
Open your repository
With your repository now forked, let’s initialise a new workspace with editable code by prefixing your git URL with https://gitpod.io/#
— for example:
https://gitpod.io/#https://github.com/gitpod-samples/EventHub/
Explore the workspace
With your workspace up, why not take a look around. Try the following:
- Open/edit a file - See how Gitpod has pulled all your files for you.
- Explore default tools - By running
npm -v
orpython --version
. - Check workspace specs - Run
gp top
for workspace memory and CPU.
Workspaces are ephemeral and entirely isolated, with full super-user privileges.
Anything you can do in Linux you can do in Gitpod. Go ahead—play around !