Skip to content

Commit 4ecdeb6

Browse files
committed
testing cli
1 parent 11a2f33 commit 4ecdeb6

File tree

3 files changed

+8
-73
lines changed

3 files changed

+8
-73
lines changed

cli/README.md

Lines changed: 4 additions & 4 deletions
Original file line numberDiff line numberDiff line change
@@ -57,7 +57,7 @@ with wasm modules:
5757
# Quick start
5858

5959
```
60-
wasmo init --name=my-first-plugin --templates=js
60+
wasmo init --name=my-first-plugin --template=js
6161
wasmo build --host=OneShotDocker --path=my-first-plugin
6262
```
6363

@@ -70,7 +70,7 @@ You can now optionally start a new plugin from a template by appending `--templa
7070
If you don't pass a template, Wasmo will list the available templates: `js`, `ts`, `opa`, `go` and `rust`.
7171

7272
```
73-
wasmo init --name=my-first-plugin --templates=[template-name] --path=[output-directory]
73+
wasmo init --name=my-first-plugin --template=[template-name] --path=[output-directory]
7474
```
7575

7676
Running this command with any of theses templates will create a directory called `my-first-plugin` inside the specified output directory (or the current if omitted). Inside that directory, it will generate the initial project structure with the metadata file pre-filled with the name of your plugin.
@@ -90,8 +90,8 @@ Assuming we want to build our `my-first-plugin` locally. Enter `wasmo build --ho
9090
Let's explain these 3 parameters:
9191
- the `path` parameter is explicitly used to indicate the plugin to build
9292
- the `host` indicates which kind of Wasmo server used. The pratical way is to use `Docker` or `OneShotDocker` because it prevents to install a Wasmo server by deploying, inside your locally Docker, a new Wasmo container. The last possible value is `Remote` and can be used to specify with a URI the remote Wasmo server used.
93-
94-
[![IMAGE ALT TEXT HERE](https://img.youtube.com/vi/NdbQR6vQ5Sk/0.jpg)](https://www.youtube.com/watch?v=NdbQR6vQ5Sk)
93+
<!--
94+
[![IMAGE ALT TEXT HERE](https://img.youtube.com/vi/NdbQR6vQ5Sk/0.jpg)](https://www.youtube.com/watch?v=NdbQR6vQ5Sk) -->
9595

9696
## Configure your configuration file
9797

docs/documentation/app/cli/getting-started/_page.mdx

Lines changed: 2 additions & 2 deletions
Original file line numberDiff line numberDiff line change
@@ -33,7 +33,7 @@ $ wasmo help
3333
# Quick start
3434

3535
```
36-
wasmo init --name=my-first-plugin --templates=js
36+
wasmo init --name=my-first-plugin --template=js
3737
wasmo build --host=OneShotDocker --path=my-first-plugin
3838
```
3939

@@ -46,7 +46,7 @@ You can now optionally start a new plugin from a template by appending `--templa
4646
If you don't pass a template, Wasmo will list the available templates: `js`, `ts`, `opa`, `go` and `rust`.
4747

4848
```
49-
wasmo init --name=my-first-plugin --templates=[template-name] --path=[output-directory]
49+
wasmo init --name=my-first-plugin --template=[template-name] --path=[output-directory]
5050
```
5151

5252
Running this command with any of theses templates will create a directory called `my-first-plugin` inside the specified output directory (or the current if omitted). Inside that directory, it will generate the initial project structure with the metadata file pre-filled with the name of your plugin.

ui/package-lock.json

Lines changed: 2 additions & 67 deletions
Some generated files are not rendered by default. Learn more about customizing how changed files appear on GitHub.

0 commit comments

Comments
 (0)