kb01/zmk
1
0
Fork 0
Code Issues Pull requests Projects Releases Packages Wiki Activity Actions

Moved info

Browse source 
Co-authored-by: Cem Aksoylar <caksoylar@users.noreply.github.com>
This commit is contained in:
Nicolas Munnich 2024-05-21 18:03:33 +02:00 • committed by GitHub
parent 57b329a52e
commit 4982d2ecd8
No known key found for this signature in database
GPG key ID: B5690EEEBB952194
1 changed files with 1 additions and 5 deletions
Show stats Download patch file Download diff file Expand all files Collapse all files

6
docs/docs/development/setup/docker.md
View file

@ -33,14 +33,10 @@ Open the `zmk` checkout folder in VS Code. The repository includes a configurati
![VS Code Dev Container Configuration Alert](../../assets/dev-setup/vscode_devcontainer.png) ![VS Code Dev Container Configuration Alert](../../assets/dev-setup/vscode_devcontainer.png)
Click `Reopen in Container` in order to reopen the VS Code with the running container. Click `Reopen in Container` in order to reopen the VS Code with the running container. If the alert fails to pop up or you accidentally close it, you can perform the same action by pressing `ctrl+shift+p` and selecting `Remote: Show Remote Menu`.
The first time you do this on your machine, it will pull the docker image down from the registry and build the container. Subsequent launches are much faster! The first time you do this on your machine, it will pull the docker image down from the registry and build the container. Subsequent launches are much faster!
:::note
If the alert fails to pop up or you accidentally close it, you can perform the same action from the remote menu: `ctrl+shift+p` and invoke `Remote: Show Remote Menu`.
:::
:::caution :::caution
All subsequent steps must be performed from the VS Code terminal _inside_ the container. All subsequent steps must be performed from the VS Code terminal _inside_ the container.
::: :::