Patrick.Sy/hello-dagger
1
0
Fork 0
Code Issues Pull requests Projects Releases Packages Wiki Activity Actions

docs(dagger): minor changes

Browse source
This commit is contained in:
Patrick Sy 2024-10-16 16:36:03 +02:00
parent c06389ce56
commit 80639cc68f
Signed by: Patrick.Sy
GPG key ID: DDDC8EC51823195E
1 changed files with 3 additions and 5 deletions
Show stats Download patch file Download diff file Expand all files Collapse all files

8
README.md
View file

@ -78,14 +78,15 @@ workdir: ""
The `Container` has to be consumed by other functions to actually export it to
some registry or run it. The same is true for other types like `File` and
`Directory` which also only expose the actual artifacts through effectful
`Directory` which also only expose the actual artifacts through 'effectful'
functions, thus the FP-like feeling. Only 'simple' strings can be exposed on
the shell. Consequently, pipelining on the shell seems not to be a common
thing.
Dagger separates the containerized build environment from the host system.
Unless specifically specified, like with `--source=.`, dagger does not expose
host resources.
host resources. This adds to the notion of trying to create reproducible
actions.
> Camel Case function names in the TS setup are available in Kebab Case on the
> shell (same applies for Go and Python). This does not only apply to your own
@ -132,9 +133,6 @@ dagger call security-scan --source=.
> Python module can be used in a Typescript config. The proper API functions
> are exposed on the `dag` object.
> Most modules are just thin wrappers around specific images that contain for
> example some tool and provide convenience functions.
Push the container image to some registry:
```shell