There was an error while loading. Please reload this page.
2 parents b024e8e + dd39973 commit 7e8aebeCopy full SHA for 7e8aebe
5 files changed
docs/GettingStarted/DeployingWithDocker/index.md
@@ -54,7 +54,7 @@ The export-then-`docker compose up` pattern above passes secrets as plain shell
54
which is fine for local evaluation but not how a real deployment should hand over credentials.
55
`Jube.Cluster/secrets-init.sh`
56
now provides this for the clustered Docker Swarm deployment - see [Creating
57
-Secrets](../DeployingWithJubeCluster/index.html#creating-secrets) - generating random credentials and an RSA keypair
+Secrets](../DeployingWithJubeCluster/DeploymentRunbook/index.html#creating-secrets) - generating random credentials and an RSA keypair
58
and loading them into Swarm's own secret store, resolved at container start via Jube's own `SecretsPath`/`[@Key@]`
59
Docker Secrets tokenisation already documented in
60
[Environment Variables](../../Concepts/EnvironmentVariables/index.html). That script relies on `docker secret
0 commit comments