Skip to content
Draft
Show file tree
Hide file tree
Changes from all commits
Commits
File filter

Filter by extension

Filter by extension

Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
Binary file added modules/ROOT/images/add-from-cli.png
Loading
Sorry, something went wrong. Reload?
Sorry, we cannot display this file.
Sorry, this file is invalid so it cannot be displayed.
Binary file modified modules/ROOT/images/new-self-managed.png
Loading
Sorry, something went wrong. Reload?
Sorry, we cannot display this file.
Sorry, this file is invalid so it cannot be displayed.
13 changes: 13 additions & 0 deletions modules/ROOT/pages/fleet-management/setup.adoc
Original file line number Diff line number Diff line change
Expand Up @@ -70,4 +70,17 @@ Registering a token associates the deployment with the Aura project used to gene
*Never register a token obtained from a third party.*
====

== Add from Neo4j Admin CLI

You can add deployments discovered on your network using a code produced by the Neo4j Admin CLI tool.
This involves first running the `neo4j-admin fleet discover` command to look for running Neo4j servers on your network.

For more information on discovering running Neo4j servers with Neo4j Admin, see link:https://neo4j.com/docs/operations-manual/current/neo4j-admin-neo4j-cli/[Operations Manual -> Neo4j Admin and Neo4j CLI].

The next step is to select the *down arrow* next to the *Add deployment* button [See Figure 1]. In the dialog that appears, paste the code you got from running `neo4j-admin` in the indicated input box.

[.shadow]
.Add a new self-managed deployment
image::add-from-cli.png[width=600]

The list of deployments discovered by `neo4j-admin` appears in the dialog. Next to each deployment is a *Register* button which can be used to register each deployment in turn. Select this button to initiate the setup wizard which is described in the previous sections.
Loading