-
Notifications
You must be signed in to change notification settings - Fork 196
Commit
This commit does not belong to any branch on this repository, and may belong to a fork outside of the repository.
- Loading branch information
Showing
9 changed files
with
70 additions
and
79 deletions.
There are no files selected for viewing
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Original file line number | Diff line number | Diff line change |
---|---|---|
@@ -1,52 +1,54 @@ | ||
--- | ||
title: Devbox Cloud Open Beta FAQ | ||
title: Devbox Playground FAQ | ||
sidebar_position: 4 | ||
--- | ||
|
||
### What do I need to use Devbox Cloud? | ||
### What do I need to use a Devbox playground? | ||
|
||
To use Devbox Cloud from your Browser, you will need a Github Account. | ||
To start a Devbox playground from your Browser, you will need a Github Account. | ||
|
||
### Does my project need to use Devbox to use Devbox Cloud? | ||
### Does my project need to use Devbox to use Devbox playgorund? | ||
|
||
While you can open any Github Repo in a Devbox Cloud Shell, you will need a `devbox.json` to install packages or configure the environment. You can add any packages in your shell by running `devbox add <pkg>` | ||
While you can open any Github Repo in a Devbox playground, you will need a `devbox.json` to install packages or configure the environment. You can add any packages in your shell by running `devbox add <pkg>` | ||
|
||
### Can I use my own IDE or editor with Devbox Cloud? | ||
### Can I use my own IDE or editor with a Devbox playground? | ||
|
||
Devbox.sh provides a Cloud IDE that you can use to edit your projects in the browser, but you can also open your project in your local VSCode Editor by clicking the `Open in Desktop` button. | ||
|
||
You can also use your own tools when you connect to the VM via SSH. See our [Getting Started Guide](index.mdx) for more details. | ||
|
||
### Do I have to pay to use Devbox Cloud during the Open Beta? | ||
### Do I have to pay to use Devbox.sh? | ||
|
||
Devbox Cloud is free to use during the Open Beta period, subject to the restrictions listed below. We expect to continue offering a free tier for personal use after the Open Beta period, but we will offer Paid Plans that provide more resources, projects, and persistence. | ||
Devbox.sh is free to use during the Beta period, subject to the restrictions described below. | ||
|
||
### What are the resource limits for Devbox Cloud VMs | ||
### What are the resource limits for Devbox playgrounds | ||
|
||
* **CPU**: 4 Cores | ||
* **RAM**: 8 GB | ||
* **SSD**: 8 GB | ||
|
||
If you need additional resources for your project, please reach out to us for **[Early Access](https://jetpack-io.typeform.com/devbox-cloud)** | ||
If you are interested in using Devbox playgrounds or CDE in an enterprise setting, please reach out to us at [[email protected]](mailto://[email protected]) | ||
|
||
### Is there a time limit on Devbox playgrounds? | ||
|
||
Your playground will be suspended after 4 hours of inactivity, and can be restarted by reopening the playground from your [dashboard](https://devbox.sh/app/projects). | ||
|
||
playgrounds are also deleted every 12 hours, regardless of activity | ||
|
||
### I want to request more resources, persistence, or a different OS for my VM | ||
|
||
Future releases will add more flexibility and features as part of our paid plans. If you'd like to sign up for early access to these plans, please sign up for **[Early Access](https://jetpack-io.typeform.com/devbox-cloud)** | ||
Please contact us at [email protected] if you are interested in a custom solution for your enterprise. | ||
|
||
### What OS does Devbox Cloud use? | ||
### What OS does the Devbox.sh use? | ||
|
||
Debian Linux, running on a x86-64 platform | ||
|
||
### How many VM's can I run concurrently? | ||
|
||
You can have up to 5 concurrent projects per Github Account. | ||
|
||
### How long will my Devbox Cloud Shell stay alive for? | ||
|
||
VMs will stay alive for up to 8 hours after going idle. After that point, the VM will be deleted. The next time you visit the same project on the Dashboard, a new VM will be created. Data in the user's home directory will automatically be downloaded to the new machine. | ||
You can have up to 5 concurrent projects per Github Account. To run more playgrounds, you can visit your [Dashboard](https://devbox.sh/app/projects) to delete older playgrounds | ||
|
||
### Where will Devbox run my VM? | ||
### Where does Devbox run my playground? | ||
|
||
Devbox VMs are run as Fly Machines in local Data Centers. To minimize latency, Devbox Cloud will attempt to create a Fly Machine as close to your current location as possible. | ||
Devbox VMs are run as Fly Machines in local Data Centers. To minimize latency, Devbox.sh will attempt to create a Fly Machine as close to your current location as possible. | ||
|
||
|
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters