You are viewing a plain text version of this content. The canonical link for it is here.
Posted to commits@eventmesh.apache.org by ch...@apache.org on 2023/01/12 13:13:37 UTC
[incubator-eventmesh-site] branch master updated: remove unused doc
This is an automated email from the ASF dual-hosted git repository.
chenguangsheng pushed a commit to branch master
in repository https://gitbox.apache.org/repos/asf/incubator-eventmesh-site.git
The following commit(s) were added to refs/heads/master by this push:
new dd07bb2 remove unused doc
dd07bb2 is described below
commit dd07bb2ef23a38b2bc0344fa5e1b4073f48aae63
Author: qqeasonchen <qq...@gmail.com>
AuthorDate: Thu Jan 12 21:13:08 2023 +0800
remove unused doc
---
docs/README.md | 99 ------------------
docs/installation/01-store.md | 44 --------
docs/installation/02-store-with-docker.md | 71 -------------
docs/installation/03-runtime.md | 107 --------------------
docs/installation/04-runtime-with-docker.md | 107 --------------------
docs/installation/05-demo.md | 152 ----------------------------
docs/installation/_category_.json | 5 -
7 files changed, 585 deletions(-)
diff --git a/docs/README.md b/docs/README.md
deleted file mode 100644
index e842c18..0000000
--- a/docs/README.md
+++ /dev/null
@@ -1,99 +0,0 @@
-<div align="center">
-
-<br /><br />
-<img src="../images/logo.png" width="256">
-<br />
-
-
-</div>
-
-
-# Apache EventMesh (Incubating)
-
-**Apache EventMesh (Incubating)** is a dynamic [event-driven](https://en.wikipedia.org/wiki/Event-driven_architecture) application multi-runtime used to decouple the application and backend middleware layer, which supports a wide range of use cases that encompass complex multi-cloud, widely distributed topologies using diverse technology stacks.
-
-### EventMesh Architecture
-
-
-
-### EventMesh Dashboard
-
-
-## Features
-
-Apache EventMesh (Incubating) has a vast amount of features to help users achieve their goals. Let us share with you some of the key features EventMesh has to offer:
-
-- Built around the [CloudEvents](https://cloudevents.io) specification.
-- Rapidty extendsible language sdk around [gRPC](https://grpc.io) protocols.
-- Rapidty extendsible middleware by connectors such as [Apache RocketMQ](https://rocketmq.apache.org), [Apache Kafka](https://kafka.apache.org), [Apache Pulsar](https://pulsar.apache.org), [RabbitMQ](https://rabbitmq.com), [Redis](https://redis.io), [Pravega](https://cncf.pravega.io), and [RDMS](https://en.wikipedia.org/wiki/Relational_database)(in progress) using [JDBC](https://en.wikipedia.org/wiki/Java_Database_Connectivity).
-- Rapidty extendsible controller such as [Consul](https://consulproject.org/en/), [Nacos](https://nacos.io), [ETCD](https://etcd.io) and [Zookeeper](https://zookeeper.apache.org/).
-- Guaranteed at-least-once delivery.
-- Deliver events between multiple EventMesh deployments.
-- Event schema management by catalog service.
-- Powerful event orchestration by [Serverless workflow](https://serverlessworkflow.io/) engine.
-- Powerful event filtering and transformation.
-- Rapid, seamless scalability to add new machines.
-
-## Roadmap
-
-Please go to the [roadmap](roadmap.md) to get the release history and new features of Apache EventMesh (Incubating).
-
-## Quick start
-Here are the guidelines:
-
-[Step 1: Deploy eventmesh-store](/instruction/01-store.md)
-
-[Step 2: Start eventmesh-runtime](/instruction/02-runtime.md)
-
-[Step 3: Run our demos](/instruction/03-demo.md)
-
-Besides, we also provide the docker-version guidelines for you if you prefer Docker:
-
-[Step 1: Deploy eventmesh-store using docker](/instruction/01-store-with-docker.md)
-
-[Step 2: Start eventmesh-runtime using docker](/instruction/02-runtime-with-docker.md)
-
-[Step 3: Run our demos](/instruction/03-demo.md)
-
-## Contributing
-
-Each contributor has played an important role in promoting the robust development of Apache EventMesh (Incubating). We sincerely appreciate all contributors who have contributed code and documents.
-
-- [Contributing Guideline](https://github.com/apache/incubator-eventmesh/blob/master/docs/en/contribute/03-new-contributor-guidelines.md)
-- [Good First Issues](https://github.com/apache/incubator-eventmesh/issues?q=is%3Aopen+is%3Aissue+label%3A%22good+first+issue%22)
-
-Here is the [List of Contributors](https://github.com/apache/incubator-eventmesh/graphs/contributors), thank you all! :)
-
-<a href="https://github.com/apache/incubator-eventmesh/graphs/contributors">
- <img src="https://contrib.rocks/image?repo=apache/incubator-eventmesh" />
-</a>
-
-
-## CNCF Landscape
-
-<div align="center">
-
-<img src="https://landscape.cncf.io/images/left-logo.svg" width="150"/>
-<img src="https://landscape.cncf.io/images/right-logo.svg" width="200"/>
-
-Apache EventMesh (Incubating) enriches the <a href="https://landscape.cncf.io/serverless?license=apache-license-2-0">CNCF Cloud Native Landscape.</a>
-
-</div>
-
-## License
-
-Apache EventMesh (Incubating) is licensed under the [Apache License, Version 2.0](http://www.apache.org/licenses/LICENSE-2.0.html).
-
-## Community
-
-|WeChat Assistant|WeChat Public Account|Slack|
-|-|-|-|
-|<img src="../images/contact/wechat-assistant.jpg" width="128"/>|<img src="../images/contact/wechat-official.jpg" width="128"/>|[Join Slack Chat](https://join.slack.com/t/apacheeventmesh/shared_invite/zt-1hgto0wcm-KXKz8pJGUwrWdk00juaQSw)|
-
-### Mailing List
-
-|Name|Description|Subscribe|Unsubscribe|Archive
-|-|-|-|-|-|
-|Users|User discussion|[Subscribe](mailto:users-subscribe@eventmesh.incubator.apache.org)|[Unsubscribe](mailto:users-unsubscribe@eventmesh.incubator.apache.org)|[Mail Archives](https://lists.apache.org/list.html?users@eventmesh.apache.org)|
-|Development|Development discussion (Design Documents, Issues, etc.)|[Subscribe](mailto:dev-subscribe@eventmesh.incubator.apache.org)|[Unsubscribe](mailto:dev-unsubscribe@eventmesh.incubator.apache.org)|[Mail Archives](https://lists.apache.org/list.html?dev@eventmesh.apache.org)|
-|Commits|Commits to related repositories| [Subscribe](mailto:commits-subscribe@eventmesh.incubator.apache.org) |[Unsubscribe](mailto:commits-unsubscribe@eventmesh.incubator.apache.org) |[Mail Archives](https://lists.apache.org/list.html?commits@eventmesh.apache.org)|
diff --git a/docs/installation/01-store.md b/docs/installation/01-store.md
deleted file mode 100644
index 603da7b..0000000
--- a/docs/installation/01-store.md
+++ /dev/null
@@ -1,44 +0,0 @@
-# Step 1: Store
-
-## Dependencies
-
-```
-64-bit OS，we recommend Linux/Unix；
-64-bit JDK 1.8+;
-Gradle 7.0+, we recommend 7.0.*
-4g+ available disk to deploy eventmesh-store
-If you choose standalone mode, you could skip this file and go to the next step: Start Eventmesh-Runtime; if not, you could choose RocketMQ as the store layer.
-```
-
-
-## Download
-
-Download the Binary code (recommended: 4.9.*) from [RocketMQ Official](https://rocketmq.apache.org/dowloading/releases/). Here we take 4.9.2 as an example.
-
-```
-unzip rocketmq-all-4.9.2-bin-release.zip
-cd rocketmq-4.9.2/
-```
-
-
-## Deploy
-
-- #### Start Name Server
-
-```
-nohup sh bin/mqnamesrv &
-tail -f ~/logs/rocketmqlogs/namesrv.log
-```
-
-- #### Start Broker
-
-```
-nohup sh bin/mqbroker -n localhost:9876 &
-tail -f ~/logs/rocketmqlogs/broker.log
-```
-
-The deployment of eventmesh-store has finished, please go to the next step: [Start Eventmesh-Runtime](docs/en/instruction/02-runtime.md)
-
-
-## Reference
-For more details about RocketMQ，please refer to <https://rocketmq.apache.org/docs/quick-start/>
diff --git a/docs/installation/02-store-with-docker.md b/docs/installation/02-store-with-docker.md
deleted file mode 100644
index 026191e..0000000
--- a/docs/installation/02-store-with-docker.md
+++ /dev/null
@@ -1,71 +0,0 @@
-# Step 1: Store (Docker)
-
-## Dependencies
-
-```
-64-bit OS，we recommend Linux/Unix；
-64-bit JDK 1.8+;
-Gradle 7.0+, we recommend 7.0.*
-4g+ available disk to deploy eventmesh-store
-If you choose standalone mode, you could skip this file and go to the next step: Start Eventmesh-Runtime; if not, you could choose RocketMQ as the store layer.
-```
-
-
-## Download
-
-Download the Binary code (recommended: 4.9.*) from [RocketMQ Official](https://rocketmq.apache.org/dowloading/releases/). Here we take 4.9.2 as an example.
-
-```
-unzip rocketmq-all-4.9.2-bin-release.zip
-cd rocketmq-4.9.2/
-```
-
-
-## Deploy
-
-- #### Start Name Server
-
-```
-nohup sh bin/mqnamesrv &
-tail -f ~/logs/rocketmqlogs/namesrv.log
-```
-
-- #### Start Broker
-
-```
-nohup sh bin/mqbroker -n localhost:9876 &
-tail -f ~/logs/rocketmqlogs/broker.log
-```
-
-The deployment of eventmesh-store has finished, please go to the next step: [Start Eventmesh-Runtime](docs/en/instruction/02-runtime.md)
-
-
-
-## Deploy
-Pull RocketMQ image from Docker Hub：
-
-```shell
-#获取namesrv镜像
-sudo docker pull rocketmqinc/rocketmq-namesrv:4.5.0-alpine
-#获取broker镜像
-sudo docker pull rocketmqinc/rocketmq-broker:4.5.0-alpine
-```
-
-Start namesrv and broker
-
-```shell
-#运行namerv容器
-sudo docker run -d -p 9876:9876 -v `pwd` /data/namesrv/logs:/root/logs -v `pwd`/data/namesrv/store:/root/store --name rmqnamesrv rocketmqinc/rocketmq-namesrv:4.5.0-alpine sh mqnamesrv
-
-#运行broker容器
-sudo docker run -d -p 10911:10911 -p 10909:10909 -v `pwd`/data/broker/logs:/root/logs -v `pwd`/data/broker/store:/root/store --name rmqbroker --link rmqnamesrv:namesrv -e "NAMESRV_ADDR=namesrv:9876" rocketmqinc/rocketmq-broker:4.5.0-alpine sh mqbroker -c ../conf/broker.conf
-```
-
-Please note that the **rocketmq-broker ip** is **pod ip**. If you want to modify this ip, you can set it your custom value in **broker.conf**。
-
-
-By now, the deployment of eventmesh-store has finished, please go to the next step: [Start Eventmesh-Runtime Using Docker](docs/en/instruction/02-runtime-with-docker.md)
-
-
-## Reference
-For more details about RocketMQ，please refer to <https://rocketmq.apache.org/docs/quick-start/>
diff --git a/docs/installation/03-runtime.md b/docs/installation/03-runtime.md
deleted file mode 100644
index 2945fd2..0000000
--- a/docs/installation/03-runtime.md
+++ /dev/null
@@ -1,107 +0,0 @@
-# Step 2: Runtime
-
-EventMesh Runtime is the core component of Apache EventMesh (Incubating). It is the middleware that transmits events between producers and consumers. The documentation introduces the step to install and start the latest release of EventMesh Runtime in the local or test environment. The EventMesh Runtime requires a Linux-based system with JDK (Java Development Kit) 8+.
-
-Here, we take JDK 8 as an example. JDK 8 could be installed with the system package manager or the [openjdk:8-jdk](https://hub.docker.com/_/openjdk) Docker image.
-
-
-## 1 Run on your local machine
-
-### 1.1 Dependencies
-
-```
-64-bit OS，we recommend Linux/Unix;
-64-bit JDK 1.8+;
-Gradle 7.0+, we recommend 7.0.*;
-4g+ available disk to deploy eventmesh-store;
-If you choose standalone mode, you could skip this file and go to the next step: Start Eventmesh-Runtime; if not, you could choose RocketMQ as the store layer.
-```
-
-### 1.2 Download Source Code
-
-Gradle is the build automation tool used by Apache EventMesh (Incubating). Please refer to the [offical guide](https://docs.gradle.org/current/userguide/installation.html) to install the latest release of Gradle.
-
-Download and extract the source code of the latest release from [EventMesh download](https://eventmesh.apache.org/download).
-
-```console
-wget https://dlcdn.apache.org/incubator/eventmesh/{version}-incubating/apache-eventmesh-{version}-incubating-source.tar.gz
-
-tar -xvzf apache-eventmesh-1.5.0-incubating-source.tar.gz
-```
-
-Build the source code with Gradle.
-
-```console
-cd apache-eventmesh-1.5.0-incubating-source
-gradle clean dist
-```
-
-Edit the `eventmesh.properties` to change the configuration (e.g. TCP port, client blacklist) of EventMesh Runtime.
-
-```console
-cd dist
-vim conf/eventmesh.properties
-```
-
-Execute the `start.sh` script to start the EventMesh Runtime server.
-
-```console
-bash bin/start.sh
-```
-
-### 1.3 Build and Load Plugins
-
-Apache EventMesh (Incubating) introduces the SPI (Service Provider Interface) mechanism, which enables EventMesh to discover and load the plugins at runtime. The plugins could be installed with these methods:
-
-- Gradle Dependencies: Declare the plugins as the build dependencies in `eventmesh-starter/build.gradle`.
-
-```gradle
-dependencies {
- implementation project(":eventmesh-runtime")
-
- // Example: Load the RocketMQ plugin
- implementation project(":eventmesh-connector-plugin:eventmesh-connector-rocketmq")
-}
-```
-
-- Plugin directory: EventMesh loads the plugins in the `dist/plugin` directory based on `eventmesh.properties`. The `installPlugin` task of Gradle builds and moves the plugins into the `dist/plugin` directory.
-
-```console
-gradle installPlugin
-```
-
-
-## 2 Remote deployment
-### 2.1 Dependencies
-
-```
-64-bit OS，we recommend Linux/Unix；
-64-bit JDK 1.8+;
-Gradle 7.0+, we recommend 7.0.*
-4g+ available disk to deploy eventmesh-store
-If you choose standalone mode, you could skip this file and go to the next step: Start Eventmesh-Runtime; if not, you could choose RocketMQ as the store layer.
-```
-
-### 2.2 Download
-Download and extract the executable binaries of the latest release from [EventMesh download](https://eventmesh.apache.org/download).
-
-```console
-wget https://github.com/apache/incubator-eventmesh/releases/download/v1.4.0/apache-eventmesh-1.4.0-incubating-bin.tar.gz
-
-tar -xvzf apache-eventmesh-1.5.0-incubating-bin.tar.gz
-```
-
-### 2.3 Deploy
-Edit the `eventmesh.properties` to change the configuration (e.g. TCP port, client blacklist) of EventMesh Runtime. The executable binaries contain all plugins in the bundle, thus there's no need to build them from source code.
-
-```console
-cd apache-eventmesh-1.5.0-incubating
-vim conf/eventmesh.properties
-```
-
-Execute the `start.sh` script to start the EventMesh Runtime server.
-
-```console
-bash bin/start.sh
-```
-
diff --git a/docs/installation/04-runtime-with-docker.md b/docs/installation/04-runtime-with-docker.md
deleted file mode 100644
index 594d910..0000000
--- a/docs/installation/04-runtime-with-docker.md
+++ /dev/null
@@ -1,107 +0,0 @@
-# Step 2: Runtime (Docker)
-
-The documentation introduces the steps to install the latest release of EventMesh Runtime with Docker and connect to Apache RocketMQ. It's recommended to use a Linux-based system with [Docker Engine](https://docs.docker.com/engine/install/). Please follow the [Docker tutorial](https://docs.docker.com/get-started/) to get familiar with the basic concepts (registry, volume, etc.) and commands of Docker.
-
-
-## Dependencies
-```
-64-bit OS，we recommend Linux/Unix；
-64-bit JDK 1.8+;
-Gradle 7.0+, we recommend 7.0.*
-4g+ available disk to deploy eventmesh-store
-If you choose standalone mode, you could skip this file and go to the next step: Start Eventmesh-Runtime; if not, you could choose RocketMQ as the store layer.
-```
-
-## Pull EventMesh Image
-
-Download the pre-built image of [`eventmesh`](https://hub.docker.com/r/eventmesh/eventmesh) from Docker Hub with `docker pull`:
-
-```console
-$ sudo docker pull eventmesh/eventmesh:v1.4.0
-```
-
-To verify that the `eventmesh/eventmesh` image is successfully installed, list the downloaded images with `docker images`:
-
-```console
-$ sudo docker images
-eventmesh/eventmesh v1.4.0 6e2964599c78 2 weeks ago 937MB
-```
-
-## Edit Configuration
-
-Edit the `eventmesh.properties` to change the configuration (e.g. TCP port, client blacklist) of EventMesh Runtime. To integrate RocketMQ as a connector, these two configuration files should be created: `eventmesh.properties` and `rocketmq-client.properties`.
-
-```shell
-sudo mkdir -p /data/eventmesh/rocketmq/conf
-cd /data/eventmesh/rocketmq/conf
-sudo touch eventmesh.properties
-sudo touch rocketmq-client.properties
-```
-
-### `eventmesh.properties`
-
-The `eventmesh.properties` file contains the properties of EventMesh runtime environment and integrated plugins. Please refer to the [default configuration file](https://github.com/apache/incubator-eventmesh/blob/master/eventmesh-runtime/conf/eventmesh.properties) for the available configuration keys.
-
-```shell
-sudo vim eventmesh.properties
-```
-
-| Configuration Key | Default Value | Description |
-|-|-|-|
-| `eventMesh.server.http.port` | 10105 | EventMesh HTTP server port |
-| `eventMesh.server.tcp.port` | 10000 | EventMesh TCP server port |
-| `eventMesh.server.grpc.port` | 10205 | EventMesh gRPC server port |
-
-### `rocketmq-client.properties`
-
-The `rocketmq-client.properties` file contains the properties of the Apache RocketMQ nameserver.
-
-```shell
-sudo vim rocketmq-client.properties
-```
-
-Please refer to the [default configuration file](https://github.com/apache/incubator-eventmesh/blob/1.3.0/eventmesh-runtime/conf/rocketmq-client.properties) and change the value of `eventMesh.server.rocketmq.namesrvAddr` to the nameserver address of RocketMQ.
-
-| Configuration Key | Default Value | Description |
-|-|-|-|
-| `eventMesh.server.rocketmq.namesrvAddr` | `127.0.0.1:9876;127.0.0.1:9876` | The address of RocketMQ nameserver |
-
-## Run and Manage EventMesh Container
-
-Run an EventMesh container from the `eventmesh/eventmesh` image with the `docker run` command. The `-p` option of the command binds the container port with the host machine port. The `-v` option of the command mounts the configuration files from files in the host machine.
-
-```shell
-sudo docker run -d -p 10000:10000 -p 10105:10105 \
--v /data/eventmesh/rocketmq/conf/eventmesh.properties:/data/app/eventmesh/conf/eventmesh.properties \
--v /data/eventmesh/rocketmq/conf/rocketmq-client.properties:/data/app/eventmesh/conf/rocketmq-client.properties \
-eventmesh/eventmesh:v1.4.0
-```
-
-The `docker ps` command lists the details (id, name, status, etc.) of the running containers. The container id is the unique identifier of the container.
-
-```console
-$ sudo docker ps
-CONTAINER ID IMAGE COMMAND CREATED STATUS PORTS NAMES
-<container_id> eventmesh/eventmesh:v1.4.0 "/bin/sh -c 'sh star…" About a minute ago Up About a minute 0.0.0.0:10000->10000/tcp, :::10000->10000/tcp, 0.0.0.0:10105->10105/tcp, :::10105->10105/tcp <container_name>
-```
-
-To connect to the EventMesh container:
-
-```shell
-sudo docker exec -it [container id or name] /bin/bash
-```
-
-To read the log of the EventMesh container:
-
-```shell
-tail -f ../logs/eventmesh.out
-```
-
-To stop or remove the container:
-
-```shell
-sudo docker stop [container id or name]
-
-sudo docker rm -f [container id or name]
-```
-
diff --git a/docs/installation/05-demo.md b/docs/installation/05-demo.md
deleted file mode 100644
index d51049c..0000000
--- a/docs/installation/05-demo.md
+++ /dev/null
@@ -1,152 +0,0 @@
-# Step 3: Run our demos
-
-[](https://maven-badges.herokuapp.com/maven-central/org.apache.eventmesh/eventmesh-sdk-java)
-
-> EventMesh-sdk-java as the client，and comminucate with eventmesh-runtime，to finish the message sub and pub
->
-> EventMesh-sdk-java support both async and broadcast.
->
-> EventMesh-sdk-java support HTT, TCP and gRPC.
-
-The test demos of TCP, HTTP 和 GRPC are in the module **eventmesh-examples**
-
-## 1 TCP DEMO
-
-### 1.1 ASYNC
-
-- Start consumer to subscribe the topic (we have created the TEST-TOPIC-TCP-ASYNC by default, you can also create other topic to test)
-
-```shell
-Run the main method of org.apache.eventmesh.tcp.demo.sub.eventmeshmessage.AsyncSubscribe
-```
-
-- Start producer to publish async message
-
-```shell
-Run the main method of org.apache.eventmesh.tcp.demo.pub.eventmeshmessage.AsyncPublish
-```
-
-### 1.2 BROADCAST
-
-- Start subscriber to subscribe the topic (we have created the TEST-TOPIC-TCP-BROADCAST by default, you can also create other topic to test)
-
-```shell
-Run the main method of org.apache.eventmesh.tcp.demo.sub.eventmeshmessage.AsyncSubscribeBroadcast
-```
-
-- Start publisher to publish async message
-
-```shell
-Run the main method of org.apache.eventmesh.tcp.demo.pub.eventmeshmessage.AsyncPublishBroadcast
-```
-
-More information about EventMesh-TCP, please refer to [EventMesh TCP](docs/zh/sdk-java/03-tcp.md)
-
-
-## 2 HTTP DEMO
-
-
-### 2.1 ASYNC
-
-- The subscriber is a SpringBoot demo, so run this demo to start subscriber (we have created the topic TEST-TOPIC-HTTP-ASYNC by default, you can also create other topic to test)
-
-```shell
-Run the main method of org.apache.eventmesh.http.demo.sub.SpringBootDemoApplication
-```
-
-- Start publisher to publish message
-
-```shell
-Run the main method of org.apache.eventmesh.http.demo.pub.eventmeshmessage.AsyncPublishInstance
-```
-More information about EventMesh-HTTP, please refer to [EventMesh HTTP](docs/zh/sdk-java/02-http.md)
-
-## 3 GRPC DEMO
-
-### 3.1 ASYNC PUBLISH & WEBHOOK SUBSCRIBE
-
-- Start publisher to publish message (we have created the topic TEST-TOPIC-GRPC-ASYNC by default, you can also create other topic to test)
-
-```shell
-Run the main method of org.apache.eventmesh.grpc.pub.eventmeshmessage.AsyncPublishInstance
-```
-
-- Start webhook subscriber
-
-```shell
-Run the main method of org.apache.eventmesh.grpc.sub.app.SpringBootDemoApplication
-```
-
-### 3.2 SYNC PUBLISH & STREAM SUBSCRIBE
-
-- Start Request-Reply publisher to publish message (we have created the topic TEST-TOPIC-GRPC-RR by default, you can also create other topic to test)
-
-```shell
-Run the main method of org.apache.eventmesh.grpc.pub.eventmeshmessage.RequestReplyInstance
-```
-
-- Start stream subscriber
-
-```shell
-Run the main method of org.apache.eventmesh.grpc.sub.EventmeshAsyncSubscribe
-```
-
-### 3.3 PUBLISH BATCH MESSAGE
-
-- Start publisher to publish batch message (we have created the TEST-TOPIC-GRPC-ASYNC by default, you can also create other topic to test)
-
-```shell
-Run the main method of org.apache.eventmesh.grpc.pub.eventmeshmessage.BatchPublishInstance
-```
-
-More information about EventMesh-gRPC, please refer to [EventMesh gRPC](docs/zh/sdk-java/04-grpc.md)
-
-## 4 Run these demos by yourself
-
-Please refer to [EventMesh Store](docs/zh/instruction/01-store.md) and [EventMesh Runtime](docs/zh/instruction/02-runtime.md) to finish the necessary deployment before try our demo
-
-After finishing the deployment of store and runtime, you can run our demos in module `eventmesh-examples`:
-
-### TCP Sub
-
- ```shell
- cd bin
- sh tcp_eventmeshmessage_sub.sh
- ```
-
-### TCP Pub
-
- ```shell
- cd bin
- sh tcp_pub_eventmeshmessage.sh
- ```
-
-### TCP Sub Broadcast
-
- ```shell
- cd bin
- sh tcp_sub_eventmeshmessage_broadcast.sh
- ```
-
-### TCP Pub Broadcast
-
- ```shell
- cd bin
- sh tcp_pub_eventmeshmessage_broadcast.sh
- ```
-
-### HTTP Sub
-
- ```shell
- cd bin
- sh http_sub.sh
- ```
-
-### HTTP Pub
-
- ```shell
- cd bin
- sh http_pub_eventmeshmessage.sh
- ```
-
-You can review the log in the folder `/logs`
diff --git a/docs/installation/_category_.json b/docs/installation/_category_.json
deleted file mode 100644
index 690c6eb..0000000
--- a/docs/installation/_category_.json
+++ /dev/null
@@ -1,5 +0,0 @@
-{
- "position": 2,
- "label": "Installation and Deployment",
- "collapsed": false
-}
---------------------------------------------------------------------
To unsubscribe, e-mail: commits-unsubscribe@eventmesh.apache.org
For additional commands, e-mail: commits-help@eventmesh.apache.org