Skip to content

Commit

Permalink
Update ex-ug-deploy.md
Browse files Browse the repository at this point in the history
  • Loading branch information
akihi99 authored Jul 5, 2023
1 parent 4f23b21 commit c59ec38
Showing 1 changed file with 5 additions and 5 deletions.
10 changes: 5 additions & 5 deletions docs-2.0/nebula-explorer/deploy-connect/ex-ug-deploy.md
Original file line number Diff line number Diff line change
Expand Up @@ -2,10 +2,6 @@

This topic describes how to deploy Explorer locally by RPM, DEB, and tar packages.

## Precautions

The Dag Controller installation package is built in Explorer starting from version 3.2.0, which provides graph computing services. The user can decide whether or not to start the Dag Controller service. If the Dag Controller service is not started, the **Workflow** menu in Explorer will appear gray and cannot be clicked.

## Prerequisites

Before deploying Explorer, you must check the following information:
Expand All @@ -26,7 +22,11 @@ Before deploying Explorer, you must check the following information:

- The Linux distribution is CentOS.

- The NFS or HDFS services are deployed if graph computing is required. The namenode uses port 8020 by default, and the datanode uses port 50010 by default.
## Precautions

The Dag Controller installation package is built in Explorer starting from version 3.2.0, which provides graph computing services. The user can decide whether or not to start the Dag Controller service. If the Dag Controller service is not started, the **Workflow** menu in Explorer will appear gray and cannot be clicked.

In addition, if you need to use **Workflow** for complex graph computing, you need to configure NFS or HDFS after installing Explorer. Namenode uses port 8020 by default, and datanode uses port 50010 by default. For details, see [Prepare resources](../../nebula-explorer/workflow/1.prepare-resources.md) of **Workflow**.

<!-- !!! caution
Expand Down

0 comments on commit c59ec38

Please sign in to comment.