Update documentation with new build commands

uselagoon · Jan 22, 2020 · 5734463 · 5734463
1 parent 32b30d3
commit 5734463
Show file tree

Hide file tree

Showing 3 changed files with 3 additions and 12 deletions.
diff --git a/docs/administering_lagoon/install.md b/docs/administering_lagoon/install.md
@@ -15,7 +15,7 @@ This process consists of 3 main stages, which are in short:
 
 ### Configure existing OpenShift
 
-Hint: This also works with the OpenShift provided via MiniShift that can be started via `make minishift`.
+Hint: This also works with the OpenShift provided via MiniShift that can be started via `make minishift/start`.
 
 In order to create resources inside OpenShift and push into the OpenShift Registry, Lagoon needs a Service Account within OpenShift \([read more about Service Accounts](https://docs.openshift.org/latest/dev_guide/service_accounts.html)\).
 

diff --git a/docs/developing_lagoon/api-debugging.md b/docs/developing_lagoon/api-debugging.md
@@ -53,7 +53,7 @@
 4 . Rebuild/restart the containers:
 
 ```
-$ rm build/api && make build/api && docker-compose restart api
+$ make build:api && docker-compose restart api
 ```
 
 5 . Restart vscode.
diff --git a/docs/developing_lagoon/index.md b/docs/developing_lagoon/index.md
@@ -36,7 +36,7 @@ If still want to build and start all services, go ahead:
 2\. Build images
 
 ```sh
-make build
+make build:all
 ```
 
 3\. start Lagoon Services
@@ -77,15 +77,6 @@ The API uses a puppet compatible yaml format to store it's data. On production t
 
 ## Troubleshooting
 
-**I can't build any docker image for any Node.js based service**
-
-Rebuild the images via
-
-```sh
-make clean
-make build
-```
-
 **I get errors about missing node_modules content when I try to build / run a NodeJS based image**
 
 Make sure to run `yarn` in lagoon's root directory, since some services have common dependencies managed by `yarn` workspaces.