# Clone the Repository

> Create a project with the MakerKit CLI, or clone with Git, then connect your own private repository.

*Canonical: https://makerkit.dev/docs/void-cloudflare/installation/clone-repository*

---

Choose the MakerKit CLI or one of the Git methods below. The examples use `my-saas-app` as the local folder name; replace it with your project name.

## Create with the MakerKit CLI

From the folder where you keep your projects, run:

```bash
npx @makerkit/cli@latest new
```

Choose **Void + Cloudflare**, enter a project name such as `my-saas-app`, and confirm. The CLI clones the kit, installs dependencies with pnpm, and records which MakerKit variant the project uses. You need pnpm available for this path; see [Prerequisites](./prerequisites).

If you already use pnpm, you can launch the CLI with `pnpm dlx @makerkit/cli@latest new` instead. If your CLI does not list Void + Cloudflare yet, use one of the Git commands below.

Once it finishes, enter the project folder:

```bash
cd my-saas-app
```

Continue with [Setup and Installation](./setup) to prepare local settings, migrations, the database, and the app. The CLI installs dependencies; it does not perform the kit's local setup journey.

## Clone with SSH

If your GitHub account has an SSH key configured:

```bash
git clone git@github.com:makerkit/void-cloudflare-saas-kit.git my-saas-app
cd my-saas-app
```

## Clone with HTTPS

Alternatively, use HTTPS with your GitHub credentials configured locally:

```bash
git clone https://github.com/makerkit/void-cloudflare-saas-kit.git my-saas-app
cd my-saas-app
```

Run subsequent commands from this folder. It contains `package.json`, `pnpm-workspace.yaml`, `apps/`, and `packages/`.

## Connect Your Own Repository

Before pushing your work, create an empty **private** repository in your GitHub account or organization. Keep the MakerKit remote as `upstream` for future kit updates and use your repository as `origin`.

Replace `YOUR_ACCOUNT` and `YOUR_REPOSITORY` with your repository details:

```bash
git remote rename origin upstream
git remote add origin git@github.com:YOUR_ACCOUNT/YOUR_REPOSITORY.git
git remote -v
```

If you use HTTPS, use `https://github.com/YOUR_ACCOUNT/YOUR_REPOSITORY.git` for the new origin instead. When you are ready to push your project:

```bash
git push -u origin HEAD
```

## Clone Problems

| Error | What to check |
| --- | --- |
| Repository not found | Your GitHub account can open the kit repository and your local Git credentials use that account |
| Permission denied (publickey) | Your SSH key is configured for GitHub, or use HTTPS |
| Destination path already exists | Choose a new folder name or use your existing clone |
| Setup cannot find project files | Run it from the cloned repository root |

---

**Next:** [Setup and Installation →](./setup)
