From afef9dd71d3ccce79dc424c3bd3fc90f782838e4 Mon Sep 17 00:00:00 2001 From: Dave Gallant Date: Wed, 17 Nov 2021 17:50:30 -0500 Subject: [PATCH] Fix typos and bump hugo to 0.89.4 --- .env | 2 +- .github/workflows/gh-pages.yml | 2 +- content/post/running-k3s-in-lxc-on-proxmox.md | 6 +++--- content/post/why-i-threw-out-my-dotfiles.md | 2 +- 4 files changed, 6 insertions(+), 6 deletions(-) diff --git a/.env b/.env index 0fb1f710..06e51e4a 100644 --- a/.env +++ b/.env @@ -1 +1 @@ -HUGO_VERSION=0.88.0 +HUGO_VERSION=0.89.4 diff --git a/.github/workflows/gh-pages.yml b/.github/workflows/gh-pages.yml index d867545a..7bccce96 100644 --- a/.github/workflows/gh-pages.yml +++ b/.github/workflows/gh-pages.yml @@ -3,7 +3,7 @@ name: github pages on: push: branches: - - main # Set a branch to deploy + - main pull_request: jobs: diff --git a/content/post/running-k3s-in-lxc-on-proxmox.md b/content/post/running-k3s-in-lxc-on-proxmox.md index 31950482..f7a0db08 100644 --- a/content/post/running-k3s-in-lxc-on-proxmox.md +++ b/content/post/running-k3s-in-lxc-on-proxmox.md @@ -34,7 +34,7 @@ sequenceDiagrams: -It has been a while since I've actively used Kubernetes and wanted to explore the evolution of tools such as [Helm](https://helm.sh) and [Tekton](https://tekton.dev). I decided to deploy [K3s](https://k3s.io), since I've had success with deploying it on resource-contrained Raspberry Pis in the past. I thought that this time it'd be convenient to have K3s running in a LXC container on Proxmox. This would allow for easy snapshotting of the entire Kubernetes deployment. LXC containers also provide an efficient way to squeeze as much out of the machine resources as possible. +It has been a while since I've actively used Kubernetes and wanted to explore the evolution of tools such as [Helm](https://helm.sh) and [Tekton](https://tekton.dev). I decided to deploy [K3s](https://k3s.io), since I've had success with deploying it on resource-contrained Raspberry Pis in the past. I thought that this time it'd be convenient to have K3s running in a LXC container on Proxmox. This would allow for easy snapshotting of the entire Kubernetes deployment. LXC containers also provide an efficient way to use a machine's resources. ## What is K3s? @@ -42,7 +42,7 @@ K3s is a Kubernetes distro that advertises itself as a lightweight binary with a ## Configure Proxmox -This [gist](https://gist.github.com/triangletodd/02f595cd4c0dc9aac5f7763ca2264185) contains snippets and discussion on how to deploy K3s in LXC on proxmox. It mentions that `bridge-nf-call-iptables` should be loaded, but I did not understand the benefit of doing this. +This [gist](https://gist.github.com/triangletodd/02f595cd4c0dc9aac5f7763ca2264185) contains snippets and discussion on how to deploy K3s in LXC on Proxmox. It mentions that `bridge-nf-call-iptables` should be loaded, but I did not understand the benefit of doing this. ## Disable swap @@ -122,7 +122,7 @@ If all goes well, you should see a path to the `kubeconfig` generated. I moved t ## Wrapping up -Installing K3s in LXC on proxmox works with a few tweaks to the default configuration. I later followed the Tekton's [Getting Started](https://tekton.dev/docs/getting-started/) guide and was able to deploy it in a few commands. +Installing K3s in LXC on Proxmox works with a few tweaks to the default configuration. I later followed the Tekton's [Getting Started](https://tekton.dev/docs/getting-started/) guide and was able to deploy it in a few commands. ```console diff --git a/content/post/why-i-threw-out-my-dotfiles.md b/content/post/why-i-threw-out-my-dotfiles.md index ecf0d85a..0a9a04b8 100644 --- a/content/post/why-i-threw-out-my-dotfiles.md +++ b/content/post/why-i-threw-out-my-dotfiles.md @@ -42,7 +42,7 @@ Before understanding home-manager, it is worth briefly discussing what nix is. [ For example, I have used nix to install the package [bind](https://search.nixos.org/packages?channel=unstable&show=bind&from=0&size=50&sort=relevance&type=packages&query=bind) which includes `dig`. You can see that it is available on multiple platforms. The absolute path of `dig` can be found by running: ```console -❯ ls -lh $(which dig) +$ ls -lh $(which dig) lrwxr-xr-x 73 root 31 Dec 1969 /run/current-system/sw/bin/dig -> /nix/store/0r4qdyprljd3dki57jn6c6a8dh2rbg9g-bind-9.16.16-dnsutils/bin/dig ```