ZS50 sandboxes sit atop and expand the capabilities of the web-based sandboxes provided by CS50. Sandboxes are ephemeral environments created from Docker images. If you're interested in learning more about how CS50 provides these environments you can find out more at https://cs50.readthedocs.io/sandbox/.
To get started with a ZS50 sandbox you just need to:
- Sign up for a Github account
- Click here to spin up a ZS50 sandbox.
Upon clicking the link, you will be asked to log into your Github account for authorization (if you're not logged in already). From there, you'll be directed to your ready-made ZS-ified dev environment.
- You should only use the link above to create your sandbox one time. After that, you can access the same sandbox from the
Recent sandboxestab of https://sandbox.cs50.io. Each time you use the link above you spin up a new ZS50 sandbox, meaning any files or configuration from your prior sandbox is not persisted. - Sandbox environments are ephemeral and may expire at any point (hey, that's the tradeoff of a free service, no?). This means that, to make sure you don't lose any Apex classes you've worked on and would like to save, you should download them to your local machine on a regular basis.
- Upon spinning up your sandbox the
zs50command line utility should be automatically linked. To check, type the commandzs50 authinto the command line. You should see the following:
No authorized dev org linked for ZS50. Authorize now? (Y/N)
If instead you see...
bash: zs50: command not found
...have no fear. Just type the following command into your terminal and hit return:
npm link ./node_modules/zs50
Try that zs50 auth command again, and this time it should work. If not, call in the helpdesk:
If your zs50 command is linked then you're good to go. Jump to the zs50 cli github repo for the full documentation on this tool.