Merge pull request SAFE-Stack#146 from theprash/master

Updates for FAKE and paket local dotnet tools in template

Author: theimowski

docs/faq-troubleshooting.md

@@ -1,9 +1,5 @@
 ## Getting Started
 
-### FAKE cannot be found
-
-If you fail to execute `fake` from command line after installing it as a global tool, you might need to add it to your `PATH` manually: (e.g. `export PATH="$HOME/.dotnet/tools:$PATH"` on unix) - [related GitHub issue](https://github.com/dotnet/cli/issues/9321)
-
 ## Diagnostics
 
 ### SocketProtocolError in Debug Console

docs/quickstart.md

@@ -5,13 +5,9 @@ This page provides some basic guidance on getting up and running with your first
 You'll need to install the following pre-requisites in order to build SAFE applications
 
 * The [.NET Core SDK 3.0](https://dotnet.microsoft.com/download/dotnet-core/3.0)
-* [FAKE](https://fake.build/) (>= 5.12) installed as global tool (`dotnet tool install -g fake-cli`)
-* [Paket](https://fsprojects.github.io/Paket) installed as global tool (`dotnet tool install paket --add-source https://www.myget.org/F/paket-netcore-as-tool/api/v3/index.json -g`) (optional\*)
 * [node.js](https://nodejs.org/) (>= 8.0)
 * [yarn](https://yarnpkg.com/) (>= 1.10.1\*\*) or [npm](https://www.npmjs.com/)
 
-\* You don't need Paket if you just want to try out SAFE. However if you need to edit NuGet dependencies you can [read docs](https://fsprojects.github.io/Paket/getting-started.html) on how to get started with Paket. When installed as global tool you can invoke it via `paket` CLI
-
 \*\* Yarn v2 is [not yet supported](https://github.com/SAFE-Stack/SAFE-template/issues/329)
 
 ## Install an F# code editor
@@ -28,7 +24,8 @@ You'll also want an IDE to create F# applications. We recommend one of the follo
 2. Open a command prompt
 3. Enter `dotnet new -i SAFE.Template` to install the [SAFE project template](template-overview.md)
 4. Enter `dotnet new SAFE` to create a new SAFE project
-5. Enter `fake build --target run` to build and run the app
+5. Enter `dotnet tool restore` to install local tools like FAKE.
+6. Enter `dotnet fake build --target run` to build and run the app
 
 Congratulations - after a short delay, you'll be presented with a basic SAFE application running in your browser! The application will by default run in "development mode", which means it automatically watches your project for changes; whenever you save a file in the client project it will refresh the browser **automatically**; if you save a file in the server project it will also restart the server in the background.
 

docs/template-appservice.md

@@ -28,7 +28,7 @@ An ARM template is a declarative JSON file which contains the details of the Azu
 
 Deploying your application through FAKE is relatively simple. Use the following command:
 ```
-fake build --target appservice
+dotnet fake build --target appservice
     -e subscriptionId=<subId>
     -e clientId=<clientId>
     -e tenantId=<tenantId>

docs/template-docker.md

@@ -10,7 +10,7 @@ The SAFE template has the ability to easily create a [Docker](https://www.docker
 ## Testing docker image locally
 
 1. Make sure you have docker installed and created the template with `--deploy docker` option
-1. Run `fake build --target docker`
+1. Run `dotnet fake build --target docker`
 1. Run `docker run -d -it -p 8085:8085 {dockerUser}/{dockerImageName}`
 1. Navigate to `{dockerHost}:8085` url
 
@@ -39,7 +39,7 @@ Create a file called `release.cmd` with the following content and configure your
     @echo off
     cls
 
-    fake build --target Deploy "DockerLoginServer=docker.io" "DockerImageName=****" "DockerUser=****" "DockerPassword=***" %*
+    dotnet fake build --target Deploy "DockerLoginServer=docker.io" "DockerImageName=****" "DockerUser=****" "DockerPassword=***" %*
 
 Don't worry the file is already in `.gitignore` so your password will not be commited.
 

docs/template-fake.md

@@ -4,7 +4,7 @@ Generated FAKE script consist of two primary build targets, used for different p
 
 ## **"Run"** target
 
-Enter `fake build --target run` to build and run the app
+Enter `dotnet fake build --target run` to build and run the app
 
 This target is used for development purposes, and provides a great live-reload experience. It consists of following steps:
 

docs/template-gcp-appengine.md

@@ -8,7 +8,7 @@ If you are already familiar with GCP and have `gcloud` in place, all you need to
 ```
 dotnet new SAFE --deploy gcp-appengine
 gcloud app create
-fake build -t Deploy
+dotnet fake build -t Deploy
 gcloud app browse
 ```
 

docs/template-gcp-kubernetes.md

@@ -6,7 +6,7 @@ If you are familiar with GCP and already have `gcloud` and `kubectl` configured
 
 ```
 dotnet new SAFE --deploy gcp-kubernetes
-fake build -t Deploy
+dotnet fake build -t Deploy
 ```
 
 The quickstart assumes you have a default zone configured, and it will deploy to a cluster named `safe-cluster`. To change the cluster add `-e SAFE_CLUSTER=<kubernetes cluster>` to the `fake` command. To get the exposed IP you need to run the following command:

docs/template-heroku.md

@@ -18,8 +18,8 @@ After installing Heroku CLI and authenticating, the template makes the process o
 
 ```
 dotnet new SAFE --deploy heroku
-fake build -t Configure <optional app:create arguments>
-fake build -t Deploy
+dotnet fake build -t Configure <optional app:create arguments>
+dotnet fake build -t Deploy
 ```
 
 After these steps if everything went right, the project should open on the browser.

docs/template-iis.md

@@ -9,7 +9,7 @@ dotnet new SAFE --deploy iis
 The template will include a custom FAKE build target called `Bundle` to package your application and make it ready for deployment, run this target using:
 
 ```
-fake build --target bundle
+dotnet fake build --target bundle
 ```
 
 When the target finishes running succesfully, you will have a new `deploy` directory with this structure: