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

replaced workspace with project

Browse Source 
Signed-off-by: Richard Jones <richard@dagger.io>
This commit is contained in:
Richard Jones
2021-09-21 14:36:51 -06:00
committed by Sam Alba
parent 9c32c8a564
commit 11749cde01
7 changed files with 23 additions and 23 deletions
Download Patch File Download Diff File Expand all files Collapse all files

4
docs/learn/1004-first-env.md
View File

@@ -89,13 +89,13 @@ Developing for Dagger takes place in a [Cue module](https://cuelang.org/docs/con
If you are familiar with Go, Cue modules are directly inspired by Go modules.
Otherwise, don't worry: a Cue module is simply a directory with one or more Cue packages in it. For example, a Cue module has a `cue.mod` directory at its root.
This guide will use the same directory as the root of the Dagger workspace and the Cue module, but you can create your Cue module anywhere inside the Dagger workspace. In general, you won't have to worry about it at all. You will initialize a dagger workspace with the following command.
This guide will use the same directory as the root of the Dagger project and the Cue module, but you can create your Cue module anywhere inside the Dagger project. In general, you won't have to worry about it at all. You will initialize a dagger project with the following command.
```shell
dagger init # Optional, already present in `todoapp`
```
> In our case, `todoapp` already contains a workspace, so this step is optional.
> In our case, `todoapp` already contains a `.dagger` directory, so this step is optional.
### Create a Cue package