Skip to content

Docker secrets should only support neo4j variables #1917

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
Oct 28, 2024
Merged

Docker secrets should only support neo4j variables #1917

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
6 changes: 5 additions & 1 deletion modules/ROOT/pages/docker/docker-compose-standalone.adoc
View file
Open in desktop
Original file line number Diff line number Diff line change
@@ -1,4 +1,5 @@
:description: Running Neo4j in a Docker container using Docker Compose
:page-role: new-5.24
[[docker-compose-neo4j-standalone]]
= Deploy a Neo4j standalone server using Docker Compose

Expand Down Expand Up @@ -85,7 +86,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