> For the complete documentation index, see [llms.txt](https://docs.cartesi.io/llms.txt)

---
id: quickstart
title: Quickstart
resources:
  - url: https://github.com/jplgarcia/cartesi-angular-frontend
    title: Angular template
---

Welcome to Quickstart. The goal of this guide is to build a decentralized application quickly with the Cartesi CLI.

## Set up your environment

The primary requirements for building on Cartesi are Docker Desktop and the Cartesi CLI.

:::note windows os configuration
If you use Windows, you must have [WSL2 installed and configured](https://learn.microsoft.com/en-us/windows/wsl/install) for building. In Docker Desktop settings, confirm that the WSL2-based engine configurations are enabled.
:::

### Install Docker Desktop and Cartesi CLI

1. [Install Docker Desktop for your operating system](https://www.docker.com/products/docker-desktop/).

    To install Docker RISC-V support without using Docker Desktop, run the following command:
    
   ```shell
    docker run --privileged --rm tonistiigi/binfmt --install all
   ```

1. [Download and install the latest version of Node.js](https://nodejs.org/en/download).

2. Cartesi CLI is an easy-to-use tool to build and deploy your dApps. To install it, run:

   ```shell
    npm i -g @cartesi/cli
   ```


## Create an application

To create the backend application from scratch, run:

```bash
cartesi create <dapp-name> --template <language>
```

This creates a new directory with template code in the language you specify.

```bash
$ cartesi create js-dapp --template javascript
✔ Application created at /js-dapp
```

Your application entry point will be the `src/index.js` file.

## Build the application

To build your application, ensure you have Docker Desktop running.

After that, you can run the command provided below:

```bash
cartesi build
```

The `cartesi build` command builds a Cartesi machine and compiles your application so that it is ready to receive requests and inputs.

## Run the environment

To run the environment, you can use the following command:

```bash
cartesi run
```
This will run your backend with the docker containers for the Cartesi Rollups environment including Rollups validator node and the Anvil devnet.

## Send inputs to the application

You have some options for sending input to your application. One option is the `cartesi send` command.

Another option is [Cast](https://book.getfoundry.sh/cast/), a command-line tool for making Ethereum RPC calls.

Additionally, you can build a custom web interface to input data into your application.

### Using Cartesi CLI

Here is how you can send input to your dApp:

```shell
cartesi send
```

This guides you through sending inputs with the CLI interactively.

```shell
? Select the send sub-command (Use arrow keys)
❯ Send DApp address input to the application.
  Send ERC-20 deposit to the application.
  Send ERC-721 deposit to the application.
  Send ether deposit to the application.
  Send generic input to the application.
```

### Using Cast

Here is how you can send input to your dApp with Cast:

```shell
cast send <InputBoxAddress> "addInput(address,bytes)" <DAppAddress> <EncodedPayload> --mnemonic <MNEMONIC>
```

This command sends an input payload to your application through the `InputBox` contract.

Replace placeholders like `<InputBoxAddress>`, `<DAppAddress>`, `<EncodedPayload>`, and `<MNEMONIC>` with the actual addresses, payload, and mnemonic for your specific use case.


You can obtain the relevant addresses by running `cartesi address-book`.

### Using a custom web interface

You can create a custom frontend that interacts with your application.

Follow [the React.js tutorial to build a frontend for your application](/cartesi-rollups/1.5/tutorials/react-frontend-application/).

## Deploy the application

There are two methods to deploy an application:

1. [Self-hosted deployment](/cartesi-rollups/1.5/deployment/self-hosted/): Deploy the application node using your infrastructure.

2. Third-party service provider: Outsource running the application node to a service provider.

:::caution important
Deployment with a third-party service provider is under development and will be available in a future release.
:::