Coder Social home page Coder Social logo

incubator-eventmesh-site's Introduction

Apache EventMesh Website

Development

Clone and install dependencies:

git clone [email protected]:apache/eventmesh-site.git
cd eventmesh-site

npm install

Preview the website in development mode:

# Start the website with English documentations
npm run start -- --locale en

# Start the website with Chinese documentations
npm run start -- --locale zh

Build and view the website:

npm run build

npm run serve

Sync Documentation from apache/eventmesh

The npm run fetch script (scripts/fetch.ts) clones the apache/eventmesh repository and copies the documentations to docs and i18n/zh/docusaurus-plugin-content-docs. To update the documentation, please create a pull request in the apache/eventmesh repository.

npm run fetch

npm run start -- --locale en

incubator-eventmesh-site's People

Contributors

alonexc avatar andream7 avatar cnzakii avatar dependabot[bot] avatar ish1yu avatar jihuayu avatar kirinzhu avatar li-xiao-shuang avatar linuxsuren avatar lrhkobe avatar majorhe1 avatar meizhouren avatar mxsm avatar nikam14 avatar pil0txia avatar qqeasonchen avatar ritakang0451 avatar ruanwenjun avatar scwlkq avatar shaowenchen avatar shriansh2002 avatar slsjl avatar tisonkun avatar vcottagiri avatar vongosling avatar walterlife avatar wizardzhang avatar wqliang avatar xiaoyang-sde avatar xwm1992 avatar

Stargazers

 avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar

Watchers

 avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar

incubator-eventmesh-site's Issues

[Bug] queryWebHookConfigById endpoint causes NPE and returns empty response

Found in PR apache/eventmesh#4273

55b07433e099064891d9a7a68d9e48d

When inserting the config, the path contains manufacturerName, and the same logic applies when querying. Therefore, if we follow the request example in the documentation, it will result in an NPE (NullPointerException).

de668469ccf5d20f22302fc5e2c1863

There are two possible solutions, with no impact on users. One way is to retrieve manufacturerName from callbackPath when making a query on our end. However, this would require specifying in the documentation that manufacturerName must be included in users' callbackPath, which doesn't seem like a common practice.

A simpler solution is to include manufacturerName in the request. Since there are likely no users for our webhook at the moment, I will go with the latter option.

[Doc] The introductions of EventMesh Connector and EventMesh Storage are incorrect

(Related issue apache/eventmesh#4680. CC @VishalMCF.)

https://github.com/apache/eventmesh-site/blob/master/docs/instruction/03-runtime.md

Current EventMesh Connector is different from the initial EventMesh Connector, and it is a standalone service now. The initial EventMesh Connector was later changed to EventMesh Storage, but the relevant instructions in the documentation were not changed, resulting in users not knowing how to use Storage and Connector, and even attempting to use Storage or Connector in the wrong way.
For example:

The content of the file is the mapping from the plugin instance name to the plugin instance, see eventmesh-connector-rocketmq plugin module for details.

implementation project(":eventmesh-connectors:eventmesh-connector-rocketmq")

#connector plugin
eventMesh.connector.plugin.type=rocketmq

// Example: Load the RocketMQ plugin
implementation project(":eventmesh-connectors:eventmesh-connector-rocketmq")

Now eventmesh-connector-rocketmq as Connector, it does not run as a plugin, here they should be eventmesh-storage-rocketmq.

Additionally, all of the image paths in this document are incorrect. They should be /static/images/... instead of /images/... (Similar issue: #142 ).

[Enhancement] Keep old version documents as they were

  1. The Installation and deployment and SDK category should be in front of the Design documents category. (completed in #152)

  2. Older versions of the documentation should remain as they were in the Git repository at the time of each release.

Improving the import and usage methods of Checkstyle.

Currently, after importing the checkStyle.xml file, IntelliJ IDEA displays an error message in the bottom right corner stating "No header file found," which prevents new contributors from using the CheckStyle plugin.

To address this issue, I propose updating the contribution guidelines. This update should include step-by-step instructions on how to import the checkStyle.xml file in the plugin settings and how to enable the scanning in the Gradle options tab. This will ensure that new contributors can utilize the CheckStyle plugin seamlessly.

Fix merge errors caused by parallel development

#120 and #125 are two branches developed in parallel. Therefore, when merging, special handling is required. It's not sufficient to simply merge master into #125. Instead, a new branch should be created from master and the existing #125 branch should be merged into this new branch.

Remind contributors to enable Actions in forked repo to ease the reviewers approving workflows

Currently, after EventMesh graduated from Incubator, all contributors who do not have write access to the repository need Maintainer approval for the CI to run after submitting a pull request. This has increased the workload for reviewers during the review process.

To address this issue, I propose adding an optional configuration to the contribution guidelines. This will kindly remind contributors to enable GitHub Actions in their forked repositories, allowing them to self-correct various errors and allowing reviewers to directly view the CI results on the right-hand side of commit message.

image
image

After clicking on "Detail," you will be redirected to the Actions page of the forked repository.

[Doc] Many image's paths in documents should be corrected to '/static/images/...'

Recommend Projects

  • React photo React

    A declarative, efficient, and flexible JavaScript library for building user interfaces.

  • Vue.js photo Vue.js

    🖖 Vue.js is a progressive, incrementally-adoptable JavaScript framework for building UI on the web.

  • Typescript photo Typescript

    TypeScript is a superset of JavaScript that compiles to clean JavaScript output.

  • TensorFlow photo TensorFlow

    An Open Source Machine Learning Framework for Everyone

  • Django photo Django

    The Web framework for perfectionists with deadlines.

  • D3 photo D3

    Bring data to life with SVG, Canvas and HTML. 📊📈🎉

Recommend Topics

  • javascript

    JavaScript (JS) is a lightweight interpreted programming language with first-class functions.

  • web

    Some thing interesting about web. New door for the world.

  • server

    A server is a program made to process requests and deliver data to clients.

  • Machine learning

    Machine learning is a way of modeling and interpreting data that allows a piece of software to respond intelligently.

  • Game

    Some thing interesting about game, make everyone happy.

Recommend Org

  • Facebook photo Facebook

    We are working to build community through open source technology. NB: members must have two-factor auth.

  • Microsoft photo Microsoft

    Open source projects and samples from Microsoft.

  • Google photo Google

    Google ❤️ Open Source for everyone.

  • D3 photo D3

    Data-Driven Documents codes.