### Setting Up ChainLaunch Development Environment - Bash

Source: https://github.com/lf-decentralized-trust-labs/chaindeploy/blob/main/CONTRIBUTING.md

This command executes the 'dev' target defined in the project's Makefile. It typically automates the setup of the development environment, which might include building binaries, initializing databases, or configuring services using Docker Compose, as indicated by the prerequisites.

```bash
make dev
```

--------------------------------

### Installing Go Dependencies for ChainLaunch - Bash

Source: https://github.com/lf-decentralized-trust-labs/chaindeploy/blob/main/CONTRIBUTING.md

This command downloads all necessary Go module dependencies for the ChainLaunch project. It ensures that all required packages and their versions, as specified in the go.mod file, are available in your local Go module cache, preparing the project for compilation and execution.

```bash
go mod download
```

--------------------------------

### Starting Development Server (Bash)

Source: https://github.com/lf-decentralized-trust-labs/chaindeploy/blob/main/web/README.md

This command initiates the local development server, typically with hot-reloading capabilities, allowing developers to preview changes in real-time during development.

```bash
pnpm dev
```

--------------------------------

### Installing Project Dependencies (Bash)

Source: https://github.com/lf-decentralized-trust-labs/chaindeploy/blob/main/web/README.md

This command uses pnpm to install all required project dependencies. It is a crucial first step before running any development or build tasks.

```bash
pnpm install
```

--------------------------------

### Running ChainLaunch Application - Bash

Source: https://github.com/lf-decentralized-trust-labs/chaindeploy/blob/main/CONTRIBUTING.md

This command executes the 'run' target defined in the project's Makefile. It is used to start the ChainLaunch application, likely leveraging Docker Compose to bring up all necessary services and components for local operation.

```bash
make run
```

--------------------------------

### Generating OpenAPI Documentation with Swag

Source: https://github.com/lf-decentralized-trust-labs/chaindeploy/blob/main/README.md

This command regenerates the Swagger/OpenAPI documentation for the ChainLaunch project. It uses the 'swag' tool to parse Go source files, specifically 'cmd/serve/serve.go', and outputs the documentation to the 'docs' directory. The flags ensure internal and dependency parsing.

```bash
swag init -g cmd/serve/serve.go -o docs --parseInternal --parseDependency --parseDepth 1 --generatedTime
```

--------------------------------

### Cloning ChainLaunch Repository - Bash

Source: https://github.com/lf-decentralized-trust-labs/chaindeploy/blob/main/CONTRIBUTING.md

This command sequence clones your forked ChainLaunch repository from GitHub to your local machine and then changes the current directory into the newly cloned repository. This is the initial step for setting up your local development environment after forking.

```bash
git clone https://github.com/YOUR_USERNAME/chainlaunch.git
cd chainlaunch
```

--------------------------------

### Generating Database Queries with sqlc

Source: https://github.com/lf-decentralized-trust-labs/chaindeploy/blob/main/README.md

This command regenerates SQL queries using the 'sqlc' tool. 'sqlc' is used to generate type-safe Go code from SQL queries, ensuring consistency between the database schema and the application's data access layer.

```bash
sqlc generate
```

--------------------------------

### Previewing Production Build Locally (Bash)

Source: https://github.com/lf-decentralized-trust-labs/chaindeploy/blob/main/web/README.md

This command serves the previously built production assets locally, enabling a final verification of the optimized application before actual deployment.

```bash
pnpm preview
```

--------------------------------

### Building Application for Production (Bash)

Source: https://github.com/lf-decentralized-trust-labs/chaindeploy/blob/main/web/README.md

This command compiles and optimizes the application's source code for production deployment, generating a set of static assets ready for serving.

```bash
pnpm build
```

--------------------------------

### Opening Playwright Test UI (Shell)

Source: https://github.com/lf-decentralized-trust-labs/chaindeploy/blob/main/web/README.md

This command launches the Playwright Test UI, providing an interactive graphical interface to run, debug, and inspect individual end-to-end tests.

```sh
bun run test:e2e:dev
```

--------------------------------

### Running Playwright E2E Tests (Shell)

Source: https://github.com/lf-decentralized-trust-labs/chaindeploy/blob/main/web/README.md

This command executes the end-to-end tests defined for the project using Playwright, orchestrated via Bun. It's essential for validating the application's complete user flows.

```sh
bun run test:e2e
```

--------------------------------

### Adding Upstream Remote to ChainLaunch - Bash

Source: https://github.com/lf-decentralized-trust-labs/chaindeploy/blob/main/CONTRIBUTING.md

This command adds the original ChainLaunch repository as an 'upstream' remote to your local git configuration. This allows you to easily fetch and merge changes from the main project into your fork, keeping your local repository up-to-date.

```bash
git remote add upstream https://github.com/original/chainlaunch.git
```

--------------------------------

### Creating New Feature Branch - Bash

Source: https://github.com/lf-decentralized-trust-labs/chaindeploy/blob/main/CONTRIBUTING.md

This command creates a new Git branch named 'feature/your-feature-name' and immediately switches to it. This is a standard practice for isolating new development work, ensuring that changes are made on a dedicated branch rather than directly on the main development line.

```bash
git checkout -b feature/your-feature-name
```

=== COMPLETE CONTENT === This response contains all available snippets from this library. No additional content exists. Do not make further requests.