Skip to content

Commit

Permalink
Merge branch 'main' into dependabot/npm_and_yarn/docs/postcss-8.4.31
Browse files Browse the repository at this point in the history
  • Loading branch information
Pantani authored Oct 19, 2023
2 parents ea7d7c7 + 5104114 commit 8b64211
Show file tree
Hide file tree
Showing 123 changed files with 17,323 additions and 101 deletions.
1 change: 1 addition & 0 deletions .github/workflows/test-lint.yml
Original file line number Diff line number Diff line change
Expand Up @@ -6,6 +6,7 @@ on:
- '**.md'
branches:
- main
- release/*

concurrency:
group: ${{ github.workflow }}-${{ github.head_ref || github.run_id }}
Expand Down
2 changes: 2 additions & 0 deletions changelog.md
Original file line number Diff line number Diff line change
Expand Up @@ -16,6 +16,7 @@
- [#3559](https://github.com/ignite/cli/pull/3559) Bump network plugin version to `v0.1.1`
- [#3581](https://github.com/ignite/cli/pull/3581) Bump cometbft and cometbft-db in the template
- [#3522](https://github.com/ignite/cli/pull/3522) Remove indentation from `chain serve` output
- [#3346](https://github.com/ignite/cli/issues/3346) Improve scaffold query --help
- [#3601](https://github.com/ignite/cli/pull/3601) Update ts-relayer version to `0.10.0`
- [#3658](https://github.com/ignite/cli/pull/3658) Rename Marshaler to Codec in EncodingConfig
- [#3653](https://github.com/ignite/cli/pull/3653) Add "app" extension to plugin binaries
Expand All @@ -26,6 +27,7 @@

### Fixes

- [#3386](https://github.com/ignite/cli/issues/3386) Prevent scaffolding of default module called "ibc"
- [#3592](https://github.com/ignite/cli/pull/3592) Fix `pkg/protoanalysis` to support HTTP rule parameter arguments
- [#3598](https://github.com/ignite/cli/pull/3598) Fix consensus param keeper constructor key in `app.go`
- [#3610](https://github.com/ignite/cli/pull/3610) Fix overflow issue of cosmos faucet in `pkg/cosmosfaucet/transfer.go` and `pkg/cosmosfaucet/cosmosfaucet.go`
Expand Down
78 changes: 60 additions & 18 deletions docs/docs/08-references/01-cli.md
Original file line number Diff line number Diff line change
Expand Up @@ -3307,19 +3307,7 @@ array.coin. An example of using field types:

ignite scaffold list pool amount:coin tags:array.string height:int

Supported types:

| Type | Alias | Index | Code Type | Description |
|--------------|---------|-------|-----------|---------------------------------|
| string | - | yes | string | Text type |
| array.string | strings | no | []string | List of text type |
| bool | - | yes | bool | Boolean type |
| int | - | yes | int32 | Integer type |
| array.int | ints | no | []int32 | List of integers types |
| uint | - | yes | uint64 | Unsigned integer type |
| array.uint | uints | no | []uint64 | List of unsigned integers types |
| coin | - | no | sdk.Coin | Cosmos SDK coin type |
| array.coin | coins | no | sdk.Coins | List of Cosmos SDK coin types |
For detailed type information use ignite scaffold type --help

"Index" indicates whether the type can be used as an index in
"ignite scaffold map".
Expand Down Expand Up @@ -3398,7 +3386,7 @@ incrementing integer, whereas "map" values are indexed by a user-provided value

Let's use the same blog post example:

ignite scaffold map post title body
ignite scaffold map post title body:string

This command scaffolds a "Post" type and CRUD functionality to create, read,
updated, and delete posts. However, when creating a new post with your chain's
Expand Down Expand Up @@ -3427,6 +3415,8 @@ Since the behavior of "list" and "map" scaffolding is very similar, you can use
the "--no-message", "--module", "--signer" flags as well as the colon syntax for
custom types.

For detailed type information use ignite scaffold type --help


```
ignite scaffold map NAME [field]... [flags]
Expand Down Expand Up @@ -3480,6 +3470,8 @@ The command above will create a new message MsgAddPool with three fields: amount
(in tokens), denom (a string), and active (a boolean). The message will be added
to the "dex" module.

For detailed type information use ignite scaffold type --help

By default, the message is defined as a proto message in the
"proto/{app}/{module}/tx.proto" and registered in the "Msg" service. A CLI command to
create and broadcast a transaction with MsgAddPool is created in the module's
Expand All @@ -3503,7 +3495,7 @@ for details.


```
ignite scaffold message [name] [field1] [field2] ... [flags]
ignite scaffold message [name] [field1:type1] [field2:type2] ... [flags]
```

**Options**
Expand Down Expand Up @@ -3648,8 +3640,14 @@ ignite scaffold packet [packetName] [field1] [field2] ... --module [moduleName]

Query for fetching data from a blockchain

**Synopsis**

Query for fetching data from a blockchain.

For detailed type information use ignite scaffold type --help.

```
ignite scaffold query [name] [request_field1] [request_field2] ... [flags]
ignite scaffold query [name] [field1:type1] [field2:type2] ... [flags]
```

**Options**
Expand Down Expand Up @@ -3695,8 +3693,20 @@ ignite scaffold react [flags]

CRUD for data stored in a single location

**Synopsis**

CRUD for data stored in a single location.

For detailed type information use ignite scaffold type --help.

```
ignite scaffold single NAME [field:type]... [flags]
```

**Examples**

```
ignite scaffold single NAME [field]... [flags]
ignite scaffold single todo-single title:string done:bool
```

**Options**
Expand All @@ -3721,8 +3731,40 @@ ignite scaffold single NAME [field]... [flags]

Type definition

**Synopsis**

Type information

Currently supports:

| Type | Alias | Index | Code Type | Description |
|--------------|---------|-------|-----------|---------------------------------|
| string | - | yes | string | Text type |
| array.string | strings | no | []string | List of text type |
| bool | - | yes | bool | Boolean type |
| int | - | yes | int32 | Integer type |
| array.int | ints | no | []int32 | List of integers types |
| uint | - | yes | uint64 | Unsigned integer type |
| array.uint | uints | no | []uint64 | List of unsigned integers types |
| coin | - | no | sdk.Coin | Cosmos SDK coin type |
| array.coin | coins | no | sdk.Coins | List of Cosmos SDK coin types |

Field Usage:
- fieldName
- fieldName:fieldType

If no :fieldType, default (string) is used



```
ignite scaffold type NAME [field:type] ... [flags]
```

**Examples**

```
ignite scaffold type NAME [field]... [flags]
ignite scaffold type todo-item priority:int desc:string tags:array.string done:bool
```

**Options**
Expand Down
63 changes: 63 additions & 0 deletions docs/versioned_docs/version-v0.27.2/01-welcome/01-index.md
Original file line number Diff line number Diff line change
@@ -0,0 +1,63 @@
---
slug: /
---

import ProjectsTable from '@site/src/components/ProjectsTable';

# Introduction to Ignite

[Ignite CLI](https://github.com/ignite/cli) offers everything you need to build, test, and launch your blockchain with a
decentralized worldwide community. Ignite CLI is built on top of [Cosmos SDK](https://docs.cosmos.network), the world’s
most popular blockchain framework. Ignite CLI accelerates chain development by scaffolding everything you need so you
can focus on business logic.

## What is Ignite CLI?

Ignite CLI is an easy-to-use CLI tool for creating and maintaining sovereign application-specific blockchains.
Blockchains created with Ignite CLI use Cosmos SDK and Tendermint. Ignite CLI and the Cosmos SDK modules are written in
the Go programming language. The scaffolded blockchain that is created with Ignite CLI includes a command line interface
that lets you manage keys, create validators, and send tokens.

With just a few commands, you can use Ignite CLI to:

- Create a modular blockchain written in Go
- Scaffold modules, messages, types with CRUD operations, IBC packets, and more
- Start a blockchain node in development with live reloading
- Connect to other blockchains with a built-in IBC relayer
- Use generated TypeScript/Vuex clients to interact with your blockchain
- Use the Vue.js web app template with a set of components and Vuex modules

## Install Ignite CLI

To install the `ignite` binary in `/usr/local/bin` run the following command:

```
curl https://get.ignite.com/cli | bash
```

## Projects using Tendermint and Cosmos SDK

Many projects already showcase the Tendermint BFT consensus engine and the Cosmos SDK. Explore
the [Cosmos ecosystem](https://cosmos.network/ecosystem/apps) to discover a wide variety of apps, blockchains, wallets,
and explorers that are built in the Cosmos ecosystem.

## Projects building with Ignite CLI

<ProjectsTable data={[
{ name: "Stride Labs", logo: "img/logo/stride.svg"},
{ name: "KYVE Network", logo: "img/logo/kyve.svg"},
{ name: "Umee", logo: "img/logo/umee.svg"},
{ name: "MediBloc Core", logo: "img/logo/medibloc.svg"},
{ name: "Cudos", logo: "img/logo/cudos.svg"},
{ name: "Firma Chain", logo: "img/logo/firmachain.svg"},
{ name: "BitCanna", logo: "img/logo/bitcanna.svg"},
{ name: "Source Protocol", logo: "img/logo/source.svg"},
{ name: "Sonr", logo: "img/logo/sonr.svg"},
{ name: "Neutron", logo: "img/logo/neutron.svg"},
{ name: "OKP4 Blockchain", logo: "img/logo/okp4.svg"},
{ name: "Dymension Hub", logo: "img/logo/dymension.svg"},
{ name: "Electra Blockchain", logo: "img/logo/electra.svg"},
{ name: "OLLO Station", logo: "img/logo/ollostation.svg"},
{ name: "Mun", logo: "img/logo/mun.svg"},
{ name: "Aura Network", logo: "img/logo/aura.svg"},
]}/>
114 changes: 114 additions & 0 deletions docs/versioned_docs/version-v0.27.2/01-welcome/02-install.md
Original file line number Diff line number Diff line change
@@ -0,0 +1,114 @@
---
sidebar_position: 1
description: Steps to install Ignite CLI on your local computer.
---

# Install Ignite CLI

You can run [Ignite CLI](https://github.com/ignite/cli) in a web-based Gitpod IDE or you can install Ignite CLI on your
local computer.

## Prerequisites

Be sure you have met the prerequisites before you install and use Ignite CLI.

### Operating systems

Ignite CLI is supported for the following operating systems:

- GNU/Linux
- macOS
- Windows Subsystem for Linux (WSL)

### Go

Ignite CLI is written in the Go programming language. To use Ignite CLI on a local system:

- Install [Go](https://golang.org/doc/install) (**version 1.19** or higher)
- Ensure the Go environment variables are [set properly](https://golang.org/doc/gopath_code#GOPATH) on your system

## Verify your Ignite CLI version

To verify the version of Ignite CLI you have installed, run the following command:

```bash
ignite version
```

## Installing Ignite CLI

To install the latest version of the `ignite` binary use the following command.

```bash
curl https://get.ignite.com/cli! | bash
```

This command invokes `curl` to download the installation script and pipes the output to `bash` to perform the
installation. The `ignite` binary is installed in `/usr/local/bin`.

To learn more or customize the installation process, see the [installer docs](https://github.com/ignite/installer) on
GitHub.

### Write permission

Ignite CLI installation requires write permission to the `/usr/local/bin/` directory. If the installation fails because
you do not have write permission to `/usr/local/bin/`, run the following command:

```bash
curl https://get.ignite.com/cli | bash
```

Then run this command to move the `ignite` executable to `/usr/local/bin/`:

```bash
sudo mv ignite /usr/local/bin/
```

On some machines, a permissions error occurs:

```bash
mv: rename ./ignite to /usr/local/bin/ignite: Permission denied
============
Error: mv failed
```

In this case, use sudo before `curl` and before `bash`:

```bash
sudo curl https://get.ignite.com/cli | sudo bash
```

## Upgrading your Ignite CLI installation

Before you install a new version of Ignite CLI, remove all existing Ignite CLI installations.

To remove the current Ignite CLI installation:

1. On your terminal window, press `Ctrl+C` to stop the chain that you started with `ignite chain serve`.
2. Remove the Ignite CLI binary with `rm $(which ignite)`.
Depending on your user permissions, run the command with or without `sudo`.
3. Repeat this step until all `ignite` installations are removed from your system.

After all existing Ignite CLI installations are removed, follow the [Installing Ignite CLI](#installing-ignite-cli)
instructions.

For details on version features and changes, see
the [changelog.md](https://github.com/ignite/cli/blob/main/changelog.md)
in the repo.

## Build from source

To experiment with the source code, you can build from source:

```bash
git clone https://github.com/ignite/cli --depth=1
cd cli && make install
```

## Summary

- Verify the prerequisites.
- To set up a local development environment, install Ignite CLI locally on your computer.
- Install Ignite CLI by fetching the binary using cURL or by building from source.
- The latest version is installed by default. You can install previous versions of the precompiled `ignite` binary.
- Stop the chain and remove existing versions before installing a new version.
Original file line number Diff line number Diff line change
@@ -0,0 +1,4 @@
{
"label": "Welcome",
"link": null
}
36 changes: 36 additions & 0 deletions docs/versioned_docs/version-v0.27.2/02-guide/00-introduction.md
Original file line number Diff line number Diff line change
@@ -0,0 +1,36 @@
---
sidebar_position: 0
title: Introduction
slug: /guide
---

# Introduction

Developer tutorials provide step-by-step instructions to help you build blockchain developer skills.

By following these developer tutorials you will learn how to:

* Install Ignite CLI on your local machine
* Create a new blockchain and start a node locally for development
* Make your blockchain say "Hello, World!"
* Scaffold a Cosmos SDK query
* Modify a keeper method to return a static string
* Use the blockchain CLI to make a query
* Write and read blog posts to your chain in the Blog tutorial
* Scaffold a Cosmos SDK message
* Define new types in protocol buffer files
* Write keeper methods to write data to the store
* Read data from the store and return it as a result a query
* Use the blockchain CLI to broadcast transactions
* Build a blockchain for buying and selling names in the Nameservice tutorial
* Scaffold CRUD logic with `map`
* Use other module methods in your custom module
* Send tokens between addresses
* Build a guessing game with rewards
* Use an escrow account to store tokens
* Use the Inter-Blockchain Communication (IBC) protocol
* Scaffold an IBC-enabled module
* Send and receive IBC packets
* Configure and run a built-in IBC relayer
* Build a decentralized order-book token exchange
* Build an advanced IBC-enabled module
Loading

0 comments on commit 8b64211

Please sign in to comment.