diff --git a/content/_header.md b/content/_header.md
index d84afa709..e61f28e11 100644
--- a/content/_header.md
+++ b/content/_header.md
@@ -1 +1 @@
-
+
diff --git a/content/contributors/erik-osterman.md b/content/contributors/erik-osterman.md
index 2629bd9dc..260c9cb1d 100644
--- a/content/contributors/erik-osterman.md
+++ b/content/contributors/erik-osterman.md
@@ -17,4 +17,4 @@ Born and raised in Southern California, Erik is a 2002 graduate of UCLA, receivi
|Blog|https://osterman.com/|
-
+
diff --git a/content/development/github/feature-branches.md b/content/development/github/feature-branches.md
index 701613d28..66d658726 100644
--- a/content/development/github/feature-branches.md
+++ b/content/development/github/feature-branches.md
@@ -21,21 +21,21 @@ The next thing that needs to happen is that the `master` branch is treated as th
Once a feature is considered ready, the developer submits a Pull Request (or PR) and assigns it to a Subject Matter Expert (SME) or peer for review.
-On the surface, this is what a well-formatted Pull Request looks like:  A _Pull Request_ allows many things to happen:
+On the surface, this is what a well-formatted Pull Request looks like:  A _Pull Request_ allows many things to happen:
-- **Title**: A "human readable" title that represents the feature! 
+- **Title**: A "human readable" title that represents the feature! 
- **Description**: A long description that details **_What_** was changed, **_Why_** it was deemed necessary, and any other **_References_** that might be useful (E.g. Jira ticket)
- **Comments**: let anyone provide arbitrary feedback viewable by everyone.
- **Diffs**: show what changed between this feature and the current master branch
-- **Formal Code Review Process:** let multiple people contribute to the code review process by submitting comments on a line-by-line basis. Having these code reviews formally documented serves as an excellent teaching tool. Over time, the reviews become faster and faster as developers learn what is expected. 
+- **Formal Code Review Process:** let multiple people contribute to the code review process by submitting comments on a line-by-line basis. Having these code reviews formally documented serves as an excellent teaching tool. Over time, the reviews become faster and faster as developers learn what is expected. 
-- **Merging**: Once the PR is approved, the developer can squash and merge their code into the master branch. Squashing allows the master branch to have a very clean commit history where every commit corresponds to a PR. 
-- **Clean Commit History**: means that every change to the master branch is documented and justified. No one is sneaking in changes. 
-- **History of Features** and when they were added 
-- **Reverting**: If a feature needs to be removed, with the click of a single button it can be removed from the `master` branch 
+- **Merging**: Once the PR is approved, the developer can squash and merge their code into the master branch. Squashing allows the master branch to have a very clean commit history where every commit corresponds to a PR. 
+- **Clean Commit History**: means that every change to the master branch is documented and justified. No one is sneaking in changes. 
+- **History of Features** and when they were added 
+- **Reverting**: If a feature needs to be removed, with the click of a single button it can be removed from the `master` branch 
# Technical Details
diff --git a/content/development/markdown/_index.md b/content/development/markdown/_index.md
index e6c8dbf77..519378aea 100644
--- a/content/development/markdown/_index.md
+++ b/content/development/markdown/_index.md
@@ -3,7 +3,7 @@ title: Markdown
excerpt: ''
---
- Markdown is a simple way to format plain text that looks great on any device without using any HTML or CSS. It doesn't permit do anything fancy like changing fonts, color, or typeface -- just the bare essentials by using keyboard symbols you already know.
+ Markdown is a simple way to format plain text that looks great on any device without using any HTML or CSS. It doesn't permit do anything fancy like changing fonts, color, or typeface -- just the bare essentials by using keyboard symbols you already know.
# Standard Formatting
diff --git a/content/development/markdown/markdown-best-practices.md b/content/development/markdown/markdown-best-practices.md
index 4438ac13d..83d0a2f0a 100644
--- a/content/development/markdown/markdown-best-practices.md
+++ b/content/development/markdown/markdown-best-practices.md
@@ -3,7 +3,7 @@ title: Markdown Best Practices
excerpt: ''
---
-
+
Using Markdown is essential for clear communication on mediums such as GitHub, Slack or just plain text. Here are some of our recommendations on when to use certain conventions.
@@ -45,9 +45,9 @@ Here's an example:
* Use `value` for all values
````
-Which will render to something like this: 
+Which will render to something like this: 
-
+
# Feature List Formatting
diff --git a/content/development/semantic-versioning.md b/content/development/semantic-versioning.md
index 9bc64611f..c82e3867c 100644
--- a/content/development/semantic-versioning.md
+++ b/content/development/semantic-versioning.md
@@ -5,7 +5,7 @@ excerpt: ''
We practice [Semantic Versioning](https://semver.org/) for all projects (e.g. GitHub Tags/Releases, Helm Charts, Terraform Modules, Docker Images).
-](/images/aa35c54-semver.png)Image credit: [Gopher Academy](https://blog.gopheracademy.com/advent-2015/semver/)
+](/assets/aa35c54-semver.png)Image credit: [Gopher Academy](https://blog.gopheracademy.com/advent-2015/semver/)
# Semantics
diff --git a/content/devops-methodology/_index.md b/content/devops-methodology/_index.md
index db6deb377..9f982b1db 100644
--- a/content/devops-methodology/_index.md
+++ b/content/devops-methodology/_index.md
@@ -41,4 +41,4 @@ This is our methodology.
# Tips & Tricks
* [Docker Tips & Tricks](doc:tips-tricks)
* [Terraform Tips & Tricks](doc:terraform-tips-tricks)
-* [Fancy Shell Prompts](doc:fancy-prompts)
\ No newline at end of file
+* [Fancy Shell Prompts](doc:fancy-prompts)
diff --git a/content/devops-methodology/root-cause-analysis-postmortem/postmortem-example.md b/content/devops-methodology/root-cause-analysis-postmortem/postmortem-example.md
index cc9e62128..e05e0e063 100644
--- a/content/devops-methodology/root-cause-analysis-postmortem/postmortem-example.md
+++ b/content/devops-methodology/root-cause-analysis-postmortem/postmortem-example.md
@@ -73,8 +73,8 @@ The site experienced the classic cascading failure that affected all components
## Unexplained problems
-- During the rollout, API keys for the `amazon-associates-link-builder` plugin got cleared 
-- During the rollout, TablePress options got cleared 
+- During the rollout, API keys for the `amazon-associates-link-builder` plugin got cleared 
+- During the rollout, TablePress options got cleared 
## Remediations
@@ -117,17 +117,17 @@ Prior to rollout, all 3 production instances indicated high memory pressure (90%
### Pingom
-
+
-
+
-
+
### Elastic Beanstalk
-ElasticBeanstalk saw a massive increase in requests which manifested as a Denial of Service Attack. This was triggered probably by mod_pagespeed generating pages for webp assets which could not be served by upgraded servers. Varnish does not cache 404s. 
+ElasticBeanstalk saw a massive increase in requests which manifested as a Denial of Service Attack. This was triggered probably by mod_pagespeed generating pages for webp assets which could not be served by upgraded servers. Varnish does not cache 404s. 
-
+
### RDS
@@ -135,23 +135,23 @@ There were no deadlocks. There was no increase in IOPS (r/w)
#### CPU Utilization spiked.
-
+
#### Connections peaked and maxed out.
-
+
#### Selects went through the roof.
-
+
#### CPU credits were not exhausted, so we had excess capacity
-
+
#### Commits / Writes went through the roof
-
+
## Related Post Mortems
diff --git a/content/devops-methodology/software-lifecycle/_index.md b/content/devops-methodology/software-lifecycle/_index.md
index 170fc584d..2340a4c58 100644
--- a/content/devops-methodology/software-lifecycle/_index.md
+++ b/content/devops-methodology/software-lifecycle/_index.md
@@ -3,7 +3,7 @@ title: Software Lifecycle
excerpt: ''
---
-Conceptual process loop is 8 segment wheel. Left half of it is about software development, right half - software execution. Process Loop Each step have legend who involved in work on that step and what tools are used General Process Loop During development we have to develop, config and execute different types of software. Depends of purpose, the process loop for that types can use different tools, involve different kind of engineers and even can skip some loop steps.
+Conceptual process loop is 8 segment wheel. Left half of it is about software development, right half - software execution. Process Loop Each step have legend who involved in work on that step and what tools are used General Process Loop During development we have to develop, config and execute different types of software. Depends of purpose, the process loop for that types can use different tools, involve different kind of engineers and even can skip some loop steps.
- [Language Libraries & Frameworks](doc:library)
- [Deployable Applications](doc:deployable-application)
diff --git a/content/devops-methodology/software-lifecycle/backing-services.md b/content/devops-methodology/software-lifecycle/backing-services.md
index 9637ad6b3..14c2bec61 100644
--- a/content/devops-methodology/software-lifecycle/backing-services.md
+++ b/content/devops-methodology/software-lifecycle/backing-services.md
@@ -15,4 +15,4 @@ This is a hybrid of two types: `Infrastructure as a Code` and `Deployable backin
`Backing Services` usually extends the functionality of kubernetes or provide some services for CI/CD and development (example: artifact storage / chartmuseum / external dns / tls certbot )
-`Backing Services` stored in the same repo with `Infrastructure as a Code` software. So `Backing Services` does not have independent build, test and release steps. On deploy step `Backing Services` deploys independently from umbrella `Infrastructure as a Code` app. Backing Services Process loop
+`Backing Services` stored in the same repo with `Infrastructure as a Code` software. So `Backing Services` does not have independent build, test and release steps. On deploy step `Backing Services` deploys independently from umbrella `Infrastructure as a Code` app. Backing Services Process loop
diff --git a/content/devops-methodology/software-lifecycle/deployable-applications.md b/content/devops-methodology/software-lifecycle/deployable-applications.md
index cb81c92f8..b83e6ab5c 100644
--- a/content/devops-methodology/software-lifecycle/deployable-applications.md
+++ b/content/devops-methodology/software-lifecycle/deployable-applications.md
@@ -6,4 +6,4 @@ excerpt: ''
*Deployable application* - is the software that can be deployed and operated independently. All required dependencies bundled into artifacts.
-This type of software has the whole process loop and we can specify some tools that are standard for all of our projects. Deployable Applications Process Loop
+This type of software has the whole process loop and we can specify some tools that are standard for all of our projects. Deployable Applications Process Loop
diff --git a/content/devops-methodology/software-lifecycle/infrastructure-as-code.md b/content/devops-methodology/software-lifecycle/infrastructure-as-code.md
index 1f03c0975..dbf3f4075 100644
--- a/content/devops-methodology/software-lifecycle/infrastructure-as-code.md
+++ b/content/devops-methodology/software-lifecycle/infrastructure-as-code.md
@@ -6,4 +6,4 @@ excerpt: ''
_Infrastructure as Code_ - is software that configures and operates basic infrastructure - servers, networking, kubernetes platform. Because this code manage very basic layer of system, it is applied manually by DevOps Engineer. _Infrastructure as Code_ - does not have the "operate" step, it modify infrastructure and then this infrastructure operates on cloud independently. Monitoring step use the common monitoring and alerting tools to monitor cloud infrastructure and notify about incidents.
-
+
diff --git a/content/devops-methodology/software-lifecycle/language-libraries-frameworks.md b/content/devops-methodology/software-lifecycle/language-libraries-frameworks.md
index 4f49d764e..a8b44fb0c 100644
--- a/content/devops-methodology/software-lifecycle/language-libraries-frameworks.md
+++ b/content/devops-methodology/software-lifecycle/language-libraries-frameworks.md
@@ -7,4 +7,4 @@ _Library_ - is the software that can be run only as a part of some other softwar
Examples are npm packages, ruby gems, python modules, etc. Ultimately, these libraries are typically bundled as part of the Docker image along with other software.
-It does not have **deploy** step because they are included as dependencies by other software. Because of that it also does not have the **operate** and **monitoring** steps Library Process Loop
+It does not have **deploy** step because they are included as dependencies by other software. Because of that it also does not have the **operate** and **monitoring** steps Library Process Loop
diff --git a/content/geodesic/_index.md b/content/geodesic/_index.md
index 09b8d014e..660c002ff 100644
--- a/content/geodesic/_index.md
+++ b/content/geodesic/_index.md
@@ -6,7 +6,7 @@ excerpt: >-
homepage: true
---
-
+
|
------------ | ----------------------------------------------------------------------------------------------------------------------------
diff --git a/content/geodesic/geodesic-module/use/with-kops.md b/content/geodesic/geodesic-module/use/with-kops.md
index f40ba0a72..67953afc9 100644
--- a/content/geodesic/geodesic-module/use/with-kops.md
+++ b/content/geodesic/geodesic-module/use/with-kops.md
@@ -43,10 +43,10 @@ terraform plan
terraform apply
```
-
+
The public and private SSH keys are created and stored automatically in the encrypted S3 bucket.
-
+
From the Terraform outputs, copy the `zone_name` and `bucket_name` into the ENV vars `CLUSTER_NAME` and `KOPS_STATE_STORE` in the `Dockerfile`.
# Build Manifest
@@ -93,7 +93,7 @@ You will find the rendered `kops` manifest file `/conf/kops/manifest.yaml`.
# Launch Cluster
Run `kops create -f manifest.yaml` to create the cluster (this will just create the cluster state and store it in the S3 bucket, but not the AWS resources for the cluster).
-
+
Run the following to add the SSH public key to the cluster.
```
kops create secret sshpublickey admin -i /secrets/tf/ssh/joany-staging-kops-us-west-2.pub \
@@ -105,7 +105,7 @@ Run the following to provision the AWS resources for the cluster.
kops update cluster --name us-west-2.staging.joany.net --yes
```
-
+
All done. The `kops` cluster is now up and running.
diff --git a/content/geodesic/geodesic-module/use/with-terraform.md b/content/geodesic/geodesic-module/use/with-terraform.md
index b1d08c97d..dc5b97001 100644
--- a/content/geodesic/geodesic-module/use/with-terraform.md
+++ b/content/geodesic/geodesic-module/use/with-terraform.md
@@ -360,7 +360,7 @@ terraform plan
terraform apply
```
-
+
## Example: Provision Backing Services with Terraform
Change directory to the required resources folder
@@ -375,7 +375,7 @@ terraform plan
terraform apply
```
-
+
Repeat for all other projects in the solution (`dns`, `acm`, etc.).
# Build and Release geodesic shell
diff --git a/content/helm-charts/_index.md b/content/helm-charts/_index.md
index ee6ff6968..f96f12fa4 100644
--- a/content/helm-charts/_index.md
+++ b/content/helm-charts/_index.md
@@ -1,4 +1,4 @@
---
title: "Helm Charts"
excerpt: ""
----
\ No newline at end of file
+---
diff --git a/content/helm-charts/supported-charts/external-dns.md b/content/helm-charts/supported-charts/external-dns.md
index 0f81540cd..cfac9c5b1 100644
--- a/content/helm-charts/supported-charts/external-dns.md
+++ b/content/helm-charts/supported-charts/external-dns.md
@@ -3,7 +3,7 @@ title: "external-dns"
excerpt: "Configure external DNS servers (AWS Route53, Google CloudDNS and others) for Kubernetes Ingresses and Services"
draft: true
---
-
+
# FAQ
diff --git a/content/kubernetes/kubernetes-resource-management.md b/content/kubernetes/kubernetes-resource-management.md
index 2d3e12773..3b63004fd 100644
--- a/content/kubernetes/kubernetes-resource-management.md
+++ b/content/kubernetes/kubernetes-resource-management.md
@@ -25,21 +25,21 @@ some-pod 0/1 OOMKilled 1 24s
By inspecting a "Node" in the kubernetes dashboard, it's really easy to tell if a cluster is oversubscribed. In the example below, we can see that pods have requested 54% of available CPU, but the hard limit has been set to 100% of available CPU. This means, that nothing else should be scheduled do this node as 100% of total available capacity has been allocated.
In terms of memory, we see that all pods of a total memory limit of 4.3GB, which is 113% of available resources. This means the cluster is overcommitted in terms of the maximum permitted amount of memory. In terms of actually requested memory, we're still under the threshold.
-
+
## How can we tell if we have enough CPU/Memory Allocated?
Navigate to the kubernetes dashboard. Click the "Cluster" menu option on the left (it's also the default view). At the top, it will show how much CPU and Memory is being consumed versus total available.
In the cluster below, you can see CPU is not constrained, but available memory is very low.
-
+
## What's the best way to view resources consumed by a namespace?
Navigate to the kubernetes dashboard. Click the "Overview" menu option on the left and then filter by the namespace. By default, the "default" namespace is selected. Generally, we don't use this namespace.
If everything is running smoothly, you should see "Deployments", "Pods" and "ReplicaSets" all at 100%, which means there are no failures.
-
+
Note, you can also select "All Namespaces" to view aggregate information for the cluster.
-
+
# How can we set resource requests & limits?
@@ -51,4 +51,4 @@ It's possible to restrict the total resources available to a namespace.
## Deployment / Pod Level
* Who is responsible for this?
* How do you do it? Go to helmfile which is capable of overriding the limits. Redeploy? Relationship to codefresh
-* We need docs on process for using `helmfile` (e.g. `helmfile sync`)
\ No newline at end of file
+* We need docs on process for using `helmfile` (e.g. `helmfile sync`)
diff --git a/content/learn-by-example/root-module/_index.md b/content/learn-by-example/root-module/_index.md
index 4a4ff6dfa..7abac97c5 100644
--- a/content/learn-by-example/root-module/_index.md
+++ b/content/learn-by-example/root-module/_index.md
@@ -8,4 +8,4 @@ weight: 1
* Configure Terraform Remote State
* Establish DNS Zones
* Provision sub accounts
-* Setup IAM Credentials to access sub accounts
\ No newline at end of file
+* Setup IAM Credentials to access sub accounts
diff --git a/content/local-development-environments/docker-compose.md b/content/local-development-environments/docker-compose.md
index 21c8b7ae6..9fdbf677e 100644
--- a/content/local-development-environments/docker-compose.md
+++ b/content/local-development-environments/docker-compose.md
@@ -2,7 +2,7 @@
title: "Docker Compose"
excerpt: ""
---
-
+
This document compiles “lessons learned” and advice for working with Docker Compose.
@@ -24,4 +24,4 @@ This document compiles “lessons learned” and advice for working with Docker
* No native way in `docker-compose` YAML to run bootstrapping scripts (e.g. init DB); recommend sidekick containers
* No way to enforce startup *delays* between containers
-* `restart: always` only works when the command exits non-zero
\ No newline at end of file
+* `restart: always` only works when the command exits non-zero
diff --git a/content/local-development-environments/dockerfile/_index.md b/content/local-development-environments/dockerfile/_index.md
index 8dd78127e..80afa542c 100644
--- a/content/local-development-environments/dockerfile/_index.md
+++ b/content/local-development-environments/dockerfile/_index.md
@@ -25,4 +25,4 @@ If you are not comfortable writing shell scripts, then this is a great time to l
# Lives alongside the application code
* When application requirements change, the developer can ensure those are captured; no more “we forgot to upgrade `libssl` in production, so that's why the application crashed”
-* CI/CD compatibility
\ No newline at end of file
+* CI/CD compatibility
diff --git a/content/local-development-environments/fancy-shell-prompts.md b/content/local-development-environments/fancy-shell-prompts.md
index 89c6d5571..0ac65719b 100644
--- a/content/local-development-environments/fancy-shell-prompts.md
+++ b/content/local-development-environments/fancy-shell-prompts.md
@@ -8,7 +8,7 @@ Fancy shell prompts are not just pretty, they're also incredibly practical. With
This is how to get a fancy shell prompt like the one below for the `bash` shell.
-
+
## Install powerline
diff --git a/content/local-development-environments/makefile/_index.md b/content/local-development-environments/makefile/_index.md
index c05d2fcae..6e0f9dba6 100644
--- a/content/local-development-environments/makefile/_index.md
+++ b/content/local-development-environments/makefile/_index.md
@@ -7,7 +7,7 @@ excerpt: ""
The `make` command has been around for decades. Predominantly, it was used to build complex projects in C & C++, but it's seen a resurgence in the ops world for automating routine tasks and orchestration of infrastructure-as-code. In the 12-factor pattern, these are your “admin tasks”.
-
+
# Understanding Makefiles
Because `make` is a very simple language, there's not very much you need to learn to get started. Some things, however, might seem unintuitive when approaching it from the perspective of other languages. Namely, `make` is really a template engine that renders “stubs” and then executes those stubs in a shell. Environment variables can be considered as the arguments to those targets.
@@ -275,4 +275,4 @@ To correct this, we could instead write:
foobar:
@export MONTH=February; \
echo $${MONTH}
-```
\ No newline at end of file
+```
diff --git a/content/local-development-environments/makefile/makefile-examples.md b/content/local-development-environments/makefile/makefile-examples.md
index bb4e3ff18..857686216 100644
--- a/content/local-development-environments/makefile/makefile-examples.md
+++ b/content/local-development-environments/makefile/makefile-examples.md
@@ -6,7 +6,7 @@ excerpt: ""
# Help Target
Our standard `help` target. This will automatically generate well-formatted output for any target that has a `##` comment preceding it.
-
+
Simply add this to your `Makefile` and you'll get this functionality.
```
diff --git a/content/local-development-environments/minikube.md b/content/local-development-environments/minikube.md
index 7a9c361a9..56ba9755c 100644
--- a/content/local-development-environments/minikube.md
+++ b/content/local-development-environments/minikube.md
@@ -2,7 +2,7 @@
title: "Minikube"
excerpt: ""
---
-
+
# Setting Up “minikube" on OSX
Just run...
diff --git a/content/local-development-environments/quickstart.md b/content/local-development-environments/quickstart.md
index f55c3cdeb..d0d8fc39d 100644
--- a/content/local-development-environments/quickstart.md
+++ b/content/local-development-environments/quickstart.md
@@ -13,7 +13,7 @@ The "Developer Tools" package is needed for tools like `make` and `git` used thr
xcode-select --install
```
-
+
## Install Homebrew
@@ -31,9 +31,9 @@ Docker for Mac is a Docker Community Edition (CE) version which is completely FR
Visit the [Docker for Mac](https://docs.docker.com/docker-for-mac/install/) site or just go ahead and directly download the [`Docker.dmg`](https://download.docker.com/mac/stable/Docker.dmg)
--  After installing, you'll now see a new docker icon in your task bar.
+-  After installing, you'll now see a new docker icon in your task bar.
- **IMPORTANT:** Docker for Mac requires OS X El Capitan 10.11 or newer macOS release running on a 2010 or newer Mac, with Intel's hardware support for MMU virtualization.
+ **IMPORTANT:** Docker for Mac requires OS X El Capitan 10.11 or newer macOS release running on a 2010 or newer Mac, with Intel's hardware support for MMU virtualization.
## Configure AWS Vault
diff --git a/content/local-development-environments/vagrant.md b/content/local-development-environments/vagrant.md
index b51e152e0..f1cad034e 100644
--- a/content/local-development-environments/vagrant.md
+++ b/content/local-development-environments/vagrant.md
@@ -2,7 +2,7 @@
title: "Vagrant"
excerpt: ""
---
-
+
# Background
Vagrant by HashiCorp is responsbile for setting up development environments under VirtualBox. Vagrant handles all configuration management and makes it easy to share development environments by developers.
diff --git a/content/monitoring-and-alerting/_index.md b/content/monitoring-and-alerting/_index.md
index 8e8383b85..79acc8ae3 100644
--- a/content/monitoring-and-alerting/_index.md
+++ b/content/monitoring-and-alerting/_index.md
@@ -1,4 +1,4 @@
---
title: "Monitoring - Alerting"
excerpt: ""
----
\ No newline at end of file
+---
diff --git a/content/popchest/staging-cluster-map/_index.md b/content/popchest/staging-cluster-map/_index.md
index 03f84b74a..3b383da6b 100644
--- a/content/popchest/staging-cluster-map/_index.md
+++ b/content/popchest/staging-cluster-map/_index.md
@@ -5,7 +5,7 @@ excerpt: ''
Staging - is kubernetes cluster running on top of AWS. Functionality of cluster extended with Kubernetes backing services.
-
+
- Grey - Kubernetes & AWS is [Infrastructure as a Code](doc:infrastructure-as-a-code)
- Blue - Kubernetes Backing Services - are [Backing Services](doc:scafflod) for extending k8s functionality
diff --git a/content/project-management/_index.md b/content/project-management/_index.md
index 567e5d818..13e83350b 100644
--- a/content/project-management/_index.md
+++ b/content/project-management/_index.md
@@ -1,4 +1,4 @@
---
title: "Project Management"
excerpt: ""
----
\ No newline at end of file
+---
diff --git a/content/project-management/gost-framework.md b/content/project-management/gost-framework.md
index 02a420f03..ba45a391e 100644
--- a/content/project-management/gost-framework.md
+++ b/content/project-management/gost-framework.md
@@ -2,7 +2,7 @@
title: "GOST Framework"
excerpt: ""
---
-
+
diff --git a/content/project-management/managers-vs-makers.md b/content/project-management/managers-vs-makers.md
index 58bb5aa04..e5e1b8553 100644
--- a/content/project-management/managers-vs-makers.md
+++ b/content/project-management/managers-vs-makers.md
@@ -2,7 +2,7 @@
title: "Managers vs Makers"
excerpt: ""
---
-
+
# TL;DR
Developers (Makers) and Managers work differently.
@@ -12,4 +12,4 @@ Developers (Makers) and Managers work differently.
Interrupts are costly for developers and therefore the business.
http://www.paulgraham.com/makersschedule.html
- (Paul Graham - YCombinator Founder)
\ No newline at end of file
+ (Paul Graham - YCombinator Founder)
diff --git a/content/release-engineering/_index.md b/content/release-engineering/_index.md
index be9d87bd9..898a13846 100644
--- a/content/release-engineering/_index.md
+++ b/content/release-engineering/_index.md
@@ -1,4 +1,4 @@
---
title: "Release Engineering"
excerpt: ""
----
\ No newline at end of file
+---
diff --git a/content/release-engineering/codefresh-kubernetes-integration.md b/content/release-engineering/codefresh-kubernetes-integration.md
index e8c724a65..f64eba7f1 100644
--- a/content/release-engineering/codefresh-kubernetes-integration.md
+++ b/content/release-engineering/codefresh-kubernetes-integration.md
@@ -10,15 +10,15 @@ Login to CodeFresh and navigate to the [Kubernetes Integration](https://g.codefr
Click "Add Provider" and select the relevant cloud platform.
-
+
Then click "Add Cluster". For `kops` based clusters, select the "Custom Providers" option.
-
+
Next, you'll be presented a form. In [Geodesic Overview](doc:geodesic) we provide a script to make this integration a little bit easier. By running the [codefresh-settings](
https://github.com/cloudposse/geodesic/blob/master/rootfs/usr/local/bin/codefresh-settings) script, it will output all the necessary information you need in order to setup the Kubernetes integration.
Enter the outputs of the script into the form and click save.
-
+
##### :information_source: READ MORE
diff --git a/content/release-engineering/codefresh.md b/content/release-engineering/codefresh.md
index 426cdffaa..847862291 100644
--- a/content/release-engineering/codefresh.md
+++ b/content/release-engineering/codefresh.md
@@ -11,9 +11,9 @@ In order to push/pull images from the CodeFresh docker registry, you'll need to
First, obtain your API key by logging into CodeFresh.
To get it, login into Codefresh and navigate to User Settings in the bottom left corner.
-
+
Then click the "generate" button next to the "Codefresh Registry" section. Make sure you click "copy token to clipboard" from there and save it in your password manager because you cannot retrieve it again.
-
+
Your `CF_USER_NAME` is probably your GitHub username, depending on how you login to CodeFresh. The `CFCR_LOGIN_TOKEN` is the one you just generated.
```
diff --git a/content/terraform-modules/_index.md b/content/terraform-modules/_index.md
index faed49526..33fa3e0ea 100644
--- a/content/terraform-modules/_index.md
+++ b/content/terraform-modules/_index.md
@@ -1,4 +1,4 @@
---
title: "Terraform Modules"
excerpt: ""
----
\ No newline at end of file
+---
diff --git a/content/terraform-modules/terraform-kubernetes-kops-modules/terraform-aws-kops-state-backend.md b/content/terraform-modules/terraform-kubernetes-kops-modules/terraform-aws-kops-state-backend.md
index aa5534f74..d02998bf1 100644
--- a/content/terraform-modules/terraform-kubernetes-kops-modules/terraform-aws-kops-state-backend.md
+++ b/content/terraform-modules/terraform-kubernetes-kops-modules/terraform-aws-kops-state-backend.md
@@ -36,7 +36,7 @@ module "kops" {
}
```
- To check that the created `kops` DNS zone has been tagged correctly, run
+ To check that the created `kops` DNS zone has been tagged correctly, run
```sh
aws route53 list-tags-for-resources --resource-type hostedzone --resource-ids Z58RWQWFVU4HT
diff --git a/content/terraform-modules/terraform-modules-overview.md b/content/terraform-modules/terraform-modules-overview.md
index 666345ca4..94c40d94d 100644
--- a/content/terraform-modules/terraform-modules-overview.md
+++ b/content/terraform-modules/terraform-modules-overview.md
@@ -4,7 +4,7 @@ excerpt: ''
weight: -3
---
-
+
Terraform modules are the best way to encapsulate "business logic" and "Best Practices" for provisioning infrastructure. Terraform modules are used almost like functions in `terraform`; that is, they take inputs (aka `variables`) and produce some `outputs`.
diff --git a/content/terraform-modules/terraform-modules-quick-start.md b/content/terraform-modules/terraform-modules-quick-start.md
index 136cd60ab..ef6eb23f0 100644
--- a/content/terraform-modules/terraform-modules-quick-start.md
+++ b/content/terraform-modules/terraform-modules-quick-start.md
@@ -4,4 +4,4 @@ excerpt: ''
weight: -2
---
-
+
diff --git a/content/terraform-modules/terraform-networking-modules/terraform-aws-vpc-peering.md b/content/terraform-modules/terraform-networking-modules/terraform-aws-vpc-peering.md
index 792e5f8c4..879a6bc24 100644
--- a/content/terraform-modules/terraform-networking-modules/terraform-aws-vpc-peering.md
+++ b/content/terraform-modules/terraform-networking-modules/terraform-aws-vpc-peering.md
@@ -12,7 +12,7 @@ excerpt: Terraform module to create a peering connection between two VPCs
| Release | [](https://github.com/cloudposse/terraform-aws-vpc-peering/releases) |
| Build Status | [](https://travis-ci.org/cloudposse/terraform-aws-vpc-peering) |
-
+
# Usage
diff --git a/content/terraform-modules/terraform-security-modules/terraform-aws-organization-access-role.md b/content/terraform-modules/terraform-security-modules/terraform-aws-organization-access-role.md
index 3890c9098..386d8d5c0 100644
--- a/content/terraform-modules/terraform-security-modules/terraform-aws-organization-access-role.md
+++ b/content/terraform-modules/terraform-security-modules/terraform-aws-organization-access-role.md
@@ -24,7 +24,7 @@ However, member accounts that you invite to join your Organization do not automa
This module creates `OrganizationAccountAccessRole` role in an invited member account.
-AWS recommends using the same name, `OrganizationAccountAccessRole`, for the created role for consistency and ease of remembering. 
+AWS recommends using the same name, `OrganizationAccountAccessRole`, for the created role for consistency and ease of remembering. 
# Usage
diff --git a/content/terraform-modules/terraform-supported-modules/_index.md b/content/terraform-modules/terraform-supported-modules/_index.md
index 307c94996..a88a11c98 100644
--- a/content/terraform-modules/terraform-supported-modules/_index.md
+++ b/content/terraform-modules/terraform-supported-modules/_index.md
@@ -2,7 +2,7 @@
title: "Terraform Supported Modules"
excerpt: ""
---
-
+
Cloud Posse is the largest provider of high quality, fully composable open source Terraform Modules (APACHE2).
diff --git a/content/terraform-modules/terraform-supported-modules/terraform-aws-tfstate-backend.md b/content/terraform-modules/terraform-supported-modules/terraform-aws-tfstate-backend.md
index 6b1f9d5c6..5f4e5f4ea 100644
--- a/content/terraform-modules/terraform-supported-modules/terraform-aws-tfstate-backend.md
+++ b/content/terraform-modules/terraform-supported-modules/terraform-aws-tfstate-backend.md
@@ -64,7 +64,7 @@ Initialize the backend with `terraform init`.
After `terraform apply`, `terraform.tfstate` file will be stored in the bucket, and the DynamoDB table will be used to lock the state to prevent concurrent modifications.
-
+
# Variables
diff --git a/content/terraform/terraform-best-practices.md b/content/terraform/terraform-best-practices.md
index 9a5734efc..a650c818a 100644
--- a/content/terraform/terraform-best-practices.md
+++ b/content/terraform/terraform-best-practices.md
@@ -6,7 +6,7 @@ tags:
- "Best Practices"
- "Terraform"
---
-
+
# Use Git Workflow
diff --git a/content/terraform/terraform-tips-tricks.md b/content/terraform/terraform-tips-tricks.md
index 260f1d936..7f4f4ec4d 100644
--- a/content/terraform/terraform-tips-tricks.md
+++ b/content/terraform/terraform-tips-tricks.md
@@ -2,7 +2,7 @@
title: "Terraform Tips & Tricks"
excerpt: ""
---
-
+
# Use Pre Commit Hooks for Linting
@@ -29,4 +29,4 @@ Then run `pre-commit install` in a given terraform repo to configure the hooks.
After setting this up, every time you commit, the `terraform fmt` command will be run to canonicalize your files and a basic smoke test to validate all configurations without requiring required variables to be set.
Any time your commit affects any `*.tf` files, the validator will ensure well-formed terraform code.
-
+
diff --git a/content/tools/_index.md b/content/tools/_index.md
index 2d1042386..b853c40b0 100644
--- a/content/tools/_index.md
+++ b/content/tools/_index.md
@@ -1,4 +1,4 @@
---
title: "Tools"
excerpt: ""
----
\ No newline at end of file
+---
diff --git a/content/tools/docker/_index.md b/content/tools/docker/_index.md
index 6e9632d5f..069b6ee6b 100644
--- a/content/tools/docker/_index.md
+++ b/content/tools/docker/_index.md
@@ -3,7 +3,7 @@ title: Docker
excerpt: ''
---
-
+
# Install Docker
diff --git a/static/images/034f19f-terraform.png b/static/assets/034f19f-terraform.png
similarity index 100%
rename from static/images/034f19f-terraform.png
rename to static/assets/034f19f-terraform.png
diff --git a/static/images/08bcd99-terraform.png b/static/assets/08bcd99-terraform.png
similarity index 100%
rename from static/images/08bcd99-terraform.png
rename to static/assets/08bcd99-terraform.png
diff --git a/static/images/0effe9c-Process_Loop_-_Library_-_Page_1.png b/static/assets/0effe9c-Process_Loop_-_Library_-_Page_1.png
similarity index 100%
rename from static/images/0effe9c-Process_Loop_-_Library_-_Page_1.png
rename to static/assets/0effe9c-Process_Loop_-_Library_-_Page_1.png
diff --git a/static/images/13f56b6-markdown.png b/static/assets/13f56b6-markdown.png
similarity index 100%
rename from static/images/13f56b6-markdown.png
rename to static/assets/13f56b6-markdown.png
diff --git a/static/images/1f27db8-image_12.png b/static/assets/1f27db8-image_12.png
similarity index 100%
rename from static/images/1f27db8-image_12.png
rename to static/assets/1f27db8-image_12.png
diff --git a/static/images/28887e9-image_8.png b/static/assets/28887e9-image_8.png
similarity index 100%
rename from static/images/28887e9-image_8.png
rename to static/assets/28887e9-image_8.png
diff --git a/static/images/2986185-Current_Staging_cluster_-_Page_1_2.png b/static/assets/2986185-Current_Staging_cluster_-_Page_1_2.png
similarity index 100%
rename from static/images/2986185-Current_Staging_cluster_-_Page_1_2.png
rename to static/assets/2986185-Current_Staging_cluster_-_Page_1_2.png
diff --git a/static/images/2b3e7eb-image_4.png b/static/assets/2b3e7eb-image_4.png
similarity index 100%
rename from static/images/2b3e7eb-image_4.png
rename to static/assets/2b3e7eb-image_4.png
diff --git a/static/images/2c9fd63-Process_Loop_-_Page_1_4.png b/static/assets/2c9fd63-Process_Loop_-_Page_1_4.png
similarity index 100%
rename from static/images/2c9fd63-Process_Loop_-_Page_1_4.png
rename to static/assets/2c9fd63-Process_Loop_-_Page_1_4.png
diff --git a/static/images/2d4fce9-image.png b/static/assets/2d4fce9-image.png
similarity index 100%
rename from static/images/2d4fce9-image.png
rename to static/assets/2d4fce9-image.png
diff --git a/static/images/2e1d7be-image_17.png b/static/assets/2e1d7be-image_17.png
similarity index 100%
rename from static/images/2e1d7be-image_17.png
rename to static/assets/2e1d7be-image_17.png
diff --git a/static/images/334a25e-Screen_Shot_2018-04-17_at_1.50.21_PM.png b/static/assets/334a25e-Screen_Shot_2018-04-17_at_1.50.21_PM.png
similarity index 100%
rename from static/images/334a25e-Screen_Shot_2018-04-17_at_1.50.21_PM.png
rename to static/assets/334a25e-Screen_Shot_2018-04-17_at_1.50.21_PM.png
diff --git a/static/images/3cf5259-Process_Loop_-_Infrastructure_as_a_Code_-_Page_1.png b/static/assets/3cf5259-Process_Loop_-_Infrastructure_as_a_Code_-_Page_1.png
similarity index 100%
rename from static/images/3cf5259-Process_Loop_-_Infrastructure_as_a_Code_-_Page_1.png
rename to static/assets/3cf5259-Process_Loop_-_Infrastructure_as_a_Code_-_Page_1.png
diff --git a/static/images/3feff88-ghost.png b/static/assets/3feff88-ghost.png
similarity index 100%
rename from static/images/3feff88-ghost.png
rename to static/assets/3feff88-ghost.png
diff --git a/static/images/404-not-found.png b/static/assets/404-not-found.png
similarity index 100%
rename from static/images/404-not-found.png
rename to static/assets/404-not-found.png
diff --git a/static/images/4132caf-image_3.png b/static/assets/4132caf-image_3.png
similarity index 100%
rename from static/images/4132caf-image_3.png
rename to static/assets/4132caf-image_3.png
diff --git a/static/images/4204bed-image_11.png b/static/assets/4204bed-image_11.png
similarity index 100%
rename from static/images/4204bed-image_11.png
rename to static/assets/4204bed-image_11.png
diff --git a/static/images/43dfb04-image_19.png b/static/assets/43dfb04-image_19.png
similarity index 100%
rename from static/images/43dfb04-image_19.png
rename to static/assets/43dfb04-image_19.png
diff --git a/static/images/500c4b8-Screen_Shot_2018-04-02_at_7.54.13_PM.png b/static/assets/500c4b8-Screen_Shot_2018-04-02_at_7.54.13_PM.png
similarity index 100%
rename from static/images/500c4b8-Screen_Shot_2018-04-02_at_7.54.13_PM.png
rename to static/assets/500c4b8-Screen_Shot_2018-04-02_at_7.54.13_PM.png
diff --git a/static/images/5a735a9-markdown.png b/static/assets/5a735a9-markdown.png
similarity index 100%
rename from static/images/5a735a9-markdown.png
rename to static/assets/5a735a9-markdown.png
diff --git a/static/images/5c0373a-docker.png b/static/assets/5c0373a-docker.png
similarity index 100%
rename from static/images/5c0373a-docker.png
rename to static/assets/5c0373a-docker.png
diff --git a/static/images/5f2f48b-Screen_Shot_2018-04-16_at_5.17.34_PM.png b/static/assets/5f2f48b-Screen_Shot_2018-04-16_at_5.17.34_PM.png
similarity index 100%
rename from static/images/5f2f48b-Screen_Shot_2018-04-16_at_5.17.34_PM.png
rename to static/assets/5f2f48b-Screen_Shot_2018-04-16_at_5.17.34_PM.png
diff --git a/static/images/60b49ab-Screen_Shot_2018-04-16_at_5.19.13_PM.png b/static/assets/60b49ab-Screen_Shot_2018-04-16_at_5.19.13_PM.png
similarity index 100%
rename from static/images/60b49ab-Screen_Shot_2018-04-16_at_5.19.13_PM.png
rename to static/assets/60b49ab-Screen_Shot_2018-04-16_at_5.19.13_PM.png
diff --git a/static/images/61e5a81-external-dns.png b/static/assets/61e5a81-external-dns.png
similarity index 100%
rename from static/images/61e5a81-external-dns.png
rename to static/assets/61e5a81-external-dns.png
diff --git a/static/images/638d917-geodesic-small.png b/static/assets/638d917-geodesic-small.png
similarity index 100%
rename from static/images/638d917-geodesic-small.png
rename to static/assets/638d917-geodesic-small.png
diff --git a/static/images/66b2538-terraform.png b/static/assets/66b2538-terraform.png
similarity index 100%
rename from static/images/66b2538-terraform.png
rename to static/assets/66b2538-terraform.png
diff --git a/static/images/6e84876-vagrant.png b/static/assets/6e84876-vagrant.png
similarity index 100%
rename from static/images/6e84876-vagrant.png
rename to static/assets/6e84876-vagrant.png
diff --git a/static/images/70b071a-Process_Loop_-_Backing_Services_-_Page_1.png b/static/assets/70b071a-Process_Loop_-_Backing_Services_-_Page_1.png
similarity index 100%
rename from static/images/70b071a-Process_Loop_-_Backing_Services_-_Page_1.png
rename to static/assets/70b071a-Process_Loop_-_Backing_Services_-_Page_1.png
diff --git a/static/images/715f6ff-Process_Loop_-_Deployable_Application_-_Page_1.png b/static/assets/715f6ff-Process_Loop_-_Deployable_Application_-_Page_1.png
similarity index 100%
rename from static/images/715f6ff-Process_Loop_-_Deployable_Application_-_Page_1.png
rename to static/assets/715f6ff-Process_Loop_-_Deployable_Application_-_Page_1.png
diff --git a/static/images/774b11e-terraform.png b/static/assets/774b11e-terraform.png
similarity index 100%
rename from static/images/774b11e-terraform.png
rename to static/assets/774b11e-terraform.png
diff --git a/static/images/7804914-docker-compose.png b/static/assets/7804914-docker-compose.png
similarity index 100%
rename from static/images/7804914-docker-compose.png
rename to static/assets/7804914-docker-compose.png
diff --git a/static/images/7bd6416-image_20.png b/static/assets/7bd6416-image_20.png
similarity index 100%
rename from static/images/7bd6416-image_20.png
rename to static/assets/7bd6416-image_20.png
diff --git a/static/images/7ee92cd-Screen_Shot_2018-04-01_at_12.03.15_AM.png b/static/assets/7ee92cd-Screen_Shot_2018-04-01_at_12.03.15_AM.png
similarity index 100%
rename from static/images/7ee92cd-Screen_Shot_2018-04-01_at_12.03.15_AM.png
rename to static/assets/7ee92cd-Screen_Shot_2018-04-01_at_12.03.15_AM.png
diff --git a/static/images/7f3a5da-Screen_Shot_2018-04-16_at_4.40.57_PM.png b/static/assets/7f3a5da-Screen_Shot_2018-04-16_at_4.40.57_PM.png
similarity index 100%
rename from static/images/7f3a5da-Screen_Shot_2018-04-16_at_4.40.57_PM.png
rename to static/assets/7f3a5da-Screen_Shot_2018-04-16_at_4.40.57_PM.png
diff --git a/static/images/81d14ff-cloudtrail.png b/static/assets/81d14ff-cloudtrail.png
similarity index 100%
rename from static/images/81d14ff-cloudtrail.png
rename to static/assets/81d14ff-cloudtrail.png
diff --git a/static/images/82718b8-vpc-peering.png b/static/assets/82718b8-vpc-peering.png
similarity index 100%
rename from static/images/82718b8-vpc-peering.png
rename to static/assets/82718b8-vpc-peering.png
diff --git a/static/images/840d66e-docker-app-drag.png b/static/assets/840d66e-docker-app-drag.png
similarity index 100%
rename from static/images/840d66e-docker-app-drag.png
rename to static/assets/840d66e-docker-app-drag.png
diff --git a/static/images/85e5ee4-codefresh.png b/static/assets/85e5ee4-codefresh.png
similarity index 100%
rename from static/images/85e5ee4-codefresh.png
rename to static/assets/85e5ee4-codefresh.png
diff --git a/static/images/89c0050-image_13.png b/static/assets/89c0050-image_13.png
similarity index 100%
rename from static/images/89c0050-image_13.png
rename to static/assets/89c0050-image_13.png
diff --git a/static/images/8d8cdf3-image_23.png b/static/assets/8d8cdf3-image_23.png
similarity index 100%
rename from static/images/8d8cdf3-image_23.png
rename to static/assets/8d8cdf3-image_23.png
diff --git a/static/images/8dd848c-vpc_and_subnets.png b/static/assets/8dd848c-vpc_and_subnets.png
similarity index 100%
rename from static/images/8dd848c-vpc_and_subnets.png
rename to static/assets/8dd848c-vpc_and_subnets.png
diff --git a/static/images/8f2e7d3-image_18.png b/static/assets/8f2e7d3-image_18.png
similarity index 100%
rename from static/images/8f2e7d3-image_18.png
rename to static/assets/8f2e7d3-image_18.png
diff --git a/static/images/944178e-kops-update-cluster.png b/static/assets/944178e-kops-update-cluster.png
similarity index 100%
rename from static/images/944178e-kops-update-cluster.png
rename to static/assets/944178e-kops-update-cluster.png
diff --git a/static/images/9d3f441-image_14.png b/static/assets/9d3f441-image_14.png
similarity index 100%
rename from static/images/9d3f441-image_14.png
rename to static/assets/9d3f441-image_14.png
diff --git a/static/images/9d5dc1c-joany-staging-kops-state-ssh-keys.png b/static/assets/9d5dc1c-joany-staging-kops-state-ssh-keys.png
similarity index 100%
rename from static/images/9d5dc1c-joany-staging-kops-state-ssh-keys.png
rename to static/assets/9d5dc1c-joany-staging-kops-state-ssh-keys.png
diff --git a/static/images/9df4fad-image_2.png b/static/assets/9df4fad-image_2.png
similarity index 100%
rename from static/images/9df4fad-image_2.png
rename to static/assets/9df4fad-image_2.png
diff --git a/static/images/a1f105a-terraform.png b/static/assets/a1f105a-terraform.png
similarity index 100%
rename from static/images/a1f105a-terraform.png
rename to static/assets/a1f105a-terraform.png
diff --git a/static/images/a2761a9-image_22.png b/static/assets/a2761a9-image_22.png
similarity index 100%
rename from static/images/a2761a9-image_22.png
rename to static/assets/a2761a9-image_22.png
diff --git a/static/images/a58bf7c-minikube.png b/static/assets/a58bf7c-minikube.png
similarity index 100%
rename from static/images/a58bf7c-minikube.png
rename to static/assets/a58bf7c-minikube.png
diff --git a/static/images/a701e1e-Screen_Shot_2018-04-17_at_1.25.03_PM.png b/static/assets/a701e1e-Screen_Shot_2018-04-17_at_1.25.03_PM.png
similarity index 100%
rename from static/images/a701e1e-Screen_Shot_2018-04-17_at_1.25.03_PM.png
rename to static/assets/a701e1e-Screen_Shot_2018-04-17_at_1.25.03_PM.png
diff --git a/static/images/aa35c54-semver.png b/static/assets/aa35c54-semver.png
similarity index 100%
rename from static/images/aa35c54-semver.png
rename to static/assets/aa35c54-semver.png
diff --git a/static/images/af54926-image_15.png b/static/assets/af54926-image_15.png
similarity index 100%
rename from static/images/af54926-image_15.png
rename to static/assets/af54926-image_15.png
diff --git a/static/images/b251e2e-kops-create.png b/static/assets/b251e2e-kops-create.png
similarity index 100%
rename from static/images/b251e2e-kops-create.png
rename to static/assets/b251e2e-kops-create.png
diff --git a/static/images/b3dae79-image_5.png b/static/assets/b3dae79-image_5.png
similarity index 100%
rename from static/images/b3dae79-image_5.png
rename to static/assets/b3dae79-image_5.png
diff --git a/static/images/b5e88dd-joany-staging-kops-state.png b/static/assets/b5e88dd-joany-staging-kops-state.png
similarity index 100%
rename from static/images/b5e88dd-joany-staging-kops-state.png
rename to static/assets/b5e88dd-joany-staging-kops-state.png
diff --git a/static/images/b7a608c-image_21.png b/static/assets/b7a608c-image_21.png
similarity index 100%
rename from static/images/b7a608c-image_21.png
rename to static/assets/b7a608c-image_21.png
diff --git a/static/images/ba3ae6b-erik_osterman.png b/static/assets/ba3ae6b-erik_osterman.png
similarity index 100%
rename from static/images/ba3ae6b-erik_osterman.png
rename to static/assets/ba3ae6b-erik_osterman.png
diff --git a/static/images/c5273c7-Screen_Shot_2018-04-16_at_5.20.30_PM.png b/static/assets/c5273c7-Screen_Shot_2018-04-16_at_5.20.30_PM.png
similarity index 100%
rename from static/images/c5273c7-Screen_Shot_2018-04-16_at_5.20.30_PM.png
rename to static/assets/c5273c7-Screen_Shot_2018-04-16_at_5.20.30_PM.png
diff --git a/static/images/cb8dbe9-terraform.png b/static/assets/cb8dbe9-terraform.png
similarity index 100%
rename from static/images/cb8dbe9-terraform.png
rename to static/assets/cb8dbe9-terraform.png
diff --git a/static/images/dbe7dad-whale-in-menu-bar.png b/static/assets/dbe7dad-whale-in-menu-bar.png
similarity index 100%
rename from static/images/dbe7dad-whale-in-menu-bar.png
rename to static/assets/dbe7dad-whale-in-menu-bar.png
diff --git a/static/images/dc4dbd3-image_16.png b/static/assets/dc4dbd3-image_16.png
similarity index 100%
rename from static/images/dc4dbd3-image_16.png
rename to static/assets/dc4dbd3-image_16.png
diff --git a/static/images/dd6447a-Screen_Shot_2018-04-02_at_2.46.35_PM.png b/static/assets/dd6447a-Screen_Shot_2018-04-02_at_2.46.35_PM.png
similarity index 100%
rename from static/images/dd6447a-Screen_Shot_2018-04-02_at_2.46.35_PM.png
rename to static/assets/dd6447a-Screen_Shot_2018-04-02_at_2.46.35_PM.png
diff --git a/static/images/e075391-Screen_Shot_2018-04-17_at_1.30.32_PM.png b/static/assets/e075391-Screen_Shot_2018-04-17_at_1.30.32_PM.png
similarity index 100%
rename from static/images/e075391-Screen_Shot_2018-04-17_at_1.30.32_PM.png
rename to static/assets/e075391-Screen_Shot_2018-04-17_at_1.30.32_PM.png
diff --git a/static/images/e24ad8c-OrganizationAccountAccessRole.png b/static/assets/e24ad8c-OrganizationAccountAccessRole.png
similarity index 100%
rename from static/images/e24ad8c-OrganizationAccountAccessRole.png
rename to static/assets/e24ad8c-OrganizationAccountAccessRole.png
diff --git a/static/images/e347aef-kops-state-backend.png b/static/assets/e347aef-kops-state-backend.png
similarity index 100%
rename from static/images/e347aef-kops-state-backend.png
rename to static/assets/e347aef-kops-state-backend.png
diff --git a/static/images/e5ae645-paul_graham.png b/static/assets/e5ae645-paul_graham.png
similarity index 100%
rename from static/images/e5ae645-paul_graham.png
rename to static/assets/e5ae645-paul_graham.png
diff --git a/static/images/e802ae2-image_3.png b/static/assets/e802ae2-image_3.png
similarity index 100%
rename from static/images/e802ae2-image_3.png
rename to static/assets/e802ae2-image_3.png
diff --git a/static/images/e82e21a-image_10.png b/static/assets/e82e21a-image_10.png
similarity index 100%
rename from static/images/e82e21a-image_10.png
rename to static/assets/e82e21a-image_10.png
diff --git a/static/images/edea654-Screen_Shot_2018-04-17_at_1.34.31_PM.png b/static/assets/edea654-Screen_Shot_2018-04-17_at_1.34.31_PM.png
similarity index 100%
rename from static/images/edea654-Screen_Shot_2018-04-17_at_1.34.31_PM.png
rename to static/assets/edea654-Screen_Shot_2018-04-17_at_1.34.31_PM.png
diff --git a/static/images/f111fb9-image_4.png b/static/assets/f111fb9-image_4.png
similarity index 100%
rename from static/images/f111fb9-image_4.png
rename to static/assets/f111fb9-image_4.png
diff --git a/static/images/f5a8966-s3-bucket-with-terraform-state.png b/static/assets/f5a8966-s3-bucket-with-terraform-state.png
similarity index 100%
rename from static/images/f5a8966-s3-bucket-with-terraform-state.png
rename to static/assets/f5a8966-s3-bucket-with-terraform-state.png
diff --git a/static/images/f9a3727-image_7.png b/static/assets/f9a3727-image_7.png
similarity index 100%
rename from static/images/f9a3727-image_7.png
rename to static/assets/f9a3727-image_7.png
diff --git a/static/images/fa5c2bb-Process_Loop_-_general_-_Page_1_1.png b/static/assets/fa5c2bb-Process_Loop_-_general_-_Page_1_1.png
similarity index 100%
rename from static/images/fa5c2bb-Process_Loop_-_general_-_Page_1_1.png
rename to static/assets/fa5c2bb-Process_Loop_-_general_-_Page_1_1.png
diff --git a/static/images/fe450ef-small-TransparentWhite-version-HQ.png b/static/images/logo.png
similarity index 100%
rename from static/images/fe450ef-small-TransparentWhite-version-HQ.png
rename to static/images/logo.png
diff --git a/content/contributors/erik-osterman.md b/content/contributors/erik-osterman.md
index 2629bd9dc..260c9cb1d 100644
--- a/content/contributors/erik-osterman.md
+++ b/content/contributors/erik-osterman.md
@@ -17,4 +17,4 @@ Born and raised in Southern California, Erik is a 2002 graduate of UCLA, receivi
|Blog|https://osterman.com/|
-
+
diff --git a/content/development/github/feature-branches.md b/content/development/github/feature-branches.md
index 701613d28..66d658726 100644
--- a/content/development/github/feature-branches.md
+++ b/content/development/github/feature-branches.md
@@ -21,21 +21,21 @@ The next thing that needs to happen is that the `master` branch is treated as th
Once a feature is considered ready, the developer submits a Pull Request (or PR) and assigns it to a Subject Matter Expert (SME) or peer for review.
-On the surface, this is what a well-formatted Pull Request looks like:  A _Pull Request_ allows many things to happen:
+On the surface, this is what a well-formatted Pull Request looks like:  A _Pull Request_ allows many things to happen:
-- **Title**: A "human readable" title that represents the feature! 
+- **Title**: A "human readable" title that represents the feature! 
- **Description**: A long description that details **_What_** was changed, **_Why_** it was deemed necessary, and any other **_References_** that might be useful (E.g. Jira ticket)
- **Comments**: let anyone provide arbitrary feedback viewable by everyone.
- **Diffs**: show what changed between this feature and the current master branch
-- **Formal Code Review Process:** let multiple people contribute to the code review process by submitting comments on a line-by-line basis. Having these code reviews formally documented serves as an excellent teaching tool. Over time, the reviews become faster and faster as developers learn what is expected. 
+- **Formal Code Review Process:** let multiple people contribute to the code review process by submitting comments on a line-by-line basis. Having these code reviews formally documented serves as an excellent teaching tool. Over time, the reviews become faster and faster as developers learn what is expected. 
-- **Merging**: Once the PR is approved, the developer can squash and merge their code into the master branch. Squashing allows the master branch to have a very clean commit history where every commit corresponds to a PR. 
-- **Clean Commit History**: means that every change to the master branch is documented and justified. No one is sneaking in changes. 
-- **History of Features** and when they were added 
-- **Reverting**: If a feature needs to be removed, with the click of a single button it can be removed from the `master` branch 
+- **Merging**: Once the PR is approved, the developer can squash and merge their code into the master branch. Squashing allows the master branch to have a very clean commit history where every commit corresponds to a PR. 
+- **Clean Commit History**: means that every change to the master branch is documented and justified. No one is sneaking in changes. 
+- **History of Features** and when they were added 
+- **Reverting**: If a feature needs to be removed, with the click of a single button it can be removed from the `master` branch 
# Technical Details
diff --git a/content/development/markdown/_index.md b/content/development/markdown/_index.md
index e6c8dbf77..519378aea 100644
--- a/content/development/markdown/_index.md
+++ b/content/development/markdown/_index.md
@@ -3,7 +3,7 @@ title: Markdown
excerpt: ''
---
- Markdown is a simple way to format plain text that looks great on any device without using any HTML or CSS. It doesn't permit do anything fancy like changing fonts, color, or typeface -- just the bare essentials by using keyboard symbols you already know.
+ Markdown is a simple way to format plain text that looks great on any device without using any HTML or CSS. It doesn't permit do anything fancy like changing fonts, color, or typeface -- just the bare essentials by using keyboard symbols you already know.
# Standard Formatting
diff --git a/content/development/markdown/markdown-best-practices.md b/content/development/markdown/markdown-best-practices.md
index 4438ac13d..83d0a2f0a 100644
--- a/content/development/markdown/markdown-best-practices.md
+++ b/content/development/markdown/markdown-best-practices.md
@@ -3,7 +3,7 @@ title: Markdown Best Practices
excerpt: ''
---
-
+
Using Markdown is essential for clear communication on mediums such as GitHub, Slack or just plain text. Here are some of our recommendations on when to use certain conventions.
@@ -45,9 +45,9 @@ Here's an example:
* Use `value` for all values
````
-Which will render to something like this: 
+Which will render to something like this: 
-
+
# Feature List Formatting
diff --git a/content/development/semantic-versioning.md b/content/development/semantic-versioning.md
index 9bc64611f..c82e3867c 100644
--- a/content/development/semantic-versioning.md
+++ b/content/development/semantic-versioning.md
@@ -5,7 +5,7 @@ excerpt: ''
We practice [Semantic Versioning](https://semver.org/) for all projects (e.g. GitHub Tags/Releases, Helm Charts, Terraform Modules, Docker Images).
-](/images/aa35c54-semver.png)Image credit: [Gopher Academy](https://blog.gopheracademy.com/advent-2015/semver/)
+](/assets/aa35c54-semver.png)Image credit: [Gopher Academy](https://blog.gopheracademy.com/advent-2015/semver/)
# Semantics
diff --git a/content/devops-methodology/_index.md b/content/devops-methodology/_index.md
index db6deb377..9f982b1db 100644
--- a/content/devops-methodology/_index.md
+++ b/content/devops-methodology/_index.md
@@ -41,4 +41,4 @@ This is our methodology.
# Tips & Tricks
* [Docker Tips & Tricks](doc:tips-tricks)
* [Terraform Tips & Tricks](doc:terraform-tips-tricks)
-* [Fancy Shell Prompts](doc:fancy-prompts)
\ No newline at end of file
+* [Fancy Shell Prompts](doc:fancy-prompts)
diff --git a/content/devops-methodology/root-cause-analysis-postmortem/postmortem-example.md b/content/devops-methodology/root-cause-analysis-postmortem/postmortem-example.md
index cc9e62128..e05e0e063 100644
--- a/content/devops-methodology/root-cause-analysis-postmortem/postmortem-example.md
+++ b/content/devops-methodology/root-cause-analysis-postmortem/postmortem-example.md
@@ -73,8 +73,8 @@ The site experienced the classic cascading failure that affected all components
## Unexplained problems
-- During the rollout, API keys for the `amazon-associates-link-builder` plugin got cleared 
-- During the rollout, TablePress options got cleared 
+- During the rollout, API keys for the `amazon-associates-link-builder` plugin got cleared 
+- During the rollout, TablePress options got cleared 
## Remediations
@@ -117,17 +117,17 @@ Prior to rollout, all 3 production instances indicated high memory pressure (90%
### Pingom
-
+
-
+
-
+
### Elastic Beanstalk
-ElasticBeanstalk saw a massive increase in requests which manifested as a Denial of Service Attack. This was triggered probably by mod_pagespeed generating pages for webp assets which could not be served by upgraded servers. Varnish does not cache 404s. 
+ElasticBeanstalk saw a massive increase in requests which manifested as a Denial of Service Attack. This was triggered probably by mod_pagespeed generating pages for webp assets which could not be served by upgraded servers. Varnish does not cache 404s. 
-
+
### RDS
@@ -135,23 +135,23 @@ There were no deadlocks. There was no increase in IOPS (r/w)
#### CPU Utilization spiked.
-
+
#### Connections peaked and maxed out.
-
+
#### Selects went through the roof.
-
+
#### CPU credits were not exhausted, so we had excess capacity
-
+
#### Commits / Writes went through the roof
-
+
## Related Post Mortems
diff --git a/content/devops-methodology/software-lifecycle/_index.md b/content/devops-methodology/software-lifecycle/_index.md
index 170fc584d..2340a4c58 100644
--- a/content/devops-methodology/software-lifecycle/_index.md
+++ b/content/devops-methodology/software-lifecycle/_index.md
@@ -3,7 +3,7 @@ title: Software Lifecycle
excerpt: ''
---
-Conceptual process loop is 8 segment wheel. Left half of it is about software development, right half - software execution. Process Loop Each step have legend who involved in work on that step and what tools are used General Process Loop During development we have to develop, config and execute different types of software. Depends of purpose, the process loop for that types can use different tools, involve different kind of engineers and even can skip some loop steps.
+Conceptual process loop is 8 segment wheel. Left half of it is about software development, right half - software execution. Process Loop Each step have legend who involved in work on that step and what tools are used General Process Loop During development we have to develop, config and execute different types of software. Depends of purpose, the process loop for that types can use different tools, involve different kind of engineers and even can skip some loop steps.
- [Language Libraries & Frameworks](doc:library)
- [Deployable Applications](doc:deployable-application)
diff --git a/content/devops-methodology/software-lifecycle/backing-services.md b/content/devops-methodology/software-lifecycle/backing-services.md
index 9637ad6b3..14c2bec61 100644
--- a/content/devops-methodology/software-lifecycle/backing-services.md
+++ b/content/devops-methodology/software-lifecycle/backing-services.md
@@ -15,4 +15,4 @@ This is a hybrid of two types: `Infrastructure as a Code` and `Deployable backin
`Backing Services` usually extends the functionality of kubernetes or provide some services for CI/CD and development (example: artifact storage / chartmuseum / external dns / tls certbot )
-`Backing Services` stored in the same repo with `Infrastructure as a Code` software. So `Backing Services` does not have independent build, test and release steps. On deploy step `Backing Services` deploys independently from umbrella `Infrastructure as a Code` app. Backing Services Process loop
+`Backing Services` stored in the same repo with `Infrastructure as a Code` software. So `Backing Services` does not have independent build, test and release steps. On deploy step `Backing Services` deploys independently from umbrella `Infrastructure as a Code` app. Backing Services Process loop
diff --git a/content/devops-methodology/software-lifecycle/deployable-applications.md b/content/devops-methodology/software-lifecycle/deployable-applications.md
index cb81c92f8..b83e6ab5c 100644
--- a/content/devops-methodology/software-lifecycle/deployable-applications.md
+++ b/content/devops-methodology/software-lifecycle/deployable-applications.md
@@ -6,4 +6,4 @@ excerpt: ''
*Deployable application* - is the software that can be deployed and operated independently. All required dependencies bundled into artifacts.
-This type of software has the whole process loop and we can specify some tools that are standard for all of our projects. Deployable Applications Process Loop
+This type of software has the whole process loop and we can specify some tools that are standard for all of our projects. Deployable Applications Process Loop
diff --git a/content/devops-methodology/software-lifecycle/infrastructure-as-code.md b/content/devops-methodology/software-lifecycle/infrastructure-as-code.md
index 1f03c0975..dbf3f4075 100644
--- a/content/devops-methodology/software-lifecycle/infrastructure-as-code.md
+++ b/content/devops-methodology/software-lifecycle/infrastructure-as-code.md
@@ -6,4 +6,4 @@ excerpt: ''
_Infrastructure as Code_ - is software that configures and operates basic infrastructure - servers, networking, kubernetes platform. Because this code manage very basic layer of system, it is applied manually by DevOps Engineer. _Infrastructure as Code_ - does not have the "operate" step, it modify infrastructure and then this infrastructure operates on cloud independently. Monitoring step use the common monitoring and alerting tools to monitor cloud infrastructure and notify about incidents.
-
+
diff --git a/content/devops-methodology/software-lifecycle/language-libraries-frameworks.md b/content/devops-methodology/software-lifecycle/language-libraries-frameworks.md
index 4f49d764e..a8b44fb0c 100644
--- a/content/devops-methodology/software-lifecycle/language-libraries-frameworks.md
+++ b/content/devops-methodology/software-lifecycle/language-libraries-frameworks.md
@@ -7,4 +7,4 @@ _Library_ - is the software that can be run only as a part of some other softwar
Examples are npm packages, ruby gems, python modules, etc. Ultimately, these libraries are typically bundled as part of the Docker image along with other software.
-It does not have **deploy** step because they are included as dependencies by other software. Because of that it also does not have the **operate** and **monitoring** steps Library Process Loop
+It does not have **deploy** step because they are included as dependencies by other software. Because of that it also does not have the **operate** and **monitoring** steps Library Process Loop
diff --git a/content/geodesic/_index.md b/content/geodesic/_index.md
index 09b8d014e..660c002ff 100644
--- a/content/geodesic/_index.md
+++ b/content/geodesic/_index.md
@@ -6,7 +6,7 @@ excerpt: >-
homepage: true
---
-
+
|
------------ | ----------------------------------------------------------------------------------------------------------------------------
diff --git a/content/geodesic/geodesic-module/use/with-kops.md b/content/geodesic/geodesic-module/use/with-kops.md
index f40ba0a72..67953afc9 100644
--- a/content/geodesic/geodesic-module/use/with-kops.md
+++ b/content/geodesic/geodesic-module/use/with-kops.md
@@ -43,10 +43,10 @@ terraform plan
terraform apply
```
-
+
The public and private SSH keys are created and stored automatically in the encrypted S3 bucket.
-
+
From the Terraform outputs, copy the `zone_name` and `bucket_name` into the ENV vars `CLUSTER_NAME` and `KOPS_STATE_STORE` in the `Dockerfile`.
# Build Manifest
@@ -93,7 +93,7 @@ You will find the rendered `kops` manifest file `/conf/kops/manifest.yaml`.
# Launch Cluster
Run `kops create -f manifest.yaml` to create the cluster (this will just create the cluster state and store it in the S3 bucket, but not the AWS resources for the cluster).
-
+
Run the following to add the SSH public key to the cluster.
```
kops create secret sshpublickey admin -i /secrets/tf/ssh/joany-staging-kops-us-west-2.pub \
@@ -105,7 +105,7 @@ Run the following to provision the AWS resources for the cluster.
kops update cluster --name us-west-2.staging.joany.net --yes
```
-
+
All done. The `kops` cluster is now up and running.
diff --git a/content/geodesic/geodesic-module/use/with-terraform.md b/content/geodesic/geodesic-module/use/with-terraform.md
index b1d08c97d..dc5b97001 100644
--- a/content/geodesic/geodesic-module/use/with-terraform.md
+++ b/content/geodesic/geodesic-module/use/with-terraform.md
@@ -360,7 +360,7 @@ terraform plan
terraform apply
```
-
+
## Example: Provision Backing Services with Terraform
Change directory to the required resources folder
@@ -375,7 +375,7 @@ terraform plan
terraform apply
```
-
+
Repeat for all other projects in the solution (`dns`, `acm`, etc.).
# Build and Release geodesic shell
diff --git a/content/helm-charts/_index.md b/content/helm-charts/_index.md
index ee6ff6968..f96f12fa4 100644
--- a/content/helm-charts/_index.md
+++ b/content/helm-charts/_index.md
@@ -1,4 +1,4 @@
---
title: "Helm Charts"
excerpt: ""
----
\ No newline at end of file
+---
diff --git a/content/helm-charts/supported-charts/external-dns.md b/content/helm-charts/supported-charts/external-dns.md
index 0f81540cd..cfac9c5b1 100644
--- a/content/helm-charts/supported-charts/external-dns.md
+++ b/content/helm-charts/supported-charts/external-dns.md
@@ -3,7 +3,7 @@ title: "external-dns"
excerpt: "Configure external DNS servers (AWS Route53, Google CloudDNS and others) for Kubernetes Ingresses and Services"
draft: true
---
-
+
# FAQ
diff --git a/content/kubernetes/kubernetes-resource-management.md b/content/kubernetes/kubernetes-resource-management.md
index 2d3e12773..3b63004fd 100644
--- a/content/kubernetes/kubernetes-resource-management.md
+++ b/content/kubernetes/kubernetes-resource-management.md
@@ -25,21 +25,21 @@ some-pod 0/1 OOMKilled 1 24s
By inspecting a "Node" in the kubernetes dashboard, it's really easy to tell if a cluster is oversubscribed. In the example below, we can see that pods have requested 54% of available CPU, but the hard limit has been set to 100% of available CPU. This means, that nothing else should be scheduled do this node as 100% of total available capacity has been allocated.
In terms of memory, we see that all pods of a total memory limit of 4.3GB, which is 113% of available resources. This means the cluster is overcommitted in terms of the maximum permitted amount of memory. In terms of actually requested memory, we're still under the threshold.
-
+
## How can we tell if we have enough CPU/Memory Allocated?
Navigate to the kubernetes dashboard. Click the "Cluster" menu option on the left (it's also the default view). At the top, it will show how much CPU and Memory is being consumed versus total available.
In the cluster below, you can see CPU is not constrained, but available memory is very low.
-
+
## What's the best way to view resources consumed by a namespace?
Navigate to the kubernetes dashboard. Click the "Overview" menu option on the left and then filter by the namespace. By default, the "default" namespace is selected. Generally, we don't use this namespace.
If everything is running smoothly, you should see "Deployments", "Pods" and "ReplicaSets" all at 100%, which means there are no failures.
-
+
Note, you can also select "All Namespaces" to view aggregate information for the cluster.
-
+
# How can we set resource requests & limits?
@@ -51,4 +51,4 @@ It's possible to restrict the total resources available to a namespace.
## Deployment / Pod Level
* Who is responsible for this?
* How do you do it? Go to helmfile which is capable of overriding the limits. Redeploy? Relationship to codefresh
-* We need docs on process for using `helmfile` (e.g. `helmfile sync`)
\ No newline at end of file
+* We need docs on process for using `helmfile` (e.g. `helmfile sync`)
diff --git a/content/learn-by-example/root-module/_index.md b/content/learn-by-example/root-module/_index.md
index 4a4ff6dfa..7abac97c5 100644
--- a/content/learn-by-example/root-module/_index.md
+++ b/content/learn-by-example/root-module/_index.md
@@ -8,4 +8,4 @@ weight: 1
* Configure Terraform Remote State
* Establish DNS Zones
* Provision sub accounts
-* Setup IAM Credentials to access sub accounts
\ No newline at end of file
+* Setup IAM Credentials to access sub accounts
diff --git a/content/local-development-environments/docker-compose.md b/content/local-development-environments/docker-compose.md
index 21c8b7ae6..9fdbf677e 100644
--- a/content/local-development-environments/docker-compose.md
+++ b/content/local-development-environments/docker-compose.md
@@ -2,7 +2,7 @@
title: "Docker Compose"
excerpt: ""
---
-
+
This document compiles “lessons learned” and advice for working with Docker Compose.
@@ -24,4 +24,4 @@ This document compiles “lessons learned” and advice for working with Docker
* No native way in `docker-compose` YAML to run bootstrapping scripts (e.g. init DB); recommend sidekick containers
* No way to enforce startup *delays* between containers
-* `restart: always` only works when the command exits non-zero
\ No newline at end of file
+* `restart: always` only works when the command exits non-zero
diff --git a/content/local-development-environments/dockerfile/_index.md b/content/local-development-environments/dockerfile/_index.md
index 8dd78127e..80afa542c 100644
--- a/content/local-development-environments/dockerfile/_index.md
+++ b/content/local-development-environments/dockerfile/_index.md
@@ -25,4 +25,4 @@ If you are not comfortable writing shell scripts, then this is a great time to l
# Lives alongside the application code
* When application requirements change, the developer can ensure those are captured; no more “we forgot to upgrade `libssl` in production, so that's why the application crashed”
-* CI/CD compatibility
\ No newline at end of file
+* CI/CD compatibility
diff --git a/content/local-development-environments/fancy-shell-prompts.md b/content/local-development-environments/fancy-shell-prompts.md
index 89c6d5571..0ac65719b 100644
--- a/content/local-development-environments/fancy-shell-prompts.md
+++ b/content/local-development-environments/fancy-shell-prompts.md
@@ -8,7 +8,7 @@ Fancy shell prompts are not just pretty, they're also incredibly practical. With
This is how to get a fancy shell prompt like the one below for the `bash` shell.
-
+
## Install powerline
diff --git a/content/local-development-environments/makefile/_index.md b/content/local-development-environments/makefile/_index.md
index c05d2fcae..6e0f9dba6 100644
--- a/content/local-development-environments/makefile/_index.md
+++ b/content/local-development-environments/makefile/_index.md
@@ -7,7 +7,7 @@ excerpt: ""
The `make` command has been around for decades. Predominantly, it was used to build complex projects in C & C++, but it's seen a resurgence in the ops world for automating routine tasks and orchestration of infrastructure-as-code. In the 12-factor pattern, these are your “admin tasks”.
-
+
# Understanding Makefiles
Because `make` is a very simple language, there's not very much you need to learn to get started. Some things, however, might seem unintuitive when approaching it from the perspective of other languages. Namely, `make` is really a template engine that renders “stubs” and then executes those stubs in a shell. Environment variables can be considered as the arguments to those targets.
@@ -275,4 +275,4 @@ To correct this, we could instead write:
foobar:
@export MONTH=February; \
echo $${MONTH}
-```
\ No newline at end of file
+```
diff --git a/content/local-development-environments/makefile/makefile-examples.md b/content/local-development-environments/makefile/makefile-examples.md
index bb4e3ff18..857686216 100644
--- a/content/local-development-environments/makefile/makefile-examples.md
+++ b/content/local-development-environments/makefile/makefile-examples.md
@@ -6,7 +6,7 @@ excerpt: ""
# Help Target
Our standard `help` target. This will automatically generate well-formatted output for any target that has a `##` comment preceding it.
-
+
Simply add this to your `Makefile` and you'll get this functionality.
```
diff --git a/content/local-development-environments/minikube.md b/content/local-development-environments/minikube.md
index 7a9c361a9..56ba9755c 100644
--- a/content/local-development-environments/minikube.md
+++ b/content/local-development-environments/minikube.md
@@ -2,7 +2,7 @@
title: "Minikube"
excerpt: ""
---
-
+
# Setting Up “minikube" on OSX
Just run...
diff --git a/content/local-development-environments/quickstart.md b/content/local-development-environments/quickstart.md
index f55c3cdeb..d0d8fc39d 100644
--- a/content/local-development-environments/quickstart.md
+++ b/content/local-development-environments/quickstart.md
@@ -13,7 +13,7 @@ The "Developer Tools" package is needed for tools like `make` and `git` used thr
xcode-select --install
```
-
+
## Install Homebrew
@@ -31,9 +31,9 @@ Docker for Mac is a Docker Community Edition (CE) version which is completely FR
Visit the [Docker for Mac](https://docs.docker.com/docker-for-mac/install/) site or just go ahead and directly download the [`Docker.dmg`](https://download.docker.com/mac/stable/Docker.dmg)
--