Skip to content

Commit 9a2c983

Browse files
authored
chore: add VM hibernation instructions and update several screenshots (#265)
* chore: add manual hibernation instructions * chore: update Open Source Collaboration * chore: add screenshot to Collaborate and Share * fix typos
1 parent 783b9dc commit 9a2c983

12 files changed

+41
-30
lines changed

packages/projects-docs/pages/learn/credit-usage/controlling-usage.mdx

Lines changed: 17 additions & 8 deletions
Original file line numberDiff line numberDiff line change
@@ -17,27 +17,36 @@ Making Devboxes private allows workspace admins to have finer control over total
1717

1818
## Templates
1919

20-
VM runtime for templates is covered by CodeSandbox. By setting a Devbox as a template, you can share your work without worrying about the costs associated with non-workspace users running your Devbox.
21-
Once a Devbox is in a template state, it cannot be edited. If you want to continue making changes to the Devbox, you will need to switch it back out of template mode.
20+
VM runtime for templates is covered by CodeSandbox. By setting a Devbox as a template, you can share your work without worrying about the costs associated with non-workspace users running your Devbox.
21+
Once a Devbox is in a template state, it cannot be edited. If you want to continue making changes to the Devbox, you will need to switch it back out of template mode.
2222

2323
## VM settings
2424

25-
Each workspace has a range of VM sizes to choose from. The range of options varies depending on the subscription tier of the workspace.
25+
Each workspace has a range of VM sizes to choose from. The range of options varies depending on the subscription tier of the workspace.
2626
By default, all Devboxes and repositories will run on [Micro](/learn/credit-usage/credits). The default VM size can be changed on the VM [settings page](https://codesandbox.io/t/vm_settings) in the workspace portal.
2727

2828
![VM settings page](../images/vm-settings.png)
2929

30-
Individual Devboxes or repositories can be set to run on VMs other than the default.
30+
Individual Devboxes or repositories can be set to run on VMs other than the default.
3131
To set the VM of a Devbox or repositority, you can create a rule. This helps ensure that heavy compute projects get the power they need without increasing VM usage across the other projects.
3232

3333
![VM Rule](../images/vm-rule.png)
3434

35+
## VM Hibernation
36+
37+
Each individual VM can be manually hibernated at any time from the editor:
38+
39+
1. Click the CodeSandbox icon at the top left.
40+
2. Click "Hibernate VM".
41+
42+
![Hibernate VM](../images/hibernate-vm.jpg)
3543

3644
## Spending limit
37-
On-demand credits will never exceed the spending limit.
45+
46+
On-demand credits will never exceed the spending limit.
3847
Once subscription credits are used, the VMs will start running on on-demand credits. These credits will be aggregated and added to the end-of-month invoice.
3948

40-
Every Pro workspace is required to have a maximum spending limit to ensure that there are no surprise bills at the end of the billing cycle.
41-
The spending limit is initially set during the Pro subscription check-out flow. Workspace admins can adjust this spending limit in the workspace portal at any time.
49+
Every Pro workspace is required to have a maximum spending limit to ensure that there are no surprise bills at the end of the billing cycle.
50+
The spending limit is initially set during the Pro subscription check-out flow. Workspace admins can adjust this spending limit in the workspace portal at any time.
4251

43-
Once the on-demand credits hit that limit, all Devboxes and Repositories will enter a [frozen state](/learn/plans/pricing-faq#my-devbox-or-repository-is-frozen-what-does-that-mean) until more credits have been added or the next billing cycle begins.
52+
Once the on-demand credits hit that limit, all Devboxes and Repositories will enter a [frozen state](/learn/plans/pricing-faq#my-devbox-or-repository-is-frozen-what-does-that-mean) until more credits have been added or the next billing cycle begins.
Binary file not shown.
91.9 KB
Loading
50.6 KB
Loading
-34.1 KB
Binary file not shown.
91.7 KB
Loading
87.2 KB
Loading
42 KB
Loading
63.8 KB
Loading

packages/projects-docs/pages/learn/repositories/collaborate-share.mdx

Lines changed: 2 additions & 0 deletions
Original file line numberDiff line numberDiff line change
@@ -25,6 +25,8 @@ This makes CodeSandbox Repositories the perfect tool to develop full-stack apps
2525
2. In the top right corner, click on **`Share`** .
2626
3. Copy the URL to share your workspace.
2727

28+
![Share a Repository](../images/editor-branch-share.jpg)
29+
2830
### Working in teams
2931

3032
For more information on managing and creating teams, go to the [Team](/learn/teams/permissions) page.

0 commit comments

Comments
 (0)