Skip to content

Commit

Permalink
Docker secrets should only support neo4j variables (#1917)
Browse files Browse the repository at this point in the history
  • Loading branch information
renetapopova committed Oct 28, 2024
1 parent b6021a1 commit bbae12a
Showing 1 changed file with 4 additions and 1 deletion.
5 changes: 4 additions & 1 deletion modules/ROOT/pages/docker/docker-compose-standalone.adoc
Original file line number Diff line number Diff line change
Expand Up @@ -87,7 +87,10 @@ secrets:
file: ./neo4j_auth.txt # <5>
----
<1> Mount the _/$HOME/neo4j/<..>:_ directories to local directories on your host machine to store logs, configuration, data, and plugins.
<2> Path to the file where the value for the `NEO4J_AUTH` environment variable can be found.
<2> Path to the secret (`neo4j_auth_file`) containing the `neo4j` username and password.
The secret value is read from the file specified in the `file` attribute of the `neo4j_auth_file` secret.
Multiple secrets can be defined in the `secrets` section of the `neo4j` service.
Secrets only support environment variables starting with `NEO4J_` and ending with `_FILE`.
<3> The name of the secret, for example `neo4j_auth_file`.
<4> Path to the _neo4j_auth.txt_ file.
<5> The name of the secret in the `neo4j` service.
Expand Down

0 comments on commit bbae12a

Please sign in to comment.