You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Copy file name to clipboardExpand all lines: packages/projects-docs/pages/faq.mdx
+6-6Lines changed: 6 additions & 6 deletions
Display the source diff
Display the rich diff
Original file line number
Diff line number
Diff line change
@@ -68,7 +68,7 @@ recommend using a [Devbox](/learn/devboxes/overview).
68
68
69
69
## Can I change the Node version used in a Devbox?
70
70
71
-
Yes, we have instructions [here](https://codesandbox.io/docs/learn/environment/vm#configuring-nodejs-version) that tell you how to change the Node version. All recent server sandboxes run in a Devbox.
71
+
Yes, we have instructions on the [VM configuration](https://codesandbox.io/docs/learn/environment/vm#configuring-nodejs-version) page that tell you how to change the Node version. All recent server sandboxes run in a Devbox.
72
72
73
73
## How can I change the editor's theme?
74
74
@@ -118,7 +118,7 @@ Yes, you can use multiple databases in the same project by running multiple Dock
118
118
119
119
### Can I use Docker Compose in CodeSandbox?
120
120
121
-
Yes, you can use Docker Compose in CodeSandbox to orchestrate multiple containers and define the relationships between them. However, you'll need to create a Docker Compose file and run the `docker-compose` command in the terminal to start the containers. We share more about this [here](https://codesandbox.io/docs/tutorial/getting-started-with-docker#4-create-docker-compose-file).
121
+
Yes, you can use Docker Compose in CodeSandbox to orchestrate multiple containers and define the relationships between them. However, you'll need to create a Docker Compose file and run the `docker-compose` command in the terminal to start the containers. We share more about this [in our Docker tutorial](https://codesandbox.io/docs/tutorial/getting-started-with-docker#4-create-docker-compose-file).
122
122
123
123
### Is it safe to use a database in CodeSandbox with Docker support?
124
124
@@ -268,9 +268,10 @@ The user will receive an email invitation and in-app notification asking them to
268
268
You can leave or delete a workspace from the "Overview" tab of your [Workspace Settings](https://codesandbox.io/t/overview), by clicking on "Leave workspace", or "Delete workspace", respectively.
269
269
270
270
There are some cases where leaving a workspace is not permitted.
271
-
1. You are the only workspace member with admin rights: Every workspace requires at least one admin member. Before you can leave the workspace, you must assign a new admin.
272
271
273
-
2. You are trying to leave the only workspace connected to your account: Every account must be associated with at least one workspace. If you want to leave the only workspace connected to your account, you may create a new workspace and then leave the workspace you want to be disassociated with. Alternatively, deleting your account will remove you from any workspaces that you are a member of.
272
+
1. You are the only workspace member with admin rights: Every workspace requires at least one admin member. Before you can leave the workspace, you must assign a new admin.
273
+
274
+
2. You are trying to leave the only workspace connected to your account: Every account must be associated with at least one workspace. If you want to leave the only workspace connected to your account, you may create a new workspace and then leave the workspace you want to be disassociated with. Alternatively, deleting your account will remove you from any workspaces that you are a member of.
274
275
275
276
## How can I change my account's email address?
276
277
@@ -343,8 +344,7 @@ If everything seems to be in order but you're still having issues with the payme
343
344
344
345
## Can I change my subscription?
345
346
346
-
Yes, you can upgrade or downgrade your plan at any time from the settings page.
347
-
347
+
Yes, you can upgrade or downgrade your plan at any time from the settings page.
Copy file name to clipboardExpand all lines: packages/projects-docs/pages/learn/editors/desktop-interface.mdx
+18-18Lines changed: 18 additions & 18 deletions
Display the source diff
Display the rich diff
Original file line number
Diff line number
Diff line change
@@ -10,27 +10,27 @@ import Video from '../../../../../shared-components/Video'
10
10
11
11
12
12
13
-
Develop any repository or devbox in your VS Code Deskop app and enjoy uniterrupted use of all the extensions and keybindings that you’ve already configured.
14
-
The CodeSandbox extenstion provides seamless interaction with all core features allowing you to retain the efficiencies and collaboration of CodeSandbox in the comfort of your own setup.
13
+
Develop any repository or Devbox in your VS Code Desktop app and enjoy uninterrupted use of all the extensions and keybindings you’ve already configured.
14
+
The CodeSandbox extension provides seamless interaction with all core features allowing you to retain the efficiency and collaboration of CodeSandbox in the comfort of your own setup.
15
15
16
16
<br/>
17
17
## Open your project from the web editor
18
18
19
-
You can jump to VS Code at anytime from the browser
19
+
You can jump to VS Code at anytime from the browser, as shown below.
20
20
21
21
22
22
23
-
> We also support opening the branch [Using Visual Studio Insiders](./insiders).
23
+
> We also support opening the branch using [Visual Studio Insiders](./insiders).
24
24
25
25
## Open your project from VS Code Desktop
26
26
27
-
Once the extension is installed, you can open a devbox or repo branch from the Dashboard section.
27
+
Once the extension is installed, you can open a Devbox or repo branch from the Dashboard section, as shown below.
28
28
29
29
30
30
31
31
You will only be able to select from a list of repositories that have been imported to CodeSandbox. If you don’t see your project in the list, check your dashboard on CodeSandbox to make sure everything is set up there first.
32
32
33
-
If at any point, you want to switch to the CodeSandbox editor, simply click ‘Open in CodeSandbox’ under the ‘Control Panel’
33
+
If, at any point, you want to switch to the CodeSandbox editor, simply click ‘Open in CodeSandbox’ under the ‘Control Panel’.
34
34
35
35
<br/>
36
36
## Control Panel
@@ -42,7 +42,7 @@ The control panel contains actions for managing branches, opening a PR, and eval
42
42
<br/>
43
43
## DevTools
44
44
45
-
Just like in the CodeSandbox editor, you have access to running ports to view code changes in the browser. The available ports are listed in the panel. Clicking on a port will open a tab in your default browser
45
+
Just like in the CodeSandbox editor, you can access running ports to view code changes in the browser. The available ports are listed in the panel. Clicking on a port will open a tab in your default browser.
@@ -52,24 +52,24 @@ Just like in the CodeSandbox editor, you have access to running ports to view co
52
52
<br/>
53
53
### View collaborators
54
54
55
-
Once you are connected to the branch, you will be able to see a list of teammates that are active on the branch. You can see the list of collaborators as well as the environment they are working from.
55
+
Once you are connected to the branch, you will be able to see a list of teammates who are active on the branch. You can also see the list of collaborators and the environment they are working from.
In this case, I am active in both VS Code and the CodeSandbox editor.
59
+
In this case, the displayed user is active in both VS Code and the CodeSandbox editor.
60
60
61
61
### Multiplayer Changes
62
62
63
-
Changes that are made to a file are reflected in the editor of every user. Select the name of a collaboratorto focus on the file and line that they are working on
63
+
Changes made to a file are reflected in every user's editor. You can click on a collaborator's name to focus on the file and line that they are working on.
64
64
65
65
<Videosrc="../../vscode-following.mp4" />
66
66
67
67
<br/>
68
68
## Reviewing PRs in VS Code
69
69
70
-
You can review PRs directly from VS Code while connected to CodeSandbox. To do this, you should install the [GitHub App of CodeSandbox](/learn/integrations/github-app). With this app, every PR will have a link to open the branch in VS Code.
70
+
You can review PRs directly from VS Code while connected to CodeSandbox. To do this, you should install the [CodeSandbox GitHub App](/learn/integrations/github-app). With this app, every PR will have a link to open the branch in VS Code.
71
71
72
-
We also recommend to install the [GitHub Pull Request](https://marketplace.visualstudio.com/items?itemName=GitHub.vscode-pull-request-github) extension, and configure it as a default extension in your user settings (as outlined [here](#default-user-extensions)). With this extension you can put comments on GitHub directly from your editor.
72
+
We also recommend installing the [GitHub Pull Request](https://marketplace.visualstudio.com/items?itemName=GitHub.vscode-pull-request-github) extension and configuring it as a default extension in your user settings (as outlined [below](#default-user-extensions)). With this extension, you can post comments on GitHub directly from your editor.
73
73
74
74
<br/>
75
75
## Settings & Extensions
@@ -88,13 +88,13 @@ This will make sure that Prettier and ESLint are installed whenever someone open
88
88
89
89
### Default User Extensions
90
90
91
-
In case you have any personal extensions that you want to have in every branch, you can define those in your VS Code settings under the setting id `remote.SSH.defaultExtensions`. To change this setting, you can open VS Code settings (`CMD/Ctrl + ,`) and search for `remote.SSH.defaultExtensions`.
91
+
If you have any personal extensions you want in every branch, you can define those in your VS Code settings under the setting id `remote.SSH.defaultExtensions`. To change this setting, you can open VS Code settings (`CMD/Ctrl + ,`) and search for `remote.SSH.defaultExtensions`.
92
92
93
93
You can copy your favourite VS Code extension ids, and put them in that setting. From then on, these extensions will be automatically installed in your branches.
94
94
95
95
### VS Code Setting Sync
96
96
97
-
To sync your settings and keybindings between branches, you can enable VS Code Setting Sync. To learn more about how to set this up, you can check [here](https://code.visualstudio.com/docs/editor/settings-sync).
97
+
To sync your settings and keybindings between branches, you can enable VS Code Setting Sync. To learn more about how to set this up, you can check the [VS Code Docs](https://code.visualstudio.com/docs/editor/settings-sync).
98
98
99
99
<br/>
100
100
## FAQs
@@ -103,12 +103,12 @@ To sync your settings and keybindings between branches, you can enable VS Code S
103
103
104
104
105
105
106
-
This modal shows up every time you launch a project folder in a new container. Since every branch will be opened with a unique SSH url, VS Code will ask you to verify that you trust the connection. This is an important security notice used to confirm that the user understands the connection being established before opening the code. You can read more about the modal [here](https://code.visualstudio.com/blogs/2021/07/06/workspace-trust).
106
+
This modal shows up every time you launch a project folder in a new container. Since every branch will be opened with a unique SSH url, VS Code will ask you to verify that you trust the connection. This is an important security notice used to confirm that the user understands the connection being established before opening the code. You can read more about the modal in the [VS Code blog](https://code.visualstudio.com/blogs/2021/07/06/workspace-trust).
107
107
108
-
### Do I have to be connected to live session on CodeSandbox in order to work on a branch?
108
+
### Do I have to be connected to a live session on CodeSandbox in order to work on a branch?
109
109
110
-
It is possible to work in an “un-synced” state. In order for CodeSandbox features to work, the branch needs to established on a remote connection AND connected to Pitcher (see How it works for more information
110
+
It is possible to work in an “un-synced” state. In order for CodeSandbox features to work, the branch needs to be established on a remote connection AND connected to Pitcher (see 'How it works' for more information).
111
111
112
112
### Who can access my code?
113
113
114
-
Only people on your CodeSandbox team with permissions to the repository may join as a collaborator. Repository permissions are carried over from GitHub. To add someone new to the team, provide access on GitHub and add them to the CodeSandbox. From there, they can access the code in the browser or follow the steps above to use VS Code.
114
+
Only people on your CodeSandbox team with permission to access the repository may join as collaborators. Repository permissions are carried over from GitHub. To add someone new to the team, provide access on GitHub and add them to the CodeSandbox. From there, they can access the code in the browser or follow the steps above to use VS Code.
Copy file name to clipboardExpand all lines: packages/projects-docs/pages/learn/editors/desktop-setup.mdx
+4-4Lines changed: 4 additions & 4 deletions
Display the source diff
Display the rich diff
Original file line number
Diff line number
Diff line change
@@ -1,11 +1,11 @@
1
1
---
2
-
title: Setting up VS Code
3
-
description: With this guide, you'll learn how to get the most out of VS Code in CodeSandbox.
2
+
title: Setting up VS Code Desktop
3
+
description: With this guide, you'll learn how to get the most out of VS Code Desktop in CodeSandbox.
4
4
---
5
5
6
6
import { Callout } from'nextra-theme-docs'
7
7
8
-
# Setting up VS Code
8
+
# Setting up VS Code Desktop
9
9
10
10
The CodeSandbox VS Code extension allows you to use VS Code to edit sandboxes and repositories on CodeSandbox.
11
11
@@ -30,7 +30,7 @@ It is possible to work on the SSH connection while disconnected from Pitcher, bu
30
30
Only people on your CodeSandbox team have access to these repositories.
31
31
</Callout>
32
32
33
-
So the VS Code extension connects directly to the container with an SSH connection, bypassing Pitcher, where it operates directly with the FileSystem.
33
+
So, the VS Code extension connects directly to the container with an SSH connection, bypassing Pitcher, where it operates directly with the FileSystem.
34
34
35
35
On top of this, we also connect to Pitcher, just like we do in the browser, where we "tie it together".
Under the main menu you will find the editor settings. This view contains settings the editor and repository as well as management tools for environment variables and options to toggle on and off experiments.
13
+
Under the main menu you will find the editor settings. This view contains settings for the editor and repository, management tools for environment variables, and options to toggle experiments on and off.
14
14
15
15
### Editor settings
16
16
17
17
#### Codeium code completion
18
-
19
-
Codeium code completion is turned on by default in most cases. If at any time you want to disable this feature, you can do so here.
18
+
19
+
Codeium code completion is turned on by default in most cases. If at any time you want to disable this feature, you can do so from this tab.
20
20
21
21
#### VIM
22
-
23
-
For all the VIM users, this setting enables the use of the command palette to control VIM
22
+
23
+
For all the VIM users, this setting enables the use of the command palette to control VIM.
24
24
25
25
#### Pointer cursor
26
-
Enabled by default, this setting determines if the cursor shows as a pointer over interactive elements
26
+
Enabled by default, this setting determines if the cursor is displayed as a pointer over interactive elements.
27
27
28
28
29
29
30
30
### Repository settings
31
-
If developing on a repository, this settings panel provide option to
32
-
* toggle Codeium code completion for the specific repository
33
-
* protect the current branch
34
-
* install the GitHub App - once installed this provides a live dev environment and preview for every PR
35
-
* manage default behavior for previews
31
+
If you are developing on a repository, this settings panel provides options to:
32
+
* Toggle Codeium code completion for the specific repository.
33
+
* Protect the current branch.
34
+
* Install the [GitHub App](/learn/integrations/github-app) - once installed, this provides a live dev environment and preview for every PR.
35
+
* Manage default behavior for previews.
36
36
37
37
38
38
39
39
### Environment variables
40
-
This tab holds the environment variables set to a Devbox or Repository.
41
-
Learn more about secret management [here](/learn/environment/secrets)
40
+
This tab holds the environment variables defined on the current Devbox or Repository.
41
+
See the [Environment variables page](/learn/environment/secrets) for additional details.
42
42
43
43
44
44
45
45
### Experiments
46
-
The product team will often launch experimental features as an opt-in experience. This tabs lists all the current experiments. You can toggle each these to explore what's cooking.
46
+
The CodeSandbox product team often launches experimental features as an opt-in experience. This tabs lists all the current experiments. You can toggle each one to explore what's cooking.
To sync your settings and keybindings between branches, you can enable VS Code Setting Sync. To learn more about how to set this up, you can check [here](https://code.visualstudio.com/docs/editor/settings-sync).
73
+
To sync your settings and keybindings between branches, you can enable VS Code Setting Sync. To learn more about how to set this up, you can check the [VS Code docs](https://code.visualstudio.com/docs/editor/settings-sync).
0 commit comments