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
+4-27Lines changed: 4 additions & 27 deletions
Original file line number
Diff line number
Diff line change
@@ -75,17 +75,6 @@ recommend using a [Devbox](/learn/devboxes/overview).
75
75
76
76
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.
77
77
78
-
For container sandboxes that are created after May 10 2021, we run Node v14.18.1 (LTS) by default.
79
-
For backwards compatibility, the older sandboxes are on Node v10. However, you can
80
-
specify a `node` value to alter the version in `sandbox.config.json` which will
81
-
be used instead. For further details, see [configuration](/learn/legacy-sandboxes/configuration).
82
-
83
-
<Callout>
84
-
This method only applies to legacy sandboxes.
85
-
</Callout>
86
-
87
-
Note that we recommend using Devboxes when you're working with Node.js projects.
88
-
89
78
## How do I change the editor's theme?
90
79
91
80
To change the [theme of a Devbox](https://codesandbox.io/docs/learn/editors/web/themes), click on the CodeSandbox logo at the top left, then go to Settings > User Preferences, and select a theme from the Themes dropdown. You can also do it from the [command palette](https://codesandbox.io/docs/learn/repositories/commandpalette).
@@ -106,18 +95,6 @@ We currently provide [Sandboxes](/learn/sandboxes/editor-features) and [Devboxes
106
95
`node_modules` and dependencies do not count toward this limit.
107
96
- The maximum file size that can be opened in the editor is 2MB. Files uploaded
108
97
that are larger than that still exist but are linked as a static asset.
109
-
- Terminal commands that alter the filesystem of the container instance aren't
110
-
synced with files shown in the editor. You'll need to refresh to see files
111
-
updated this way.
112
-
- When using a container, there is a sync limit of 10 files per second and only
113
-
files up to 2MB are synced with the editor. Files larger than that still exist
114
-
but are not shown in the editor's file tree. You're still able to write and
115
-
read to and from them in your code and they can be seen and edited via the
116
-
terminal.
117
-
- When using a container, the sandbox sleeps after around 10 minutes and can be woken by opening
118
-
the sandbox or preview in a web browser.
119
-
- When using a container, the sandbox has a 1GB persistent storage limit, a 1GB vCPU soft
120
-
limit, and a hard memory limit of 2 GB.
121
98
122
99
Devboxes are part of our evolved CodeSandbox experience, so we highly advise you to use them to avoid encountering these limitations.
123
100
@@ -138,19 +115,19 @@ No, you don't need to install Docker on your local machine. CodeSandbox has [bui
138
115
139
116
### How do I access the database once it's running in a Docker container?
140
117
141
-
You can access the database using the appropriate driver for your language or framework. Typically, you'll need to provide the hostname, port number, username, and password to connect to the database.
118
+
You can access the database using the appropriate driver for your language or framework. Typically, you'll need to provide the hostname, port number, username, and password to connect to the database. If you want to connect locally to the database, you can use our VSCode integration to open the Devbox inside VSCode, and then forward the port of the database to localhost.
142
119
143
120
### Can I use multiple databases in the same CodeSandbox project?
144
121
145
-
Yes, you can use multiple databases in the same project by running multiple Docker containers with different port numbers. However, keep in mind that running multiple databases can put a strain on your system resources and affect performance.
122
+
Yes, you can use multiple databases in the same project by running multiple Docker containers with different port numbers.
146
123
147
124
### Can I use Docker Compose in CodeSandbox?
148
125
149
-
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.
126
+
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).
150
127
151
128
### Is it safe to use a database in CodeSandbox with Docker support?
152
129
153
-
Yes, it's safe to use a database in CodeSandbox with Docker support, as long as you follow best practices for security and keep your database credentials private. Docker provides a secure and isolated environment for running containers, so your database is protected from external threats.
130
+
Yes, it's safe to use a database in CodeSandbox with Docker support, as long as you follow best practices for security and keep your database credentials private. Docker provides a secure and isolated environment for running containers, so your database is protected from external threats. We also prevent any connections to your Devbox without sign in if your Devbox is private.
154
131
155
132
### How do I troubleshoot issues with my database in CodeSandbox with Docker support?
0 commit comments