Skip to content

Commit 5f41a84

Browse files
committed
update
1 parent d149b85 commit 5f41a84

File tree

1 file changed

+10
-10
lines changed

1 file changed

+10
-10
lines changed

docs/contributing-to-lagoon/developing-lagoon.md

Lines changed: 10 additions & 10 deletions
Original file line numberDiff line numberDiff line change
@@ -99,22 +99,22 @@ At the end of the process, the command will provide some useful information that
9999
At this point, it is helpful to configure the Lagoon CLI to work with the local lagoon.
100100
First however, you must add your ssh public key to a user.
101101
If you set up a seed user in earlier steps, then you can use that one.
102-
Visit the user's settings page in the UI, most likely located at [https://lagoon-ui.172.18.0.240.nip.io/settings](https://lagoon-ui.172.18.0.240.nip.io/settings).
102+
Visit the user's settings page in the UI, most likely located at [https://lagoon-ui.${LAGOON_IP}.nip.io/settings](https://lagoon-ui.${LAGOON_IP}.nip.io/settings), where LAGOON_IP is the IP address of the k3d cluster.
103103
Next, you should install and configure the Lagoon CLI - the instructions for which are located [here](/installing-lagoon/lagoon-cli/).
104-
However, in this case specifically the command in step 2 will most likely be:
104+
However, in this case the correct command can be found using `make k3d/get-lagoon-cli-details`, which will return something like:
105105

106106
```bash title="Add local-stack lagoon to Lagoon CLI"
107107
lagoon config add \
108-
--graphql https://lagoon-api.172.18.0.240/graphql \
109-
--ui https://lagoon-ui.172.18.0.240 \
110-
--hostname https://lagoon-ssh.172.18.0.240 \
111-
--ssh-key PATH_TO_PRIVATE_SSH_KEY
112-
--lagoon local-stack \
113-
--port 2020
108+
--lagoon local-k3d \
109+
--graphql http://lagoon-api.${LAGOON_IP}.nip.io/graphql \
110+
--token TOKEN \
111+
--hostname lagoon-token.${LAGOON_SSH_IP}.nip.io \
112+
--port 2223
114113
```
115114

116-
To test deploying a project in the local stack, you will also need to add a "deploy target" to your organization.
117-
First, you will need to get the ID of preconfigured Lagoon Remote with:
115+
In order for Lagoon to deploy a project, it needs a "deploy target" to be set.
116+
The organizations created via the `make k3d/seed-data` make target will already have this configured for you, but not organizations created via the `LAGOON_SEED_ORGANIZATION` environment variable.
117+
To add a deploy target to an organization, you will first need to get the ID of preconfigured Lagoon Remote with:
118118

119119
```bash
120120
lagoon list deploytargets

0 commit comments

Comments
 (0)