Metarepo for the Gobo project

In the instructions that follow, numerous steps involve running Tempo commands. Although the instructions don’t show this, you can run Tempo using npx. You can also install Tempo globally or alias tempo to npx tempo. In

1. Clone this repo.
2. Run git switch <branch> to switch to the branch you want to work in.
3. Run pnpm i in the repo.
4. Run tempo sync to clone all the repos in the metarepo.
5. Run tempo run switch <branch> to ensure all the repos are in the right branch.
6. Run tempo run install. This runs pnpm i within all the repos in the metarepo. Warning: You may need to run this step twice, depending on how many repos are in the metarepo, since it can overwhelm the OS and cause some of the installs to hang.
7. Run tempo run build. This verifies that everything has been installed correctly. Important: This may deploy AWS dependencies as necessary for modules that rely on them.
8. Run tempo run deploy. This will deploy all necessary AWS infrastructure, which includes several APIs, a browser client, an edge router, S3 buckets, and more.

To develop within the metarepo:

1. Run genie watch on any repos that you are actively developing against. Important: Don’t run genie watch more than you need to because watching files is CPU-intensive.
2. Make your changes. You may need to run genie deploy if your changes are server-side. For changes that only affect the client, you just need to refresh the browser.

• .scripts contains convenience scripts. These are different than the “scripts” described in the scripts.yaml file in the .tempo directory.
• .targets contains target files that can be used to target Tempo commands at specific repos. Typically, you would use these to tag a set of repos and use the tag from that point forward.
• .templates contains templates for creating new repositories. These current include templates for Node-only (node), browser-only (browser), and “universal” (universal)—both Node and browser—repositories.
• .tempo contains all the Tempo configuration files. For more information on these, see the Tempo documentation.