# Repo Structure

First step is then to clone our `infra-external` github repo locally and `cd` into it:

```bash
git clone https://github.com/switchboard-xyz/infra-external
cd infra-external
```

This repository structure is divided into three main areas:

```bash
infra-external/
│
├── README.md
│
├── cfg/
│   │
│   ├── 00-common-vars.cfg
│   ├── 00-devnet-vars.cfg
│   └── 00-mainnet-vars.cfg
│
├── data/
│   │
│   ├── devnet_payer.json
│   └── mainnet_payer.json
│
└── oracle/
    │
    └── bare-metal/
        └── kubernetes/
            └── ... scripts ...

```

These areas serve as follows:

* `cfg/`: Contains configuration files for two environments, `devnet` and `mainnet` plus a shared one called `common` that contains shared variables that apply to both.\
  You may want to backup this directory at least once or every time you change its content.
* `data/`: Holds essential data files like `devnet_payer.json` and `mainnet_payer.json` needed for setting up the Oracles. May be populated by other directories after setup.\
  You may want to backup this directory at least once or every time you change its content.
* `oracle/`: Includes scripts for setting up Oracles.\
  This directory can be ignored during backups and will change as we update our process.
* `README.md`: it's the README file for the repo, in Markdown format.

Continue to the next section where we'll take care of the configuring files.


---

# Agent Instructions: Querying This Documentation

If you need additional information that is not directly available in this page, you can query the documentation dynamically by asking a question.

Perform an HTTP GET request on the current page URL with the `ask` query parameter:

```
GET https://docs.switchboard.xyz/how-it-works/switchboard-protocol/running-a-switchboard-oracle/the-git-repo-clone-our-code/repo-structure.md?ask=<question>
```

The question should be specific, self-contained, and written in natural language.
The response will contain a direct answer to the question and relevant excerpts and sources from the documentation.

Use this mechanism when the answer is not explicitly present in the current page, you need clarification or additional context, or you want to retrieve related documentation sections.