Skip to content

Patch FAQ on supportability #1002

New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

Sign up for GitHub

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Merged
merged 1 commit into from
Feb 10, 2025
Merged

Patch FAQ on supportability #1002

Changes from all commits
Commits
Show all changes
1 commit
Select commit
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
13 changes: 2 additions & 11 deletions docs/modules/ROOT/pages/user-guide/faq.adoc
View file
Open in desktop
Original file line number Diff line number Diff line change
Expand Up @@ -48,17 +48,8 @@ If you need help setting this up, please contact the NeoDash team.

== 4. Is NeoDash Production Ready?

NeoDash is safe to be used in a production environment. As it is a
reporting tool, keep the following things in mind:

- Always use *read-only* Neo4j accounts when connecting to a dashboard.
- Always deploy NeoDash with SSL, so that an encrypted Neo4j connection must be
used.
- As NeoDash accesses Neo4j directly, make sure you only give
access to the right people. As a rule of thumb, you should give NeoDash
access to the people that can also see Bloom.

For other questions regarding setting up your own production deployment, contact the NeoDash team.
NeoDash Labs is an experimental tool without official support.
For production-grade usage with Neo4j Enterprise Edition, we recommend a `NeoDash commercial` license.

== 5. Can I use NeoDash with Neo4j Community Edition?

Expand Down
Loading