A workspace is what the user would interact with day to day. You can create a new workspace directly from a repository link, or a project.

Workspace Creation

You can create a workspace directly from a repository URL. It should accept any URL that you can git clone. Any public Git repositories or your private repositories will be supported.

When the workspace is created, Lapdev will try to read the devcontainers config in the repository, and build the workspace image based on the devcontainers config. After the image is built, the workspace container instance will be created based on that image.

After the workspace is created, you can click Open to open the web IDE, or Open it in your local VSCode.

You can start/stop/delete the workspace.

If the repository is worked on by your team, we suggest you add the repository as a project. Then the whole team will benefit from prebuilds, which saves everyone from building the image again and again. You can learn more about projects here.

Docker Compose

If you've defined Docker Compose in your devcontainer, all the services will be created in separate containers, and when you start/stop/delete the workspace, all the containers will be controlled at the same time. Within each container, you can access other containers by their service name, just like what you'd expect in Docker Compose. You can also open and get into each container individually.

Workspace Access

You can access the workspace by SSH. And the details are on the workspace details page. To be able to access workspaces by SSH, you'll need to add your SSH public keys to your user settings.

Last updated