Improve docs for macOS installation (#2497) (#2621)

Author: renetapopova

modules/ROOT/images/aura-add-deployment.png

@@ -3,38 +3,32 @@
 = macOS installation
 
 Before you install Neo4j on macOS, check xref:installation/requirements.adoc[System Requirements] to see if your setup is suitable.
-
+If it is not already installed, get link:https://openjdk.org/[OpenJDK 21] or link:https://www.azul.com/downloads/[ZuluJDK 21].
 
 [[osx-console]]
-== Unix console application
+== Install and start Neo4j
 
-. If it is not already installed, get link:https://openjdk.org/[OpenJDK 21] or link:https://www.azul.com/downloads/[ZuluJDK 21].
-. Download the latest release from link:{neo4j-download-center-uri}[Neo4j Deployment Center].
-+
-Select the appropriate tar.gz distribution for your platform.
-. Make sure to download Neo4j from link:{neo4j-download-center-uri}[Neo4j Deployment Center] and always check that the SHA hash of the downloaded file is correct:
-.. To find the correct SHA hash, go to Neo4j Deployment Center and click on `SHA-256` which will be located below your downloaded file.
-.. Using the appropriate commands for your platform, display the `SHA-256` hash for the file that you downloaded.
-.. Ensure that the two are identical.
-. Extract the contents of the archive, using `tar -xf` <filename>.
-For example, `tar -xf neo4j-community-{neo4j-version-exact}-unix.tar.gz`.
+You can install Neo4j on macOS either by downloading and extracting a TAR archive or by using the Homebrew package manager.
+
+=== Install Neo4j using a tar archive
+
+. Download the Linux/Mac Executable {neo4j-version-exact} (TAR) release from link:{neo4j-download-center-uri}[Neo4j Deployment Center].
+. Extract the contents of the archive, using `tar -xf <filename>` or by double-clicking the file.
 . Place the extracted files in a permanent home on your server and set the environment variable `NEO4J_HOME` to point to the extracted directory, for example, `export NEO4J_HOME=/path/to/_<NEO4J_HOME>` to make it easier to refer to it later.
-. xref:configuration/file-locations.adoc#file-locations-file-locations[Change the default locations] of the _data_, _conf_, _certificates_, _licenses_, and _plugins_ (if you plan to use custom plugins) directories by setting the environment variable `NEO4J_CONF` and the respective xref:configuration/configuration-settings.adoc#_server_directories_settings[`server.directories.*`] settings to point to the desired locations.
+. (Recommended) xref:configuration/file-locations.adoc#file-locations-file-locations[Change the default locations] of the _data_, _conf_, _certificates_, _licenses_, and _plugins_ (if you plan to use custom plugins) directories by setting the environment variable `NEO4J_CONF` and the respective xref:configuration/configuration-settings.adoc#_server_directories_settings[`server.directories.*`] settings to point to the desired locations.
 +
 [NOTE]
 ====
 Storing your Neo4j files outside `NEO4J_HOME` will simplify the upgrade process later because you will be able to replace the DBMS binaries without affecting the configuration and state.
 Otherwise, these Neo4j files will remain in the old installation folder and may be accidentally overwritten during an upgrade or deleted during a subsequent uninstall.
 ====
-. Accept either the commercial or the evaluation license agreement before running the Neo4j Enterprise Edition.
+. label:enterprise[Enterprise Edition] Accept either the commercial or the evaluation license agreement.
 If you are using Community Edition, you can skip this step.
 * Use one of the following options to accept the commercial license agreement.
 See the link:https://legal.neo4j.com/[Neo4j licensing] page for details on the available agreements.
-+
 ** Set the environment variable `NEO4J_ACCEPT_LICENSE_AGREEMENT=yes`.
 ** Run `$NEO4J_HOME/bin/neo4j-admin server license --accept-commercial`
 * Use one of the following options to accept the link:https://neo4j.com/terms/enterprise_us/[Neo4j Evaluation Agreement for Neo4j Software]:
-+
 ** Set the environment variable `NEO4J_ACCEPT_LICENSE_AGREEMENT=eval`.
 ** Run `$NEO4J_HOME/bin/neo4j-admin server license --accept-evaluation`.
 . Before starting up the database for the first time, it is recommended to use the `set-initial-password` command of `neo4j-admin` to define the password for the native user `neo4j`.
@@ -45,18 +39,69 @@ For more information, see xref:configuration/set-initial-password.adoc[].
 . Start Neo4j:
 * To run Neo4j as a console application, use: `$NEO4J_HOME/bin/neo4j console`.
 * To run Neo4j in a background process, use: `$NEO4J_HOME/bin/neo4j start`.
-. Open  _\http://localhost:7474/_ in your web browser.
-. Connect using the username `neo4j` with your password or the default password `neo4j`.
-You will then be prompted to change the password.
-. Stop the server by typing `Ctrl-C` in the console.
 
-When Neo4j runs in console mode, logs are printed to the terminal.
+=== Install Neo4j as a macOS service
+
+The easiest way to install Neo4j as a service on macOS is to use the Homebrew package manager (see https://brew.sh/[Homebrew installation instructions]).
+
+. Install Neo4j using Homebrew:
++
+[source, shell]
+----
+brew install neo4j
+----
++
+This command installs Neo4j Community Edition and sets it up as a service that can be managed using Homebrew.
+. (Recommended) If you want to change the default directories or other settings, you can do so in the `neo4j.conf` file located at `/opt/homebrew/Cellar/neo4j/{neo4j-version-exact}/libexec/conf/neo4j.conf`.
+If already started, changes to the configuration file will not take effect until you restart the Neo4j service using `brew services restart neo4j`.
+. Start Neo4j as a macOS service:
++
+[source, shell]
+----
+brew services start neo4j
+----
++
+This command starts the Neo4j service and sets it to launch automatically at system startup.
+. To check the status of the Neo4j service, use:
++
+[source, shell]
+----
+brew services list
+----
 
+Alternatively, if you want to install Neo4j Enterprise or prefer native service control, you can use the standard macOS system tools, such as `launchd`, to create a service based on the `neo4j` command.
 
-== macOS service
+== Access Neo4j
 
-Use the standard macOS system tools to create a service based on the `neo4j` command.
+By default, Neo4j Community Edition does not include graph tools such as visualization, data exploration, and monitoring.
+However, you can use the Neo4j Aura console to access these features for free.
+No subscription is required.
 
+. Sign up or log in to the link:http://console-preview.neo4j.io/self-managed[Aura Console].
+. On the *Instances* page, click the *Self-managed* tab and then *+ Add deployment* button.
+. Select *URL Connection*.
+. Provide a *Name* and *Connection URL*.
+If you have installed Neo4j locally on your system, you can connect to _\http://localhost:7474_.
+. Click the *Connect* dropdown to launch various graph tools such as *Query*, *Explore*, and *Dashboards*.
+. Type the username `neo4j` and your password or the default password `neo4j`.
+You will be prompted to change the latter upon first login.
++
+image::aura-add-deployment.png[width=800,alt=Aura add self-managed deployment]
+
+You are now connected and can use the Aura Console to run Cypher queries, visualize graphs, and optionally monitor your local Neo4j database in Neo4j Aura.
+For details, see link:https://neo4j.com/docs/getting-started/#_work_with_data[Get started with Neo4j].
+
+Alternatively, you can use the Neo4j Browser, a web-based user interface for interacting with Neo4j that is included with the Neo4j installation.
+To access the Neo4j Browser, open a web browser and navigate to _\http://localhost:7474_.
+Connect using the username `neo4j` with your password or the default password `neo4j`.
+If the default password is used, you will be prompted to change it upon first login.
+
+== Logging
+
+Neo4j logs are written to the _logs_ directory under _NEO4J_HOME_.
+For detailed information about the log files, see xref:monitoring/logging.adoc[Logging].
+
+When Neo4j runs in console mode, logs are printed to the terminal.
 
 == macOS file descriptor limits