From 7799f2369b5725f8518561bf2a6ed7717f442c45 Mon Sep 17 00:00:00 2001 From: Cesar De la Torre Date: Mon, 18 Sep 2017 14:47:30 -0700 Subject: [PATCH] Updated 10. Setting the solution up in ACS Kubernetes (markdown) --- 10.-Setting-the-solution-up-in-ACS-Kubernetes.md | 3 +++ 1 file changed, 3 insertions(+) diff --git a/10.-Setting-the-solution-up-in-ACS-Kubernetes.md b/10.-Setting-the-solution-up-in-ACS-Kubernetes.md index 10b1186..6bc5393 100644 --- a/10.-Setting-the-solution-up-in-ACS-Kubernetes.md +++ b/10.-Setting-the-solution-up-in-ACS-Kubernetes.md @@ -276,6 +276,9 @@ Right after running that command you now will have the file `config` with the ne **Prerequisites** Before publishing the code to k8s you should have compiled and published your code to `obj/Docker/publish` folder (on any project path). The best way to do it is to run the `/cli-windows/buid-bits.ps1` script in windows or the `/cli-linux/build-bits-linux.sh` on Linux or the `/cli-mac/build-bits.sh` on Mac. +NOTE: Make sure you have npm and bower installed. If Bower is not installed globally, you might have errors when building the bits for the MVC and WebStatus apps. +If you don't have Bower installed, run: `npm install -g bower` + If you prefer, you can force the `publish.ps1` script to build and publish the code for you using the `-buildBits $true` parameter. Using this parameter the publishing script will recompile and republish all projects (default value is `$false`). We have simplified the deployment so you can do it just by executing a script by following the following few steps: