Reference

Reference Docs

Brev is the fastest way to get into your terminal or code editor. Brev creates your powerful computer in the cloud for development and sets up the environment to run your code. To do this, we have to do two things:


1. Hardware Infrastructure

Hardware could be GPU, CPU, storage, etc. Brev will connect all the clouds to guarantee you an instance at the cheapest price. Clouds, regions, and availability zones shouldn't get in your way. You're not in the AWS or GCP console because your goal is to set up hardware, your goal is through your hardware.

2. Environment Setup

For environment, you might have strong opinions in which case, great. But you probably don't give a shit and just want it to run. We get that. Just commit a .brev/setup.sh file to your repo and it'll run automatically. This is simple because you can just put whatever you would run in the terminal in that file and trust that it'll now run automatically. We have some recommendations here, and see here for a full library of scripts we've used.

By the way, you don't have to commit to the repo, you can store the scripts in a separate repo, private or public. You can apply personal terminal settings in a similar way, with a .brev/setup.sh in it's own repo.

Environment variablers are often shared in a shoddy way, so we loaded Hashicorp Vault into every environment. This is the most robust way to keep your secrets encrypted, and how the most secure conscious teams operate.

Hardware + Environment = Template

Share it with whoever or clone it yourself if you bork yours. Congrats! We're no longer constrained by machine problems!

If you're looking for GPU instance type documentation, please click here.