While this will add node_modules folders to git, they won't be displayed in the UI. You can override this behaviour by adding !node_modules in your own project. The node_modules folder is globally ignored. There is no lost work from cleaning up memory snapshots. Memory snapshots (which allow instant resume of VMs) will be cleaned up after 7 to 31 days of inactivity. This means that you will never lose your work, even if we delete /project after 31 days of inactivity. All your uncommitted work is restored when you open a branch where the /project folder is deleted. This means that the next time you start this branch again, we will reinitialize /project by doing a fresh clone.įor any uncommitted work we make a backup. If your branch has not been accessed for 31 days, we delete the contents of /project. Your home folder is inaccessible for other users. Your project folder lives in /project/, your home folder lives in /project/home/. Every file change outside of /project will usually be persisted, but there is a chance that those changes will be cleared. PersistenceĮverything you save in /project is guaranteed to be persisted between reboots, hibernations and forks. If you require specs that go beyond our Pro plan defaults, get in touch and our team will adjust the limits to suit your project. To upgrade to higher specs, you can ugrade to one of our Pro plans (opens in a new tab). Default resourcesīased on our analysis of usual resource needs, we have defined these resources as default: Typeīut we can go higher, up to 12vCPUs, 16GB memory and 30GB storage. Each branch and cloud sandbox gets its own microVM and their resources (shown below) are set to each one of these instances. CodeSandbox Repositories and Cloud Sandboxes run on microVM technology (opens in a new tab).
0 kommentar(er)
