Updates for CLI which uses stack.yaml by default

Signed-off-by: Alex Ellis (OpenFaaS Ltd) <alexellis2@gmail.com>

Author: alexellis

_includes/landing-page/code-examples/javascript.html

@@ -1,5 +1,5 @@
 <div id="Javascript" class="tabcontent">
-<pre><code class="language-shell">$ faas-cli new --lang node18 javascript-fn 
+<pre><code class="language-shell">$ faas-cli new --lang node20 javascript-fn 
 </code></pre>
 <div class="has-text-grey-darker has-text-weight-light">
     handler.js

_includes/products-page/products-cards.html

@@ -86,7 +86,7 @@ <h3 class="title is-size-12 is-size-8-desktop has-text-grey-darker">
                             <subtitle class="is-size-5 mb-3">
                                 Expose services to the Internet from localhost or Kubernetes
                             </subtitle>
-                            <p style="padding-bottom: 20px" class="has-text-weight-light">Expose TCP & HTTP endpoints without rate-limits and complete privacy.</p>
+                            <p style="padding-bottom: 20px" class="has-text-weight-light">Expose TCP & HTTP endpoints through cloud VMs for complete privacy.</p>
                         </div>
                         <div>
                            <a class="button is-primary is-medium" href="https://inlets.dev">inlets.dev</a>

_posts/2018-08-02-read-only-functions.md

@@ -54,7 +54,6 @@ The example code will be available [on GitHub here](https://github.com/alexellis
 
 ```bash
 faas-cli new --lang node access-control --prefix=alexellis2
-mv access-control.yml stack.yml
 echo "alexellis" > ./access-control/valid_user.txt
 ```
 

_posts/2018-08-22-five-cli-tips.md

@@ -41,7 +41,7 @@ Now if you were to run a `build`, `push` or `deploy` you'd carry that step out f
 
 You can simply type in `faas-cli build --filter=filter2` for instance.
 
-Now if you do happen to edit most of your functions most of the time such as with [OpenFaaS Cloud](https://github.com/openfaas/openfaas-cloud/blob/master/stack.yml), then you can use the `--parallel` flag and your images will be built concurrently. If you have 16 functions in one YAML file and use `--parallel=4` they will build in batches of 4 saving time overall. This speed-boosting feature isn't available when working with Docker outside of OpenFaaS.
+Now if you do happen to edit most of your functions most of the time such as with [OpenFaaS Cloud](https://github.com/openfaas/openfaas-cloud/blob/master/stack.yaml), then you can use the `--parallel` flag and your images will be built concurrently. If you have 16 functions in one YAML file and use `--parallel=4` they will build in batches of 4 saving time overall. This speed-boosting feature isn't available when working with Docker outside of OpenFaaS.
 
 You can also split your functions into separate folders, repos or YAML files.
 
@@ -111,7 +111,7 @@ Successfully tagged alexellis2/test1:latest-b6d5661
 
 If we change the tag in the YAML file from `latest` to `0.1` then the image tag would have been: `test1:0.1-b6d5661`. This is useful for CI/CD jobs and is supported by the verbs: `build`, `push`, `deploy` and `up`.
 
-You can also omit the `--yaml/-f` flag if you rename your YAML file to `stack.yml`
+You can also omit the `--yaml/-f` flag if you rename your YAML file to `stack.yaml`
 
 ## Tip 5: Use `faas-cli up` and save on typing
 

_posts/2018-09-06-stateless-microservices.md

@@ -294,7 +294,7 @@ The guestbook code stores its state in a MySQL table which means that it can be
 
 To enable [scaling to zero](https://www.openfaas.com/blog/zero-scale/) simply [follow the documentation](https://docs.openfaas.com/architecture/autoscaling/#zero-scale) to enable the `faas-idler`.
 
-Then add a label to your `stack.yml` file to tell OpenFaaS that your function is eligible for zero-scaling:
+Then add a label to your `stack.yaml` file to tell OpenFaaS that your function is eligible for zero-scaling:
 
 ```yaml
     labels:

_posts/2019-01-24-unified-secrets.md

@@ -34,7 +34,7 @@ environment variables can be used to configure non-confidential data such as fea
 
 * Do manage config with environment variables
 
-You can manage configuration with environment variables by declaring an `environment:` section in your function's `stack.yml` file. Or you can create an external file for your environmental configuration with `environment_file:`.
+You can manage configuration with environment variables by declaring an `environment:` section in your function's `stack.yaml` file. Or you can create an external file for your environmental configuration with `environment_file:`.
 
 Read more about using environment variables for config in the [YAML reference](https://docs.openfaas.com/reference/yaml/#function-environmental-variables).
 

_posts/2019-01-29-multifile-python-functions.md

@@ -49,7 +49,7 @@ The project should now look like
 
 ```txt
 .
-├── stack.yml
+├── stack.yaml
 ├── template
 │   ├── python27-flask
 │   │   ├ ...
@@ -78,7 +78,7 @@ The project should now look like this
 
 ```txt
 .
-├── stack.yml
+├── stack.yaml
 ├── template
 │   ├── ...
 └── wordcount

_posts/2019-02-04-digitalocean-one-click.md

@@ -118,12 +118,6 @@ Function created in folder: hello-digitalocean
 Stack file written: hello-digitalocean.yml
 ```
 
-* Rename `hello-digitalocean.yml` to `stack.yml`:
-
-```sh
-$ mv hello-digitalocean.yml stack.yml
-```
-
 * Edit `hello-digitalocean/handler.py` to add our function's code:
 
 ```python

_posts/2019-02-12-openfaas-on-fargate.md

@@ -59,7 +59,7 @@ scheduled in a `private subnet` that has no access to the Internet
 to manage service registration / de-registration
 * **\[logging\]** we configure each container workload to log to [AWS cloudwatch](https://aws.amazon.com/cloudwatch).
 * **\[secrets\]** managed using [AWS Secrets Manager](https://aws.amazon.com/secrets-manager/) and assigned access to functions
-in the `stack.yml`
+in the `stack.yaml`
 * **\[tls\]** ingress TLS is automatically provisioned using [Certbot](https://certbot.eff.org/) and the
 [Let's Encrypt](https://letsencrypt.org/) certificate authority.
 

_posts/2019-02-14-serverless-single-page-app.md

@@ -231,7 +231,7 @@ Functions:
 
 Other files:
 
-* `stack.yml` - defines the functions and is generated by the `faas-cli`
+* `stack.yaml` - defines the functions and is generated by the `faas-cli`
 * `secrets.yaml` - defines encrypted or "sealed" secrets generated by `faas-cli cloud seal`
 
 The database schema is written in the README.md file at the root.