@settlemint/sdk-cli 0.8.6-predc2ddfc → 0.8.6-prefafe2e2
This diff represents the content of publicly available package versions that have been released to one of the supported registries. The information contained in this diff is provided for informational purposes only and reflects changes between package versions as they appear in their respective public registries.
- package/README.md +120 -10
- package/dist/cli.js +224 -252
- package/dist/cli.js.map +46 -45
- package/package.json +3 -3
package/README.md
CHANGED
|
@@ -40,7 +40,125 @@ The SettleMint CLI provides a command-line interface for interacting with the Se
|
|
|
40
40
|
|
|
41
41
|
## Usage
|
|
42
42
|
|
|
43
|
-
|
|
43
|
+
### Login to the platform
|
|
44
|
+
|
|
45
|
+
To use the SettleMint CLI, you first need to authenticate with the platform. Create a Personal Access Token (PAT) on the SettleMint platformand paste it when prompted by the login command.
|
|
46
|
+
|
|
47
|
+
Visit [the documentation](https://console.settlemint.com/documentation/docs/using-platform/personal-access-tokens/) to learn how to create a Personal Access Token.
|
|
48
|
+
|
|
49
|
+
Then run the login command and paste your token when prompted:
|
|
50
|
+
|
|
51
|
+
```bash
|
|
52
|
+
settlemint login
|
|
53
|
+
```
|
|
54
|
+
|
|
55
|
+
### Creating a new project from a starter kit template
|
|
56
|
+
|
|
57
|
+
To create a new project from a starter kit template, use the `create` command with the `--template` flag:
|
|
58
|
+
|
|
59
|
+
```bash
|
|
60
|
+
settlemint create --project-name <project-name> --template <template-name>
|
|
61
|
+
```
|
|
62
|
+
|
|
63
|
+
#### Installing dependencies
|
|
64
|
+
|
|
65
|
+
To install the dependencies for your project, use the `dependencies` command.
|
|
66
|
+
|
|
67
|
+
##### Using bun
|
|
68
|
+
|
|
69
|
+
```bash
|
|
70
|
+
bun install
|
|
71
|
+
bun run dependencies
|
|
72
|
+
```
|
|
73
|
+
|
|
74
|
+
##### Using npm
|
|
75
|
+
|
|
76
|
+
```bash
|
|
77
|
+
npm install
|
|
78
|
+
npm run dependencies
|
|
79
|
+
```
|
|
80
|
+
|
|
81
|
+
##### Using yarn
|
|
82
|
+
|
|
83
|
+
```bash
|
|
84
|
+
yarn install
|
|
85
|
+
yarn run dependencies
|
|
86
|
+
```
|
|
87
|
+
|
|
88
|
+
##### Using pnpm
|
|
89
|
+
|
|
90
|
+
```bash
|
|
91
|
+
pnpm install
|
|
92
|
+
pnpm run dependencies
|
|
93
|
+
```
|
|
94
|
+
|
|
95
|
+
#### Connecting to your SettleMint infrastructure
|
|
96
|
+
|
|
97
|
+
After creating your project, you'll need to connect it to your SettleMint infrastructure. This requires setting up environment variables with your SettleMint credentials and infrastructure details.
|
|
98
|
+
|
|
99
|
+
You can use the `connect` command to automatically configure your project and select the services you want to connect to.
|
|
100
|
+
|
|
101
|
+
```bash
|
|
102
|
+
settlemint connect
|
|
103
|
+
```
|
|
104
|
+
|
|
105
|
+
#### Deploying your smart contracts and subgraphs
|
|
106
|
+
|
|
107
|
+
To deploy your smart contracts and subgraphs, you can use the `deploy` command.
|
|
108
|
+
|
|
109
|
+
```bash
|
|
110
|
+
settlemint scs hardhat deploy remote --accept-defaults
|
|
111
|
+
```
|
|
112
|
+
|
|
113
|
+
To deploy your subgraphs, use the `subgraph` command.
|
|
114
|
+
|
|
115
|
+
```bash
|
|
116
|
+
settlemint scs subgraph deploy --accept-defaults <subgraph-name>
|
|
117
|
+
```
|
|
118
|
+
|
|
119
|
+
#### Generating code for your dApp
|
|
120
|
+
|
|
121
|
+
After deploying your smart contracts and subgraphs, you can generate TypeScript code for your dApp to interact with them. The `codegen` command will generate type-safe code for your integrations with the services selected in the `connect` command.
|
|
122
|
+
|
|
123
|
+
```bash
|
|
124
|
+
settlemint codegen
|
|
125
|
+
```
|
|
126
|
+
|
|
127
|
+
#### Start your dApp in development mode
|
|
128
|
+
|
|
129
|
+
```bash
|
|
130
|
+
bun run dev
|
|
131
|
+
```
|
|
132
|
+
|
|
133
|
+
### Creating a new project from a smart contract template
|
|
134
|
+
|
|
135
|
+
To create a new project from a smart contract template, use the `create` command with the `--use-case` flag:
|
|
136
|
+
|
|
137
|
+
```bash
|
|
138
|
+
settlemint scs create --project-name <project-name> --use-case <use-case-name>
|
|
139
|
+
```
|
|
140
|
+
|
|
141
|
+
#### Testing your smart contracts on a local network
|
|
142
|
+
|
|
143
|
+
To test your smart contracts, you can use the `test` command.
|
|
144
|
+
|
|
145
|
+
```bash
|
|
146
|
+
settlemint scs foundry test
|
|
147
|
+
```
|
|
148
|
+
|
|
149
|
+
#### Deploying your smart contracts and subgraphs
|
|
150
|
+
|
|
151
|
+
To deploy your smart contracts and subgraphs, you can use the `deploy` command.
|
|
152
|
+
|
|
153
|
+
```bash
|
|
154
|
+
settlemint scs hardhat deploy remote --accept-defaults
|
|
155
|
+
```
|
|
156
|
+
|
|
157
|
+
To deploy your subgraphs, use the `subgraph` command.
|
|
158
|
+
|
|
159
|
+
```bash
|
|
160
|
+
settlemint scs subgraph deploy --accept-defaults <subgraph-name>
|
|
161
|
+
```
|
|
44
162
|
|
|
45
163
|
## API Reference
|
|
46
164
|
|
|
@@ -48,15 +166,7 @@ See the [documentation](./docs/settlemint.md) for available commands.
|
|
|
48
166
|
|
|
49
167
|
## Contributing
|
|
50
168
|
|
|
51
|
-
We welcome contributions to the SettleMint SDK
|
|
52
|
-
|
|
53
|
-
1. Fork the repository
|
|
54
|
-
2. Create a new branch for your feature or bug fix
|
|
55
|
-
3. Make your changes and commit them with a clear commit message
|
|
56
|
-
4. Push your changes to your fork
|
|
57
|
-
5. Create a pull request to the main repository
|
|
58
|
-
|
|
59
|
-
Please ensure that your code follows the existing style and includes appropriate tests and documentation.
|
|
169
|
+
We welcome contributions from the community! Please check out our [Contributing](../../.github/CONTRIBUTING.md) guide to learn how you can help improve the SettleMint SDK through bug reports, feature requests, documentation updates, or code contributions.
|
|
60
170
|
|
|
61
171
|
## License
|
|
62
172
|
|