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

Docs: 102: group initial setup

Browse Source 
Signed-off-by: Solomon Hykes <solomon@dagger.io>
This commit is contained in:
Solomon Hykes 2021-06-16 16:54:28 +00:00 committed by Solomon Hykes
parent b393ecc034
commit 2d0b4a7dcb
1 changed files with 6 additions and 4 deletions
Show Stats Download Patch File Download Diff File Expand all files Collapse all files

10
docs/learn/102-dev.md
View File

@ -27,8 +27,6 @@ An environment is made of 3 parts:
We will first develop our environment's *plan*, then configure its initial inputs, then finally run it to verify that it works.
## Developing your plan
### Anatomy of a plan
A _plan_ specifies, in code, how to deliver a particular application in a particular way.
@ -60,12 +58,14 @@ steps to get started, and give you resources to learn more.
In technical terms, our plan is a [Cue Package](https://cuelang.org/docs/concepts/packages/#packages). In this tutorial we will develop a new Cue package from scratch for our plan; but you can use any Cue package as a plan.
## Initial setup
### Install Cue
Although not strictly necessary, for an optimal development experience we recommend
[installing a recent version of Cue](https://github.com/cuelang/cue/releases/).
### (optional) Prepare Cue learning resources
### Prepare Cue learning resources
If you are new to Cue, we recommend keeping the following resources in browser tabs:
@ -88,6 +88,8 @@ Make sure that all commands are run from the `todoapp` directory:
cd examples/todoapp
```
## Develop the plan
### Initialize a Cue module
Developing for Dagger takes place in a [Cue module](https://cuelang.org/docs/concepts/packages/#modules).
@ -100,7 +102,7 @@ In this guide we will use the same directory as the root of the Dagger workspace
cue mod init
```
### Organize your package
### Create a Cue package
Now we start developing our Cue package at the root of our Cue module.