Installer neo4j-desktop avec Homebrew Cask

Liens du projet

• Page d'accueil
• Page du gestionnaire de paquets

Commandes et alias

Aucun alias exécutable n'a été trouvé dans la base locale des paquets.

Historique du projet

Neo4j Desktop began as a desktop packaging of the Neo4j graph platform with a bundled JVM, Developer Edition database, and graph applications. The official project repository describes it as a client containing everything needed to start working with Neo4j.

Desktop 2.x is described by Neo4j as an evolution of the original Desktop, with a redesigned and more unified experience that mirrors the Neo4j Aura console. It consolidated local instance management with Import, Query, Bloom, and Dashboards in Desktop Studio.

Historique d'adoption

Neo4j Desktop packages a local developer environment around Neo4j rather than requiring users to assemble a database server, JVM, query UI, import tooling, and visualization tools separately. It supports macOS, Windows, and Linux and can manage local databases while also connecting to remote Neo4j and Aura instances.

Desktop includes a Developer edition license for local single-user use and supports installing plugins through its interface, making it a common entry point for graph application development and Cypher experimentation.

Modes d'utilisation

Developers create projects and local DBMS instances, select a Neo4j version, start or stop instances, edit each instance's `neo4j.conf`, install plugins, import data, and query or visualize graphs from the bundled Studio tools.

The official UI exposes each local instance's folder, log, configuration file, data path, connection URI, security controls, backup actions, and upgrade workflow.

Pourquoi les passionnés de paquets s'y intéressent

Neo4j Desktop is the batteries-included desktop distribution in the Neo4j ecosystem. Package users care about it because the application manages multiple DBMS versions and instance directories while bundling import, query, Bloom visualization, and dashboard tools.

It differs from the standalone Neo4j server package: Desktop prioritizes an interactive local workspace and lifecycle management, whereas the server and Cypher Shell packages better suit services, scripts, and headless environments.

Chronologie

• The original Neo4j Desktop combined a local Neo4j developer installation with bundled graph applications.
• Desktop 2.x introduced a redesigned workspace aligned with the Aura console and unified Import, Query, Bloom, and Dashboards as Desktop Studio.
• Desktop 2.x added migration support for cloning compatible instances from Desktop 1.x.

Related projects

• Neo4j DBMS is the graph database managed locally by Desktop.
• Neo4j Aura supplies managed remote Neo4j instances that Desktop can connect to.
• Cypher Shell provides a command-line path for running queries and administrative commands.
• APOC plugins can be installed into compatible local instances from Desktop.

Sources

• https://github.com/neo4j-devtools/neo4j-desktop
• https://neo4j.com/docs/desktop/current/
• https://neo4j.com/docs/desktop/current/operations/instance-management/
• https://neo4j.com/docs/desktop/current/visual-tour/