kjuulh/dagger
Archived
1
0
Fork 0
Code Issues 1 Pull Requests 1 Projects Releases Wiki Activity

docs: 101: fixed init command

Browse Source 
Signed-off-by: Sam Alba <sam.alba@gmail.com>
This commit is contained in:
Sam Alba 2021-06-17 17:13:49 +02:00
parent a4e31949a3
commit a8889d69fc
1 changed files with 2 additions and 2 deletions
Show Stats Download Patch File Download Diff File Expand all files Collapse all files

4
docs/learn/101-use.md
View File

@ -41,7 +41,7 @@ Dagger natively supports encrypted secrets: when a user inputs a value marked as
(for example a password, API token or ssh key) it is automatically encrypted with that user's key, (for example a password, API token or ssh key) it is automatically encrypted with that user's key,
and no other user can access that value unless they are explicitly given access. and no other user can access that value unless they are explicitly given access.
In the interest of security, Dagger has no way *not* to encrypt a secret value. In the interest of security, Dagger has no way _not_ to encrypt a secret value.
But this causes a dilemma for this tutorial: how do we give unrestricted public access to our But this causes a dilemma for this tutorial: how do we give unrestricted public access to our
(carefully sandboxed) infrastructure, so that anyone can deploy to it? (carefully sandboxed) infrastructure, so that anyone can deploy to it?
@ -49,7 +49,7 @@ To solve this dilemma, we included the private key used to encrypt the tutorial'
Simply import the key to your Dagger installation, and you're good to go: Simply import the key to your Dagger installation, and you're good to go:
```shell ```shell
dagger input list || curl -sfL https://releases.dagger.io/examples/key.txt >> ~/.config/dagger/keys.txt ./import-tutorial-key.sh
``` ```
## First deployment ## First deployment