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

refacto/doc: remove 'cue init' step from doc

Browse Source 
Signed-off-by: Guillaume de Rouville <guillaume.derouville@gmail.com>
This commit is contained in:
Guillaume de Rouville 2021-09-08 22:31:47 +02:00
parent 3820151013
commit 6f23e9fe2a
4 changed files with 4 additions and 27 deletions
Show Stats Download Patch File Download Diff File Expand all files Collapse all files

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

@ -95,12 +95,14 @@ 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. 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. 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. 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.
```shell ```shell
cue mod init dagger init # Optional, already present in `todoapp`
``` ```
> In our case, `todoapp` already contains a workspace, so this step is optional.
### Create a Cue package ### Create a Cue package
Now we start developing our Cue package at the root of our Cue module. Now we start developing our Cue package at the root of our Cue module.

8
docs/learn/1006-google-cloud-run.md
View File

@ -25,14 +25,6 @@ Make sure that all commands are being run from the todoapp directory:
cd examples/todoapp cd examples/todoapp
``` ```
### (optional) Initialize a Cue module
This guide will use the same directory as the root of the Dagger workspace and the root of the Cue module, but you can create your Cue module anywhere inside the Dagger workspace.
```shell
cue mod init
```
### Organize your package ### Organize your package
Let's create a new directory for our Cue package: Let's create a new directory for our Cue package:

9
docs/learn/1007-kubernetes.md
View File

@ -97,15 +97,6 @@ Make sure that all commands are run from the todoapp directory:
cd examples/todoapp cd examples/todoapp
``` ```
### (optional) Initialize a Cue module
This guide will use the same directory as the root of the Dagger workspace and the root of the Cue module, but you can
create your Cue module anywhere inside the Dagger workspace.
```shell
cue mod init
```
### Organize your package ### Organize your package
Let's create a new directory for our Cue package: Let's create a new directory for our Cue package:

8
docs/learn/1008-aws-cloudformation.md
View File

@ -36,14 +36,6 @@ Make sure to run all commands from the todoapp directory:
cd examples/todoapp cd examples/todoapp
``` ```
### (optional) Initialize a Cue module
This guide will use the same directory as the root of the Dagger workspace and the root of the Cue module, but you can create your Cue module anywhere inside the Dagger workspace.
```shell
cue mod init
```
### Organize your package ### Organize your package
Let's create a new directory for our Cue package: Let's create a new directory for our Cue package: