From 58fa7533b1d3e744a8f56ad1de631e986ee32626 Mon Sep 17 00:00:00 2001 From: Paul Buetow Date: Sun, 10 Dec 2023 07:56:23 +0200 Subject: Update content for md --- gemfeed/2021-04-24-welcome-to-the-geminispace.md | 4 ++-- gemfeed/2022-01-01-bash-golf-part-2.md | 2 ++ 2 files changed, 4 insertions(+), 2 deletions(-) (limited to 'gemfeed') diff --git a/gemfeed/2021-04-24-welcome-to-the-geminispace.md b/gemfeed/2021-04-24-welcome-to-the-geminispace.md index 682d5f47..fc9e43e9 100644 --- a/gemfeed/2021-04-24-welcome-to-the-geminispace.md +++ b/gemfeed/2021-04-24-welcome-to-the-geminispace.md @@ -75,8 +75,8 @@ This site was generated with Gemtexter. You can read more about it here: Check out one of the following links for more information about Gemini. For example, you will find a FAQ that explains why the protocol is named Gemini. Many Gemini capsules are dual-hosted via Gemini and HTTP(S) so that people new to Gemini can sneak peek at the content with a regular web browser. Some people go as far as tri-hosting all their content via HTTP(S), Gemini and Gopher. -[gemini://gemini.circumlunar.space](gemini://gemini.circumlunar.space) -[https://gemini.circumlunar.space](https://gemini.circumlunar.space) +[gemini://geminiprotocol.net/](gemini://geminiprotocol.net/) +[https://geminiprotocol.net/](https://geminiprotocol.net/) Other related posts are: diff --git a/gemfeed/2022-01-01-bash-golf-part-2.md b/gemfeed/2022-01-01-bash-golf-part-2.md index f9792a39..21bd47f9 100644 --- a/gemfeed/2022-01-01-bash-golf-part-2.md +++ b/gemfeed/2022-01-01-bash-golf-part-2.md @@ -47,6 +47,8 @@ Foo Foo ``` +> Update: A reader pointed out, that the redirection should actually go to `/proc/self/fd/1` and not `0`. But apparently, either way works for this particular example. Do you know why? + Other useful redirections are: * Redirect stderr to stdin: "echo foo 2>&1" -- cgit v1.2.3 From 554facb80137bed60ef0f4b4a2606d5c96b33eb0 Mon Sep 17 00:00:00 2001 From: Paul Buetow Date: Sun, 10 Dec 2023 11:38:30 +0200 Subject: Update content for md --- .../2021-05-16-personal-bash-coding-style-guide.md | 1 + ...-05-gemtexter-one-bash-script-to-rule-it-all.md | 1 + gemfeed/2021-11-29-bash-golf-part-1.md | 2 + gemfeed/2022-01-01-bash-golf-part-2.md | 2 + ...s-static-web-photo-albums-with-photoalbum.sh.md | 1 + gemfeed/2023-12-10-bash-golf-part-3.md | 369 +++++++++++++++++++++ .../2023-12-10-bash-golf-part-3/bash-fork-bomb.jpg | Bin 0 -> 209399 bytes gemfeed/index.md | 1 + 8 files changed, 377 insertions(+) create mode 100644 gemfeed/2023-12-10-bash-golf-part-3.md create mode 100644 gemfeed/2023-12-10-bash-golf-part-3/bash-fork-bomb.jpg (limited to 'gemfeed') diff --git a/gemfeed/2021-05-16-personal-bash-coding-style-guide.md b/gemfeed/2021-05-16-personal-bash-coding-style-guide.md index 21cd38f2..8eebbbe0 100644 --- a/gemfeed/2021-05-16-personal-bash-coding-style-guide.md +++ b/gemfeed/2021-05-16-personal-bash-coding-style-guide.md @@ -386,6 +386,7 @@ Other related posts are: [2021-06-05 Gemtexter - One Bash script to rule it all](./2021-06-05-gemtexter-one-bash-script-to-rule-it-all.md) [2021-11-29 Bash Golf Part 1](./2021-11-29-bash-golf-part-1.md) [2022-01-01 Bash Golf Part 2](./2022-01-01-bash-golf-part-2.md) +[2023-12-10 Bash Golf Part 3](./2023-12-10-bash-golf-part-3.md) E-Mail your comments to `paul@nospam.buetow.org` :-) diff --git a/gemfeed/2021-06-05-gemtexter-one-bash-script-to-rule-it-all.md b/gemfeed/2021-06-05-gemtexter-one-bash-script-to-rule-it-all.md index de6a843f..bf69af53 100644 --- a/gemfeed/2021-06-05-gemtexter-one-bash-script-to-rule-it-all.md +++ b/gemfeed/2021-06-05-gemtexter-one-bash-script-to-rule-it-all.md @@ -173,6 +173,7 @@ Other related posts are: [2022-08-27 Gemtexter 1.1.0 - Let's Gemtext again](./2022-08-27-gemtexter-1.1.0-lets-gemtext-again.md) [2023-03-25 Gemtexter 2.0.0 - Let's Gemtext again²](./2023-03-25-gemtexter-2.0.0-lets-gemtext-again-2.md) [2023-07-21 Gemtexter 2.1.0 - Let's Gemtext again³](./2023-07-21-gemtexter-2.1.0-lets-gemtext-again-3.md) +[2023-12-10 Bash Golf Part 3](./2023-12-10-bash-golf-part-3.md) E-Mail your comments to `paul@nospam.buetow.org` :-) diff --git a/gemfeed/2021-11-29-bash-golf-part-1.md b/gemfeed/2021-11-29-bash-golf-part-1.md index 60c4ed08..63ffebb0 100644 --- a/gemfeed/2021-11-29-bash-golf-part-1.md +++ b/gemfeed/2021-11-29-bash-golf-part-1.md @@ -18,6 +18,7 @@ This is the first blog post about my Bash Golf series. This series is about rand [2021-11-29 Bash Golf Part 1 (You are currently reading this)](./2021-11-29-bash-golf-part-1.md) [2022-01-01 Bash Golf Part 2](./2022-01-01-bash-golf-part-2.md) +[2023-12-10 Bash Golf Part 3](./2023-12-10-bash-golf-part-3.md) ## TCP/IP networking @@ -469,6 +470,7 @@ Other related posts are: [2021-06-05 Gemtexter - One Bash script to rule it all](./2021-06-05-gemtexter-one-bash-script-to-rule-it-all.md) [2021-11-29 Bash Golf Part 1 (You are currently reading this)](./2021-11-29-bash-golf-part-1.md) [2022-01-01 Bash Golf Part 2](./2022-01-01-bash-golf-part-2.md) +[2023-12-10 Bash Golf Part 3](./2023-12-10-bash-golf-part-3.md) E-Mail your comments to `paul@nospam.buetow.org` :-) diff --git a/gemfeed/2022-01-01-bash-golf-part-2.md b/gemfeed/2022-01-01-bash-golf-part-2.md index 21bd47f9..88a17126 100644 --- a/gemfeed/2022-01-01-bash-golf-part-2.md +++ b/gemfeed/2022-01-01-bash-golf-part-2.md @@ -18,6 +18,7 @@ This is the second blog post about my Bash Golf series. This series is random Ba [2021-11-29 Bash Golf Part 1](./2021-11-29-bash-golf-part-1.md) [2022-01-01 Bash Golf Part 2 (You are currently reading this)](./2022-01-01-bash-golf-part-2.md) +[2023-12-10 Bash Golf Part 3](./2023-12-10-bash-golf-part-3.md) ## Redirection @@ -488,6 +489,7 @@ Other related posts are: [2021-06-05 Gemtexter - One Bash script to rule it all](./2021-06-05-gemtexter-one-bash-script-to-rule-it-all.md) [2021-11-29 Bash Golf Part 1](./2021-11-29-bash-golf-part-1.md) [2022-01-01 Bash Golf Part 2 (You are currently reading this)](./2022-01-01-bash-golf-part-2.md) +[2023-12-10 Bash Golf Part 3](./2023-12-10-bash-golf-part-3.md) E-Mail your comments to `paul@nospam.buetow.org` :-) diff --git a/gemfeed/2023-10-29-kiss-static-web-photo-albums-with-photoalbum.sh.md b/gemfeed/2023-10-29-kiss-static-web-photo-albums-with-photoalbum.sh.md index 1b3639e7..140c9925 100644 --- a/gemfeed/2023-10-29-kiss-static-web-photo-albums-with-photoalbum.sh.md +++ b/gemfeed/2023-10-29-kiss-static-web-photo-albums-with-photoalbum.sh.md @@ -268,6 +268,7 @@ Other Bash and KISS-related posts are: [2022-01-01 Bash Golf Part 2](./2022-01-01-bash-golf-part-2.md) [2023-06-01 KISS server monitoring with Gogios](./2023-06-01-kiss-server-monitoring-with-gogios.md) [2023-10-29 KISS static web photo albums with `photoalbum.sh` (You are currently reading this)](./2023-10-29-kiss-static-web-photo-albums-with-photoalbum.sh.md) +[2023-12-10 Bash Golf Part 3](./2023-12-10-bash-golf-part-3.md) E-Mail your comments to `paul@nospam.buetow.org` :-) diff --git a/gemfeed/2023-12-10-bash-golf-part-3.md b/gemfeed/2023-12-10-bash-golf-part-3.md new file mode 100644 index 00000000..46cd231f --- /dev/null +++ b/gemfeed/2023-12-10-bash-golf-part-3.md @@ -0,0 +1,369 @@ +# Bash Golf Part 3 + +> Published at 2023-12-10T11:35:54+02:00 + +``` + + '\ '\ '\ . . |>18>> + \ \ \ . ' . | + O>> O>> O>> . 'o | + \ .\. .. .\. .. . | + /\ . /\ . /\ . . | + / / . / / .'. / / .' . | +jgs^^^^^^^`^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^ + Art by Joan Stark, mod. by Paul Buetow +``` + +This is the third blog post about my Bash Golf series. This series is random Bash tips, tricks, and weirdnesses I have encountered over time. + +[2021-11-29 Bash Golf Part 1](./2021-11-29-bash-golf-part-1.md) +[2022-01-01 Bash Golf Part 2](./2022-01-01-bash-golf-part-2.md) +[2023-12-10 Bash Golf Part 3 (You are currently reading this)](./2023-12-10-bash-golf-part-3.md) + +## `FUNCNAME` + +`FUNCNAME` is an array you are looking for a way to dynamically determine the name of the current function (which could be considered the callee in the context of its own execution), you can use the special variable `FUNCNAME`. This is an array variable that contains the names of all shell functions currently in the execution call stack. The element `FUNCNAME[0]` holds the name of the currently executing function, `FUNCNAME[1]` the name of the function that called that, and so on. + +This is particularly useful for logging when you want to include the callee function in the log output. E.g. look at this log helper: + +```bash +#!/usr/bin/env bash + +log () { + local -r level="$1"; shift + local -r message="$1"; shift + local -i pid="$$" + + local -r callee=${FUNCNAME[1]} + local -r stamp=$(date +%Y%m%d-%H%M%S) + + echo "$level|$stamp|$pid|$callee|$message" >&2 +} + +at_home_friday_evening () { + log INFO 'One Peperoni Pizza, please' +} + +at_home_friday_evening +``` + +The output is as follows: + +```bash +❯ ./logexample.sh +INFO|20231210-082732|123002|at_home_friday_evening|One Peperoni Pizza, please +``` + +## `:(){ :|:& };:` + +This one may be widely known already, but I am including it here as I found a cute image illustrating it. But to break `:(){ :|:& };:` down: + +* `:(){ }` is really a declaration of the function `:` +* The `;` is ending the current statement +* The `:` at the end is calling the function `:` +* `:|:&` is the function body + +Let's break down the function body `:|:&`: + +* The first `:` is calling the function recursively +* The `|:` is piping the output to the function `:` again (parallel recursion) +* The `&` lets it run in the background. + +So, it's a fork bomb. If you run it, your computer will run out of resources eventually. (Modern Linux distributions could have reasonable limits configured for your login session, so it won't bring down your whole system anymore unless you run it as `root`!) + +And here is the cute illustration: + +[![Bash fork bomb](./2023-12-10-bash-golf-part-3/bash-fork-bomb.jpg "Bash fork bomb")](./2023-12-10-bash-golf-part-3/bash-fork-bomb.jpg) + +## Inner functions + +Bash defines variables as it is interpreting the code. The same applies to function declarations. Let's consider this code: + +```bash +#!/usr/bin/env bash + +outer() { + inner() { + echo 'Intel inside!' + } + inner +} + +inner +outer +inner +``` + +And let's execute it: + +``` +❯ ./inner.sh +/tmp/inner.sh: line 10: inner: command not found +Intel inside! +Intel inside! +``` + +What happened? The first time `inner` was called, it wasn't defined yet. That only happens after the `outer` run. Note that `inner` will still be globally defined. But functions can be declared multiple times (the last version wins): + +```bash +#!/usr/bin/env bash + +outer1() { + inner() { + echo 'Intel inside!' + } + inner +} + +outer2() { + inner() { + echo 'Wintel inside!' + } + inner +} + +outer1 +inner +outer2 +inner +``` + +And let's run it: + +``` +❯ ./inner2.sh +Intel inside! +Intel inside! +Wintel inside! +Wintel inside! +``` + +## Exporting functions + +Have you ever wondered how to execute a shell function in parallel through `xargs`? The problem is that this won't work: + +```bash +#!/usr/bin/env bash + +some_expensive_operations() { + echo "Doing expensive operations with '$1' from pid $$" +} + +for i in {0..9}; do echo $i; done \ + | xargs -P10 -I{} bash -c 'some_expensive_operations "{}"' +``` + +We try here to run ten parallel processes; each of them should run the `some_expensive_operations` function with a different argument. The arguments are provided to `xargs` through `STDIN` one per line. When executed, we get this: + +``` +❯ ./xargs.sh +bash: line 1: some_expensive_operations: command not found +bash: line 1: some_expensive_operations: command not found +bash: line 1: some_expensive_operations: command not found +bash: line 1: some_expensive_operations: command not found +bash: line 1: some_expensive_operations: command not found +bash: line 1: some_expensive_operations: command not found +bash: line 1: some_expensive_operations: command not found +bash: line 1: some_expensive_operations: command not found +bash: line 1: some_expensive_operations: command not found +bash: line 1: some_expensive_operations: command not found +``` + +There's an easy solution for this. Just export the function! It will then be magically available in any sub-shell! + +```bash +#!/usr/bin/env bash + +some_expensive_operations() { + echo "Doing expensive operations with '$1' from pid $$" +} +export -f some_expensive_operations + +for i in {0..9}; do echo $i; done \ + | xargs -P10 -I{} bash -c 'some_expensive_operations "{}"' +``` + +When we run this now, we get: + +``` +❯ ./xargs.sh +Doing expensive operations with '0' from pid 132831 +Doing expensive operations with '1' from pid 132832 +Doing expensive operations with '2' from pid 132833 +Doing expensive operations with '3' from pid 132834 +Doing expensive operations with '4' from pid 132835 +Doing expensive operations with '5' from pid 132836 +Doing expensive operations with '6' from pid 132837 +Doing expensive operations with '7' from pid 132838 +Doing expensive operations with '8' from pid 132839 +Doing expensive operations with '9' from pid 132840 +``` + +If `some_expensive_function` would call another function, the other function must also be exported. Otherwise, there will be a runtime error again. E.g., this won't work: + +```bash +#!/usr/bin/env bash + +some_other_function() { + echo "$1" +} + +some_expensive_operations() { + some_other_function "Doing expensive operations with '$1' from pid $$" +} +export -f some_expensive_operations + +for i in {0..9}; do echo $i; done \ + | xargs -P10 -I{} bash -c 'some_expensive_operations "{}"' +``` + +... because `some_other_function` isn't exported! You will also need to add an `export -f some_other_function`! + +## Dynamic variables with `local` + +You may know that `local` is how to declare local variables in a function. Most don't know that those variables actually have dynamic scope. Let's consider the following example: + +```bash +#!/usr/bin/env bash + +foo() { + local foo=bar # Declare local/dynamic variable + bar + echo "$foo" +} + +bar() { + echo "$foo" + foo=baz +} + +foo=foo # Declare global variable +foo # Call function foo +echo "$foo" +``` + +Let's pause a minute. What do you think the output would be? + +Let's run it: + +``` +❯ ./dynamic.sh +bar +baz +foo +``` + +What happened? The variable `foo` (declared with `local`) is available in the function it was declared in and in all other functions down the call stack! We can even modify the value of `foo', and the change will be visible up the call stack. It's not a global variable; on the last line, `echo "$foo"` echoes the global variable content. + + +## `if` conditionals + +Consider all variants here more or less equivalent: + +```bash +#!/usr/bin/env bash + +declare -r foo=foo +declare -r bar=bar + +if [ "$foo" = foo ]; then + if [ "$bar" = bar ]; then + echo ok1 + fi +fi + +if [ "$foo" = foo ] && [ "$bar" == bar ]; then + echo ok2a +fi + +[ "$foo" = foo ] && [ "$bar" == bar ] && echo ok2b + +if [[ "$foo" = foo && "$bar" == bar ]]; then + echo ok3a +fi + + [[ "$foo" = foo && "$bar" == bar ]] && echo ok3b + +if test "$foo" = foo && test "$bar" = bar; then + echo ok4a +fi + +test "$foo" = foo && test "$bar" = bar && echo ok4b +``` + +The output we get is: + +``` +❯ ./if.sh +ok1 +ok2a +ok2b +ok3a +ok3b +ok4a +ok4b +``` + +## Multi-line comments + +You all know how to comment. Put a `#` in front of it. You could use multiple single-line comments or abuse heredocs and redirect it to the `:` no-op command to emulate multi-line comments. + +```bash +#!/usr/bin/env bash + +# Single line comment + +# These are two single line +# comments one after another + +: <> $0 +echo bar +``` + +When it is run, it will do: + +``` +❯ ./if.sh +foo +bar +baz +❯ cat if.sh +#!/usr/bin/env bash + +echo foo +echo echo baz >> $0 +echo bar +echo baz +``` + +So what happened? The `echo baz` line was appended to the script while it was still executed! And the interpreter also picked it up! It tells us that Bash evaluates each line as it encounters it. This can lead to nasty side effects when editing the script while it is still being executed! You should always keep this in mind! + + +Other related posts are: + +[2021-05-16 Personal Bash coding style guide](./2021-05-16-personal-bash-coding-style-guide.md) +[2021-06-05 Gemtexter - One Bash script to rule it all](./2021-06-05-gemtexter-one-bash-script-to-rule-it-all.md) +[2021-11-29 Bash Golf Part 1](./2021-11-29-bash-golf-part-1.md) +[2022-01-01 Bash Golf Part 2](./2022-01-01-bash-golf-part-2.md) +[2023-12-10 Bash Golf Part 3 (You are currently reading this)](./2023-12-10-bash-golf-part-3.md) + +E-Mail your comments to `paul@nospam.buetow.org` :-) + +[Back to the main site](../) diff --git a/gemfeed/2023-12-10-bash-golf-part-3/bash-fork-bomb.jpg b/gemfeed/2023-12-10-bash-golf-part-3/bash-fork-bomb.jpg new file mode 100644 index 00000000..6967c03a Binary files /dev/null and b/gemfeed/2023-12-10-bash-golf-part-3/bash-fork-bomb.jpg differ diff --git a/gemfeed/index.md b/gemfeed/index.md index 5290577c..fcf83d14 100644 --- a/gemfeed/index.md +++ b/gemfeed/index.md @@ -2,6 +2,7 @@ ## To be in the .zone! +[2023-12-10 - Bash Golf Part 3](./2023-12-10-bash-golf-part-3.md) [2023-11-11 - 'Mind Management' book notes](./2023-11-11-mind-management-book-notes.md) [2023-10-29 - KISS static web photo albums with `photoalbum.sh`](./2023-10-29-kiss-static-web-photo-albums-with-photoalbum.sh.md) [2023-09-25 - DTail usage examples](./2023-09-25-dtail-usage-examples.md) -- cgit v1.2.3 From 2cce4c76f0b3e792852397b3c52d7b6c5b711877 Mon Sep 17 00:00:00 2001 From: Paul Buetow Date: Sun, 10 Dec 2023 11:46:22 +0200 Subject: Update content for md --- gemfeed/2023-12-10-bash-golf-part-3.md | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) (limited to 'gemfeed') diff --git a/gemfeed/2023-12-10-bash-golf-part-3.md b/gemfeed/2023-12-10-bash-golf-part-3.md index 46cd231f..7735bcb7 100644 --- a/gemfeed/2023-12-10-bash-golf-part-3.md +++ b/gemfeed/2023-12-10-bash-golf-part-3.md @@ -253,7 +253,7 @@ baz foo ``` -What happened? The variable `foo` (declared with `local`) is available in the function it was declared in and in all other functions down the call stack! We can even modify the value of `foo', and the change will be visible up the call stack. It's not a global variable; on the last line, `echo "$foo"` echoes the global variable content. +What happened? The variable `foo` (declared with `local`) is available in the function it was declared in and in all other functions down the call stack! We can even modify the value of `foo`, and the change will be visible up the call stack. It's not a global variable; on the last line, `echo "$foo"` echoes the global variable content. ## `if` conditionals -- cgit v1.2.3 From 60ade7e934dd65eac561099d92ea923b4e197463 Mon Sep 17 00:00:00 2001 From: Paul Buetow Date: Sun, 10 Dec 2023 17:12:14 +0200 Subject: Update content for md --- .../2021-05-16-personal-bash-coding-style-guide.md | 64 ++++++++++++---------- 1 file changed, 34 insertions(+), 30 deletions(-) (limited to 'gemfeed') diff --git a/gemfeed/2021-05-16-personal-bash-coding-style-guide.md b/gemfeed/2021-05-16-personal-bash-coding-style-guide.md index 8eebbbe0..58bb7e76 100644 --- a/gemfeed/2021-05-16-personal-bash-coding-style-guide.md +++ b/gemfeed/2021-05-16-personal-bash-coding-style-guide.md @@ -27,13 +27,13 @@ These are my modifications to the Google Guide. Google recommends using always... -``` +```bash #!/bin/bash ``` ... as the shebang line, but that does not work on all Unix and Unix-like operating systems (e.g., the *BSDs don't have Bash installed to /bin/bash). Better is: -``` +```bash #!/usr/bin/env bash ``` @@ -51,7 +51,7 @@ I hit the 80 character line length quicker with the four spaces than with two sp Google recommends breaking up long pipes like this: -``` +```bash # All fits on one line command1 | command2 @@ -64,7 +64,7 @@ command1 \ I think there is a better way like the following, which is less noisy. The pipe | already indicates the Bash that another command is expected, thus making the explicit line breaks with \ obsolete: -``` +```bash # Long commands command1 | command2 | @@ -72,11 +72,13 @@ command1 | command4 ``` +> Update: It's 2023 now, and I have changed my mind. I think Google's way is the better one. It may be a bit more to type, but the leading `|` are a nice eye catcher, so you know immediately what is going on! + ### Quoting your variables Google recommends always quote your variables. Generally, it would be best if you did that only for variables where you are unsure about the content/values of the variables (e.g., content is from an external input source and may contain whitespace or other special characters). In my opinion, the code will become quite noisy when you always quote your variables like this: -``` +```bash greet () { local -r greeting="${1}" local -r name="${2}" @@ -86,7 +88,7 @@ greet () { In this particular example, I agree that you should quote them as you don't know the input (are there, for example, whitespace characters?). But if you are sure that you are only using simple bare words, then I think that the code looks much cleaner when you do this instead: -``` +```bash say_hello_to_paul () { local -r greeting=Hello local -r name=Paul @@ -96,7 +98,7 @@ say_hello_to_paul () { You see, I also omitted the curly braces { } around the variables. I only use the curly braces around variables when it makes the code either easier/clearer to read or if it is necessary to use them: -``` +```bash declare FOO=bar # Curly braces around FOO are necessary echo "foo${FOO}baz" @@ -108,7 +110,7 @@ A few more words on always quoting the variables: For the sake of consistency (a Google recommends using the built-in commands over available external commands where possible: -``` +```bash # Prefer this: addition=$(( X + Y )) substitution="${string/#foo/bar}" @@ -132,7 +134,7 @@ I even didn't get started with what you can do with awk (especially GNU Awk), a Bash does not support a boolean type. I tend just to use the strings 'yes' and 'no' here. I used 0 for false and 1 for true for some time, but I think that the yes/no strings are easier to read. Yes, the Bash script would need to perform string comparisons on every check, but if performance is crucial to you, you wouldn't want to use a Bash script anyway, correct? -``` +```bash declare -r SUGAR_FREE=yes declare -r I_NEED_THE_BUZZ=no @@ -153,14 +155,13 @@ buy_soda $I_NEED_THE_BUZZ Google is in the opinion that eval should be avoided. I think so too. They list these examples in their guide: -``` +```bash # What does this set? # Did it succeed? In part or whole? eval $(set_my_variables) # What happens if one of the returned values has a space in it? variable="$(eval some_function)" - ``` However, if I want to read variables from another file, I don't have to use eval here. I only have to source the file: @@ -195,7 +196,7 @@ The downside is that ShellCheck won't be able to follow the dynamic sourcing any When I do list processing in Bash, I prefer to use pipes. You can chain them through Bash functions as well, which is pretty neat. Usually, my list processing scripts are of a structure like this: -``` +```bash filter_lines () { echo 'Start filtering lines in a fancy way!' >&2 grep ... | sed .... @@ -239,35 +240,38 @@ I often refactor existing Bash code. That leads me to add and removing function The solution is to use of the "assign-then-shift"-method, which goes like this: "local -r var1=$1; shift; local -r var2=$1; shift". The idea is that you only use "$1" to assign function arguments to named (better readable) local function variables. You will never have to bother about "$2" or above. That is very useful when you constantly refactor your code and remove or add function arguments. It's something that I picked up from a colleague (a pure Bash wizard) some time ago: -``` +```bash some_function () { local -r param_foo="$1"; shift local -r param_baz="$1"; shift local -r param_bay="$1"; shift - ... + + # ... } ``` Want to add a param_baz? Just do this: -``` +```bash some_function () { local -r param_foo="$1"; shift local -r param_bar="$1"; shift local -r param_baz="$1"; shift local -r param_bay="$1"; shift - ... + + # ... } ``` Want to remove param_foo? Nothing easier than that: -``` +```bash some_function () { local -r param_bar="$1"; shift local -r param_baz="$1"; shift local -r param_bay="$1"; shift - ... + + # ... } ``` @@ -277,7 +281,7 @@ As you can see, I didn't need to change any other assignments within the functio I call this the paranoid mode. The Bash will stop executing when a command exits with a status not equal to 0: -``` +```bash set -e grep -q foo <<< bar echo Jo @@ -285,14 +289,14 @@ echo Jo Here 'Jo' will never be printed out as the grep didn't find any match. It's unrealistic for most scripts to run in paranoid mode purely, so there must be a way to add exceptions. Critical Bash scripts of mine tend to look like this: -``` +```bash #!/usr/bin/env bash set -e some_function () { - .. some critical code - ... + # .. some critical code + # ... set +e # Grep might fail, but that's OK now @@ -300,11 +304,11 @@ some_function () { local -i ec=$? set -e - .. critical code continues ... + # .. critical code continues ... if [[ $ec -ne 0 ]]; then - ... + : # ... fi - ... + # ... } ``` @@ -316,7 +320,7 @@ There are also a couple of things I've learned from Google's guide. The following looks like a valid Bash code: -``` +```bash if [[ "${my_var}" > 3 ]]; then # True for 4, false for 22. do_something @@ -325,7 +329,7 @@ fi ... but it is probably an unintended lexicographical comparison. A correct way would be: -``` +```bash if (( my_var > 3 )); then do_something fi @@ -333,7 +337,7 @@ fi or -``` +```bash if [[ "${my_var}" -gt 3 ]]; then do_something fi @@ -345,7 +349,7 @@ I have never used the PIPESTATUS variable before. I knew that it's there, but I The PIPESTATUS variable in Bash allows checking of the return code from all parts of a pipe. If it's only necessary to check the success or failure of the whole pipe, then the following is acceptable: -``` +```bash tar -cf - ./* | ( cd "${dir}" && tar -xf - ) if (( PIPESTATUS[0] != 0 || PIPESTATUS[1] != 0 )); then echo "Unable to tar files to ${dir}" >&2 @@ -354,7 +358,7 @@ fi However, as PIPESTATUS will be overwritten as soon as you do any other command, if you need to act differently on errors based on where it happened in the pipe, you'll need to assign PIPESTATUS to another variable immediately after running the command (don't forget that [ is a command and will wipe out PIPESTATUS). -``` +```bash tar -cf - ./* | ( cd "${DIR}" && tar -xf - ) return_codes=( "${PIPESTATUS[@]}" ) if (( return_codes[0] != 0 )); then -- cgit v1.2.3 From 171e61019c783ed393d7516a0b6b64a7c65646e6 Mon Sep 17 00:00:00 2001 From: Paul Buetow Date: Tue, 9 Jan 2024 18:45:34 +0200 Subject: Update content for md --- ...23-08-18-site-reliability-engineering-part-1.md | 10 ++-- ...23-08-19-site-reliability-engineering-part-2.md | 50 ------------------ ...23-08-20-site-reliability-engineering-part-3.md | 59 ---------------------- ...23-11-19-site-reliability-engineering-part-2.md | 50 ++++++++++++++++++ ...24-01-09-site-reliability-engineering-part-3.md | 57 +++++++++++++++++++++ gemfeed/index.md | 4 +- 6 files changed, 114 insertions(+), 116 deletions(-) delete mode 100644 gemfeed/2023-08-19-site-reliability-engineering-part-2.md delete mode 100644 gemfeed/2023-08-20-site-reliability-engineering-part-3.md create mode 100644 gemfeed/2023-11-19-site-reliability-engineering-part-2.md create mode 100644 gemfeed/2024-01-09-site-reliability-engineering-part-3.md (limited to 'gemfeed') diff --git a/gemfeed/2023-08-18-site-reliability-engineering-part-1.md b/gemfeed/2023-08-18-site-reliability-engineering-part-1.md index 4ce87aaf..7d1d098c 100644 --- a/gemfeed/2023-08-18-site-reliability-engineering-part-1.md +++ b/gemfeed/2023-08-18-site-reliability-engineering-part-1.md @@ -2,11 +2,11 @@ > Published at 2023-08-18T22:43:47+03:00 -The universe of Site Reliability Engineering (SRE) is like an intricate tapestry woven with diverse technology, culture, and personal grit threads. Site Reliability Engineering is one of the most demanding jobs. With all the facets, it's impossible to get bored. There is always a new challenge to master, and there is always a new technology to tinker with. It's not just technical; it's also about communication, collaboration and teamwork. I am currently employed as a Principal Site Reliability Engineer and will try to share what SRE is about in this blog series. +The universe of Site Reliability Engineering (SRE) is like an intricate tapestry woven with diverse technology, culture, and personal grit threads. Site Reliability Engineering is one of the most demanding jobs. With all the facets, it's impossible to get bored. There is always a new challenge to master, and there is always a new technology to tinker with. It's not just technical; it's also about communication, collaboration and teamwork. I am currently employed as a Site Reliability Engineer and will try to share what SRE is about in this blog series. [2023-08-18 Site Reliability Engineering - Part 1: SRE and Organizational Culture (You are currently reading this)](./2023-08-18-site-reliability-engineering-part-1.md) -[2023-08-19 Site Reliability Engineering - Part 2: Operational Balance in SRE](./2023-08-19-site-reliability-engineering-part-2.md) -[2023-08-20 Site Reliability Engineering - Part 3: On-Call Culture and the Human Aspect](./2023-08-20-site-reliability-engineering-part-3.md) +[2023-11-19 Site Reliability Engineering - Part 2: Operational Balance in SRE](./2023-11-19-site-reliability-engineering-part-2.md) +[2024-01-09 Site Reliability Engineering - Part 3: On-Call Culture and the Human Aspect](./2024-01-09-site-reliability-engineering-part-3.md) ``` ▓▓▓▓░░ @@ -36,7 +36,7 @@ At the heart of SRE lies the proactive mindset of "prevention over cure." Tradit Another defining SRE idea concept the "error budget." This ingenious framework accepts that no system is flawless. Failures are inevitable. However, instead of being punitive, the culture here is to accept, learn, and iterate. By providing teams with a "budget" for errors, organisations create an environment where innovation is encouraged, and failures are viewed as learning opportunities. -But SRE isn't just about technology and metrics; it's deeply human. It challenges the "hero culture" that plagues many IT teams. While individual heroics might occasionally save the day, a sustainable model requires collective expertise. An SRE culture recognises that heroes achieve their best within teams, negating the need for a hero-centric environment. This philosophy promotes a balanced on-call experience, emphasising the importance of trust, ownership, effective communication, and collaboration as cornerstones of team success. I personally have fallen into the hero trap, and know it's unsustainable to be the only go-to person for every problem. +But SRE isn't just about technology and metrics; it's also human. It challenges the "hero culture" that plagues many IT teams. While individual heroics might occasionally save the day, a sustainable model requires collective expertise. An SRE culture recognises that heroes achieve their best within teams, negating the need for a hero-centric environment. This philosophy promotes a balanced on-call experience, emphasising the importance of trust, ownership, effective communication, and collaboration as cornerstones of team success. I personally have fallen into the hero trap, and know it's unsustainable to be the only go-to person for every arising problem. Additionally, the SRE model requires good documentation. However, it's essential ensuring that this documentation undergoes the same quality checks as code, reinforcing effective onboarding, training and communication. @@ -52,7 +52,7 @@ Organisations with the implementation of SLIs, SLOs and error budgets are alread Continue with the second part of this series: -[2023-08-19 Site Reliability Engineering - Part 2: Operational Balance in SRE](./2023-08-19-site-reliability-engineering-part-2.md) +[2023-11-19 Site Reliability Engineering - Part 2: Operational Balance in SRE](./2023-11-19-site-reliability-engineering-part-2.md) E-Mail your comments to `paul@nospam.buetow.org` :-) diff --git a/gemfeed/2023-08-19-site-reliability-engineering-part-2.md b/gemfeed/2023-08-19-site-reliability-engineering-part-2.md deleted file mode 100644 index b3e908f4..00000000 --- a/gemfeed/2023-08-19-site-reliability-engineering-part-2.md +++ /dev/null @@ -1,50 +0,0 @@ -# Site Reliability Engineering - Part 2: Operational Balance in SRE - -> Published at 2023-08-19T00:18:18+03:00 - -This is the second part of my Site Reliability Engineering (SRE) series. I am currently employed as a Principal Site Reliability Engineer and will try to share what SRE is about in this blog series. - -[2023-08-18 Site Reliability Engineering - Part 1: SRE and Organizational Culture](./2023-08-18-site-reliability-engineering-part-1.md) -[2023-08-19 Site Reliability Engineering - Part 2: Operational Balance in SRE (You are currently reading this)](./2023-08-19-site-reliability-engineering-part-2.md) -[2023-08-20 Site Reliability Engineering - Part 3: On-Call Culture and the Human Aspect](./2023-08-20-site-reliability-engineering-part-3.md) - -``` -⠀⠀⠀⠀⠀⠀⠀⠀⠀⠀⠀⠀⢀⣠⣾⣷⣄⡀⠀⠀⠀⠀⠀⠀⠀⠀⠀⠀⠀⠀ -⠀⠀⠀⠀⣾⠿⠿⠿⠶⠾⠿⠿⣿⣿⣿⣿⣿⣿⠿⠿⠶⠶⠿⠿⠿⣷⠀⠀⠀⠀ -⠀⠀⠀⣸⢿⣆⠀⠀⠀⠀⠀⠀⠀⠙⢿⡿⠉⠀⠀⠀⠀⠀⠀⠀⣸⣿⡆⠀⠀⠀ -⠀⠀⢠⡟⠀⢻⣆⠀⠀⠀⠀⠀⠀⠀⣾⣧⠀⠀⠀⠀⠀⠀⠀⣰⡟⠀⢻⡄⠀⠀ -⠀⢀⣾⠃⠀⠀⢿⡄⠀⠀⠀⠀⠀⢠⣿⣿⡀⠀⠀⠀⠀⠀⢠⡿⠀⠀⠘⣷⡀⠀ -⠀⣼⣏⣀⣀⣀⣈⣿⡀⠀⠀⠀⠀⣸⣿⣿⡇⠀⠀⠀⠀⢀⣿⣃⣀⣀⣀⣸⣧⠀ -⠀⢻⣿⣿⣿⣿⣿⣿⠃⠀⠀⠀⠀⣿⣿⣿⣿⠀⠀⠀⠀⠈⢿⣿⣿⣿⣿⣿⡿⠀ -⠀⠀⠉⠛⠛⠛⠋⠁⠀⠀⠀⠀⢸⣿⣿⣿⣿⡆⠀⠀⠀⠀⠈⠙⠛⠛⠛⠉⠀⠀ -⠀⠀⠀⠀⠀⠀⠀⠀⠀⠀⠀⠀⠸⣿⣿⣿⣿⠇⠀⠀⠀⠀⠀⠀⠀⠀⠀⠀⠀⠀ -⠀⠀⠀⠀⠀⠀⠀⠀⠀⠀⠀⠀⣠⣾⣿⣿⣷⣄⠀⠀⠀⠀⠀⠀⠀⠀⠀⠀⠀⠀ -⠀⠀⠀⠀⠀⠀⠀⠀⠀⠀⠀⣸⣿⣿⣿⣿⣿⣿⣆⠀⠀⠀⠀⠀⠀⠀⠀⠀⠀⠀ -⠀⠀⠀⠀⠀⠀⠴⠶⠿⠿⠿⠿⠿⠿⠿⠿⠿⠿⠿⠿⠿⠿⠶⠦⠀⠀ -``` - -## Operational Balance in SRE: Finding the Equilibrium in Reliability and Velocity - -Site Reliability Engineering has established itself as more than just a set of best practices or methodologies. Instead, it stands as a beacon of operational excellence, which guides engineering teams through the turbulent waters of modern software development and system management. - -In the universe of software production, two fundamental forces are often at odds: The drive for rapid feature release (velocity) and the need for system reliability. Traditionally, the faster teams moved, the more risk was introduced into systems. SRE offers a approach to mitigate these conflicting drives through concepts like error budgets and SLIs/SLOs. These mechanisms offer a tangible metric, allowing teams to quantify how much they can push changes while ensuring they don't compromise system health. Thus, the error budget becomes a balancing act, where teams weigh the trade-offs between innovation and reliability. - -An important part of this balance is the dichotomy between operations and coding. According to SRE principles, an engineer should ideally spend an equal amount of time on operations work and coding - 50% on each. This isn't just a random metric; it's a reflection of the value SRE places on both maintaining operational excellence and progressing forward with innovations. This balance ensures that while SREs are solving today's problems, they are also preparing for tomorrow's challenges. - -However, not all operational tasks are equal. SRE differentiates between "ops work" and "toil". While ops work is integral to system maintenance and can provide value, toil represents repetitive, mundane tasks which offer little value in the long run. Recognising and minimising toil is crucial. A culture that allows engineers to drown in toil stifles innovation and growth. Hence, an organisation's approach to toil indicates its operational health and commitment to balance. - -A cornerstone of achieving operational balance lies in the tools and processes SREs use. Effective monitoring, observability tools, and ensuring that tools can handle high cardinality data are foundational. These aren't just technical requisites but reflective of an organisational culture prioritising proactive problem-solving. By having systems that effectively flag potential issues before they escalate, SREs can maintain the balance between system stability and forward momentum. - -Moreover, operational balance isn't just a technological or process challenge; it's a human one. The health of on-call engineers is as crucial as the health of the services they manage. On-call postmortems, continuous feedback loops, and recognising gaps (be it tooling, operational expertise, or resources) ensure that the human elements of operations are noticed. - -In conclusion, operational balance in SRE isn't static thing but an ongoing journey. It requires organisations to constantly evaluate their practices, tools, and, most importantly, their culture. By achieving this balance, organisations can ensure that they have time for innovation while maintaining the robustness and reliability of their systems, resulting in sustainable long-term success. - -That all sounds very romantic. The truth is, it's brutal to archive the perfect balance. No system will ever be perfect. But at least we should aim for it! - -Continue with the third part of this series: - -[2023-08-20 Site Reliability Engineering - Part 3: On-Call Culture and the Human Aspect](./2023-08-20-site-reliability-engineering-part-3.md) - -E-Mail your comments to `paul@nospam.buetow.org` :-) - -[Back to the main site](../) diff --git a/gemfeed/2023-08-20-site-reliability-engineering-part-3.md b/gemfeed/2023-08-20-site-reliability-engineering-part-3.md deleted file mode 100644 index 831eb156..00000000 --- a/gemfeed/2023-08-20-site-reliability-engineering-part-3.md +++ /dev/null @@ -1,59 +0,0 @@ -# Site Reliability Engineering - Part 3: On-Call Culture and the Human Aspect - -> Published at 2023-08-20T12:17:56+03:00 - -This is the third part of my Site Reliability Engineering (SRE) series. I am currently employed as a Principal Site Reliability Engineer and will try to share what SRE is about in this blog series. - -[2023-08-18 Site Reliability Engineering - Part 1: SRE and Organizational Culture](./2023-08-18-site-reliability-engineering-part-1.md) -[2023-08-19 Site Reliability Engineering - Part 2: Operational Balance in SRE](./2023-08-19-site-reliability-engineering-part-2.md) -[2023-08-20 Site Reliability Engineering - Part 3: On-Call Culture and the Human Aspect (You are currently reading this)](./2023-08-20-site-reliability-engineering-part-3.md) - -``` - ..--""""----.. - .-" ..--""""--.j-. - .-" .-" .--.""--.. - .-" .-" ..--"-. \/ ; - .-" .-"_.--..--"" ..--' "-. : - .' .' / `. \..--"" __ _ \ ; - :.__.-" \ / .' ( )"-. Y - ; ;: ( ) ( ). \ - .': /:: : \ \ - .'.-"\._ _.-" ; ; ( ) .-. ( ) \ - " `.""" .j" : : \ ; ; \ - bug /"""""/ ; ( ) "" :.( ) \ - /\ / : \ \`.: _ \ - : `. / ; `( ) (\/ :" \ \ - \ `. : "-.(_)_.' t-' ; - \ `. ; ..--": - `. `. : ..--"" : - `. "-. ; ..--"" ; - `. "-.:_..--"" ..--" - `. : ..--"" - "-. : ..--"" - "-.;_..--"" - -``` - -## On-Call Culture and the Human Aspect: Prioritising Well-being in the Realm of Reliability - -Site Reliability Engineering is synonymous with ensuring system reliability, but the human factor is an often-underestimated part of this discipline. Ensuring an healthy on-call culture is as critical as any technical solution. The well-being of the engineers is an important factor. - -Firstly, a healthy on-call rotation is about more than just managing and responding to incidents. It's about the entire ecosystem that supports this practice. This involves reducing pain points, offering mentorship, rapid iteration, and ensuring that engineers have the right tools and processes. One ceavat is, that engineers should be willing to learn. Especially in on-call rotation embedding SREs with other engineers (for example Software Engineers or QA Engineers), it's difficult to motivate everyone to engage. QA Engineers want to test the software, Software Engineers want to implement new features; they don't want to troubleshoot and debug production incidents. It can be depressing for the mentoring SRE. - -Furthermore, the metrics that measure the success of an on-call experience are only sometimes straightforward. While one might assume that fewer pages translate to better on-call expertise (which is true to a degree, as who wants to receive a page out of office hours?), it's not always the volume of pages that matters most. Trust, ownership, accountability, and effective communication play the important roles. - -An important part is giving feedback about the on-call experience to ensure continuous learning. If alerts are mostly noise, they should be tuned or even eliminated. If alerts are actionable, can recurring tasks be automated? If there are knowledge gaps, is the documentation not good enough? Continuous retrospection ensures that not only do systems evolve, but the experience for the on-call engineers becomes progressively better. - -Onboarding for on-call duties is a crucial aspect of ensuring the reliability and efficiency of systems. This process involves equipping new team members with the knowledge, tools, and support to handle incidents confidently. It begins with an overview of the system architecture and common challenges, followed by training on monitoring tools, alerting mechanisms, and incident response protocols. Shadowing experienced on-call engineers can offer practical exposure. Too often, new engineers are thrown into the cold water without proper onboarding and training because the more experienced engineers are too busy fire-fighting production issues in the first place. - -An always-on, always-alert culture can lead to burnout. Engineers should be encouraged to recognise their limits, take breaks, and seek support when needed. This isn't just about individual health; a burnt-out engineer can have cascading effects on the entire team and the systems they manage. A successful on-call culture ensures that while systems are kept running, the engineers are kept happy, healthy, and supported. The more experienced engineers should take time to mentor the junior engineers, but the junior engineers should also be fully engaged, try to investigate and learn new things by themselves. - -For the junior engineer, it's too easy to fall back and ask the experts in the team every time an issue arises. This seems reasonable, but serving recipes for solving production issues on a silver tablet won't scale forever, as there are infinite scenarios of how production systems can break. So every engineer should learn to debug, troubleshoot and resolve production incidents independently. The experts will still be there for guidance and step in when the junior gets stuck after trying, but the experts should also learn to step down so that lesser experienced engineers can step up and learn. But mistakes can always happen here; that's why having a blameless on-call culture is essential. - -A blameless on-call culture is a must for a safe and collaborative environment where engineers can effectively respond to incidents without fear of retribution. This approach acknowledges that mistakes are a natural part of the learning and innovation process. When individuals are assured they won't be punished for errors, they're more likely to openly discuss mistakes, allowing the entire team to learn and grow from each incident. Furthermore, a blameless culture promotes psychological safety, enhances job satisfaction, reduces burnout, and ensures that talent remains committed and engaged. - -The fourth part of this blog series will be published soon :-) - -E-Mail your comments to `paul@nospam.buetow.org` :-) - -[Back to the main site](../) diff --git a/gemfeed/2023-11-19-site-reliability-engineering-part-2.md b/gemfeed/2023-11-19-site-reliability-engineering-part-2.md new file mode 100644 index 00000000..0db86f50 --- /dev/null +++ b/gemfeed/2023-11-19-site-reliability-engineering-part-2.md @@ -0,0 +1,50 @@ +# Site Reliability Engineering - Part 2: Operational Balance in SRE + +> Published at 2023-11-19T00:18:18+03:00 + +This is the second part of my Site Reliability Engineering (SRE) series. I am currently employed as a Site Reliability Engineer and will try to share what SRE is about in this blog series. + +[2023-08-18 Site Reliability Engineering - Part 1: SRE and Organizational Culture](./2023-08-18-site-reliability-engineering-part-1.md) +[2023-11-19 Site Reliability Engineering - Part 2: Operational Balance in SRE (You are currently reading this)](./2023-11-19-site-reliability-engineering-part-2.md) +[2024-01-09 Site Reliability Engineering - Part 3: On-Call Culture and the Human Aspect](./2024-01-09-site-reliability-engineering-part-3.md) + +``` +⠀⠀⠀⠀⠀⠀⠀⠀⠀⠀⠀⠀⢀⣠⣾⣷⣄⡀⠀⠀⠀⠀⠀⠀⠀⠀⠀⠀⠀⠀ +⠀⠀⠀⠀⣾⠿⠿⠿⠶⠾⠿⠿⣿⣿⣿⣿⣿⣿⠿⠿⠶⠶⠿⠿⠿⣷⠀⠀⠀⠀ +⠀⠀⠀⣸⢿⣆⠀⠀⠀⠀⠀⠀⠀⠙⢿⡿⠉⠀⠀⠀⠀⠀⠀⠀⣸⣿⡆⠀⠀⠀ +⠀⠀⢠⡟⠀⢻⣆⠀⠀⠀⠀⠀⠀⠀⣾⣧⠀⠀⠀⠀⠀⠀⠀⣰⡟⠀⢻⡄⠀⠀ +⠀⢀⣾⠃⠀⠀⢿⡄⠀⠀⠀⠀⠀⢠⣿⣿⡀⠀⠀⠀⠀⠀⢠⡿⠀⠀⠘⣷⡀⠀ +⠀⣼⣏⣀⣀⣀⣈⣿⡀⠀⠀⠀⠀⣸⣿⣿⡇⠀⠀⠀⠀⢀⣿⣃⣀⣀⣀⣸⣧⠀ +⠀⢻⣿⣿⣿⣿⣿⣿⠃⠀⠀⠀⠀⣿⣿⣿⣿⠀⠀⠀⠀⠈⢿⣿⣿⣿⣿⣿⡿⠀ +⠀⠀⠉⠛⠛⠛⠋⠁⠀⠀⠀⠀⢸⣿⣿⣿⣿⡆⠀⠀⠀⠀⠈⠙⠛⠛⠛⠉⠀⠀ +⠀⠀⠀⠀⠀⠀⠀⠀⠀⠀⠀⠀⠸⣿⣿⣿⣿⠇⠀⠀⠀⠀⠀⠀⠀⠀⠀⠀⠀⠀ +⠀⠀⠀⠀⠀⠀⠀⠀⠀⠀⠀⠀⣠⣾⣿⣿⣷⣄⠀⠀⠀⠀⠀⠀⠀⠀⠀⠀⠀⠀ +⠀⠀⠀⠀⠀⠀⠀⠀⠀⠀⠀⣸⣿⣿⣿⣿⣿⣿⣆⠀⠀⠀⠀⠀⠀⠀⠀⠀⠀⠀ +⠀⠀⠀⠀⠀⠀⠴⠶⠿⠿⠿⠿⠿⠿⠿⠿⠿⠿⠿⠿⠿⠿⠶⠦⠀⠀ +``` + +## Operational Balance in SRE: Finding the Equilibrium in Reliability and Velocity + +Site Reliability Engineering has established itself as more than just a set of best practices or methodologies. Instead, it stands as a beacon of operational excellence, which guides engineering teams through the turbulent waters of modern software development and system management. + +In the universe of software production, two fundamental forces are often at odds: The drive for rapid feature release (velocity) and the need for system reliability. Traditionally, the faster teams moved, the more risk was introduced into systems. SRE offers a approach to mitigate these conflicting drives through concepts like error budgets and SLIs/SLOs. These mechanisms offer a tangible metric, allowing teams to quantify how much they can push changes while ensuring they don't compromise system health. Thus, the error budget becomes a balancing act, where teams weigh the trade-offs between innovation and reliability. + +An important part of this balance is the dichotomy between operations and coding. According to SRE principles, an engineer should ideally spend an equal amount of time on operations work and coding - 50% on each. This isn't just a random metric; it's a reflection of the value SRE places on both maintaining operational excellence and progressing forward with innovations. This balance ensures that while SREs are solving today's problems, they are also preparing for tomorrow's challenges. + +However, not all operational tasks are equal. SRE differentiates between "ops work" and "toil". While ops work is integral to system maintenance and can provide value, toil represents repetitive, mundane tasks which offer little value in the long run. Recognising and minimising toil is crucial. A culture that allows engineers to drown in toil stifles innovation and growth. Hence, an organisation's approach to toil indicates its operational health and commitment to balance. + +A cornerstone of achieving operational balance lies in the tools and processes SREs use. Effective monitoring, observability tools, and ensuring that tools can handle high cardinality data are foundational. These aren't just technical requisites but reflective of an organisational culture prioritising proactive problem-solving. By having systems that effectively flag potential issues before they escalate, SREs can maintain the balance between system stability and forward momentum. + +Moreover, operational balance isn't just a technological or process challenge; it's a human one. The health of on-call engineers is as crucial as the health of the services they manage. On-call postmortems, continuous feedback loops, and recognising gaps (be it tooling, operational expertise, or resources) ensure that the human elements of operations are noticed. + +In conclusion, operational balance in SRE isn't static thing but an ongoing journey. It requires organisations to constantly evaluate their practices, tools, and, most importantly, their culture. By achieving this balance, organisations can ensure that they have time for innovation while maintaining the robustness and reliability of their systems, resulting in sustainable long-term success. + +That all sounds very romantic. The truth is, it's brutal to archive the perfect balance. No system will ever be perfect. But at least we should aim for it! + +Continue with the third part of this series: + +[2024-01-09 Site Reliability Engineering - Part 3: On-Call Culture and the Human Aspect](./2024-01-09-site-reliability-engineering-part-3.md) + +E-Mail your comments to `paul@nospam.buetow.org` :-) + +[Back to the main site](../) diff --git a/gemfeed/2024-01-09-site-reliability-engineering-part-3.md b/gemfeed/2024-01-09-site-reliability-engineering-part-3.md new file mode 100644 index 00000000..d53c083f --- /dev/null +++ b/gemfeed/2024-01-09-site-reliability-engineering-part-3.md @@ -0,0 +1,57 @@ +# Site Reliability Engineering - Part 3: On-Call Culture and the Human Aspect + +> Published at 2024-01-09T18:35:48+02:00 + +This is the third part of my Site Reliability Engineering (SRE) series. I am currently employed as a Site Reliability Engineer and will try to share what SRE is about in this blog series. + +[2023-08-18 Site Reliability Engineering - Part 1: SRE and Organizational Culture](./2023-08-18-site-reliability-engineering-part-1.md) +[2023-11-19 Site Reliability Engineering - Part 2: Operational Balance in SRE](./2023-11-19-site-reliability-engineering-part-2.md) +[2024-01-09 Site Reliability Engineering - Part 3: On-Call Culture and the Human Aspect (You are currently reading this)](./2024-01-09-site-reliability-engineering-part-3.md) + +``` + ..--""""----.. + .-" ..--""""--.j-. + .-" .-" .--.""--.. + .-" .-" ..--"-. \/ ; + .-" .-"_.--..--"" ..--' "-. : + .' .' / `. \..--"" __ _ \ ; + :.__.-" \ / .' ( )"-. Y + ; ;: ( ) ( ). \ + .': /:: : \ \ + .'.-"\._ _.-" ; ; ( ) .-. ( ) \ + " `.""" .j" : : \ ; ; \ + bug /"""""/ ; ( ) "" :.( ) \ + /\ / : \ \`.: _ \ + : `. / ; `( ) (\/ :" \ \ + \ `. : "-.(_)_.' t-' ; + \ `. ; ..--": + `. `. : ..--"" : + `. "-. ; ..--"" ; + `. "-.:_..--"" ..--" + `. : ..--"" + "-. : ..--"" + "-.;_..--"" + +``` + +## On-Call Culture and the Human Aspect: Prioritising Well-being in the Realm of Reliability + +Site Reliability Engineering is synonymous with ensuring system reliability, but the human factor is an often-underestimated part of this discipline. Ensuring an healthy on-call culture is as critical as any technical solution. The well-being of the engineers is an important factor. + +Firstly, a healthy on-call rotation is about more than just managing and responding to incidents. It's about the entire ecosystem that supports this practice. This involves reducing pain points, offering mentorship, rapid iteration, and ensuring that engineers have the right tools and processes. One ceavat is, that engineers should be willing to learn. Especially in on-call rotation embedding SREs with other engineers (for example Software Engineers or QA Engineers), it's difficult to motivate everyone to engage. QA Engineers want to test the software, Software Engineers want to implement new features; they don't want to troubleshoot and debug production incidents. It can be depressing for the mentoring SRE. + +Furthermore, the metrics that measure the success of an on-call experience are only sometimes straightforward. While one might assume that fewer pages translate to better on-call expertise (which is true to a degree, as who wants to receive a page out of office hours?), it's not always the volume of pages that matters most. Trust, ownership, accountability, and effective communication play the important roles. + +An important part is giving feedback about the on-call experience to ensure continuous learning. If alerts are mostly noise, they should be tuned or even eliminated. If alerts are actionable, can recurring tasks be automated? If there are knowledge gaps, is the documentation not good enough? Continuous retrospection ensures that not only do systems evolve, but the experience for the on-call engineers becomes progressively better. + +Onboarding for on-call duties is a crucial aspect of ensuring the reliability and efficiency of systems. This process involves equipping new team members with the knowledge, tools, and support to handle incidents confidently. It begins with an overview of the system architecture and common challenges, followed by training on monitoring tools, alerting mechanisms, and incident response protocols. Shadowing experienced on-call engineers can offer practical exposure. Too often, new engineers are thrown into the cold water without proper onboarding and training because the more experienced engineers are too busy fire-fighting production issues in the first place. + +An always-on, always-alert culture can lead to burnout. Engineers should be encouraged to recognise their limits, take breaks, and seek support when needed. This isn't just about individual health; a burnt-out engineer can have cascading effects on the entire team and the systems they manage. A successful on-call culture ensures that while systems are kept running, the engineers are kept happy, healthy, and supported. The more experienced engineers should take time to mentor the junior engineers, but the junior engineers should also be fully engaged, try to investigate and learn new things by themselves. + +For the junior engineer, it's too easy to fall back and ask the experts in the team every time an issue arises. This seems reasonable, but serving recipes for solving production issues on a silver tablet won't scale forever, as there are infinite scenarios of how production systems can break. So every engineer should learn to debug, troubleshoot and resolve production incidents independently. The experts will still be there for guidance and step in when the junior gets stuck after trying, but the experts should also learn to step down so that lesser experienced engineers can step up and learn. But mistakes can always happen here; that's why having a blameless on-call culture is essential. + +A blameless on-call culture is a must for a safe and collaborative environment where engineers can effectively respond to incidents without fear of retribution. This approach acknowledges that mistakes are a natural part of the learning and innovation process. When individuals are assured they won't be punished for errors, they're more likely to openly discuss mistakes, allowing the entire team to learn and grow from each incident. Furthermore, a blameless culture promotes psychological safety, enhances job satisfaction, reduces burnout, and ensures that talent remains committed and engaged. + +E-Mail your comments to `paul@nospam.buetow.org` :-) + +[Back to the main site](../) diff --git a/gemfeed/index.md b/gemfeed/index.md index fcf83d14..0eccfe89 100644 --- a/gemfeed/index.md +++ b/gemfeed/index.md @@ -2,12 +2,12 @@ ## To be in the .zone! +[2024-01-09 - Site Reliability Engineering - Part 3: On-Call Culture and the Human Aspect](./2024-01-09-site-reliability-engineering-part-3.md) [2023-12-10 - Bash Golf Part 3](./2023-12-10-bash-golf-part-3.md) +[2023-11-19 - Site Reliability Engineering - Part 2: Operational Balance in SRE](./2023-11-19-site-reliability-engineering-part-2.md) [2023-11-11 - 'Mind Management' book notes](./2023-11-11-mind-management-book-notes.md) [2023-10-29 - KISS static web photo albums with `photoalbum.sh`](./2023-10-29-kiss-static-web-photo-albums-with-photoalbum.sh.md) [2023-09-25 - DTail usage examples](./2023-09-25-dtail-usage-examples.md) -[2023-08-20 - Site Reliability Engineering - Part 3: On-Call Culture and the Human Aspect](./2023-08-20-site-reliability-engineering-part-3.md) -[2023-08-19 - Site Reliability Engineering - Part 2: Operational Balance in SRE](./2023-08-19-site-reliability-engineering-part-2.md) [2023-08-18 - Site Reliability Engineering - Part 1: SRE and Organizational Culture](./2023-08-18-site-reliability-engineering-part-1.md) [2023-07-21 - Gemtexter 2.1.0 - Let's Gemtext again³](./2023-07-21-gemtexter-2.1.0-lets-gemtext-again-3.md) [2023-07-17 - 'Software Developmers Career Guide and Soft Skills' book notes](./2023-07-17-career-guide-and-soft-skills-book-notes.md) -- cgit v1.2.3 From dd6db3673ccb6cc67aa48edcfcf7ce5bdbb86b03 Mon Sep 17 00:00:00 2001 From: Paul Buetow Date: Sat, 13 Jan 2024 23:08:14 +0200 Subject: Update content for md --- ...6-04-09-jails-and-zfs-on-freebsd-with-puppet.md | 7 +++ ...2022-07-30-lets-encrypt-with-openbsd-and-rex.md | 7 +++ .../2024-01-13-one-reason-why-i-love-openbsd.md | 71 ++++++++++++++++++++++ gemfeed/index.md | 1 + 4 files changed, 86 insertions(+) create mode 100644 gemfeed/2024-01-13-one-reason-why-i-love-openbsd.md (limited to 'gemfeed') diff --git a/gemfeed/2016-04-09-jails-and-zfs-on-freebsd-with-puppet.md b/gemfeed/2016-04-09-jails-and-zfs-on-freebsd-with-puppet.md index 7b49b7f9..2f9c3b4d 100644 --- a/gemfeed/2016-04-09-jails-and-zfs-on-freebsd-with-puppet.md +++ b/gemfeed/2016-04-09-jails-and-zfs-on-freebsd-with-puppet.md @@ -385,6 +385,13 @@ Of course I am operating multiple Jails on the same host this way with Puppet: All done in a pretty automated manor. +Other *BSD related posts are: + +[2016-04-09 Jails and ZFS with Puppet on FreeBSD (You are currently reading this)](./2016-04-09-jails-and-zfs-on-freebsd-with-puppet.md) +[2022-07-30 Let's Encrypt with OpenBSD and Rex](./2022-07-30-lets-encrypt-with-openbsd-and-rex.md) +[2022-10-30 Installing DTail on OpenBSD](./2022-10-30-installing-dtail-on-openbsd.md) +[2024-01-13 One reason why I love OpenBSD](./2024-01-13-one-reason-why-i-love-openbsd.md) + E-Mail your comments to `paul@nospam.buetow.org` :-) [Back to the main site](../) diff --git a/gemfeed/2022-07-30-lets-encrypt-with-openbsd-and-rex.md b/gemfeed/2022-07-30-lets-encrypt-with-openbsd-and-rex.md index bc3800ca..2a54391a 100644 --- a/gemfeed/2022-07-30-lets-encrypt-with-openbsd-and-rex.md +++ b/gemfeed/2022-07-30-lets-encrypt-with-openbsd-and-rex.md @@ -656,6 +656,13 @@ OpenBSD suits perfectly here as all the tools are already part of the base insta Why re-inventing the wheel? I love that a `Rexfile` is just a Perl DSL. Also, OpenBSD comes with Perl in the base system. So no new programming language had to be added to my mix for the configuration management system. Also, the `acme.sh` shell script is not a Bash but a standard Bourne shell script, so I didn't have to install an additional shell as OpenBSD does not come with the Bash pre-installed. +Other *BSD related posts are: + +[2016-04-09 Jails and ZFS with Puppet on FreeBSD](./2016-04-09-jails-and-zfs-on-freebsd-with-puppet.md) +[2022-07-30 Let's Encrypt with OpenBSD and Rex (You are currently reading this)](./2022-07-30-lets-encrypt-with-openbsd-and-rex.md) +[2022-10-30 Installing DTail on OpenBSD](./2022-10-30-installing-dtail-on-openbsd.md) +[2024-01-13 One reason why I love OpenBSD](./2024-01-13-one-reason-why-i-love-openbsd.md) + E-Mail your comments to `paul@nospam.buetow.org` :-) [Back to the main site](../) diff --git a/gemfeed/2024-01-13-one-reason-why-i-love-openbsd.md b/gemfeed/2024-01-13-one-reason-why-i-love-openbsd.md new file mode 100644 index 00000000..b52913e5 --- /dev/null +++ b/gemfeed/2024-01-13-one-reason-why-i-love-openbsd.md @@ -0,0 +1,71 @@ +# One reason why I love OpenBSD + +> Published at 2024-01-13T22:55:33+02:00 + +``` + . + A ; + | ,--,-/ \---,-/| , + _|\,'. /| /| `/|-. + \`.' /| , `;. + ,'\ A A A A _ /| `.; + ,/ _ A _ / _ /| ; + /\ / \ , , A / / `/| + /_| | _ \ , , ,/ \ + // | |/ `.\ ,- , , ,/ ,/ \/ + / @| |@ / /' \ \ , > /| ,--. + |\_/ \_/ / | | , ,/ \ ./' __:.. + | __ __ | | | .--. , > > |-' / ` + ,/| / ' \ | | | \ , | / + / |<--.__,->| | | . `. > > / ( +/_,' \\ ^ / \ / / `. >-- /^\ | + \\___/ \ / / \__' \ \ \/ \ | + `. |/ , , /`\ \ ) + \ ' |/ , V \ / `-\ + `|/ ' V V \ \.' \_ + '`-. V V \./'\ + `|/-. \ / \ /,---`\ kat + n + / `._____V_____V' + ' ' +``` + +I just upgraded my OpenBSD's from `7.3` to `7.4` by following the unattended upgrade guide: + +[https://www.openbsd.org/faq/upgrade74.html](https://www.openbsd.org/faq/upgrade74.html) + +```shell +doas installboot sd0 # Update the bootloader (not for every upgrade required) +doas sysupgrade # Update all binaries (including Kernel) +``` + +`sysupgrade` downloaded and upgraded to the next release and rebooted the system. After the reboot, I run: + +```shell +doas sysmerge # Update system configuration files +doas pkg_add -u # Update all packages +doas reboot # Just in case, reboot one more time +``` + +That's it! Took me around 5 minutes in total! No issues, only these few comands, only 5 minutes! It just works! No problems, no conflicts, no tons (actually none) config file merge conflicts. + +I followed the same procedure the previous times and never encountered any difficulties with any OpenBSD upgrades. + +I have seen upgrades of other Operating Systems either take a long time or break the system (which takes manual steps to repair). That's just one of many reasons why I love OpenBSD! There appear never to be any problems. It just gets its job done! + +[The OpenBSD Project](https://www.openbsd.org) + +BTW: are you looking for an opinionated OpenBSD VM hoster? OpenBSD Amsterdam may be for you. They rock (I am having a VM there, too)! + +[https://openbsd.amsterdam](https://openbsd.amsterdam) + +Other *BSD related posts are: + +[2016-04-09 Jails and ZFS with Puppet on FreeBSD](./2016-04-09-jails-and-zfs-on-freebsd-with-puppet.md) +[2022-07-30 Let's Encrypt with OpenBSD and Rex](./2022-07-30-lets-encrypt-with-openbsd-and-rex.md) +[2022-10-30 Installing DTail on OpenBSD](./2022-10-30-installing-dtail-on-openbsd.md) +[2024-01-13 One reason why I love OpenBSD (You are currently reading this)](./2024-01-13-one-reason-why-i-love-openbsd.md) + +E-Mail your comments to `paul@nospam.buetow.org` :-) + +[Back to the main site](../) diff --git a/gemfeed/index.md b/gemfeed/index.md index 0eccfe89..33d72833 100644 --- a/gemfeed/index.md +++ b/gemfeed/index.md @@ -2,6 +2,7 @@ ## To be in the .zone! +[2024-01-13 - One reason why I love OpenBSD](./2024-01-13-one-reason-why-i-love-openbsd.md) [2024-01-09 - Site Reliability Engineering - Part 3: On-Call Culture and the Human Aspect](./2024-01-09-site-reliability-engineering-part-3.md) [2023-12-10 - Bash Golf Part 3](./2023-12-10-bash-golf-part-3.md) [2023-11-19 - Site Reliability Engineering - Part 2: Operational Balance in SRE](./2023-11-19-site-reliability-engineering-part-2.md) -- cgit v1.2.3 From 220b7665fc2b822c9dabb131969ca28a5f8a339c Mon Sep 17 00:00:00 2001 From: Paul Buetow Date: Sat, 13 Jan 2024 23:11:25 +0200 Subject: Update content for md --- gemfeed/2016-04-09-jails-and-zfs-on-freebsd-with-puppet.md | 4 ++-- gemfeed/2021-04-22-dtail-the-distributed-log-tail-program.md | 4 ++-- gemfeed/2021-06-05-gemtexter-one-bash-script-to-rule-it-all.md | 4 ++-- gemfeed/2022-03-06-the-release-of-dtail-4.0.0.md | 4 ++-- gemfeed/2022-05-27-perl-is-still-a-great-choice.md | 4 ++-- gemfeed/2022-07-30-lets-encrypt-with-openbsd-and-rex.md | 4 ++-- gemfeed/2023-03-25-gemtexter-2.0.0-lets-gemtext-again-2.md | 4 ++-- gemfeed/2023-05-01-unveiling-guprecords | 0 gemfeed/2023-06-01-kiss-server-monitoring-with-gogios.md | 4 ++-- gemfeed/2023-07-21-gemtexter-2.1.0-lets-gemtext-again-3.md | 4 ++-- gemfeed/2023-12-10-bash-golf-part-3.md | 3 +-- 11 files changed, 19 insertions(+), 20 deletions(-) create mode 100644 gemfeed/2023-05-01-unveiling-guprecords (limited to 'gemfeed') diff --git a/gemfeed/2016-04-09-jails-and-zfs-on-freebsd-with-puppet.md b/gemfeed/2016-04-09-jails-and-zfs-on-freebsd-with-puppet.md index 2f9c3b4d..3a2d1514 100644 --- a/gemfeed/2016-04-09-jails-and-zfs-on-freebsd-with-puppet.md +++ b/gemfeed/2016-04-09-jails-and-zfs-on-freebsd-with-puppet.md @@ -385,6 +385,8 @@ Of course I am operating multiple Jails on the same host this way with Puppet: All done in a pretty automated manor. +E-Mail your comments to `paul@nospam.buetow.org` :-) + Other *BSD related posts are: [2016-04-09 Jails and ZFS with Puppet on FreeBSD (You are currently reading this)](./2016-04-09-jails-and-zfs-on-freebsd-with-puppet.md) @@ -392,6 +394,4 @@ Other *BSD related posts are: [2022-10-30 Installing DTail on OpenBSD](./2022-10-30-installing-dtail-on-openbsd.md) [2024-01-13 One reason why I love OpenBSD](./2024-01-13-one-reason-why-i-love-openbsd.md) -E-Mail your comments to `paul@nospam.buetow.org` :-) - [Back to the main site](../) diff --git a/gemfeed/2021-04-22-dtail-the-distributed-log-tail-program.md b/gemfeed/2021-04-22-dtail-the-distributed-log-tail-program.md index 3430990e..8adf5491 100644 --- a/gemfeed/2021-04-22-dtail-the-distributed-log-tail-program.md +++ b/gemfeed/2021-04-22-dtail-the-distributed-log-tail-program.md @@ -103,6 +103,8 @@ Mimecast highly encourages you to have a look at DTail and submit an issue for a [https://dtail.dev](https://dtail.dev) +E-Mail your comments to `paul@nospam.buetow.org` :-) + Other related posts are: [2021-04-22 DTail - The distributed log tail program (You are currently reading this)](./2021-04-22-dtail-the-distributed-log-tail-program.md) @@ -110,6 +112,4 @@ Other related posts are: [2022-10-30 Installing DTail on OpenBSD](./2022-10-30-installing-dtail-on-openbsd.md) [2023-09-25 DTail usage examples](./2023-09-25-dtail-usage-examples.md) -E-Mail your comments to `paul@nospam.buetow.org` :-) - [Back to the main site](../) diff --git a/gemfeed/2021-06-05-gemtexter-one-bash-script-to-rule-it-all.md b/gemfeed/2021-06-05-gemtexter-one-bash-script-to-rule-it-all.md index bf69af53..41b23f71 100644 --- a/gemfeed/2021-06-05-gemtexter-one-bash-script-to-rule-it-all.md +++ b/gemfeed/2021-06-05-gemtexter-one-bash-script-to-rule-it-all.md @@ -163,6 +163,8 @@ It was quite a lot of fun writing Gemtexter. It's a relatively small project, bu I finally revamped my personal internet site and started to blog again. I wanted the result to be exactly how it is now: A slightly retro-inspired internet site built for fun with unconventional tools. +E-Mail your comments to `paul@nospam.buetow.org` :-) + Other related posts are: [2021-04-24 Welcome to the Geminispace](./2021-04-24-welcome-to-the-geminispace.md) @@ -175,6 +177,4 @@ Other related posts are: [2023-07-21 Gemtexter 2.1.0 - Let's Gemtext again³](./2023-07-21-gemtexter-2.1.0-lets-gemtext-again-3.md) [2023-12-10 Bash Golf Part 3](./2023-12-10-bash-golf-part-3.md) -E-Mail your comments to `paul@nospam.buetow.org` :-) - [Back to the main site](../) diff --git a/gemfeed/2022-03-06-the-release-of-dtail-4.0.0.md b/gemfeed/2022-03-06-the-release-of-dtail-4.0.0.md index dcfcea69..eb50d81a 100644 --- a/gemfeed/2022-03-06-the-release-of-dtail-4.0.0.md +++ b/gemfeed/2022-03-06-the-release-of-dtail-4.0.0.md @@ -286,6 +286,8 @@ I use usually DTail at work, but I have recently installed it on my personal Ope I am a bit busy at the moment with two other pet projects of mine (one internal work-project, and one personal one, the latter you will read about in the next couple of months). If you have ideas (or even a patch), then please don't hesitate to contact me (either via E-Mail or a request at GitHub). +E-Mail your comments to `paul@nospam.buetow.org` :-) + Other related posts are: [2021-04-22 DTail - The distributed log tail program](./2021-04-22-dtail-the-distributed-log-tail-program.md) @@ -297,6 +299,4 @@ Thanks! Paul -E-Mail your comments to `paul@nospam.buetow.org` :-) - [Back to the main site](../) diff --git a/gemfeed/2022-05-27-perl-is-still-a-great-choice.md b/gemfeed/2022-05-27-perl-is-still-a-great-choice.md index a1c9712e..4462b862 100644 --- a/gemfeed/2022-05-27-perl-is-still-a-great-choice.md +++ b/gemfeed/2022-05-27-perl-is-still-a-great-choice.md @@ -134,6 +134,8 @@ Btw.: Did you know that the first version of PHP was a set of Perl snippets? Onl [Why Perl is still relevant in 2022](https://stackoverflow.blog/2022/07/06/why-perl-is-still-relevant-in-2022/) +E-Mail your comments to `paul@nospam.buetow.org` :-) + Other related posts are: [2008-06-26 Perl Poetry](./2008-06-26-perl-poetry.md) @@ -141,6 +143,4 @@ Other related posts are: [2022-05-27 Perl is still a great choice (You are currently reading this)](./2022-05-27-perl-is-still-a-great-choice.md) [2023-05-01 Unveiling `guprecords.raku`: Global Uptime Records with Raku](./2023-05-01-unveiling-guprecords:-uptime-records-with-raku.md) -E-Mail your comments to `paul@nospam.buetow.org` :-) - [Back to the main site](../) diff --git a/gemfeed/2022-07-30-lets-encrypt-with-openbsd-and-rex.md b/gemfeed/2022-07-30-lets-encrypt-with-openbsd-and-rex.md index 2a54391a..16e8d656 100644 --- a/gemfeed/2022-07-30-lets-encrypt-with-openbsd-and-rex.md +++ b/gemfeed/2022-07-30-lets-encrypt-with-openbsd-and-rex.md @@ -656,6 +656,8 @@ OpenBSD suits perfectly here as all the tools are already part of the base insta Why re-inventing the wheel? I love that a `Rexfile` is just a Perl DSL. Also, OpenBSD comes with Perl in the base system. So no new programming language had to be added to my mix for the configuration management system. Also, the `acme.sh` shell script is not a Bash but a standard Bourne shell script, so I didn't have to install an additional shell as OpenBSD does not come with the Bash pre-installed. +E-Mail your comments to `paul@nospam.buetow.org` :-) + Other *BSD related posts are: [2016-04-09 Jails and ZFS with Puppet on FreeBSD](./2016-04-09-jails-and-zfs-on-freebsd-with-puppet.md) @@ -663,6 +665,4 @@ Other *BSD related posts are: [2022-10-30 Installing DTail on OpenBSD](./2022-10-30-installing-dtail-on-openbsd.md) [2024-01-13 One reason why I love OpenBSD](./2024-01-13-one-reason-why-i-love-openbsd.md) -E-Mail your comments to `paul@nospam.buetow.org` :-) - [Back to the main site](../) diff --git a/gemfeed/2023-03-25-gemtexter-2.0.0-lets-gemtext-again-2.md b/gemfeed/2023-03-25-gemtexter-2.0.0-lets-gemtext-again-2.md index c988a01d..422932e5 100644 --- a/gemfeed/2023-03-25-gemtexter-2.0.0-lets-gemtext-again-2.md +++ b/gemfeed/2023-03-25-gemtexter-2.0.0-lets-gemtext-again-2.md @@ -136,6 +136,8 @@ Optionally, when the `xmllint` binary is installed, Gemtexter will perform a sim Additionally, there were a couple of bug fixes, refactorings and overall improvements in the documentation made. +E-Mail your comments to `paul@nospam.buetow.org` :-) + Other related posts are: [2021-04-24 Welcome to the Geminispace](./2021-04-24-welcome-to-the-geminispace.md) @@ -144,6 +146,4 @@ Other related posts are: [2023-03-25 Gemtexter 2.0.0 - Let's Gemtext again² (You are currently reading this)](./2023-03-25-gemtexter-2.0.0-lets-gemtext-again-2.md) [2023-07-21 Gemtexter 2.1.0 - Let's Gemtext again³](./2023-07-21-gemtexter-2.1.0-lets-gemtext-again-3.md) -E-Mail your comments to `paul@nospam.buetow.org` :-) - [Back to the main site](../) diff --git a/gemfeed/2023-05-01-unveiling-guprecords b/gemfeed/2023-05-01-unveiling-guprecords new file mode 100644 index 00000000..e69de29b diff --git a/gemfeed/2023-06-01-kiss-server-monitoring-with-gogios.md b/gemfeed/2023-06-01-kiss-server-monitoring-with-gogios.md index 9d3a777f..fd651af1 100644 --- a/gemfeed/2023-06-01-kiss-server-monitoring-with-gogios.md +++ b/gemfeed/2023-06-01-kiss-server-monitoring-with-gogios.md @@ -236,12 +236,12 @@ There are plans to make it possible to execute certain checks only on certain no Gogios is a lightweight and straightforward monitoring tool that is perfect for small-scale environments. With its compatibility with the Nagios Check API, email notifications, and CRON-based scheduling, Gogios offers an easy-to-use solution for those looking to monitor a limited number of resources. I personally use it to execute around 500 checks on my personal server infrastructure. I am very happy with this solution. +E-Mail your comments to `paul@nospam.buetow.org` :-) + Other KISS-related posts are: [2021-09-12 Keep it simple and stupid](./2021-09-12-keep-it-simple-and-stupid.md) [2023-06-01 KISS server monitoring with Gogios (You are currently reading this)](./2023-06-01-kiss-server-monitoring-with-gogios.md) [2023-10-29 KISS static web photo albums with `photoalbum.sh`](./2023-10-29-kiss-static-web-photo-albums-with-photoalbum.sh.md) -E-Mail your comments to `paul@nospam.buetow.org` :-) - [Back to the main site](../) diff --git a/gemfeed/2023-07-21-gemtexter-2.1.0-lets-gemtext-again-3.md b/gemfeed/2023-07-21-gemtexter-2.1.0-lets-gemtext-again-3.md index a0f703a8..9d3e58f2 100644 --- a/gemfeed/2023-07-21-gemtexter-2.1.0-lets-gemtext-again-3.md +++ b/gemfeed/2023-07-21-gemtexter-2.1.0-lets-gemtext-again-3.md @@ -91,6 +91,8 @@ The resulting line in the HTML output will be something as follows: Additionally, there were a couple of bug fixes, refactorings and overall improvements in the documentation made. +E-Mail your comments to `paul@nospam.buetow.org` :-) + Other related posts are: [2021-04-24 Welcome to the Geminispace](./2021-04-24-welcome-to-the-geminispace.md) @@ -99,6 +101,4 @@ Other related posts are: [2023-03-25 Gemtexter 2.0.0 - Let's Gemtext again²](./2023-03-25-gemtexter-2.0.0-lets-gemtext-again-2.md) [2023-07-21 Gemtexter 2.1.0 - Let's Gemtext again³ (You are currently reading this)](./2023-07-21-gemtexter-2.1.0-lets-gemtext-again-3.md) -E-Mail your comments to `paul@nospam.buetow.org` :-) - [Back to the main site](../) diff --git a/gemfeed/2023-12-10-bash-golf-part-3.md b/gemfeed/2023-12-10-bash-golf-part-3.md index 7735bcb7..570793a7 100644 --- a/gemfeed/2023-12-10-bash-golf-part-3.md +++ b/gemfeed/2023-12-10-bash-golf-part-3.md @@ -355,6 +355,7 @@ echo baz So what happened? The `echo baz` line was appended to the script while it was still executed! And the interpreter also picked it up! It tells us that Bash evaluates each line as it encounters it. This can lead to nasty side effects when editing the script while it is still being executed! You should always keep this in mind! +E-Mail your comments to `paul@nospam.buetow.org` :-) Other related posts are: @@ -364,6 +365,4 @@ Other related posts are: [2022-01-01 Bash Golf Part 2](./2022-01-01-bash-golf-part-2.md) [2023-12-10 Bash Golf Part 3 (You are currently reading this)](./2023-12-10-bash-golf-part-3.md) -E-Mail your comments to `paul@nospam.buetow.org` :-) - [Back to the main site](../) -- cgit v1.2.3 From 50e4eb7ad8b3d17a23f18f2b0fc5bfe4e5cb7e1f Mon Sep 17 00:00:00 2001 From: Paul Buetow Date: Sat, 13 Jan 2024 23:34:24 +0200 Subject: Update content for md --- gemfeed/2008-06-26-perl-poetry.md | 4 +-- .../2011-05-07-perl-daemon-service-framework.md | 4 +-- gemfeed/2021-04-24-welcome-to-the-geminispace.md | 4 +-- .../2021-05-16-personal-bash-coding-style-guide.md | 4 +-- gemfeed/2021-09-12-keep-it-simple-and-stupid.md | 4 +-- gemfeed/2021-11-29-bash-golf-part-1.md | 4 +-- gemfeed/2022-01-01-bash-golf-part-2.md | 4 +-- ...022-08-27-gemtexter-1.1.0-lets-gemtext-again.md | 4 +-- gemfeed/2022-10-30-installing-dtail-on-openbsd.md | 4 +-- ...23-03-16-the-pragmatic-programmer-book-notes.md | 4 +-- ...-04-01-never-split-the-difference-book-notes.md | 4 +-- ...veiling-guprecords:-uptime-records-with-raku.md | 4 +-- ...023-05-06-the-obstacle-is-the-way-book-notes.md | 4 +-- ...7-17-career-guide-and-soft-skills-book-notes.md | 4 +-- gemfeed/2023-09-25-dtail-usage-examples.md | 4 +-- ...s-static-web-photo-albums-with-photoalbum.sh.md | 4 +-- gemfeed/2023-11-11-mind-management-book-notes.md | 4 +-- .../2024-01-13-one-reason-why-i-love-openbsd.md | 42 ++++++++-------------- 18 files changed, 49 insertions(+), 61 deletions(-) (limited to 'gemfeed') diff --git a/gemfeed/2008-06-26-perl-poetry.md b/gemfeed/2008-06-26-perl-poetry.md index 08f12e4c..9d6c6c02 100644 --- a/gemfeed/2008-06-26-perl-poetry.md +++ b/gemfeed/2008-06-26-perl-poetry.md @@ -161,12 +161,12 @@ Did you like what you saw? Have a look at Codeberg to see my other poems too: [https://codeberg.org/snonux/perl-poetry](https://codeberg.org/snonux/perl-poetry) +E-Mail your comments to `paul@nospam.buetow.org` :-) + Other related posts are: [2008-06-26 Perl Poetry (You are currently reading this)](./2008-06-26-perl-poetry.md) [2011-05-07 Perl Daemon (Service Framework)](./2011-05-07-perl-daemon-service-framework.md) [2022-05-27 Perl is still a great choice](./2022-05-27-perl-is-still-a-great-choice.md) -E-Mail your comments to `paul@nospam.buetow.org` :-) - [Back to the main site](../) diff --git a/gemfeed/2011-05-07-perl-daemon-service-framework.md b/gemfeed/2011-05-07-perl-daemon-service-framework.md index 3b4214c4..183a3de1 100644 --- a/gemfeed/2011-05-07-perl-daemon-service-framework.md +++ b/gemfeed/2011-05-07-perl-daemon-service-framework.md @@ -158,12 +158,12 @@ You can find PerlDaemon (including the examples) at: [https://codeberg.org/snonux/perldaemon](https://codeberg.org/snonux/perldaemon) +E-Mail your comments to `paul@nospam.buetow.org` :-) + Other related posts are: [2008-06-26 Perl Poetry](./2008-06-26-perl-poetry.md) [2011-05-07 Perl Daemon (Service Framework) (You are currently reading this)](./2011-05-07-perl-daemon-service-framework.md) [2022-05-27 Perl is still a great choice](./2022-05-27-perl-is-still-a-great-choice.md) -E-Mail your comments to `paul@nospam.buetow.org` :-) - [Back to the main site](../) diff --git a/gemfeed/2021-04-24-welcome-to-the-geminispace.md b/gemfeed/2021-04-24-welcome-to-the-geminispace.md index fc9e43e9..a7231f44 100644 --- a/gemfeed/2021-04-24-welcome-to-the-geminispace.md +++ b/gemfeed/2021-04-24-welcome-to-the-geminispace.md @@ -78,6 +78,8 @@ Check out one of the following links for more information about Gemini. For exam [gemini://geminiprotocol.net/](gemini://geminiprotocol.net/) [https://geminiprotocol.net/](https://geminiprotocol.net/) +E-Mail your comments to `paul@nospam.buetow.org` :-) + Other related posts are: [2021-04-24 Welcome to the Geminispace (You are currently reading this)](./2021-04-24-welcome-to-the-geminispace.md) @@ -86,6 +88,4 @@ Other related posts are: [2023-03-25 Gemtexter 2.0.0 - Let's Gemtext again²](./2023-03-25-gemtexter-2.0.0-lets-gemtext-again-2.md) [2023-07-21 Gemtexter 2.1.0 - Let's Gemtext again³](./2023-07-21-gemtexter-2.1.0-lets-gemtext-again-3.md) -E-Mail your comments to `paul@nospam.buetow.org` :-) - [Back to the main site](../) diff --git a/gemfeed/2021-05-16-personal-bash-coding-style-guide.md b/gemfeed/2021-05-16-personal-bash-coding-style-guide.md index 58bb7e76..1389be26 100644 --- a/gemfeed/2021-05-16-personal-bash-coding-style-guide.md +++ b/gemfeed/2021-05-16-personal-bash-coding-style-guide.md @@ -384,6 +384,8 @@ I also highly recommend having a read through the "Advanced Bash-Scripting Guide [Advanced Bash-Scripting Guide](https://tldp.org/LDP/abs/html/) +E-Mail your comments to `paul@nospam.buetow.org` :-) + Other related posts are: [2021-05-16 Personal Bash coding style guide (You are currently reading this)](./2021-05-16-personal-bash-coding-style-guide.md) @@ -392,6 +394,4 @@ Other related posts are: [2022-01-01 Bash Golf Part 2](./2022-01-01-bash-golf-part-2.md) [2023-12-10 Bash Golf Part 3](./2023-12-10-bash-golf-part-3.md) -E-Mail your comments to `paul@nospam.buetow.org` :-) - [Back to the main site](../) diff --git a/gemfeed/2021-09-12-keep-it-simple-and-stupid.md b/gemfeed/2021-09-12-keep-it-simple-and-stupid.md index c596b881..5cdb8e1d 100644 --- a/gemfeed/2021-09-12-keep-it-simple-and-stupid.md +++ b/gemfeed/2021-09-12-keep-it-simple-and-stupid.md @@ -94,14 +94,14 @@ There is, however, a trap. The more you spend time with things, the more these t Enough ranted for now! +E-Mail your comments to `paul@nospam.buetow.org` :-) + Other KISS-related posts are: [2021-09-12 Keep it simple and stupid (You are currently reading this)](./2021-09-12-keep-it-simple-and-stupid.md) [2023-06-01 KISS server monitoring with Gogios](./2023-06-01-kiss-server-monitoring-with-gogios.md) [2023-10-29 KISS static web photo albums with `photoalbum.sh`](./2023-10-29-kiss-static-web-photo-albums-with-photoalbum.sh.md) -E-Mail your comments to `paul@nospam.buetow.org` :-) - > Controversially, a lack of features is a feature. Enjoy your peace an quiet. - Michael W Lucas [Back to the main site](../) diff --git a/gemfeed/2021-11-29-bash-golf-part-1.md b/gemfeed/2021-11-29-bash-golf-part-1.md index 63ffebb0..062a7cfd 100644 --- a/gemfeed/2021-11-29-bash-golf-part-1.md +++ b/gemfeed/2021-11-29-bash-golf-part-1.md @@ -464,6 +464,8 @@ In the Bash you will have to fall back to an external command like "bc" (the arb See you later for the next post of this series. +E-Mail your comments to `paul@nospam.buetow.org` :-) + Other related posts are: [2021-05-16 Personal Bash coding style guide](./2021-05-16-personal-bash-coding-style-guide.md) @@ -472,6 +474,4 @@ Other related posts are: [2022-01-01 Bash Golf Part 2](./2022-01-01-bash-golf-part-2.md) [2023-12-10 Bash Golf Part 3](./2023-12-10-bash-golf-part-3.md) -E-Mail your comments to `paul@nospam.buetow.org` :-) - [Back to the main site](../) diff --git a/gemfeed/2022-01-01-bash-golf-part-2.md b/gemfeed/2022-01-01-bash-golf-part-2.md index 88a17126..e7d11702 100644 --- a/gemfeed/2022-01-01-bash-golf-part-2.md +++ b/gemfeed/2022-01-01-bash-golf-part-2.md @@ -483,6 +483,8 @@ To change this behaviour, pipefile can be used. Now, the pipes exit status is 1 1 ``` +E-Mail your comments to `paul@nospam.buetow.org` :-) + Other related posts are: [2021-05-16 Personal Bash coding style guide](./2021-05-16-personal-bash-coding-style-guide.md) @@ -491,6 +493,4 @@ Other related posts are: [2022-01-01 Bash Golf Part 2 (You are currently reading this)](./2022-01-01-bash-golf-part-2.md) [2023-12-10 Bash Golf Part 3](./2023-12-10-bash-golf-part-3.md) -E-Mail your comments to `paul@nospam.buetow.org` :-) - [Back to the main site](../) diff --git a/gemfeed/2022-08-27-gemtexter-1.1.0-lets-gemtext-again.md b/gemfeed/2022-08-27-gemtexter-1.1.0-lets-gemtext-again.md index fd162e92..358c5866 100644 --- a/gemfeed/2022-08-27-gemtexter-1.1.0-lets-gemtext-again.md +++ b/gemfeed/2022-08-27-gemtexter-1.1.0-lets-gemtext-again.md @@ -85,6 +85,8 @@ Additionally, there were a couple of bug fixes, refactorings and overall improve Overall I think it's a pretty solid `1.1.0` release without anything groundbreaking (therefore no major version jump). But I am happy about it. +E-Mail your comments to `paul@nospam.buetow.org` :-) + Other related posts are: [2021-04-24 Welcome to the Geminispace](./2021-04-24-welcome-to-the-geminispace.md) @@ -93,6 +95,4 @@ Other related posts are: [2023-03-25 Gemtexter 2.0.0 - Let's Gemtext again²](./2023-03-25-gemtexter-2.0.0-lets-gemtext-again-2.md) [2023-07-21 Gemtexter 2.1.0 - Let's Gemtext again³](./2023-07-21-gemtexter-2.1.0-lets-gemtext-again-3.md) -E-Mail your comments to `paul@nospam.buetow.org` :-) - [Back to the main site](../) diff --git a/gemfeed/2022-10-30-installing-dtail-on-openbsd.md b/gemfeed/2022-10-30-installing-dtail-on-openbsd.md index c0bc56ed..849f0407 100644 --- a/gemfeed/2022-10-30-installing-dtail-on-openbsd.md +++ b/gemfeed/2022-10-30-installing-dtail-on-openbsd.md @@ -339,6 +339,8 @@ Check out the following for more information: [https://github.com/mimecast/dtail](https://github.com/mimecast/dtail) [https://www.rexify.org](https://www.rexify.org) +E-Mail your comments to `paul@nospam.buetow.org` :-) + Other related posts are: [2021-04-22 DTail - The distributed log tail program](./2021-04-22-dtail-the-distributed-log-tail-program.md) @@ -346,6 +348,4 @@ Other related posts are: [2022-10-30 Installing DTail on OpenBSD (You are currently reading this)](./2022-10-30-installing-dtail-on-openbsd.md) [2023-09-25 DTail usage examples](./2023-09-25-dtail-usage-examples.md) -E-Mail your comments to `paul@nospam.buetow.org` :-) - [Back to the main site](../) diff --git a/gemfeed/2023-03-16-the-pragmatic-programmer-book-notes.md b/gemfeed/2023-03-16-the-pragmatic-programmer-book-notes.md index 7c1ca4b4..c44ad505 100644 --- a/gemfeed/2023-03-16-the-pragmatic-programmer-book-notes.md +++ b/gemfeed/2023-03-16-the-pragmatic-programmer-book-notes.md @@ -76,6 +76,8 @@ How to motivate others to contribute something (e.g. ideas to a startup): By working together, everyone contributes what they can, achieving a greater good together. +E-Mail your comments to `paul@nospam.buetow.org` :-) + Other book notes of mine are: [2023-03-16 "The Pragmatic Programmer" book notes (You are currently reading this)](./2023-03-16-the-pragmatic-programmer-book-notes.md) @@ -84,7 +86,5 @@ Other book notes of mine are: [2023-07-17 "Software Developmers Career Guide and Soft Skills" book notes](./2023-07-17-career-guide-and-soft-skills-book-notes.md) [2023-11-11 "Mind Management" book notes](./2023-11-11-mind-management-book-notes.md) -E-Mail your comments to `paul@nospam.buetow.org` :-) - [More books and other resources I found useful.](../resources.md) [Back to the main site](../) diff --git a/gemfeed/2023-04-01-never-split-the-difference-book-notes.md b/gemfeed/2023-04-01-never-split-the-difference-book-notes.md index 953e8e73..f43360f3 100644 --- a/gemfeed/2023-04-01-never-split-the-difference-book-notes.md +++ b/gemfeed/2023-04-01-never-split-the-difference-book-notes.md @@ -120,6 +120,8 @@ Establish a range at top places like corp. I get... (e.g. remote London on a pro Slow.... it.... down.... +E-Mail your comments to `paul@nospam.buetow.org` :-) + Other book notes of mine are: [2023-03-16 "The Pragmatic Programmer" book notes](./2023-03-16-the-pragmatic-programmer-book-notes.md) @@ -128,6 +130,4 @@ Other book notes of mine are: [2023-07-17 "Software Developmers Career Guide and Soft Skills" book notes](./2023-07-17-career-guide-and-soft-skills-book-notes.md) [2023-11-11 "Mind Management" book notes](./2023-11-11-mind-management-book-notes.md) -E-Mail your comments to `paul@nospam.buetow.org` :-) - [Back to the main site](../) diff --git a/gemfeed/2023-05-01-unveiling-guprecords:-uptime-records-with-raku.md b/gemfeed/2023-05-01-unveiling-guprecords:-uptime-records-with-raku.md index 5fccb52b..b4fe170e 100644 --- a/gemfeed/2023-05-01-unveiling-guprecords:-uptime-records-with-raku.md +++ b/gemfeed/2023-05-01-unveiling-guprecords:-uptime-records-with-raku.md @@ -147,6 +147,8 @@ So far, I have only scratched the surface of what Raku can do. I hope to find mo * A social media sharing scheduler a la `buffer.com`. I am using Buffer at the moment to share posts on Mastadon, Twitter, Telegram and LinkedIn, but it is proprietary and also it's not really reliable. * Rewrite the static photo album generator of `irregular.ninja` in Raku (from Bash). +E-Mail your comments to hi@foo.zone :-) + Other related posts are: [2008-06-26 Perl Poetry](./2008-06-26-perl-poetry.md) @@ -155,6 +157,4 @@ Other related posts are: [2022-06-15 Sweating the small stuff - Tiny projects of mine](./2022-06-15-sweating-the-small-stuff.md) [2023-05-01 Unveiling `guprecords.raku`: Global Uptime Records with Raku (You are currently reading this)](./2023-05-01-unveiling-guprecords:-uptime-records-with-raku.md) -E-Mail your comments to hi@foo.zone :-) - [Back to the main site](../) diff --git a/gemfeed/2023-05-06-the-obstacle-is-the-way-book-notes.md b/gemfeed/2023-05-06-the-obstacle-is-the-way-book-notes.md index 9d8ab114..5d42d741 100644 --- a/gemfeed/2023-05-06-the-obstacle-is-the-way-book-notes.md +++ b/gemfeed/2023-05-06-the-obstacle-is-the-way-book-notes.md @@ -82,6 +82,8 @@ Should I hate people who hate me? That's their problem and not mine. Be always c Life is a marathon, not a sprint. Each obstacle we overcome prepares us for the next one. Remember, the obstacle is not just a barrier to be turned upside down; it can also be used as a catapult to propel us forward. By embracing challenges and using them as opportunities for growth, we become stronger, more adaptable, and, ultimately, more successful. +E-Mail your comments to `paul@nospam.buetow.org` :-) + Other book notes of mine are: [2023-03-16 "The Pragmatic Programmer" book notes](./2023-03-16-the-pragmatic-programmer-book-notes.md) @@ -90,7 +92,5 @@ Other book notes of mine are: [2023-07-17 "Software Developmers Career Guide and Soft Skills" book notes](./2023-07-17-career-guide-and-soft-skills-book-notes.md) [2023-11-11 "Mind Management" book notes](./2023-11-11-mind-management-book-notes.md) -E-Mail your comments to `paul@nospam.buetow.org` :-) - [More books and other resources I found useful.](../resources.md) [Back to the main site](../) diff --git a/gemfeed/2023-07-17-career-guide-and-soft-skills-book-notes.md b/gemfeed/2023-07-17-career-guide-and-soft-skills-book-notes.md index 623685dc..5b6d1220 100644 --- a/gemfeed/2023-07-17-career-guide-and-soft-skills-book-notes.md +++ b/gemfeed/2023-07-17-career-guide-and-soft-skills-book-notes.md @@ -272,6 +272,8 @@ Unit testing Vs regression testing: Unit tests test the smallest possible unit a * The war of Art (to combat procrastination) * Willpower Instinct +E-Mail your comments to `paul@nospam.buetow.org` :-) + Other book notes of mine are: [2023-03-16 "The Pragmatic Programmer" book notes](./2023-03-16-the-pragmatic-programmer-book-notes.md) @@ -280,7 +282,5 @@ Other book notes of mine are: [2023-07-17 "Software Developmers Career Guide and Soft Skills" book notes (You are currently reading this)](./2023-07-17-career-guide-and-soft-skills-book-notes.md) [2023-11-11 "Mind Management" book notes](./2023-11-11-mind-management-book-notes.md) -E-Mail your comments to `paul@nospam.buetow.org` :-) - [More books and other resources I found useful.](../resources.md) [Back to the main site](../) diff --git a/gemfeed/2023-09-25-dtail-usage-examples.md b/gemfeed/2023-09-25-dtail-usage-examples.md index 90c829a9..6b85775e 100644 --- a/gemfeed/2023-09-25-dtail-usage-examples.md +++ b/gemfeed/2023-09-25-dtail-usage-examples.md @@ -228,6 +228,8 @@ diff /etc/test /etc/passwd Use `--help` for more available options. Or go to the DTail page for more information! Hope you find DTail useful! +E-Mail your comments to `paul@nospam.buetow.org` :-) + Other related posts are: [2021-04-22 DTail - The distributed log tail program](./2021-04-22-dtail-the-distributed-log-tail-program.md) @@ -239,6 +241,4 @@ I hope you find the tools presented in this post useful! Paul -E-Mail your comments to `paul@nospam.buetow.org` :-) - [Back to the main site](../) diff --git a/gemfeed/2023-10-29-kiss-static-web-photo-albums-with-photoalbum.sh.md b/gemfeed/2023-10-29-kiss-static-web-photo-albums-with-photoalbum.sh.md index 140c9925..c0a94752 100644 --- a/gemfeed/2023-10-29-kiss-static-web-photo-albums-with-photoalbum.sh.md +++ b/gemfeed/2023-10-29-kiss-static-web-photo-albums-with-photoalbum.sh.md @@ -259,6 +259,8 @@ Also, I like the CSS effects which I recently added. In particular, for the Irre [`photoalbum.sh` source code on Codeberg.](https://codeberg.org/snonux/photoalbum) +E-Mail your comments to `paul@nospam.buetow.org` :-) + Other Bash and KISS-related posts are: [2021-05-16 Personal Bash coding style guide](./2021-05-16-personal-bash-coding-style-guide.md) @@ -270,6 +272,4 @@ Other Bash and KISS-related posts are: [2023-10-29 KISS static web photo albums with `photoalbum.sh` (You are currently reading this)](./2023-10-29-kiss-static-web-photo-albums-with-photoalbum.sh.md) [2023-12-10 Bash Golf Part 3](./2023-12-10-bash-golf-part-3.md) -E-Mail your comments to `paul@nospam.buetow.org` :-) - [Back to the main site](../) diff --git a/gemfeed/2023-11-11-mind-management-book-notes.md b/gemfeed/2023-11-11-mind-management-book-notes.md index c19ba472..b0d86f16 100644 --- a/gemfeed/2023-11-11-mind-management-book-notes.md +++ b/gemfeed/2023-11-11-mind-management-book-notes.md @@ -91,6 +91,8 @@ You could schedule exploratory tasks when you are under grief. Sound systems sho * Talk slowly and deepen your voice a bit to appear more confident. You will also become more confident. * Also, use power positions for better confidence. +E-Mail your comments to `paul@nospam.buetow.org` :-) + Other book notes of mine are: [2023-03-16 "The Pragmatic Programmer" book notes](./2023-03-16-the-pragmatic-programmer-book-notes.md) @@ -99,7 +101,5 @@ Other book notes of mine are: [2023-07-17 "Software Developmers Career Guide and Soft Skills" book notes](./2023-07-17-career-guide-and-soft-skills-book-notes.md) [2023-11-11 "Mind Management" book notes (You are currently reading this)](./2023-11-11-mind-management-book-notes.md) -E-Mail your comments to `paul@nospam.buetow.org` :-) - [More books and other resources I found useful.](../resources.md) [Back to the main site](../) diff --git a/gemfeed/2024-01-13-one-reason-why-i-love-openbsd.md b/gemfeed/2024-01-13-one-reason-why-i-love-openbsd.md index b52913e5..d9a8c0e1 100644 --- a/gemfeed/2024-01-13-one-reason-why-i-love-openbsd.md +++ b/gemfeed/2024-01-13-one-reason-why-i-love-openbsd.md @@ -3,31 +3,19 @@ > Published at 2024-01-13T22:55:33+02:00 ``` - . - A ; - | ,--,-/ \---,-/| , - _|\,'. /| /| `/|-. - \`.' /| , `;. - ,'\ A A A A _ /| `.; - ,/ _ A _ / _ /| ; - /\ / \ , , A / / `/| - /_| | _ \ , , ,/ \ - // | |/ `.\ ,- , , ,/ ,/ \/ - / @| |@ / /' \ \ , > /| ,--. - |\_/ \_/ / | | , ,/ \ ./' __:.. - | __ __ | | | .--. , > > |-' / ` - ,/| / ' \ | | | \ , | / - / |<--.__,->| | | . `. > > / ( -/_,' \\ ^ / \ / / `. >-- /^\ | - \\___/ \ / / \__' \ \ \/ \ | - `. |/ , , /`\ \ ) - \ ' |/ , V \ / `-\ - `|/ ' V V \ \.' \_ - '`-. V V \./'\ - `|/-. \ / \ /,---`\ kat - n - / `._____V_____V' - ' ' + FISHKISSFISHKIS + SFISHKISSFISHKISSFISH F + ISHK ISSFISHKISSFISHKISS FI + SHKISS FISHKISSFISHKISSFISS FIS +HKISSFISHKISSFISHKISSFISHKISSFISH KISS + FISHKISSFISHKISSFISHKISSFISHKISS FISHK + SSFISHKISSFISHKISSFISHKISSFISHKISSF + ISHKISSFISHKISSFISHKISSFISHKISSF ISHKI +SSFISHKISSFISHKISSFISHKISSFISHKIS SFIS + HKISSFISHKISSFISHKISSFISHKISS FIS + HKISSFISHKISSFISHKISSFISHK IS + SFISHKISSFISHKISSFISH K + ISSFISHKISSFISHK ``` I just upgraded my OpenBSD's from `7.3` to `7.4` by following the unattended upgrade guide: @@ -59,6 +47,8 @@ BTW: are you looking for an opinionated OpenBSD VM hoster? OpenBSD Amsterdam may [https://openbsd.amsterdam](https://openbsd.amsterdam) +E-Mail your comments to `paul@nospam.buetow.org` :-) + Other *BSD related posts are: [2016-04-09 Jails and ZFS with Puppet on FreeBSD](./2016-04-09-jails-and-zfs-on-freebsd-with-puppet.md) @@ -66,6 +56,4 @@ Other *BSD related posts are: [2022-10-30 Installing DTail on OpenBSD](./2022-10-30-installing-dtail-on-openbsd.md) [2024-01-13 One reason why I love OpenBSD (You are currently reading this)](./2024-01-13-one-reason-why-i-love-openbsd.md) -E-Mail your comments to `paul@nospam.buetow.org` :-) - [Back to the main site](../) -- cgit v1.2.3 From c0d950b762d513b34d81c93d7e15a3f90ee0fe33 Mon Sep 17 00:00:00 2001 From: Paul Buetow Date: Sun, 14 Jan 2024 00:23:23 +0200 Subject: Update content for md --- gemfeed/2024-01-13-one-reason-why-i-love-openbsd.md | 10 +++++----- 1 file changed, 5 insertions(+), 5 deletions(-) (limited to 'gemfeed') diff --git a/gemfeed/2024-01-13-one-reason-why-i-love-openbsd.md b/gemfeed/2024-01-13-one-reason-why-i-love-openbsd.md index d9a8c0e1..d0fe6a99 100644 --- a/gemfeed/2024-01-13-one-reason-why-i-love-openbsd.md +++ b/gemfeed/2024-01-13-one-reason-why-i-love-openbsd.md @@ -23,16 +23,16 @@ I just upgraded my OpenBSD's from `7.3` to `7.4` by following the unattended upg [https://www.openbsd.org/faq/upgrade74.html](https://www.openbsd.org/faq/upgrade74.html) ```shell -doas installboot sd0 # Update the bootloader (not for every upgrade required) -doas sysupgrade # Update all binaries (including Kernel) +$ doas installboot sd0 # Update the bootloader (not for every upgrade required) +$ doas sysupgrade # Update all binaries (including Kernel) ``` `sysupgrade` downloaded and upgraded to the next release and rebooted the system. After the reboot, I run: ```shell -doas sysmerge # Update system configuration files -doas pkg_add -u # Update all packages -doas reboot # Just in case, reboot one more time +$ doas sysmerge # Update system configuration files +$ doas pkg_add -u # Update all packages +$ doas reboot # Just in case, reboot one more time ``` That's it! Took me around 5 minutes in total! No issues, only these few comands, only 5 minutes! It just works! No problems, no conflicts, no tons (actually none) config file merge conflicts. -- cgit v1.2.3 From 21d368883bd1b52f1b1c31ac58849924b9b6724e Mon Sep 17 00:00:00 2001 From: Paul Buetow Date: Sun, 4 Feb 2024 00:52:36 +0200 Subject: Update content for md --- ...024-02-04-from-babylon5.buetow.org-to-.cloud.md | 163 +++++++++++++++++++++ .../from-.org-to-.cloud/old-man-yells-at-cloud.jpg | Bin 0 -> 48052 bytes gemfeed/index.md | 1 + 3 files changed, 164 insertions(+) create mode 100644 gemfeed/2024-02-04-from-babylon5.buetow.org-to-.cloud.md create mode 100644 gemfeed/from-.org-to-.cloud/old-man-yells-at-cloud.jpg (limited to 'gemfeed') diff --git a/gemfeed/2024-02-04-from-babylon5.buetow.org-to-.cloud.md b/gemfeed/2024-02-04-from-babylon5.buetow.org-to-.cloud.md new file mode 100644 index 00000000..2ac386cd --- /dev/null +++ b/gemfeed/2024-02-04-from-babylon5.buetow.org-to-.cloud.md @@ -0,0 +1,163 @@ +# From `babylon5.buetow.org` to `*.buetow.cloud` + +> Published at 2024-02-04T00:50:50+02:00 + +Recently, my employer sent me to a week-long AWS course. After the course, there wasn't any hands-on project I could dive into immediately, so I moved parts of my personal infrastructure to AWS to level up a bit through practical hands-on. + +So, I migrated all of my Docker-based self-hosted services to AWS. Usually, I am not a big fan of big cloud providers and instead use smaller hosters or indie providers and self-made solutions. However, I also must go with the times and try out technologies currently hot on the job market. I don't want to become the old man who yells at cloud :D + +[![Old man yells at cloud](./from-.org-to-.cloud/old-man-yells-at-cloud.jpg "Old man yells at cloud")](./from-.org-to-.cloud/old-man-yells-at-cloud.jpg) + +## The old `*.buetow.org` way + +Before the migration, all those services were reachable through `buetow.org`-subdomains (Buetow is my last name) and ran on Docker containers on a single Rocky Linux 9 VM at Hetzner. And there was a Nginx reverse proxy with TLS offloading (with Let's Encrypt certificates). The Rocky Linux 9's hostname was `babylon5.buetow.org` (based on the Science Fiction series). + +[https://en.wikipedia.org/wiki/Babylon_5](https://en.wikipedia.org/wiki/Babylon_5) + +The downsides of this setup were: + +* Not highly available. If the server goes down, no service is reachable until it's repaired. To be fair, the Hetzner cloud VM is redundant by itself and would have re-spawned on a different worker node, I suppose. +* Manual installation. + +About the manual installation part: I could have used a configuration management system like Rexify, Puppet, etc. But I decided against it back in time, as setting up Docker containers isn't so complicated through simple start scripts. And it's only a single Linux box where a manual installation is less painful. However, regular backups (which Hetzner can do automatically for you) were a must. + +The benefits of this setup were: + +* KISS (Keep it Simple Stupid) +* Cheap + +## I kept my `buetow.org` OpenBSD boxes alive + +As pointed out, I only migrated the Docker-based self-hosted services (which run on the Babylon 5 Rocky Linux box) to AWS. Many self-hostable apps come with ready-to-use container images, making deploying them easy. + +My other two OpenBSD VMs (`blowfish.buetow.org`, hosted at Hetzner, and `fishfinger.buetow.org`, hosted at OpenBSD Amsterdam) still run (and they will keep running) the following services: + +* HTTP server for my websites (e.g. `https://foo.zone`, ...) +* ACME for Let's Encrypt TLS certificate auto-renewal. +* Gemini server for my capsules (e.g. `gemini://foo.zone`) +* Authoritative DNS servers for my domains (but `buetow.cloud`, which is on Route 53 now) +* Mail transfer agent (MTA) +* My Gogios monitoring system. +* My IRC bouncer. + +It is all automated with Rex, aka Rexify. This OpenBSD setup is my "fun" or "for pleasure" setup. Whereas the Rocky Linux 9 one I always considered the "pratical means to the end"-setup to have 3rd party Docker containers up and running with as little work as possible. + +[(R)?ex, the friendly automation framework](https://www.rexify.org) +[KISS server monitoring with Gogios](./2023-06-01-kiss-server-monitoring-with-gogios.md) +[Let's encrypt with OpenBSD and Rex](./2022-07-30-lets-encrypt-with-openbsd-and-rex.md) + +## The new `*.buetow.cloud` way + +With AWS, I decided to get myself a new domain name, as I could fully separate my AWS setup from my conventional setup and give Route 53 as an authoritative DNS a spin. + +I decided to automate everything with Terraform, as I wanted to learn to use it as it appears standard now in the job market. + +All services are installed automatically to AWS ECS Fargate. ECS is AWS's Elastic Container Service, and Fargate automatically manages the underlying hardware infrastructure (e.g., how many CPUs, RAM, etc.) for me. So I don't have to bother about having enough EC2 instances to serve my demands, for example. + +The authoritative DNS for the `buetow.cloud` domain is AWS Route 53. TLS certificates are free here at AWS and offloaded through the AWS Application Load Balancer. The LB acts as a proxy to the ECS container instances of the services. A few services I run in ECS Fargate also require the AWS Network Load Balancer. + +All services require some persistent storage. For that, I use an encrypted EFS file system, automatically replicated across all AZs (availability zones) of my region of choice, `eu-central-1`. + +In case of an AZ outage, I could re-deploy all the failed containers in another AZ, and all the data would still be there. + +The EFS automatically gets backed up by AWS for me following their standard Backup schedule. The daily backups are kept for 30 days. + +Domain registration, TLS certificate configuration and configuration of the EFS backup were quickly done through the AWS web interface. These were only one-off tasks, so they weren't fully automated through Terraform. + +You can find all Terraform manifests here: + +[https://codeberg.org/snonux/terraform](https://codeberg.org/snonux/terraform) + +Whereas: + +* `org-buetow-base` sets up the bare VPS, EFS, and Route 53 zone. It's the requirement for most other Terraform manifests in this repository. +* `org-buetow-bastion` sets up a minimal Amazon Linux EC2 instance where I can manually SSH into and look at the EFS file system (if required). +* `org-buetow-elb` sets up the Elastic Load Balancer, a prerequisite for any service running in ECS Fargate. +* `org-buetow-ecs` finally sets up and deploys all the Docker apps mentioned above. Any apps can be turned on or off via the `variables.tf` file. + +## The container apps + +And here, finally, is the list of all the container apps my Terraform manifests deploy. The FQDNs here may not be reachable. I spin them up only on demand (for cost reasons). All services are fully dual-stacked (IPv4 & IPv6). + +### `flux.buetow.cloud` + +Miniflux is a minimalist and opinionated feed reader. With the move to AWS, I also retired my bloated instance of NextCloud. So, with Miniflux, I retired from NextCloud News. + +Miniflux requires two ECS containers. One is the Miniflux app, and the other is the PostgreSQL DB. + +[https://miniflux.app/](https://miniflux.app/) + + +### `audiobookshelf.buetow.cloud` + +Audiobookshelf was the first Docker app I installed. It is a Self-hosted audiobook and podcast server. It comes with a neat web interface, and there is also an Android app available, which works also in offline mode. This is great, as I only have the ECS instance sometimes running for cost savings. + +With Audiobookshelf, I replaced my former Audible subscription and my separate Podcast app. For Podcast synchronisation I used to use the Gpodder NextCloud sync app. But that one I retired now with Audiobookshelf as well :-) + +[https://www.audiobookshelf.org](https://www.audiobookshelf.org) + +### `syncthing.buetow.cloud` + +Syncthing is a continuous file synchronisation program. In real-time, it synchronises files between two or more computers, safely protected from prying eyes. Your data is your own, and you deserve to choose where it is stored, whether it is shared with some third party, and how it's transmitted over the internet. + +With Syncthing, I retired my old NextCloud Files and file sync client on all my devices. I also quit my NextCloud Notes setup. All my Notes are now plain Markdown files in a `Notes` directory. On Android, I can edit them with any text or Markdown editor (e.g. Obsidian), and they will be synchronised via Syncthing to my other computers, both forward and back. + +I use Syncthing to synchronise some of my Phone's data (e.g. Notes, Pictures and other documents). Initially, I synced all of my pictures, videos, etc., with AWS. But that was pretty expensive. So for now, I use it only whilst travelling. Otherwise, I will use my Syncthing instance here on my LAN (I have a cheap cloud backup in AWS S3 Glacier Deep Archive, but that's for another blog post). + +[https://syncthing.net/](https://syncthing.net/) + +### `radicale.buetow.cloud` + +Radicale is an excellent minimalist WebDAV calendar and contact synchronisation server. It was good enough to replace my NextCloud Calendar and NextCloud Contacts setup. Unfortunately, there wasn't a ready-to-use Docker image. So, I created my own. + +On Android, it works great together with the DAVx5 client for synchronisation. + +[https://radicale.org/](https://radicale.org/) +[https://codeberg.org/snonux/docker-radicale-server](https://codeberg.org/snonux/docker-radicale-server) +[https://www.davx5.com/](https://www.davx5.com/) + +### `bag.buetow.cloud` + +Wallabag is a self-hostable "save now - read later" service, and it also comes with an Android app which also has an offline mode. Think of Getpocket, but open-source! + +[https://wallabag.org/](https://wallabag.org/) +[https://github.com/wallabag/wallabag](https://github.com/wallabag/wallabag) + +### `anki.buetow.cloud` + +Anki is a great (the greatest) flash-card learning program. I am currently learning Bulgarian as my 3rd language. There is also an Android app that has an offline mode, and advanced users can also self-host the server `anki-sync-server`. For some reason (not going into the details here), I had to build my own Docker image for the server. + +[https://apps.ankiweb.net/](https://apps.ankiweb.net/) +[https://codeberg.org/snonux/docker-anki-sync-server](https://codeberg.org/snonux/docker-anki-sync-server) + +### `vault.buetow.cloud` + +Vaultwarden is an alternative implementation of the Bitwarden server API written in Rust and compatible with upstream Bitwarden clients, perfect for self-hosted deployment where running the official resource-heavy service might not be ideal. So, this is a great password manager server which can be used with any Bitwarden Android app. + +I currently don't use it, but I may in the future. I made it available in my ECS Fargate setup anyway for now. + +[https://github.com/dani-garcia/vaultwarden](https://github.com/dani-garcia/vaultwarden) + +I currently use `geheim`, a Ruby command line tool I wrote, as my current password manager. You can read a little bit about it here under "More": + +[Sweating the small stuff ](./2022-06-15-sweating-the-small-stuff.md) + +### `bastion.buetow.cloud` + +This is a tiny ARM-based Amazon Linux EC2 instance, which I sometimes spin up for investigation or manual work on my EFS file system in AWS. + +## Conclusion + +I have learned a lot about AWS and Terraform during this migration. This was actually my first AWS hands-on project with practical use. + +All of this was not particularly difficult (but at times a bit confusing). I see the use of Terraform managing more extensive infrastructures (it was even helpful for my small setup here). At least I know now what all the buzz is about :-). I don't think Terraform is a nice language. It get's it's job done, but it could be more elegant IMHO. + +Deploying updates to AWS are much easier, and some of the manual maintenance burdens of my Rocky Linux 9 VM are no longer needed. So I will have more time for other projects! + +Will I keep it in the cloud? I don't know yet. But maybe I won't renew the `buetow.cloud` domain and instead will use `*.cloud.buetow.org` or `*.aws.buetow.org` subdomains. + +Will the AWS setup be cheaper than my old Rocky Linux setup? It might be more affordable as I only turn ECS and the load balancers on or off on-demand. Time will tell! The first forecasts suggest that it will be around the same costs. + +E-Mail your comments to `paul@nospam.buetow.org` :-) + +[Back to the main site](../) diff --git a/gemfeed/from-.org-to-.cloud/old-man-yells-at-cloud.jpg b/gemfeed/from-.org-to-.cloud/old-man-yells-at-cloud.jpg new file mode 100644 index 00000000..da1170f8 Binary files /dev/null and b/gemfeed/from-.org-to-.cloud/old-man-yells-at-cloud.jpg differ diff --git a/gemfeed/index.md b/gemfeed/index.md index 33d72833..71feea8a 100644 --- a/gemfeed/index.md +++ b/gemfeed/index.md @@ -2,6 +2,7 @@ ## To be in the .zone! +[2024-02-04 - From `babylon5.buetow.org` to `*.buetow.cloud`](./2024-02-04-from-babylon5.buetow.org-to-.cloud.md) [2024-01-13 - One reason why I love OpenBSD](./2024-01-13-one-reason-why-i-love-openbsd.md) [2024-01-09 - Site Reliability Engineering - Part 3: On-Call Culture and the Human Aspect](./2024-01-09-site-reliability-engineering-part-3.md) [2023-12-10 - Bash Golf Part 3](./2023-12-10-bash-golf-part-3.md) -- cgit v1.2.3 From f8400d9c602317c13e692debae8de0f381bf6cac Mon Sep 17 00:00:00 2001 From: Paul Buetow Date: Sun, 4 Feb 2024 18:35:47 +0200 Subject: Update content for md --- gemfeed/2024-02-04-from-babylon5.buetow.org-to-.cloud.md | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) (limited to 'gemfeed') diff --git a/gemfeed/2024-02-04-from-babylon5.buetow.org-to-.cloud.md b/gemfeed/2024-02-04-from-babylon5.buetow.org-to-.cloud.md index 2ac386cd..be8e42ba 100644 --- a/gemfeed/2024-02-04-from-babylon5.buetow.org-to-.cloud.md +++ b/gemfeed/2024-02-04-from-babylon5.buetow.org-to-.cloud.md @@ -70,7 +70,7 @@ You can find all Terraform manifests here: Whereas: -* `org-buetow-base` sets up the bare VPS, EFS, and Route 53 zone. It's the requirement for most other Terraform manifests in this repository. +* `org-buetow-base` sets up the bare VPN (IPv4 and IPv6 subnets in 3 AZs, EFS, ECR (the AWS container registry for some self-built containers) and Route 53 zone. It's the requirement for most other Terraform manifests in this repository. * `org-buetow-bastion` sets up a minimal Amazon Linux EC2 instance where I can manually SSH into and look at the EFS file system (if required). * `org-buetow-elb` sets up the Elastic Load Balancer, a prerequisite for any service running in ECS Fargate. * `org-buetow-ecs` finally sets up and deploys all the Docker apps mentioned above. Any apps can be turned on or off via the `variables.tf` file. -- cgit v1.2.3 From 963b765ea2a19100b885cd9fa0a6378f13e47102 Mon Sep 17 00:00:00 2001 From: Paul Buetow Date: Sun, 4 Feb 2024 18:37:32 +0200 Subject: Update content for md --- gemfeed/2024-02-04-from-babylon5.buetow.org-to-.cloud.md | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) (limited to 'gemfeed') diff --git a/gemfeed/2024-02-04-from-babylon5.buetow.org-to-.cloud.md b/gemfeed/2024-02-04-from-babylon5.buetow.org-to-.cloud.md index be8e42ba..9dcc0e9d 100644 --- a/gemfeed/2024-02-04-from-babylon5.buetow.org-to-.cloud.md +++ b/gemfeed/2024-02-04-from-babylon5.buetow.org-to-.cloud.md @@ -70,7 +70,7 @@ You can find all Terraform manifests here: Whereas: -* `org-buetow-base` sets up the bare VPN (IPv4 and IPv6 subnets in 3 AZs, EFS, ECR (the AWS container registry for some self-built containers) and Route 53 zone. It's the requirement for most other Terraform manifests in this repository. +* `org-buetow-base` sets up the bare VPC (IPv4 and IPv6 subnets in 3 AZs, EFS, ECR (the AWS container registry for some self-built containers) and Route 53 zone. It's the requirement for most other Terraform manifests in this repository. * `org-buetow-bastion` sets up a minimal Amazon Linux EC2 instance where I can manually SSH into and look at the EFS file system (if required). * `org-buetow-elb` sets up the Elastic Load Balancer, a prerequisite for any service running in ECS Fargate. * `org-buetow-ecs` finally sets up and deploys all the Docker apps mentioned above. Any apps can be turned on or off via the `variables.tf` file. -- cgit v1.2.3 From 623d2b605111c4d4caa27088cbcfde0e5b8c5b89 Mon Sep 17 00:00:00 2001 From: Paul Buetow Date: Sun, 4 Feb 2024 18:41:36 +0200 Subject: Update content for md --- gemfeed/2024-02-04-from-babylon5.buetow.org-to-.cloud.md | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) (limited to 'gemfeed') diff --git a/gemfeed/2024-02-04-from-babylon5.buetow.org-to-.cloud.md b/gemfeed/2024-02-04-from-babylon5.buetow.org-to-.cloud.md index 9dcc0e9d..dacb1fe5 100644 --- a/gemfeed/2024-02-04-from-babylon5.buetow.org-to-.cloud.md +++ b/gemfeed/2024-02-04-from-babylon5.buetow.org-to-.cloud.md @@ -150,7 +150,7 @@ This is a tiny ARM-based Amazon Linux EC2 instance, which I sometimes spin up fo I have learned a lot about AWS and Terraform during this migration. This was actually my first AWS hands-on project with practical use. -All of this was not particularly difficult (but at times a bit confusing). I see the use of Terraform managing more extensive infrastructures (it was even helpful for my small setup here). At least I know now what all the buzz is about :-). I don't think Terraform is a nice language. It get's it's job done, but it could be more elegant IMHO. +All of this was not particularly difficult (but at times a bit confusing). I see the use of Terraform managing more extensive infrastructures (it was even helpful for my small setup here). At least I know now what all the buzz is about :-). I don't think Terraform's HCL is a nice language. It get's it's job done, but it could be more elegant IMHO. Deploying updates to AWS are much easier, and some of the manual maintenance burdens of my Rocky Linux 9 VM are no longer needed. So I will have more time for other projects! -- cgit v1.2.3 From 344012986444b1d27219cbd63d473bbbd97faad6 Mon Sep 17 00:00:00 2001 From: Paul Buetow Date: Sun, 3 Mar 2024 00:08:43 +0200 Subject: Update content for md --- ...r-quickly-logging-ideas-programmed-in-golang.md | 52 +++++++++++++++++++++ .../logo-small.png | Bin 0 -> 63314 bytes .../screenshot-android.png | Bin 0 -> 45089 bytes gemfeed/index.md | 1 + 4 files changed, 53 insertions(+) create mode 100644 gemfeed/2024-03-03-a-fine-fyne-android-app-for-quickly-logging-ideas-programmed-in-golang.md create mode 100644 gemfeed/2024-03-03-a-fine-fyne-android-app-for-quickly-logging-ideas-programmed-in-golang/logo-small.png create mode 100644 gemfeed/2024-03-03-a-fine-fyne-android-app-for-quickly-logging-ideas-programmed-in-golang/screenshot-android.png (limited to 'gemfeed') diff --git a/gemfeed/2024-03-03-a-fine-fyne-android-app-for-quickly-logging-ideas-programmed-in-golang.md b/gemfeed/2024-03-03-a-fine-fyne-android-app-for-quickly-logging-ideas-programmed-in-golang.md new file mode 100644 index 00000000..559f6723 --- /dev/null +++ b/gemfeed/2024-03-03-a-fine-fyne-android-app-for-quickly-logging-ideas-programmed-in-golang.md @@ -0,0 +1,52 @@ +# A fine Fyne Android app for quickly logging ideas programmed in Go + +> Published at 2024-03-03T00:07:21+02:00 + +I am an ideas person. I find myself frequently somewhere on the streets with an idea in my head but no journal paper noting it down. + +I have tried many note apps for my Android (I use GrapheneOS) phone. Most of them either don't do what I want, are proprietary software, or are too bloated. I was never into mobile app development, as I'm not too fond of the complexity of the developer toolchains. I don't want to use Android Studio (as a NeoVim user), and I don't want to use Java or Kotlin. I want to use a language I know (and like) for mobile app development. Go would be one of those languages. + +[![Quick logger Logo](2024-03-03-a-fine-fyne-android-app-for-quickly-logging-ideas-programmed-in-golang/logo-small.png "Quick logger Logo")](2024-03-03-a-fine-fyne-android-app-for-quickly-logging-ideas-programmed-in-golang/logo-small.png) + +Enter Quick logger – a compact GUI Android (well, cross-platform due to Fyne) app I've crafted using Go and the nifty Fyne framework. With Fyne, the app can be compiled easily into an Android APK. As of this writing, this app's whole Go source code is only 75 lines short!! This little tool is designed for spontaneous moments, allowing me to quickly log my thoughts as plain text files on my Android phone. There are no fancy file formats. Just plain text! + +[https://codeberg.org/snonux/quicklogger](https://codeberg.org/snonux/quicklogger) +[https://fyne.io](https://fyne.io) +[https://go.dev](https://go.dev) + +There's no need to navigate complex menus or deal with sync issues. I jot down my Idea, and Quick logger saves it to a plain text file in a designated local folder on my phone. There is one text file per note (timestamp in the file name). Once logged, the file can't be edited anymore (it keeps it simple). If I want to correct or change a note, I simply write a new one. My notes are always small (usually one short sentence each), so there isn't the need for an edit functionality. I can edit them later on my actual computer if I want to. + +With Syncthing, the note files are then synchronised to my home computer to my `~/Notes` directory. From there, a Raku script adds them to my Taskwarrior DB so that I can process them later (e.g. take action on that one Idea I had). That then will delete the original note files from my computer and also (through Syncthing) from my phone. + +[https://syncthing.net](https://syncthing.net) +[https://raku.org](https://raku.org) +[https://taskwarrior.org](https://taskwarrior.org) + +Quick logger's user interface is as minimal as it gets. When I launch Quick logger, I'm greeted with a simple window where I can type plain text. Hit the "Log text" button, and voilà – the input is timestamped and saved as a file in my chosen directory. If I need to change the directory, the "Preferences" button brings up a window where I can set the notes folder and get back to logging. + +For the code-savvy folks out there, Quick logger is a neat example of what you can achieve with Go and Fyne. It's a testament to building functional, cross-platform apps without getting bogged down in the nitty-gritty of platform-specific details. Thanks to Fyne, I am pleased with how easy it is to make mobile Android apps in Go. + +[![Quick logger running on Android](2024-03-03-a-fine-fyne-android-app-for-quickly-logging-ideas-programmed-in-golang/screenshot-android.png "Quick logger running on Android")](2024-03-03-a-fine-fyne-android-app-for-quickly-logging-ideas-programmed-in-golang/screenshot-android.png) + +My Android apps will never be polished, but they will get the job done, and this is precisely how I want them to be. Minimalistic but functional. I could spend more time polishing Quick logger, but my Quick logger app then may be the same as any other notes app out there (complicated or bloated). + +## All easy-peasy? + +I did have some issues with the App logo for Android, though. Android always showed the default app icon and not my custom icon whenever I used a custom `AndroidManifest.xml` for custom app storage permissions. Without a custom `AndroidAmnifest.xml` the app icon would be displayed under Android, but then the app would not have the `MANAGE_EXTERNAL_STORAGE` permission, which is required for Quick logger to write to a custom directory. I found a workaround, which I commented on here at Github: + +[https://github.com/fyne-io/fyne/issues/3077#issuecomment-1912697360](https://github.com/fyne-io/fyne/issues/3077#issuecomment-1912697360) + +> What worked however (app icon showing up) was to clone the fyne project, change the occurances of android.permission.INTERNET to android.permission.MANAGE_EXTERNAL_STORAGE (as these are all the changes I want in my custom android manifest) in the source tree, re-compile fyne. Now all works. I know, this is more of an hammer approach! + +Hopefully, I won't need to use this workaround anymore. But for now, it is a fair tradeoff for what I am getting. + +I hope this will inspire you to write your own small mobile apps in Go using the awesome Fyne framework! + +E-Mail your comments to `paul@nospam.buetow.org` :-) + +Other Go related posts are: + +[2023-04-09 Algorithms and Data Structures in Go - Part 1](./2023-04-09-algorithms-and-data-structures-in-golang-part-1.md) +[2024-03-03 A fine Fyne Android app for quickly logging ideas programmed in Go (You are currently reading this)](./2024-03-03-a-fine-fyne-android-app-for-quickly-logging-ideas-programmed-in-golang.md) + +[Back to the main site](../) diff --git a/gemfeed/2024-03-03-a-fine-fyne-android-app-for-quickly-logging-ideas-programmed-in-golang/logo-small.png b/gemfeed/2024-03-03-a-fine-fyne-android-app-for-quickly-logging-ideas-programmed-in-golang/logo-small.png new file mode 100644 index 00000000..dc29011c Binary files /dev/null and b/gemfeed/2024-03-03-a-fine-fyne-android-app-for-quickly-logging-ideas-programmed-in-golang/logo-small.png differ diff --git a/gemfeed/2024-03-03-a-fine-fyne-android-app-for-quickly-logging-ideas-programmed-in-golang/screenshot-android.png b/gemfeed/2024-03-03-a-fine-fyne-android-app-for-quickly-logging-ideas-programmed-in-golang/screenshot-android.png new file mode 100644 index 00000000..a8a604e3 Binary files /dev/null and b/gemfeed/2024-03-03-a-fine-fyne-android-app-for-quickly-logging-ideas-programmed-in-golang/screenshot-android.png differ diff --git a/gemfeed/index.md b/gemfeed/index.md index 71feea8a..fc62cc72 100644 --- a/gemfeed/index.md +++ b/gemfeed/index.md @@ -2,6 +2,7 @@ ## To be in the .zone! +[2024-03-03 - A fine Fyne Android app for quickly logging ideas programmed in Go](./2024-03-03-a-fine-fyne-android-app-for-quickly-logging-ideas-programmed-in-golang.md) [2024-02-04 - From `babylon5.buetow.org` to `*.buetow.cloud`](./2024-02-04-from-babylon5.buetow.org-to-.cloud.md) [2024-01-13 - One reason why I love OpenBSD](./2024-01-13-one-reason-why-i-love-openbsd.md) [2024-01-09 - Site Reliability Engineering - Part 3: On-Call Culture and the Human Aspect](./2024-01-09-site-reliability-engineering-part-3.md) -- cgit v1.2.3 From 7b2a7ceb5fb3a33604d639c49a745b272023c860 Mon Sep 17 00:00:00 2001 From: Paul Buetow Date: Sun, 3 Mar 2024 00:17:51 +0200 Subject: Update content for md --- ...e-fyne-android-app-for-quickly-logging-ideas-programmed-in-golang.md | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) (limited to 'gemfeed') diff --git a/gemfeed/2024-03-03-a-fine-fyne-android-app-for-quickly-logging-ideas-programmed-in-golang.md b/gemfeed/2024-03-03-a-fine-fyne-android-app-for-quickly-logging-ideas-programmed-in-golang.md index 559f6723..cb340383 100644 --- a/gemfeed/2024-03-03-a-fine-fyne-android-app-for-quickly-logging-ideas-programmed-in-golang.md +++ b/gemfeed/2024-03-03-a-fine-fyne-android-app-for-quickly-logging-ideas-programmed-in-golang.md @@ -32,7 +32,7 @@ My Android apps will never be polished, but they will get the job done, and this ## All easy-peasy? -I did have some issues with the App logo for Android, though. Android always showed the default app icon and not my custom icon whenever I used a custom `AndroidManifest.xml` for custom app storage permissions. Without a custom `AndroidAmnifest.xml` the app icon would be displayed under Android, but then the app would not have the `MANAGE_EXTERNAL_STORAGE` permission, which is required for Quick logger to write to a custom directory. I found a workaround, which I commented on here at Github: +I did have some issues with the app logo for Android, though. Android always showed the default app icon and not my custom icon whenever I used a custom `AndroidManifest.xml` for custom app storage permissions. Without a custom `AndroidAmnifest.xml` the app icon would be displayed under Android, but then the app would not have the `MANAGE_EXTERNAL_STORAGE` permission, which is required for Quick logger to write to a custom directory. I found a workaround, which I commented on here at Github: [https://github.com/fyne-io/fyne/issues/3077#issuecomment-1912697360](https://github.com/fyne-io/fyne/issues/3077#issuecomment-1912697360) -- cgit v1.2.3 From 6505bdfa5388b85428c6030d8209ed9a20c97379 Mon Sep 17 00:00:00 2001 From: Paul Buetow Date: Sun, 3 Mar 2024 00:24:19 +0200 Subject: Update content for md --- ...e-fyne-android-app-for-quickly-logging-ideas-programmed-in-golang.md | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) (limited to 'gemfeed') diff --git a/gemfeed/2024-03-03-a-fine-fyne-android-app-for-quickly-logging-ideas-programmed-in-golang.md b/gemfeed/2024-03-03-a-fine-fyne-android-app-for-quickly-logging-ideas-programmed-in-golang.md index cb340383..124138d0 100644 --- a/gemfeed/2024-03-03-a-fine-fyne-android-app-for-quickly-logging-ideas-programmed-in-golang.md +++ b/gemfeed/2024-03-03-a-fine-fyne-android-app-for-quickly-logging-ideas-programmed-in-golang.md @@ -40,7 +40,7 @@ I did have some issues with the app logo for Android, though. Android always sho Hopefully, I won't need to use this workaround anymore. But for now, it is a fair tradeoff for what I am getting. -I hope this will inspire you to write your own small mobile apps in Go using the awesome Fyne framework! +I hope this will inspire you to write your own small mobile apps in Go using the awesome Fyne framework! PS: The Quick logger logo was generated by ChatGPT. E-Mail your comments to `paul@nospam.buetow.org` :-) -- cgit v1.2.3 From 7f979cb56df9e459f2ab6d09efb5f46bf132bb06 Mon Sep 17 00:00:00 2001 From: Paul Buetow Date: Sun, 3 Mar 2024 00:38:45 +0200 Subject: Update content for md --- ...e-fyne-android-app-for-quickly-logging-ideas-programmed-in-golang.md | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) (limited to 'gemfeed') diff --git a/gemfeed/2024-03-03-a-fine-fyne-android-app-for-quickly-logging-ideas-programmed-in-golang.md b/gemfeed/2024-03-03-a-fine-fyne-android-app-for-quickly-logging-ideas-programmed-in-golang.md index 124138d0..5fde74af 100644 --- a/gemfeed/2024-03-03-a-fine-fyne-android-app-for-quickly-logging-ideas-programmed-in-golang.md +++ b/gemfeed/2024-03-03-a-fine-fyne-android-app-for-quickly-logging-ideas-programmed-in-golang.md @@ -16,7 +16,7 @@ Enter Quick logger – a compact GUI Android (well, cross-platform due to Fyne) There's no need to navigate complex menus or deal with sync issues. I jot down my Idea, and Quick logger saves it to a plain text file in a designated local folder on my phone. There is one text file per note (timestamp in the file name). Once logged, the file can't be edited anymore (it keeps it simple). If I want to correct or change a note, I simply write a new one. My notes are always small (usually one short sentence each), so there isn't the need for an edit functionality. I can edit them later on my actual computer if I want to. -With Syncthing, the note files are then synchronised to my home computer to my `~/Notes` directory. From there, a Raku script adds them to my Taskwarrior DB so that I can process them later (e.g. take action on that one Idea I had). That then will delete the original note files from my computer and also (through Syncthing) from my phone. +With Syncthing, the note files are then synchronised to my home computer to my `~/Notes` directory. From there, a small glue Raku script adds them to my Taskwarrior DB so that I can process them later (e.g. take action on that one Idea I had). That then will delete the original note files from my computer and also (through Syncthing) from my phone. [https://syncthing.net](https://syncthing.net) [https://raku.org](https://raku.org) -- cgit v1.2.3 From 2f17e72d78abcce8ff4947b9f9f8649fe6a26abb Mon Sep 17 00:00:00 2001 From: Paul Buetow Date: Sun, 3 Mar 2024 00:51:22 +0200 Subject: Update content for md --- ...e-fyne-android-app-for-quickly-logging-ideas-programmed-in-golang.md | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) (limited to 'gemfeed') diff --git a/gemfeed/2024-03-03-a-fine-fyne-android-app-for-quickly-logging-ideas-programmed-in-golang.md b/gemfeed/2024-03-03-a-fine-fyne-android-app-for-quickly-logging-ideas-programmed-in-golang.md index 5fde74af..930fcbe6 100644 --- a/gemfeed/2024-03-03-a-fine-fyne-android-app-for-quickly-logging-ideas-programmed-in-golang.md +++ b/gemfeed/2024-03-03-a-fine-fyne-android-app-for-quickly-logging-ideas-programmed-in-golang.md @@ -2,7 +2,7 @@ > Published at 2024-03-03T00:07:21+02:00 -I am an ideas person. I find myself frequently somewhere on the streets with an idea in my head but no journal paper noting it down. +I am an ideas person. I find myself frequently somewhere on the streets with an idea in my head but no paper journal noting it down. I have tried many note apps for my Android (I use GrapheneOS) phone. Most of them either don't do what I want, are proprietary software, or are too bloated. I was never into mobile app development, as I'm not too fond of the complexity of the developer toolchains. I don't want to use Android Studio (as a NeoVim user), and I don't want to use Java or Kotlin. I want to use a language I know (and like) for mobile app development. Go would be one of those languages. -- cgit v1.2.3 From 552c0b13ff89e51adc02387cb6dc068571d14fae Mon Sep 17 00:00:00 2001 From: Paul Buetow Date: Sun, 3 Mar 2024 11:31:18 +0200 Subject: Update content for md --- ...e-fyne-android-app-for-quickly-logging-ideas-programmed-in-golang.md | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) (limited to 'gemfeed') diff --git a/gemfeed/2024-03-03-a-fine-fyne-android-app-for-quickly-logging-ideas-programmed-in-golang.md b/gemfeed/2024-03-03-a-fine-fyne-android-app-for-quickly-logging-ideas-programmed-in-golang.md index 930fcbe6..5665b5e9 100644 --- a/gemfeed/2024-03-03-a-fine-fyne-android-app-for-quickly-logging-ideas-programmed-in-golang.md +++ b/gemfeed/2024-03-03-a-fine-fyne-android-app-for-quickly-logging-ideas-programmed-in-golang.md @@ -4,7 +4,7 @@ I am an ideas person. I find myself frequently somewhere on the streets with an idea in my head but no paper journal noting it down. -I have tried many note apps for my Android (I use GrapheneOS) phone. Most of them either don't do what I want, are proprietary software, or are too bloated. I was never into mobile app development, as I'm not too fond of the complexity of the developer toolchains. I don't want to use Android Studio (as a NeoVim user), and I don't want to use Java or Kotlin. I want to use a language I know (and like) for mobile app development. Go would be one of those languages. +I have tried many note apps for my Android (I use GrapheneOS) phone. Most of them either don't do what I want, are proprietary software, require Google Play services (I have the main profile on my phone de-googled) or are too bloated. I was never into mobile app development, as I'm not too fond of the complexity of the developer toolchains. I don't want to use Android Studio (as a NeoVim user), and I don't want to use Java or Kotlin. I want to use a language I know (and like) for mobile app development. Go would be one of those languages. [![Quick logger Logo](2024-03-03-a-fine-fyne-android-app-for-quickly-logging-ideas-programmed-in-golang/logo-small.png "Quick logger Logo")](2024-03-03-a-fine-fyne-android-app-for-quickly-logging-ideas-programmed-in-golang/logo-small.png) -- cgit v1.2.3 From dbf9a92bdec35e128666091f438aaf6a00b26c2f Mon Sep 17 00:00:00 2001 From: Paul Buetow Date: Sat, 30 Mar 2024 22:14:29 +0200 Subject: Update content for md --- ...24-04-01-KISS-high-availability-with-OpenBSD.md | 288 +++++++++++++++++++++ .../DRAFT-KISS-high-availability-with-OpenBSD.md | 286 ++++++++++++++++++++ gemfeed/index.md | 1 + 3 files changed, 575 insertions(+) create mode 100644 gemfeed/2024-04-01-KISS-high-availability-with-OpenBSD.md create mode 100644 gemfeed/DRAFT-KISS-high-availability-with-OpenBSD.md (limited to 'gemfeed') diff --git a/gemfeed/2024-04-01-KISS-high-availability-with-OpenBSD.md b/gemfeed/2024-04-01-KISS-high-availability-with-OpenBSD.md new file mode 100644 index 00000000..6ac7c89e --- /dev/null +++ b/gemfeed/2024-04-01-KISS-high-availability-with-OpenBSD.md @@ -0,0 +1,288 @@ +# KISS high-availability with OpenBSD + +> Published at 2024-03-30T22:12:56+02:00 + +``` +Art by Michael J. Penick (mod. by Paul B) + + __________ + / nsd tower\ ( + /____________\ (\) awk-ward + |:_:_:_:_:_| )) plant + |_:_,--.:_:| dig-bubble (\// ) + |:_:|__|_:_| relayd-castle _ ) )) (( + _ |_ _ :_:| _ _ _ (_) (((( /)\` + | |_| |_| | _| | |_| |_| | o \\)) (( ( + \_:_:_:_:/|_|_|_|\:_:_:_:_/ . (( )))) + |_,-._:_:_:_:_:_:_:_.-,_| )) ((// + |:|_|:_:_:,---,:_:_:|_|:| ,-. )/ + |_:_:_:_,'puffy `,_:_:_:_| _ o ,;'))(( + |:_:_:_/ _ | _ \_:_:_:| (_O (( )) +_____|_:_:_| (o)-(o) |_:_:_|--'`-. ,--. ksh under-water (((\'/ + ', ;|:_:_:| -( .-. )- |:_:_:| ', ; `--._\ /,---.~ goat \`)) +. ` |_:_:_| \`-'/ |_:_:_|. ` . ` /()\.__( ) .,-----'`-\(( sed-root + ', ;|:_:_:| `-' |:_:_:| ', ; ', ; `--'| \ ', ; ', ; ',')).,-- +. ` MJP ` . ` . ` . ` . httpd-soil ` . . ` . ` . ` . ` . ` + ', ; ', ; ', ; ', ; ', ; ', ; ', ; ', ; ', ; ', ; ', ; ', ; ', ; ', ; + +``` + +I have always wanted a highly available setup for my personal websites. I could have used off-the-shelf hosting solutions or hosted my sites in an AWS S3 bucket. I have used technologies like BGP, LVS/IPVS, ldirectord, Pacemaker, heartbeat, heartbeat2, Corosync, keepalived, DRBD, and commercial F5 Load Balancers for high availability at work. + +But still, my personal sites were never highly available. All those technologies are great for professional use, but I was looking for something much more straightforward for my personal space—something as KISS (keep it simple and stupid) as possible. + +It would be fine if my personal website wasn't highly available, but the geek in me wants it anyway. + +> PS: ASCII-art reflects the OpenBSD under-water world with all the tools available in the base system. + +## My auto-failover requirements + +* Be OpenBSD-based (I prefer OpenBSD because of the cleanliness and good documentation) and rely on as few external packages as possible. +* Don't rely on the hottest and newest tech (don't want to migrate everything to a new and fancier technology next month). +* It should be reasonably cheap. I want to avoid paying a premium for floating IPs or fancy Elastic Load Balancers. +* It should be geo-redundant. +* It's fine if my sites aren't reachable for five or ten minutes every other month. Due to their static nature, I don't care if there's a split-brain scenario where some requests reach one server and other requests reach another server. +* Failover should work for both HTTP/HTTPS and Gemini protocols. My self-hosted MTAs and DNS servers should also be highly available. +* Let's Encrypt TLS certificates should always work (before and after a failover). +* Have good monitoring in place so I know when a failover was performed and when something went wrong with the failover. +* Don't configure everything manually. The configuration should be automated and reproducible. + +## My HA solution + +### Only OpenBSD base installation required + +My HA solution for Web and Gemini is based on DNS (OpenBSD's `nsd`) and a simple shell script (OpenBSD's `ksh` and some little `sed` and `awk` and `grep`). All software used here is part of the OpenBSD base system and no external package needs to be installed - OpenBSD is a complete operating system. + +[https://man.OpenBSD.org/nsd.8](https://man.OpenBSD.org/nsd.8) +[https://man.OpenBSD.org/ksh](https://man.OpenBSD.org/ksh) +[https://man.OpenBSD.org/awk](https://man.OpenBSD.org/awk) +[https://man.OpenBSD.org/sed](https://man.OpenBSD.org/sed) +[https://man.OpenBSD.org/dig](https://man.OpenBSD.org/dig) +[https://man.OpenBSD.org/ftp](https://man.OpenBSD.org/ftp) + +I also used the `dig` (for DNS checks) and `ftp` (for HTTP/HTTPS checks) programs. + +The DNS failover is performed automatically between the two OpenBSD VMs involved (my setup doesn't require any quorum for a failover, so there isn't a need for a 3rd VM). The `ksh` script, executed once per minute via CRON (on both VMs), performs a health check to determine whether the current master node is available. If the current master isn't available (no HTTP response as expected), a failover is performed to the standby VM: + +```sh +#!/bin/ksh + +ZONES_DIR=/var/nsd/zones/master/ +DEFAULT_MASTER=fishfinger.buetow.org +DEFAULT_STANDBY=blowfish.buetow.org + +determine_master_and_standby () { + local master=$DEFAULT_MASTER + local standby=$DEFAULT_STANDBY + + . + . + . + + local -i health_ok=1 + if ! ftp -4 -o - https://$master/index.txt | grep -q "Welcome to $master"; then + echo "https://$master/index.txt IPv4 health check failed" + health_ok=0 + elif ! ftp -6 -o - https://$master/index.txt | grep -q "Welcome to $master"; then + echo "https://$master/index.txt IPv6 health check failed" + health_ok=0 + fi + if [ $health_ok -eq 0 ]; then + local tmp=$master + master=$standby + standby=$tmp + fi + + . + . + . +} +``` + +The failover scripts looks for the ` ; Enable failover` string in the DNS zone files and swaps the `A` and `AAAA` records of the DNS entries accordingly: + +```sh +fishfinger$ grep failover /var/nsd/zones/master/foo.zone.zone + 300 IN A 46.23.94.99 ; Enable failover + 300 IN AAAA 2a03:6000:6f67:624::99 ; Enable failover +www 300 IN A 46.23.94.99 ; Enable failover +www 300 IN AAAA 2a03:6000:6f67:624::99 ; Enable failover +standby 300 IN A 23.88.35.144 ; Enable failover +standby 300 IN AAAA 2a01:4f8:c17:20f1::42 ; Enable failover +``` + +```sh +tramsform () { + sed -E ' + /IN A .*; Enable failover/ { + /^standby/! { + s/^(.*) 300 IN A (.*) ; (.*)/\1 300 IN A '$(cat /var/nsd/run/master_a)' ; \3/; + } + /^standby/ { + s/^(.*) 300 IN A (.*) ; (.*)/\1 300 IN A '$(cat /var/nsd/run/standby_a)' ; \3/; + } + } + /IN AAAA .*; Enable failover/ { + /^standby/! { + s/^(.*) 300 IN AAAA (.*) ; (.*)/\1 300 IN AAAA '$(cat /var/nsd/run/master_aaaa)' ; \3/; + } + /^standby/ { + s/^(.*) 300 IN AAAA (.*) ; (.*)/\1 300 IN AAAA '$(cat /var/nsd/run/standby_aaaa)' ; \3/; + } + } + / ; serial/ { + s/^( +) ([0-9]+) .*; (.*)/\1 '$(date +%s)' ; \3/; + } + ' +} +``` + +After the failover, the script reloads `nsd` and performs a sanity check to see if DNS still works. If not, a rollback will be performed: + +```sh +# Race condition (e.g. script execution abored in the middle of the previous run) +if [ -f $zone_file.bak ]; then + mv $zone_file.bak $zone_file +fi + +cat $zone_file | transform > $zone_file.new.tmp + +grep -v ' ; serial' $zone_file.new.tmp > $zone_file.new.noserial.tmp +grep -v ' ; serial' $zone_file > $zone_file.old.noserial.tmp + +echo "Has zone $zone_file changed?" +if diff -u $zone_file.old.noserial.tmp $zone_file.new.noserial.tmp; then + echo "The zone $zone_file hasn't changed" + rm $zone_file.*.tmp + return 0 +fi + +cp $zone_file $zone_file.bak +mv $zone_file.new.tmp $zone_file +rm $zone_file.*.tmp +echo "Reloading nsd" +nsd-control reload + +if ! zone_is_ok $zone; then + echo "Rolling back $zone_file changes" + cp $zone_file $zone_file.invalid + mv $zone_file.bak $zone_file + echo "Reloading nsd" + nsd-control reload + zone_is_ok $zone + return 3 +fi + +for cleanup in invalid bak; do + if [ -f $zone_file.$cleanup ]; then + rm $zone_file.$cleanup + fi +done + +echo "Failover of zone $zone to $MASTER completed" +return 1 +``` + +A non-zero return code (here, 3 when a rollback and 1 when a DNS failover was performed) will cause CRON to send an E-Mail with the whole script output. + +The nameserver is running on both VMs, and both are configured to be "master" DNS servers so that they have their own individual zone files, which can be changed independently. Otherwise, my setup wouldn't work. The side effect is that under a split-brain scenario (both VMs cannot see each other), both would promote themselves to master via their local DNS entries. More about that later, but that's fine in my use case. + +Check out the whole script here: + +[https://codeberg.org/snonux/rexfiles/src/branch/master/frontends/scripts/dns-failover.ksh](https://codeberg.org/snonux/rexfiles/src/branch/master/frontends/scripts/dns-failover.ksh) + +### Fairly cheap and geo-redundant + +I am renting two small OpenBSD VMs: One at OpenBSD Amsterdam and the other at Hetzner Cloud. So, both VMs are hosted at another provider, in different IP subnets, and in different countries (the Netherlands and Germany). + +[https://openbsd.amsterdam](https://openbsd.amsterdam) +[https://www.hetzner.cloud](https://www.hetzner.cloud) + +I only have a little traffic on my sites. I could always upload the static content to AWS S3 if I suddenly had to. But this will never be required. + +A DNS-based failover is cheap, as there isn't any BGP or fancy load balancer to pay for. Small VMs also cost less than millions. + +### Failover time and split-brain + +A DNS failover doesn't happen immediately. I've configured a DNS TTL of `300` seconds, and the failover script checks once per minute whether to perform a failover or not. So, in total, a failover can take six minutes (not including other DNS caching servers somewhere in the interweb, but that's fine - eventually, all requests will resolve to the new master after a failover). + +A split-brain scenario between the old master and the new master might happen. That's OK, as my sites are static, and there's no database to synchronise other than HTML, CSS, and images when the site is updated. + +### Failover support for multiple protocols + +With the DNS failover, HTTP, HTTPS, and Gemini protocols are failovered. This works because all domain virtual hosts are configured on either VM's `httpd` (OpenBSD's HTTP server) and `relayd` (it's also part of OpenBSD and I use it to TLS offload the Gemini protocol). So, both VMs accept requests for all the hosts. It's just a matter of the DNS entry, which hosts receive the requests. + +[https://man.openbsd.org/httpd.8](https://man.openbsd.org/httpd.8) +[https://man.openbsd.org/relayd.8](https://man.openbsd.org/relayd.8) + +For example, the master is responsible for the `https://www.foo.zone` and `https://foo.zone` hosts, whereas the standby can be reached via `https://standby.foo.zone` (port 80 for plain HTTP works as well). The same principle is followed with all the other hosts, e.g. `irregular.ninja`, `paul.buetow.org` and so on. The same applies to my Gemini capsules for `gemini://foo.zone`, `gemini://standby.foo.zone`, `gemini://paul.buetow.org` and `gemini://standby.paul.buetow.org`. + +On DNS failover, master and standby swap roles without config changes other than the DNS entries. That's KISS (keep it simple and stupid)! + +### Let's encrypt TLS certificates + +All my hosts use TLS certificates from Let's Encrypt. The ACME automation for requesting and keeping the certificates valid (up to date) requires that the host requesting a certificate from Let's Encrypt is also the host using that certificate. + +If the master always serves `foo.zone` and the standby always `standby.foo.zone`, then there would be a problem after the failover, as the new master wouldn't have a valid certificate for `foo.zone` and the new standby wouldn't have a valid certificate for `standby.foo.zone` which would lead to TLS errors on the clients. + +As a solution, the CRON job responsible for the DNS failover also checks for the current week number of the year so that: + +* In an odd week number, the first server is the default master +* In an even week number, the second server is the default master. + +Which translates to: + +```sh +# Weekly auto-failover for Let's Encrypt automation +local -i -r week_of_the_year=$(date +%U) +if [ $(( week_of_the_year % 2 )) -eq 0 ]; then + local tmp=$master + master=$standby + standby=$tmp +fi +``` + +This way, a DNS failover is performed weekly so that the ACME automation can update the Let's Encrypt certificates (for master and standby) before they expire on each VM. + +The ACME automation is yet another daily CRON script `/usr/local/bin/acme.sh`. It iterates over all of my Let's Encrypt hosts, checks whether they resolve to the same IP address as the current VM, and only then invokes the ACME client to request or renew the TLS certificates. So, there are always correct requests made to Let's Encrypt. + +Let's encrypt certificates usually expire after 3 months, so a weekly failover of my VMs is plenty. + +[`acme.sh.tpl` - Rex template for the `acme.sh` script of mine.](https://codeberg.org/snonux/rexfiles/src/branch/master/frontends/scripts/acme.sh.tpl) +[https://man.openbsd.org/acme-client.1](https://man.openbsd.org/acme-client.1) +[Let's Encrypt with OpenBSD and Rex](./2022-07-30-lets-encrypt-with-openbsd-and-rex.md) + +### Monitoring + +CRON is sending me an E-Mail whenever a failover is performed (or whenever a failover failed). Furthermore, I am monitoring my DNS servers and hosts through Gogios, the monitoring system I have developed. + +[https://codeberg.org/snonux/gogios](https://codeberg.org/snonux/gogios) +[KISS server monitoring with Gogios](./2023-06-01-kiss-server-monitoring-with-gogios.md) + +### Rex automation + +I use Rexify, a friendly configuration management system that allows automatic deployment and configuration. + +[https://www.rexify.org](https://www.rexify.org) +[https://codeberg.org/snonux/rexfiles/src/branch/master/frontends](https://codeberg.org/snonux/rexfiles/src/branch/master/frontends) + +## More HA + +Other high-available services running on my OpenBSD VMs are my MTAs for mail forwarding (OpenSMTPD) and the authoritative DNS servers (`nsd`) for all my domains. No particular HA setup is required, though, as the protocols (SMTP and DNS) already take care of the failover to the next available host! + +As a password manager, I use `geheim`, a command-line tool I wrote in Ruby with encrypted files in a git repository (I even have it installed in Termux on my Phone). For HA reasons, I simply updated the client code so that it always synchronises the database with both servers when I run the `sync` command there. + +[https://codeberg.org/snonux/geheim](https://codeberg.org/snonux/geheim) + +E-Mail your comments to `paul@nospam.buetow.org` :-) + +Other *BSD and KISS related posts are: + +[2016-04-09 Jails and ZFS with Puppet on FreeBSD](./2016-04-09-jails-and-zfs-on-freebsd-with-puppet.md) +[2022-07-30 Let's Encrypt with OpenBSD and Rex](./2022-07-30-lets-encrypt-with-openbsd-and-rex.md) +[2022-10-30 Installing DTail on OpenBSD](./2022-10-30-installing-dtail-on-openbsd.md) +[2023-06-01 KISS server monitoring with Gogios](./2023-06-01-kiss-server-monitoring-with-gogios.md) +[2023-10-29 KISS static web photo albums with `photoalbum.sh`](./2023-10-29-kiss-static-web-photo-albums-with-photoalbum.sh.md) +[2024-01-13 One reason why I love OpenBSD](./2024-01-13-one-reason-why-i-love-openbsd.md) + +[Back to the main site](../) diff --git a/gemfeed/DRAFT-KISS-high-availability-with-OpenBSD.md b/gemfeed/DRAFT-KISS-high-availability-with-OpenBSD.md new file mode 100644 index 00000000..3e388ffe --- /dev/null +++ b/gemfeed/DRAFT-KISS-high-availability-with-OpenBSD.md @@ -0,0 +1,286 @@ +# KISS high-availability with OpenBSD + +``` +Art by Michael J. Penick (mod. by Paul B) + + __________ + / nsd tower\ ( + /____________\ (\) awk-ward + |:_:_:_:_:_| )) plant + |_:_,--.:_:| dig-bubble (\// ) + |:_:|__|_:_| relayd-castle _ ) )) (( + _ |_ _ :_:| _ _ _ (_) (((( /)\` + | |_| |_| | _| | |_| |_| | o \\)) (( ( + \_:_:_:_:/|_|_|_|\:_:_:_:_/ . (( )))) + |_,-._:_:_:_:_:_:_:_.-,_| )) ((// + |:|_|:_:_:,---,:_:_:|_|:| ,-. )/ + |_:_:_:_,'puffy `,_:_:_:_| _ o ,;'))(( + |:_:_:_/ _ | _ \_:_:_:| (_O (( )) +_____|_:_:_| (o)-(o) |_:_:_|--'`-. ,--. ksh under-water (((\'/ + ', ;|:_:_:| -( .-. )- |:_:_:| ', ; `--._\ /,---.~ goat \`)) +. ` |_:_:_| \`-'/ |_:_:_|. ` . ` /()\.__( ) .,-----'`-\(( sed-root + ', ;|:_:_:| `-' |:_:_:| ', ; ', ; `--'| \ ', ; ', ; ',')).,-- +. ` MJP ` . ` . ` . ` . httpd-soil ` . . ` . ` . ` . ` . ` + ', ; ', ; ', ; ', ; ', ; ', ; ', ; ', ; ', ; ', ; ', ; ', ; ', ; ', ; + +``` + +I have always wanted a highly available setup for my personal websites. I could have used off-the-shelf hosting solutions or hosted my sites in an AWS S3 bucket. I have used technologies like BGP, LVS/IPVS, ldirectord, Pacemaker, heartbeat, heartbeat2, Corosync, keepalived, DRBD, and commercial F5 Load Balancers for high availability at work. + +But still, my personal sites were never highly available. All those technologies are great for professional use, but I was looking for something much more straightforward for my personal space—something as KISS (keep it simple and stupid) as possible. + +It would be fine if my personal website wasn't highly available, but the geek in me wants it anyway. + +> PS: ASCII-art reflects the OpenBSD under-water world with all the tools available in the base system. + +## My auto-failover requirements + +* Be OpenBSD-based (I prefer OpenBSD because of the cleanliness and good documentation) and rely on as few external packages as possible. +* Don't rely on the hottest and newest tech (don't want to migrate everything to a new and fancier technology next month). +* It should be reasonably cheap. I want to avoid paying a premium for floating IPs or fancy Elastic Load Balancers. +* It should be geo-redundant. +* It's fine if my sites aren't reachable for five or ten minutes every other month. Due to their static nature, I don't care if there's a split-brain scenario where some requests reach one server and other requests reach another server. +* Failover should work for both HTTP/HTTPS and Gemini protocols. My self-hosted MTAs and DNS servers should also be highly available. +* Let's Encrypt TLS certificates should always work (before and after a failover). +* Have good monitoring in place so I know when a failover was performed and when something went wrong with the failover. +* Don't configure everything manually. The configuration should be automated and reproducible. + +## My HA solution + +### Only OpenBSD base installation required + +My HA solution for Web and Gemini is based on DNS (OpenBSD's `nsd`) and a simple shell script (OpenBSD's `ksh` and some little `sed` and `awk` and `grep`). All software used here is part of the OpenBSD base system and no external package needs to be installed - OpenBSD is a complete operating system. + +[https://man.OpenBSD.org/nsd.8](https://man.OpenBSD.org/nsd.8) +[https://man.OpenBSD.org/ksh](https://man.OpenBSD.org/ksh) +[https://man.OpenBSD.org/awk](https://man.OpenBSD.org/awk) +[https://man.OpenBSD.org/sed](https://man.OpenBSD.org/sed) +[https://man.OpenBSD.org/dig](https://man.OpenBSD.org/dig) +[https://man.OpenBSD.org/ftp](https://man.OpenBSD.org/ftp) + +I also used the `dig` (for DNS checks) and `ftp` (for HTTP/HTTPS checks) programs. + +The DNS failover is performed automatically between the two OpenBSD VMs involved (my setup doesn't require any quorum for a failover, so there isn't a need for a 3rd VM). The `ksh` script, executed once per minute via CRON (on both VMs), performs a health check to determine whether the current master node is available. If the current master isn't available (no HTTP response as expected), a failover is performed to the standby VM: + +```sh +#!/bin/ksh + +ZONES_DIR=/var/nsd/zones/master/ +DEFAULT_MASTER=fishfinger.buetow.org +DEFAULT_STANDBY=blowfish.buetow.org + +determine_master_and_standby () { + local master=$DEFAULT_MASTER + local standby=$DEFAULT_STANDBY + + . + . + . + + local -i health_ok=1 + if ! ftp -4 -o - https://$master/index.txt | grep -q "Welcome to $master"; then + echo "https://$master/index.txt IPv4 health check failed" + health_ok=0 + elif ! ftp -6 -o - https://$master/index.txt | grep -q "Welcome to $master"; then + echo "https://$master/index.txt IPv6 health check failed" + health_ok=0 + fi + if [ $health_ok -eq 0 ]; then + local tmp=$master + master=$standby + standby=$tmp + fi + + . + . + . +} +``` + +The failover scripts looks for the ` ; Enable failover` string in the DNS zone files and swaps the `A` and `AAAA` records of the DNS entries accordingly: + +```sh +fishfinger$ grep failover /var/nsd/zones/master/foo.zone.zone + 300 IN A 46.23.94.99 ; Enable failover + 300 IN AAAA 2a03:6000:6f67:624::99 ; Enable failover +www 300 IN A 46.23.94.99 ; Enable failover +www 300 IN AAAA 2a03:6000:6f67:624::99 ; Enable failover +standby 300 IN A 23.88.35.144 ; Enable failover +standby 300 IN AAAA 2a01:4f8:c17:20f1::42 ; Enable failover +``` + +```sh +tramsform () { + sed -E ' + /IN A .*; Enable failover/ { + /^standby/! { + s/^(.*) 300 IN A (.*) ; (.*)/\1 300 IN A '$(cat /var/nsd/run/master_a)' ; \3/; + } + /^standby/ { + s/^(.*) 300 IN A (.*) ; (.*)/\1 300 IN A '$(cat /var/nsd/run/standby_a)' ; \3/; + } + } + /IN AAAA .*; Enable failover/ { + /^standby/! { + s/^(.*) 300 IN AAAA (.*) ; (.*)/\1 300 IN AAAA '$(cat /var/nsd/run/master_aaaa)' ; \3/; + } + /^standby/ { + s/^(.*) 300 IN AAAA (.*) ; (.*)/\1 300 IN AAAA '$(cat /var/nsd/run/standby_aaaa)' ; \3/; + } + } + / ; serial/ { + s/^( +) ([0-9]+) .*; (.*)/\1 '$(date +%s)' ; \3/; + } + ' +} +``` + +After the failover, the script reloads `nsd` and performs a sanity check to see if DNS still works. If not, a rollback will be performed: + +```sh +# Race condition (e.g. script execution abored in the middle of the previous run) +if [ -f $zone_file.bak ]; then + mv $zone_file.bak $zone_file +fi + +cat $zone_file | transform > $zone_file.new.tmp + +grep -v ' ; serial' $zone_file.new.tmp > $zone_file.new.noserial.tmp +grep -v ' ; serial' $zone_file > $zone_file.old.noserial.tmp + +echo "Has zone $zone_file changed?" +if diff -u $zone_file.old.noserial.tmp $zone_file.new.noserial.tmp; then + echo "The zone $zone_file hasn't changed" + rm $zone_file.*.tmp + return 0 +fi + +cp $zone_file $zone_file.bak +mv $zone_file.new.tmp $zone_file +rm $zone_file.*.tmp +echo "Reloading nsd" +nsd-control reload + +if ! zone_is_ok $zone; then + echo "Rolling back $zone_file changes" + cp $zone_file $zone_file.invalid + mv $zone_file.bak $zone_file + echo "Reloading nsd" + nsd-control reload + zone_is_ok $zone + return 3 +fi + +for cleanup in invalid bak; do + if [ -f $zone_file.$cleanup ]; then + rm $zone_file.$cleanup + fi +done + +echo "Failover of zone $zone to $MASTER completed" +return 1 +``` + +A non-zero return code (here, 3 when a rollback and 1 when a DNS failover was performed) will cause CRON to send an E-Mail with the whole script output. + +The nameserver is running on both VMs, and both are configured to be "master" DNS servers so that they have their own individual zone files, which can be changed independently. Otherwise, my setup wouldn't work. The side effect is that under a split-brain scenario (both VMs cannot see each other), both would promote themselves to master via their local DNS entries. More about that later, but that's fine in my use case. + +Check out the whole script here: + +[https://codeberg.org/snonux/rexfiles/src/branch/master/frontends/scripts/dns-failover.ksh](https://codeberg.org/snonux/rexfiles/src/branch/master/frontends/scripts/dns-failover.ksh) + +### Fairly cheap and geo-redundant + +I am renting two small OpenBSD VMs: One at OpenBSD Amsterdam and the other at Hetzner Cloud. So, both VMs are hosted at another provider, in different IP subnets, and in different countries (the Netherlands and Germany). + +[https://openbsd.amsterdam](https://openbsd.amsterdam) +[https://www.hetzner.cloud](https://www.hetzner.cloud) + +I only have a little traffic on my sites. I could always upload the static content to AWS S3 if I suddenly had to. But this will never be required. + +A DNS-based failover is cheap, as there isn't any BGP or fancy load balancer to pay for. Small VMs also cost less than millions. + +### Failover time and split-brain + +A DNS failover doesn't happen immediately. I've configured a DNS TTL of `300` seconds, and the failover script checks once per minute whether to perform a failover or not. So, in total, a failover can take six minutes (not including other DNS caching servers somewhere in the interweb, but that's fine - eventually, all requests will resolve to the new master after a failover). + +A split-brain scenario between the old master and the new master might happen. That's OK, as my sites are static, and there's no database to synchronise other than HTML, CSS, and images when the site is updated. + +### Failover support for multiple protocols + +With the DNS failover, HTTP, HTTPS, and Gemini protocols are failovered. This works because all domain virtual hosts are configured on either VM's `httpd` (OpenBSD's HTTP server) and `relayd` (it's also part of OpenBSD and I use it to TLS offload the Gemini protocol). So, both VMs accept requests for all the hosts. It's just a matter of the DNS entry, which hosts receive the requests. + +[https://man.openbsd.org/httpd.8](https://man.openbsd.org/httpd.8) +[https://man.openbsd.org/relayd.8](https://man.openbsd.org/relayd.8) + +For example, the master is responsible for the `https://www.foo.zone` and `https://foo.zone` hosts, whereas the standby can be reached via `https://standby.foo.zone` (port 80 for plain HTTP works as well). The same principle is followed with all the other hosts, e.g. `irregular.ninja`, `paul.buetow.org` and so on. The same applies to my Gemini capsules for `gemini://foo.zone`, `gemini://standby.foo.zone`, `gemini://paul.buetow.org` and `gemini://standby.paul.buetow.org`. + +On DNS failover, master and standby swap roles without config changes other than the DNS entries. That's KISS (keep it simple and stupid)! + +### Let's encrypt TLS certificates + +All my hosts use TLS certificates from Let's Encrypt. The ACME automation for requesting and keeping the certificates valid (up to date) requires that the host requesting a certificate from Let's Encrypt is also the host using that certificate. + +If the master always serves `foo.zone` and the standby always `standby.foo.zone`, then there would be a problem after the failover, as the new master wouldn't have a valid certificate for `foo.zone` and the new standby wouldn't have a valid certificate for `standby.foo.zone` which would lead to TLS errors on the clients. + +As a solution, the CRON job responsible for the DNS failover also checks for the current week number of the year so that: + +* In an odd week number, the first server is the default master +* In an even week number, the second server is the default master. + +Which translates to: + +```sh +# Weekly auto-failover for Let's Encrypt automation +local -i -r week_of_the_year=$(date +%U) +if [ $(( week_of_the_year % 2 )) -eq 0 ]; then + local tmp=$master + master=$standby + standby=$tmp +fi +``` + +This way, a DNS failover is performed weekly so that the ACME automation can update the Let's Encrypt certificates (for master and standby) before they expire on each VM. + +The ACME automation is yet another daily CRON script `/usr/local/bin/acme.sh`. It iterates over all of my Let's Encrypt hosts, checks whether they resolve to the same IP address as the current VM, and only then invokes the ACME client to request or renew the TLS certificates. So, there are always correct requests made to Let's Encrypt. + +Let's encrypt certificates usually expire after 3 months, so a weekly failover of my VMs is plenty. + +[`acme.sh.tpl` - Rex template for the `acme.sh` script of mine.](https://codeberg.org/snonux/rexfiles/src/branch/master/frontends/scripts/acme.sh.tpl) +[https://man.openbsd.org/acme-client.1](https://man.openbsd.org/acme-client.1) +[Let's Encrypt with OpenBSD and Rex](./2022-07-30-lets-encrypt-with-openbsd-and-rex.md) + +### Monitoring + +CRON is sending me an E-Mail whenever a failover is performed (or whenever a failover failed). Furthermore, I am monitoring my DNS servers and hosts through Gogios, the monitoring system I have developed. + +[https://codeberg.org/snonux/gogios](https://codeberg.org/snonux/gogios) +[KISS server monitoring with Gogios](./2023-06-01-kiss-server-monitoring-with-gogios.md) + +### Rex automation + +I use Rexify, a friendly configuration management system that allows automatic deployment and configuration. + +[https://www.rexify.org](https://www.rexify.org) +[https://codeberg.org/snonux/rexfiles/src/branch/master/frontends](https://codeberg.org/snonux/rexfiles/src/branch/master/frontends) + +## More HA + +Other high-available services running on my OpenBSD VMs are my MTAs for mail forwarding (OpenSMTPD) and the authoritative DNS servers (`nsd`) for all my domains. No particular HA setup is required, though, as the protocols (SMTP and DNS) already take care of the failover to the next available host! + +As a password manager, I use `geheim`, a command-line tool I wrote in Ruby with encrypted files in a git repository (I even have it installed in Termux on my Phone). For HA reasons, I simply updated the client code so that it always synchronises the database with both servers when I run the `sync` command there. + +[https://codeberg.org/snonux/geheim](https://codeberg.org/snonux/geheim) + +E-Mail your comments to `paul@nospam.buetow.org` :-) + +Other *BSD and KISS related posts are: + +[2016-04-09 Jails and ZFS with Puppet on FreeBSD](./2016-04-09-jails-and-zfs-on-freebsd-with-puppet.md) +[2022-07-30 Let's Encrypt with OpenBSD and Rex](./2022-07-30-lets-encrypt-with-openbsd-and-rex.md) +[2022-10-30 Installing DTail on OpenBSD](./2022-10-30-installing-dtail-on-openbsd.md) +[2023-06-01 KISS server monitoring with Gogios](./2023-06-01-kiss-server-monitoring-with-gogios.md) +[2023-10-29 KISS static web photo albums with `photoalbum.sh`](./2023-10-29-kiss-static-web-photo-albums-with-photoalbum.sh.md) +[2024-01-13 One reason why I love OpenBSD](./2024-01-13-one-reason-why-i-love-openbsd.md) + +[Back to the main site](../) diff --git a/gemfeed/index.md b/gemfeed/index.md index fc62cc72..d33b4992 100644 --- a/gemfeed/index.md +++ b/gemfeed/index.md @@ -2,6 +2,7 @@ ## To be in the .zone! +[2024-04-01 - KISS high-availability with OpenBSD](./2024-04-01-KISS-high-availability-with-OpenBSD.md) [2024-03-03 - A fine Fyne Android app for quickly logging ideas programmed in Go](./2024-03-03-a-fine-fyne-android-app-for-quickly-logging-ideas-programmed-in-golang.md) [2024-02-04 - From `babylon5.buetow.org` to `*.buetow.cloud`](./2024-02-04-from-babylon5.buetow.org-to-.cloud.md) [2024-01-13 - One reason why I love OpenBSD](./2024-01-13-one-reason-why-i-love-openbsd.md) -- cgit v1.2.3 From 3849ba8d0355acd41f4f5b780d601dfdded1fb25 Mon Sep 17 00:00:00 2001 From: Paul Buetow Date: Sat, 30 Mar 2024 22:17:10 +0200 Subject: Update content for md --- gemfeed/2024-04-01-KISS-high-availability-with-OpenBSD.md | 8 ++++---- 1 file changed, 4 insertions(+), 4 deletions(-) (limited to 'gemfeed') diff --git a/gemfeed/2024-04-01-KISS-high-availability-with-OpenBSD.md b/gemfeed/2024-04-01-KISS-high-availability-with-OpenBSD.md index 6ac7c89e..c49837ca 100644 --- a/gemfeed/2024-04-01-KISS-high-availability-with-OpenBSD.md +++ b/gemfeed/2024-04-01-KISS-high-availability-with-OpenBSD.md @@ -3,7 +3,7 @@ > Published at 2024-03-30T22:12:56+02:00 ``` -Art by Michael J. Penick (mod. by Paul B) +Art by Michael J. Penick (mod. by Paul B.) __________ / nsd tower\ ( @@ -29,16 +29,16 @@ _____|_:_:_| (o)-(o) |_:_:_|--'`-. ,--. ksh under-water (((\'/ I have always wanted a highly available setup for my personal websites. I could have used off-the-shelf hosting solutions or hosted my sites in an AWS S3 bucket. I have used technologies like BGP, LVS/IPVS, ldirectord, Pacemaker, heartbeat, heartbeat2, Corosync, keepalived, DRBD, and commercial F5 Load Balancers for high availability at work. -But still, my personal sites were never highly available. All those technologies are great for professional use, but I was looking for something much more straightforward for my personal space—something as KISS (keep it simple and stupid) as possible. +But still, my personal sites were never highly available. All those technologies are great for professional use, but I was looking for something much more straightforward for my personal space - something as KISS (keep it simple and stupid) as possible. It would be fine if my personal website wasn't highly available, but the geek in me wants it anyway. -> PS: ASCII-art reflects the OpenBSD under-water world with all the tools available in the base system. +> PS: ASCII-art reflects an OpenBSD under-water world with all the tools available in the base system. ## My auto-failover requirements * Be OpenBSD-based (I prefer OpenBSD because of the cleanliness and good documentation) and rely on as few external packages as possible. -* Don't rely on the hottest and newest tech (don't want to migrate everything to a new and fancier technology next month). +* Don't rely on the hottest and newest tech (don't want to migrate everything to a new and fancier technology next month already). * It should be reasonably cheap. I want to avoid paying a premium for floating IPs or fancy Elastic Load Balancers. * It should be geo-redundant. * It's fine if my sites aren't reachable for five or ten minutes every other month. Due to their static nature, I don't care if there's a split-brain scenario where some requests reach one server and other requests reach another server. -- cgit v1.2.3 From f82fce225a7ee75fb471274bde08e3cff51bbbde Mon Sep 17 00:00:00 2001 From: Paul Buetow Date: Sat, 30 Mar 2024 22:18:33 +0200 Subject: Update content for md --- gemfeed/2024-04-01-KISS-high-availability-with-OpenBSD.md | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) (limited to 'gemfeed') diff --git a/gemfeed/2024-04-01-KISS-high-availability-with-OpenBSD.md b/gemfeed/2024-04-01-KISS-high-availability-with-OpenBSD.md index c49837ca..dfa0c933 100644 --- a/gemfeed/2024-04-01-KISS-high-availability-with-OpenBSD.md +++ b/gemfeed/2024-04-01-KISS-high-availability-with-OpenBSD.md @@ -27,7 +27,7 @@ _____|_:_:_| (o)-(o) |_:_:_|--'`-. ,--. ksh under-water (((\'/ ``` -I have always wanted a highly available setup for my personal websites. I could have used off-the-shelf hosting solutions or hosted my sites in an AWS S3 bucket. I have used technologies like BGP, LVS/IPVS, ldirectord, Pacemaker, heartbeat, heartbeat2, Corosync, keepalived, DRBD, and commercial F5 Load Balancers for high availability at work. +I have always wanted a highly available setup for my personal websites. I could have used off-the-shelf hosting solutions or hosted my sites in an AWS S3 bucket. I have used technologies like BGP, LVS/IPVS, ldirectord, Pacemaker, STONITH, heartbeat, heartbeat2, Corosync, keepalived, DRBD, and commercial F5 Load Balancers for high availability at work. But still, my personal sites were never highly available. All those technologies are great for professional use, but I was looking for something much more straightforward for my personal space - something as KISS (keep it simple and stupid) as possible. -- cgit v1.2.3 From 30f3eea186f74241275970e876e6713bd52d0762 Mon Sep 17 00:00:00 2001 From: Paul Buetow Date: Sat, 30 Mar 2024 22:25:09 +0200 Subject: Update content for md --- gemfeed/2024-04-01-KISS-high-availability-with-OpenBSD.md | 1 + 1 file changed, 1 insertion(+) (limited to 'gemfeed') diff --git a/gemfeed/2024-04-01-KISS-high-availability-with-OpenBSD.md b/gemfeed/2024-04-01-KISS-high-availability-with-OpenBSD.md index dfa0c933..67e0484b 100644 --- a/gemfeed/2024-04-01-KISS-high-availability-with-OpenBSD.md +++ b/gemfeed/2024-04-01-KISS-high-availability-with-OpenBSD.md @@ -59,6 +59,7 @@ My HA solution for Web and Gemini is based on DNS (OpenBSD's `nsd`) and a simple [https://man.OpenBSD.org/sed](https://man.OpenBSD.org/sed) [https://man.OpenBSD.org/dig](https://man.OpenBSD.org/dig) [https://man.OpenBSD.org/ftp](https://man.OpenBSD.org/ftp) +[https://man.openbsd.org/cron](https://man.openbsd.org/cron) I also used the `dig` (for DNS checks) and `ftp` (for HTTP/HTTPS checks) programs. -- cgit v1.2.3 From b63917315dcd34dc49fe2ab90108b91c59151d6e Mon Sep 17 00:00:00 2001 From: Paul Buetow Date: Sat, 30 Mar 2024 22:26:11 +0200 Subject: Update content for md --- gemfeed/2024-04-01-KISS-high-availability-with-OpenBSD.md | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) (limited to 'gemfeed') diff --git a/gemfeed/2024-04-01-KISS-high-availability-with-OpenBSD.md b/gemfeed/2024-04-01-KISS-high-availability-with-OpenBSD.md index 67e0484b..d9d336dd 100644 --- a/gemfeed/2024-04-01-KISS-high-availability-with-OpenBSD.md +++ b/gemfeed/2024-04-01-KISS-high-availability-with-OpenBSD.md @@ -141,7 +141,7 @@ tramsform () { After the failover, the script reloads `nsd` and performs a sanity check to see if DNS still works. If not, a rollback will be performed: ```sh -# Race condition (e.g. script execution abored in the middle of the previous run) +# Race condition (e.g. script execution aborted in the middle of the previous run) if [ -f $zone_file.bak ]; then mv $zone_file.bak $zone_file fi -- cgit v1.2.3 From 7e43816cc69e30bfee815aa511997a51a98df693 Mon Sep 17 00:00:00 2001 From: Paul Buetow Date: Sat, 30 Mar 2024 22:27:31 +0200 Subject: Update content for md --- gemfeed/2024-04-01-KISS-high-availability-with-OpenBSD.md | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) (limited to 'gemfeed') diff --git a/gemfeed/2024-04-01-KISS-high-availability-with-OpenBSD.md b/gemfeed/2024-04-01-KISS-high-availability-with-OpenBSD.md index d9d336dd..d636a6ec 100644 --- a/gemfeed/2024-04-01-KISS-high-availability-with-OpenBSD.md +++ b/gemfeed/2024-04-01-KISS-high-availability-with-OpenBSD.md @@ -186,7 +186,7 @@ return 1 A non-zero return code (here, 3 when a rollback and 1 when a DNS failover was performed) will cause CRON to send an E-Mail with the whole script output. -The nameserver is running on both VMs, and both are configured to be "master" DNS servers so that they have their own individual zone files, which can be changed independently. Otherwise, my setup wouldn't work. The side effect is that under a split-brain scenario (both VMs cannot see each other), both would promote themselves to master via their local DNS entries. More about that later, but that's fine in my use case. +The authorative nameserver for my domains runs on both VMs, and both are configured to be a "master" DNS server so that they have their own individual zone files, which can be changed independently. Otherwise, my setup wouldn't work. The side effect is that under a split-brain scenario (both VMs cannot see each other), both would promote themselves to master via their local DNS entries. More about that later, but that's fine in my use case. Check out the whole script here: -- cgit v1.2.3 From 75fe2cd66ec16fda1ee6ed4bcbe43874b670a2b1 Mon Sep 17 00:00:00 2001 From: Paul Buetow Date: Sat, 30 Mar 2024 22:35:46 +0200 Subject: Update content for md --- gemfeed/2024-04-01-KISS-high-availability-with-OpenBSD.md | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) (limited to 'gemfeed') diff --git a/gemfeed/2024-04-01-KISS-high-availability-with-OpenBSD.md b/gemfeed/2024-04-01-KISS-high-availability-with-OpenBSD.md index d636a6ec..0412d6d2 100644 --- a/gemfeed/2024-04-01-KISS-high-availability-with-OpenBSD.md +++ b/gemfeed/2024-04-01-KISS-high-availability-with-OpenBSD.md @@ -27,7 +27,7 @@ _____|_:_:_| (o)-(o) |_:_:_|--'`-. ,--. ksh under-water (((\'/ ``` -I have always wanted a highly available setup for my personal websites. I could have used off-the-shelf hosting solutions or hosted my sites in an AWS S3 bucket. I have used technologies like BGP, LVS/IPVS, ldirectord, Pacemaker, STONITH, heartbeat, heartbeat2, Corosync, keepalived, DRBD, and commercial F5 Load Balancers for high availability at work. +I have always wanted a highly available setup for my personal websites. I could have used off-the-shelf hosting solutions or hosted my sites in an AWS S3 bucket. I have used technologies like (in unsorted and slightly unrelated order) BGP, LVS/IPVS, ldirectord, Pacemaker, STONITH, scripted VIP failover via ARP, heartbeat, heartbeat2, Corosync, keepalived, DRBD, and commercial F5 Load Balancers for high availability at work. But still, my personal sites were never highly available. All those technologies are great for professional use, but I was looking for something much more straightforward for my personal space - something as KISS (keep it simple and stupid) as possible. -- cgit v1.2.3 From b5e0cf471976f95aae88309e08b3389bd3b88296 Mon Sep 17 00:00:00 2001 From: Paul Buetow Date: Sat, 30 Mar 2024 22:42:25 +0200 Subject: Update content for md --- gemfeed/2024-04-01-KISS-high-availability-with-OpenBSD.md | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) (limited to 'gemfeed') diff --git a/gemfeed/2024-04-01-KISS-high-availability-with-OpenBSD.md b/gemfeed/2024-04-01-KISS-high-availability-with-OpenBSD.md index 0412d6d2..4fa285be 100644 --- a/gemfeed/2024-04-01-KISS-high-availability-with-OpenBSD.md +++ b/gemfeed/2024-04-01-KISS-high-availability-with-OpenBSD.md @@ -4,7 +4,7 @@ ``` Art by Michael J. Penick (mod. by Paul B.) - + ACME-sky __________ / nsd tower\ ( /____________\ (\) awk-ward -- cgit v1.2.3 From 3ad4a3576172bfd951c6a1e954fb6168b4bf2d1f Mon Sep 17 00:00:00 2001 From: Paul Buetow Date: Sat, 30 Mar 2024 22:48:15 +0200 Subject: Update content for md --- gemfeed/2024-04-01-KISS-high-availability-with-OpenBSD.md | 6 +++--- 1 file changed, 3 insertions(+), 3 deletions(-) (limited to 'gemfeed') diff --git a/gemfeed/2024-04-01-KISS-high-availability-with-OpenBSD.md b/gemfeed/2024-04-01-KISS-high-availability-with-OpenBSD.md index 4fa285be..f1668995 100644 --- a/gemfeed/2024-04-01-KISS-high-availability-with-OpenBSD.md +++ b/gemfeed/2024-04-01-KISS-high-availability-with-OpenBSD.md @@ -38,14 +38,14 @@ It would be fine if my personal website wasn't highly available, but the geek in ## My auto-failover requirements * Be OpenBSD-based (I prefer OpenBSD because of the cleanliness and good documentation) and rely on as few external packages as possible. -* Don't rely on the hottest and newest tech (don't want to migrate everything to a new and fancier technology next month already). +* Don't rely on the hottest and newest tech (don't want to migrate everything to a new and fancier technology next month already!). * It should be reasonably cheap. I want to avoid paying a premium for floating IPs or fancy Elastic Load Balancers. * It should be geo-redundant. * It's fine if my sites aren't reachable for five or ten minutes every other month. Due to their static nature, I don't care if there's a split-brain scenario where some requests reach one server and other requests reach another server. * Failover should work for both HTTP/HTTPS and Gemini protocols. My self-hosted MTAs and DNS servers should also be highly available. * Let's Encrypt TLS certificates should always work (before and after a failover). -* Have good monitoring in place so I know when a failover was performed and when something went wrong with the failover. -* Don't configure everything manually. The configuration should be automated and reproducible. +* Have good monitoring in place so I know when a failover was performed and when something went wrong with the failover. (This isn't part of the OpenBSD base system, but I coded my own monigoring system in Go) +* Don't configure everything manually. The configuration should be automated and reproducible. (This isn't part of the OpenBSD base syste, but I didn't need to install any external package on OpenBSD either) ## My HA solution -- cgit v1.2.3 From ada9cfa1d37c61c7ff86cd28af2935151757b1cb Mon Sep 17 00:00:00 2001 From: Paul Buetow Date: Sat, 30 Mar 2024 22:49:04 +0200 Subject: Update content for md --- gemfeed/2024-04-01-KISS-high-availability-with-OpenBSD.md | 4 ++-- 1 file changed, 2 insertions(+), 2 deletions(-) (limited to 'gemfeed') diff --git a/gemfeed/2024-04-01-KISS-high-availability-with-OpenBSD.md b/gemfeed/2024-04-01-KISS-high-availability-with-OpenBSD.md index f1668995..36031420 100644 --- a/gemfeed/2024-04-01-KISS-high-availability-with-OpenBSD.md +++ b/gemfeed/2024-04-01-KISS-high-availability-with-OpenBSD.md @@ -44,8 +44,8 @@ It would be fine if my personal website wasn't highly available, but the geek in * It's fine if my sites aren't reachable for five or ten minutes every other month. Due to their static nature, I don't care if there's a split-brain scenario where some requests reach one server and other requests reach another server. * Failover should work for both HTTP/HTTPS and Gemini protocols. My self-hosted MTAs and DNS servers should also be highly available. * Let's Encrypt TLS certificates should always work (before and after a failover). -* Have good monitoring in place so I know when a failover was performed and when something went wrong with the failover. (This isn't part of the OpenBSD base system, but I coded my own monigoring system in Go) -* Don't configure everything manually. The configuration should be automated and reproducible. (This isn't part of the OpenBSD base syste, but I didn't need to install any external package on OpenBSD either) +* Have good monitoring in place so I know when a failover was performed and when something went wrong with the failover. (This isn't part of the OpenBSD base system, but I coded my own monigoring system in Go.) +* Don't configure everything manually. The configuration should be automated and reproducible. (This isn't part of the OpenBSD base system, but I didn't need to install any external package on OpenBSD either.) ## My HA solution -- cgit v1.2.3 From 0cab33385a30fa70c628da947da65c9ec385db9f Mon Sep 17 00:00:00 2001 From: Paul Buetow Date: Sat, 30 Mar 2024 22:50:43 +0200 Subject: Update content for md --- gemfeed/2024-04-01-KISS-high-availability-with-OpenBSD.md | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) (limited to 'gemfeed') diff --git a/gemfeed/2024-04-01-KISS-high-availability-with-OpenBSD.md b/gemfeed/2024-04-01-KISS-high-availability-with-OpenBSD.md index 36031420..f5f0a126 100644 --- a/gemfeed/2024-04-01-KISS-high-availability-with-OpenBSD.md +++ b/gemfeed/2024-04-01-KISS-high-availability-with-OpenBSD.md @@ -45,7 +45,7 @@ It would be fine if my personal website wasn't highly available, but the geek in * Failover should work for both HTTP/HTTPS and Gemini protocols. My self-hosted MTAs and DNS servers should also be highly available. * Let's Encrypt TLS certificates should always work (before and after a failover). * Have good monitoring in place so I know when a failover was performed and when something went wrong with the failover. (This isn't part of the OpenBSD base system, but I coded my own monigoring system in Go.) -* Don't configure everything manually. The configuration should be automated and reproducible. (This isn't part of the OpenBSD base system, but I didn't need to install any external package on OpenBSD either.) +* Don't configure everything manually. The configuration should be automated and reproducible. (This isn't part of the OpenBSD base system, but I didn't need to install any external software on OpenBSD either.) ## My HA solution -- cgit v1.2.3 From e1c1287b029c0475b2ab11763b011e406bec18de Mon Sep 17 00:00:00 2001 From: Paul Buetow Date: Sat, 30 Mar 2024 22:55:38 +0200 Subject: Update content for md --- gemfeed/2016-04-09-jails-and-zfs-on-freebsd-with-puppet.md | 1 + gemfeed/2021-09-12-keep-it-simple-and-stupid.md | 1 + gemfeed/2022-07-30-lets-encrypt-with-openbsd-and-rex.md | 1 + gemfeed/2023-06-01-kiss-server-monitoring-with-gogios.md | 1 + gemfeed/2023-10-29-kiss-static-web-photo-albums-with-photoalbum.sh.md | 1 + gemfeed/2024-01-13-one-reason-why-i-love-openbsd.md | 1 + gemfeed/2024-04-01-KISS-high-availability-with-OpenBSD.md | 1 + 7 files changed, 7 insertions(+) (limited to 'gemfeed') diff --git a/gemfeed/2016-04-09-jails-and-zfs-on-freebsd-with-puppet.md b/gemfeed/2016-04-09-jails-and-zfs-on-freebsd-with-puppet.md index 3a2d1514..ff7e2413 100644 --- a/gemfeed/2016-04-09-jails-and-zfs-on-freebsd-with-puppet.md +++ b/gemfeed/2016-04-09-jails-and-zfs-on-freebsd-with-puppet.md @@ -393,5 +393,6 @@ Other *BSD related posts are: [2022-07-30 Let's Encrypt with OpenBSD and Rex](./2022-07-30-lets-encrypt-with-openbsd-and-rex.md) [2022-10-30 Installing DTail on OpenBSD](./2022-10-30-installing-dtail-on-openbsd.md) [2024-01-13 One reason why I love OpenBSD](./2024-01-13-one-reason-why-i-love-openbsd.md) +[2024-04-01 KISS high-availability with OpenBSD](./2024-04-01-KISS-high-availability-with-OpenBSD.md) [Back to the main site](../) diff --git a/gemfeed/2021-09-12-keep-it-simple-and-stupid.md b/gemfeed/2021-09-12-keep-it-simple-and-stupid.md index 5cdb8e1d..4948944f 100644 --- a/gemfeed/2021-09-12-keep-it-simple-and-stupid.md +++ b/gemfeed/2021-09-12-keep-it-simple-and-stupid.md @@ -101,6 +101,7 @@ Other KISS-related posts are: [2021-09-12 Keep it simple and stupid (You are currently reading this)](./2021-09-12-keep-it-simple-and-stupid.md) [2023-06-01 KISS server monitoring with Gogios](./2023-06-01-kiss-server-monitoring-with-gogios.md) [2023-10-29 KISS static web photo albums with `photoalbum.sh`](./2023-10-29-kiss-static-web-photo-albums-with-photoalbum.sh.md) +[2024-04-01 KISS high-availability with OpenBSD](./2024-04-01-KISS-high-availability-with-OpenBSD.md) > Controversially, a lack of features is a feature. Enjoy your peace an quiet. - Michael W Lucas diff --git a/gemfeed/2022-07-30-lets-encrypt-with-openbsd-and-rex.md b/gemfeed/2022-07-30-lets-encrypt-with-openbsd-and-rex.md index 16e8d656..b25f8669 100644 --- a/gemfeed/2022-07-30-lets-encrypt-with-openbsd-and-rex.md +++ b/gemfeed/2022-07-30-lets-encrypt-with-openbsd-and-rex.md @@ -664,5 +664,6 @@ Other *BSD related posts are: [2022-07-30 Let's Encrypt with OpenBSD and Rex (You are currently reading this)](./2022-07-30-lets-encrypt-with-openbsd-and-rex.md) [2022-10-30 Installing DTail on OpenBSD](./2022-10-30-installing-dtail-on-openbsd.md) [2024-01-13 One reason why I love OpenBSD](./2024-01-13-one-reason-why-i-love-openbsd.md) +[2024-04-01 KISS high-availability with OpenBSD](./2024-04-01-KISS-high-availability-with-OpenBSD.md) [Back to the main site](../) diff --git a/gemfeed/2023-06-01-kiss-server-monitoring-with-gogios.md b/gemfeed/2023-06-01-kiss-server-monitoring-with-gogios.md index fd651af1..981a63a8 100644 --- a/gemfeed/2023-06-01-kiss-server-monitoring-with-gogios.md +++ b/gemfeed/2023-06-01-kiss-server-monitoring-with-gogios.md @@ -243,5 +243,6 @@ Other KISS-related posts are: [2021-09-12 Keep it simple and stupid](./2021-09-12-keep-it-simple-and-stupid.md) [2023-06-01 KISS server monitoring with Gogios (You are currently reading this)](./2023-06-01-kiss-server-monitoring-with-gogios.md) [2023-10-29 KISS static web photo albums with `photoalbum.sh`](./2023-10-29-kiss-static-web-photo-albums-with-photoalbum.sh.md) +[2024-04-01 KISS high-availability with OpenBSD](./2024-04-01-KISS-high-availability-with-OpenBSD.md) [Back to the main site](../) diff --git a/gemfeed/2023-10-29-kiss-static-web-photo-albums-with-photoalbum.sh.md b/gemfeed/2023-10-29-kiss-static-web-photo-albums-with-photoalbum.sh.md index c0a94752..ad26ab09 100644 --- a/gemfeed/2023-10-29-kiss-static-web-photo-albums-with-photoalbum.sh.md +++ b/gemfeed/2023-10-29-kiss-static-web-photo-albums-with-photoalbum.sh.md @@ -271,5 +271,6 @@ Other Bash and KISS-related posts are: [2023-06-01 KISS server monitoring with Gogios](./2023-06-01-kiss-server-monitoring-with-gogios.md) [2023-10-29 KISS static web photo albums with `photoalbum.sh` (You are currently reading this)](./2023-10-29-kiss-static-web-photo-albums-with-photoalbum.sh.md) [2023-12-10 Bash Golf Part 3](./2023-12-10-bash-golf-part-3.md) +[2024-04-01 KISS high-availability with OpenBSD](./2024-04-01-KISS-high-availability-with-OpenBSD.md) [Back to the main site](../) diff --git a/gemfeed/2024-01-13-one-reason-why-i-love-openbsd.md b/gemfeed/2024-01-13-one-reason-why-i-love-openbsd.md index d0fe6a99..f598189b 100644 --- a/gemfeed/2024-01-13-one-reason-why-i-love-openbsd.md +++ b/gemfeed/2024-01-13-one-reason-why-i-love-openbsd.md @@ -55,5 +55,6 @@ Other *BSD related posts are: [2022-07-30 Let's Encrypt with OpenBSD and Rex](./2022-07-30-lets-encrypt-with-openbsd-and-rex.md) [2022-10-30 Installing DTail on OpenBSD](./2022-10-30-installing-dtail-on-openbsd.md) [2024-01-13 One reason why I love OpenBSD (You are currently reading this)](./2024-01-13-one-reason-why-i-love-openbsd.md) +[2024-04-01 KISS high-availability with OpenBSD](./2024-04-01-KISS-high-availability-with-OpenBSD.md) [Back to the main site](../) diff --git a/gemfeed/2024-04-01-KISS-high-availability-with-OpenBSD.md b/gemfeed/2024-04-01-KISS-high-availability-with-OpenBSD.md index f5f0a126..6b32eaeb 100644 --- a/gemfeed/2024-04-01-KISS-high-availability-with-OpenBSD.md +++ b/gemfeed/2024-04-01-KISS-high-availability-with-OpenBSD.md @@ -285,5 +285,6 @@ Other *BSD and KISS related posts are: [2023-06-01 KISS server monitoring with Gogios](./2023-06-01-kiss-server-monitoring-with-gogios.md) [2023-10-29 KISS static web photo albums with `photoalbum.sh`](./2023-10-29-kiss-static-web-photo-albums-with-photoalbum.sh.md) [2024-01-13 One reason why I love OpenBSD](./2024-01-13-one-reason-why-i-love-openbsd.md) +[2024-04-01 KISS high-availability with OpenBSD (You are currently reading this)](./2024-04-01-KISS-high-availability-with-OpenBSD.md) [Back to the main site](../) -- cgit v1.2.3 From 3c1273840565f16fb717a6c75a478ad3555bce4f Mon Sep 17 00:00:00 2001 From: Paul Buetow Date: Sat, 30 Mar 2024 23:00:54 +0200 Subject: Update content for md --- gemfeed/2024-04-01-KISS-high-availability-with-OpenBSD.md | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) (limited to 'gemfeed') diff --git a/gemfeed/2024-04-01-KISS-high-availability-with-OpenBSD.md b/gemfeed/2024-04-01-KISS-high-availability-with-OpenBSD.md index 6b32eaeb..bbad2f6c 100644 --- a/gemfeed/2024-04-01-KISS-high-availability-with-OpenBSD.md +++ b/gemfeed/2024-04-01-KISS-high-availability-with-OpenBSD.md @@ -44,7 +44,7 @@ It would be fine if my personal website wasn't highly available, but the geek in * It's fine if my sites aren't reachable for five or ten minutes every other month. Due to their static nature, I don't care if there's a split-brain scenario where some requests reach one server and other requests reach another server. * Failover should work for both HTTP/HTTPS and Gemini protocols. My self-hosted MTAs and DNS servers should also be highly available. * Let's Encrypt TLS certificates should always work (before and after a failover). -* Have good monitoring in place so I know when a failover was performed and when something went wrong with the failover. (This isn't part of the OpenBSD base system, but I coded my own monigoring system in Go.) +* Have good monitoring in place so I know when a failover was performed and when something went wrong with the failover. (This isn't part of the OpenBSD base system, but I coded my own monitoring system in Go.) * Don't configure everything manually. The configuration should be automated and reproducible. (This isn't part of the OpenBSD base system, but I didn't need to install any external software on OpenBSD either.) ## My HA solution -- cgit v1.2.3 From 3a90bd63cd4cc6365e6a8d3f65eb228842900668 Mon Sep 17 00:00:00 2001 From: Paul Buetow Date: Sat, 30 Mar 2024 23:37:05 +0200 Subject: Update content for md --- gemfeed/2024-04-01-KISS-high-availability-with-OpenBSD.md | 4 ++-- 1 file changed, 2 insertions(+), 2 deletions(-) (limited to 'gemfeed') diff --git a/gemfeed/2024-04-01-KISS-high-availability-with-OpenBSD.md b/gemfeed/2024-04-01-KISS-high-availability-with-OpenBSD.md index bbad2f6c..54733209 100644 --- a/gemfeed/2024-04-01-KISS-high-availability-with-OpenBSD.md +++ b/gemfeed/2024-04-01-KISS-high-availability-with-OpenBSD.md @@ -190,7 +190,7 @@ The authorative nameserver for my domains runs on both VMs, and both are configu Check out the whole script here: -[https://codeberg.org/snonux/rexfiles/src/branch/master/frontends/scripts/dns-failover.ksh](https://codeberg.org/snonux/rexfiles/src/branch/master/frontends/scripts/dns-failover.ksh) +[dns-failover.ksh](https://codeberg.org/snonux/rexfiles/src/branch/master/frontends/scripts/dns-failover.ksh) ### Fairly cheap and geo-redundant @@ -265,7 +265,7 @@ CRON is sending me an E-Mail whenever a failover is performed (or whenever a fai I use Rexify, a friendly configuration management system that allows automatic deployment and configuration. [https://www.rexify.org](https://www.rexify.org) -[https://codeberg.org/snonux/rexfiles/src/branch/master/frontends](https://codeberg.org/snonux/rexfiles/src/branch/master/frontends) +[codeberg.org/snonux/rexfiles/frontends](https://codeberg.org/snonux/rexfiles/src/branch/master/frontends) ## More HA -- cgit v1.2.3 From c995a54b35546d3a8835b8235b21c2fa463062c2 Mon Sep 17 00:00:00 2001 From: Paul Buetow Date: Sun, 31 Mar 2024 11:01:33 +0300 Subject: Update content for md --- gemfeed/2024-04-01-KISS-high-availability-with-OpenBSD.md | 14 ++++++++++---- 1 file changed, 10 insertions(+), 4 deletions(-) (limited to 'gemfeed') diff --git a/gemfeed/2024-04-01-KISS-high-availability-with-OpenBSD.md b/gemfeed/2024-04-01-KISS-high-availability-with-OpenBSD.md index 54733209..2bc5f162 100644 --- a/gemfeed/2024-04-01-KISS-high-availability-with-OpenBSD.md +++ b/gemfeed/2024-04-01-KISS-high-availability-with-OpenBSD.md @@ -44,8 +44,8 @@ It would be fine if my personal website wasn't highly available, but the geek in * It's fine if my sites aren't reachable for five or ten minutes every other month. Due to their static nature, I don't care if there's a split-brain scenario where some requests reach one server and other requests reach another server. * Failover should work for both HTTP/HTTPS and Gemini protocols. My self-hosted MTAs and DNS servers should also be highly available. * Let's Encrypt TLS certificates should always work (before and after a failover). -* Have good monitoring in place so I know when a failover was performed and when something went wrong with the failover. (This isn't part of the OpenBSD base system, but I coded my own monitoring system in Go.) -* Don't configure everything manually. The configuration should be automated and reproducible. (This isn't part of the OpenBSD base system, but I didn't need to install any external software on OpenBSD either.) +* Have good monitoring in place so I know when a failover was performed and when something went wrong with the failover. +* Don't configure everything manually. The configuration should be automated and reproducible. ## My HA solution @@ -259,7 +259,9 @@ CRON is sending me an E-Mail whenever a failover is performed (or whenever a fai [https://codeberg.org/snonux/gogios](https://codeberg.org/snonux/gogios) [KISS server monitoring with Gogios](./2023-06-01-kiss-server-monitoring-with-gogios.md) - + +Gogios, as I developed it by myself, isn't part of the OpenBSD base system. + ### Rex automation I use Rexify, a friendly configuration management system that allows automatic deployment and configuration. @@ -267,9 +269,13 @@ I use Rexify, a friendly configuration management system that allows automatic d [https://www.rexify.org](https://www.rexify.org) [codeberg.org/snonux/rexfiles/frontends](https://codeberg.org/snonux/rexfiles/src/branch/master/frontends) +Rex isn't part of the OpenBSD base system, but I didn't need to install any external software on OpenBSD either as Rex is invoked from my Laptop! + ## More HA -Other high-available services running on my OpenBSD VMs are my MTAs for mail forwarding (OpenSMTPD) and the authoritative DNS servers (`nsd`) for all my domains. No particular HA setup is required, though, as the protocols (SMTP and DNS) already take care of the failover to the next available host! +Other high-available services running on my OpenBSD VMs are my MTAs for mail forwarding (OpenSMTPD - also part of the OpenBSD base system) and the authoritative DNS servers (`nsd`) for all my domains. No particular HA setup is required, though, as the protocols (SMTP and DNS) already take care of the failover to the next available host! + +[https://www.opensmtpd.org/](https://www.opensmtpd.org/) As a password manager, I use `geheim`, a command-line tool I wrote in Ruby with encrypted files in a git repository (I even have it installed in Termux on my Phone). For HA reasons, I simply updated the client code so that it always synchronises the database with both servers when I run the `sync` command there. -- cgit v1.2.3 From 96d827b2b502df181ae547fd773d4f4306d684d1 Mon Sep 17 00:00:00 2001 From: Paul Buetow Date: Tue, 2 Apr 2024 01:33:34 +0300 Subject: Update content for md --- gemfeed/2024-04-01-KISS-high-availability-with-OpenBSD.md | 4 ++-- 1 file changed, 2 insertions(+), 2 deletions(-) (limited to 'gemfeed') diff --git a/gemfeed/2024-04-01-KISS-high-availability-with-OpenBSD.md b/gemfeed/2024-04-01-KISS-high-availability-with-OpenBSD.md index 2bc5f162..7f137793 100644 --- a/gemfeed/2024-04-01-KISS-high-availability-with-OpenBSD.md +++ b/gemfeed/2024-04-01-KISS-high-availability-with-OpenBSD.md @@ -59,7 +59,7 @@ My HA solution for Web and Gemini is based on DNS (OpenBSD's `nsd`) and a simple [https://man.OpenBSD.org/sed](https://man.OpenBSD.org/sed) [https://man.OpenBSD.org/dig](https://man.OpenBSD.org/dig) [https://man.OpenBSD.org/ftp](https://man.OpenBSD.org/ftp) -[https://man.openbsd.org/cron](https://man.openbsd.org/cron) +[https://man.OpenBSD.org/cron](https://man.OpenBSD.org/cron) I also used the `dig` (for DNS checks) and `ftp` (for HTTP/HTTPS checks) programs. @@ -211,7 +211,7 @@ A split-brain scenario between the old master and the new master might happen. T ### Failover support for multiple protocols -With the DNS failover, HTTP, HTTPS, and Gemini protocols are failovered. This works because all domain virtual hosts are configured on either VM's `httpd` (OpenBSD's HTTP server) and `relayd` (it's also part of OpenBSD and I use it to TLS offload the Gemini protocol). So, both VMs accept requests for all the hosts. It's just a matter of the DNS entry, which hosts receive the requests. +With the DNS failover, HTTP, HTTPS, and Gemini protocols are failovered. This works because all domain virtual hosts are configured on either VM's `httpd` (OpenBSD's HTTP server) and `relayd` (it's also part of OpenBSD and I use it to TLS offload the Gemini protocol). So, both VMs accept requests for all the hosts. It's just a matter of the DNS entries, which VM receives the requests. [https://man.openbsd.org/httpd.8](https://man.openbsd.org/httpd.8) [https://man.openbsd.org/relayd.8](https://man.openbsd.org/relayd.8) -- cgit v1.2.3 From 596e6601039e9f8d343da4b04cb2ad941acc00ac Mon Sep 17 00:00:00 2001 From: Paul Buetow Date: Wed, 3 Apr 2024 00:06:36 +0300 Subject: Update content for md --- gemfeed/2024-04-01-KISS-high-availability-with-OpenBSD.md | 6 +++--- 1 file changed, 3 insertions(+), 3 deletions(-) (limited to 'gemfeed') diff --git a/gemfeed/2024-04-01-KISS-high-availability-with-OpenBSD.md b/gemfeed/2024-04-01-KISS-high-availability-with-OpenBSD.md index 7f137793..542e4c60 100644 --- a/gemfeed/2024-04-01-KISS-high-availability-with-OpenBSD.md +++ b/gemfeed/2024-04-01-KISS-high-availability-with-OpenBSD.md @@ -113,8 +113,8 @@ standby 300 IN AAAA 2a01:4f8:c17:20f1::42 ; Enable failover ``` ```sh -tramsform () { - sed -E ' +transform () { + sed -E ' /IN A .*; Enable failover/ { /^standby/! { s/^(.*) 300 IN A (.*) ; (.*)/\1 300 IN A '$(cat /var/nsd/run/master_a)' ; \3/; @@ -134,7 +134,7 @@ tramsform () { / ; serial/ { s/^( +) ([0-9]+) .*; (.*)/\1 '$(date +%s)' ; \3/; } - ' + ' } ``` -- cgit v1.2.3 From f42d9230e976a7332c25f6d97dd20112e92bcffc Mon Sep 17 00:00:00 2001 From: Paul Buetow Date: Sat, 13 Apr 2024 00:15:08 +0300 Subject: Update content for md --- gemfeed/2024-04-01-KISS-high-availability-with-OpenBSD.md | 12 ++++++------ 1 file changed, 6 insertions(+), 6 deletions(-) (limited to 'gemfeed') diff --git a/gemfeed/2024-04-01-KISS-high-availability-with-OpenBSD.md b/gemfeed/2024-04-01-KISS-high-availability-with-OpenBSD.md index 542e4c60..f5477fe3 100644 --- a/gemfeed/2024-04-01-KISS-high-availability-with-OpenBSD.md +++ b/gemfeed/2024-04-01-KISS-high-availability-with-OpenBSD.md @@ -196,8 +196,8 @@ Check out the whole script here: I am renting two small OpenBSD VMs: One at OpenBSD Amsterdam and the other at Hetzner Cloud. So, both VMs are hosted at another provider, in different IP subnets, and in different countries (the Netherlands and Germany). -[https://openbsd.amsterdam](https://openbsd.amsterdam) -[https://www.hetzner.cloud](https://www.hetzner.cloud) +[https://OpenBSD.Amsterdam](https://OpenBSD.Amsterdam) +[https://www.Hetzner.cloud](https://www.Hetzner.cloud) I only have a little traffic on my sites. I could always upload the static content to AWS S3 if I suddenly had to. But this will never be required. @@ -213,8 +213,8 @@ A split-brain scenario between the old master and the new master might happen. T With the DNS failover, HTTP, HTTPS, and Gemini protocols are failovered. This works because all domain virtual hosts are configured on either VM's `httpd` (OpenBSD's HTTP server) and `relayd` (it's also part of OpenBSD and I use it to TLS offload the Gemini protocol). So, both VMs accept requests for all the hosts. It's just a matter of the DNS entries, which VM receives the requests. -[https://man.openbsd.org/httpd.8](https://man.openbsd.org/httpd.8) -[https://man.openbsd.org/relayd.8](https://man.openbsd.org/relayd.8) +[https://man.OpenBSD.org/httpd.8](https://man.OpenBSD.org/httpd.8) +[https://man.OpenBSD.org/relayd.8](https://man.OpenBSD.org/relayd.8) For example, the master is responsible for the `https://www.foo.zone` and `https://foo.zone` hosts, whereas the standby can be reached via `https://standby.foo.zone` (port 80 for plain HTTP works as well). The same principle is followed with all the other hosts, e.g. `irregular.ninja`, `paul.buetow.org` and so on. The same applies to my Gemini capsules for `gemini://foo.zone`, `gemini://standby.foo.zone`, `gemini://paul.buetow.org` and `gemini://standby.paul.buetow.org`. @@ -250,7 +250,7 @@ The ACME automation is yet another daily CRON script `/usr/local/bin/acme.sh`. I Let's encrypt certificates usually expire after 3 months, so a weekly failover of my VMs is plenty. [`acme.sh.tpl` - Rex template for the `acme.sh` script of mine.](https://codeberg.org/snonux/rexfiles/src/branch/master/frontends/scripts/acme.sh.tpl) -[https://man.openbsd.org/acme-client.1](https://man.openbsd.org/acme-client.1) +[https://man.OpenBSD.org/acme-client.1](https://man.OpenBSD.org/acme-client.1) [Let's Encrypt with OpenBSD and Rex](./2022-07-30-lets-encrypt-with-openbsd-and-rex.md) ### Monitoring @@ -275,7 +275,7 @@ Rex isn't part of the OpenBSD base system, but I didn't need to install any exte Other high-available services running on my OpenBSD VMs are my MTAs for mail forwarding (OpenSMTPD - also part of the OpenBSD base system) and the authoritative DNS servers (`nsd`) for all my domains. No particular HA setup is required, though, as the protocols (SMTP and DNS) already take care of the failover to the next available host! -[https://www.opensmtpd.org/](https://www.opensmtpd.org/) +[https://www.OpenSMTPD.org/](https://www.OpenSMTPD.org/) As a password manager, I use `geheim`, a command-line tool I wrote in Ruby with encrypted files in a git repository (I even have it installed in Termux on my Phone). For HA reasons, I simply updated the client code so that it always synchronises the database with both servers when I run the `sync` command there. -- cgit v1.2.3 From 73c837385e4e8132cd729d82b509b1b97012dbb4 Mon Sep 17 00:00:00 2001 From: Paul Buetow Date: Sun, 21 Apr 2024 11:44:58 +0300 Subject: Update content for md --- .../2024-04-01-KISS-high-availability-with-OpenBSD.md | 18 ++++++++++++++++++ 1 file changed, 18 insertions(+) (limited to 'gemfeed') diff --git a/gemfeed/2024-04-01-KISS-high-availability-with-OpenBSD.md b/gemfeed/2024-04-01-KISS-high-availability-with-OpenBSD.md index f5477fe3..39f0c59c 100644 --- a/gemfeed/2024-04-01-KISS-high-availability-with-OpenBSD.md +++ b/gemfeed/2024-04-01-KISS-high-availability-with-OpenBSD.md @@ -27,6 +27,24 @@ _____|_:_:_| (o)-(o) |_:_:_|--'`-. ,--. ksh under-water (((\'/ ``` +``` +Table of contents: + KISS high-availability with OpenBSD + My auto-failover requirements + My HA solution + Only OpenBSD base installation required + !/bin/ksh + Race condition (e.g. script execution aborted in the middle of the previous run) + Fairly cheap and geo-redundant + Failover time and split-brain + Failover support for multiple protocols + Let's encrypt TLS certificates + Weekly auto-failover for Let's Encrypt automation + Monitoring + Rex automation + More HA +``` + I have always wanted a highly available setup for my personal websites. I could have used off-the-shelf hosting solutions or hosted my sites in an AWS S3 bucket. I have used technologies like (in unsorted and slightly unrelated order) BGP, LVS/IPVS, ldirectord, Pacemaker, STONITH, scripted VIP failover via ARP, heartbeat, heartbeat2, Corosync, keepalived, DRBD, and commercial F5 Load Balancers for high availability at work. But still, my personal sites were never highly available. All those technologies are great for professional use, but I was looking for something much more straightforward for my personal space - something as KISS (keep it simple and stupid) as possible. -- cgit v1.2.3 From 919ea99ce73c30b838e7dbcd74d5cb728ec1ef78 Mon Sep 17 00:00:00 2001 From: Paul Buetow Date: Sun, 21 Apr 2024 11:53:02 +0300 Subject: Update content for md --- gemfeed/2024-04-01-KISS-high-availability-with-OpenBSD.md | 8 +++----- 1 file changed, 3 insertions(+), 5 deletions(-) (limited to 'gemfeed') diff --git a/gemfeed/2024-04-01-KISS-high-availability-with-OpenBSD.md b/gemfeed/2024-04-01-KISS-high-availability-with-OpenBSD.md index 39f0c59c..8a39fbc1 100644 --- a/gemfeed/2024-04-01-KISS-high-availability-with-OpenBSD.md +++ b/gemfeed/2024-04-01-KISS-high-availability-with-OpenBSD.md @@ -33,13 +33,10 @@ Table of contents: My auto-failover requirements My HA solution Only OpenBSD base installation required - !/bin/ksh - Race condition (e.g. script execution aborted in the middle of the previous run) Fairly cheap and geo-redundant Failover time and split-brain Failover support for multiple protocols Let's encrypt TLS certificates - Weekly auto-failover for Let's Encrypt automation Monitoring Rex automation More HA @@ -159,7 +156,8 @@ transform () { After the failover, the script reloads `nsd` and performs a sanity check to see if DNS still works. If not, a rollback will be performed: ```sh -# Race condition (e.g. script execution aborted in the middle of the previous run) +#! Race condition !# + if [ -f $zone_file.bak ]; then mv $zone_file.bak $zone_file fi @@ -252,7 +250,7 @@ As a solution, the CRON job responsible for the DNS failover also checks for the Which translates to: ```sh -# Weekly auto-failover for Let's Encrypt automation +#! Weekly auto-failover for Let's Encrypt automation !# local -i -r week_of_the_year=$(date +%U) if [ $(( week_of_the_year % 2 )) -eq 0 ]; then local tmp=$master -- cgit v1.2.3 From 4e5ecbedb9dfb8b432bdf49c0cc1138a0288e41d Mon Sep 17 00:00:00 2001 From: Paul Buetow Date: Sun, 21 Apr 2024 13:47:09 +0300 Subject: Update content for md --- gemfeed/2024-04-01-KISS-high-availability-with-OpenBSD.md | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) (limited to 'gemfeed') diff --git a/gemfeed/2024-04-01-KISS-high-availability-with-OpenBSD.md b/gemfeed/2024-04-01-KISS-high-availability-with-OpenBSD.md index 8a39fbc1..75e50778 100644 --- a/gemfeed/2024-04-01-KISS-high-availability-with-OpenBSD.md +++ b/gemfeed/2024-04-01-KISS-high-availability-with-OpenBSD.md @@ -250,7 +250,7 @@ As a solution, the CRON job responsible for the DNS failover also checks for the Which translates to: ```sh -#! Weekly auto-failover for Let's Encrypt automation !# +# Weekly auto-failover for Let's Encrypt automation local -i -r week_of_the_year=$(date +%U) if [ $(( week_of_the_year % 2 )) -eq 0 ]; then local tmp=$master -- cgit v1.2.3 From 53c97f25cbbc9acf9c0b6b10bcdeddb98d39e390 Mon Sep 17 00:00:00 2001 From: Paul Buetow Date: Sat, 27 Apr 2024 14:34:52 +0300 Subject: Update content for md --- ...23-03-16-the-pragmatic-programmer-book-notes.md | 1 + ...-04-01-never-split-the-difference-book-notes.md | 1 + ...023-05-06-the-obstacle-is-the-way-book-notes.md | 1 + ...7-17-career-guide-and-soft-skills-book-notes.md | 1 + gemfeed/2023-11-11-mind-management-book-notes.md | 1 + gemfeed/2024-05-01-slow-productivity-book-notes.md | 137 +++++++++++++++++++++ gemfeed/index.md | 1 + 7 files changed, 143 insertions(+) create mode 100644 gemfeed/2024-05-01-slow-productivity-book-notes.md (limited to 'gemfeed') diff --git a/gemfeed/2023-03-16-the-pragmatic-programmer-book-notes.md b/gemfeed/2023-03-16-the-pragmatic-programmer-book-notes.md index c44ad505..b6c5784a 100644 --- a/gemfeed/2023-03-16-the-pragmatic-programmer-book-notes.md +++ b/gemfeed/2023-03-16-the-pragmatic-programmer-book-notes.md @@ -85,6 +85,7 @@ Other book notes of mine are: [2023-05-06 "The Obstacle is the Way" book notes](./2023-05-06-the-obstacle-is-the-way-book-notes.md) [2023-07-17 "Software Developmers Career Guide and Soft Skills" book notes](./2023-07-17-career-guide-and-soft-skills-book-notes.md) [2023-11-11 "Mind Management" book notes](./2023-11-11-mind-management-book-notes.md) +[2024-05-01 "Slow Productivity" book notes](./2024-05-01-slow-productivity-book-notes.md) [More books and other resources I found useful.](../resources.md) [Back to the main site](../) diff --git a/gemfeed/2023-04-01-never-split-the-difference-book-notes.md b/gemfeed/2023-04-01-never-split-the-difference-book-notes.md index f43360f3..946601fc 100644 --- a/gemfeed/2023-04-01-never-split-the-difference-book-notes.md +++ b/gemfeed/2023-04-01-never-split-the-difference-book-notes.md @@ -129,5 +129,6 @@ Other book notes of mine are: [2023-05-06 "The Obstacle is the Way" book notes](./2023-05-06-the-obstacle-is-the-way-book-notes.md) [2023-07-17 "Software Developmers Career Guide and Soft Skills" book notes](./2023-07-17-career-guide-and-soft-skills-book-notes.md) [2023-11-11 "Mind Management" book notes](./2023-11-11-mind-management-book-notes.md) +[2024-05-01 "Slow Productivity" book notes](./2024-05-01-slow-productivity-book-notes.md) [Back to the main site](../) diff --git a/gemfeed/2023-05-06-the-obstacle-is-the-way-book-notes.md b/gemfeed/2023-05-06-the-obstacle-is-the-way-book-notes.md index 5d42d741..72bb0233 100644 --- a/gemfeed/2023-05-06-the-obstacle-is-the-way-book-notes.md +++ b/gemfeed/2023-05-06-the-obstacle-is-the-way-book-notes.md @@ -91,6 +91,7 @@ Other book notes of mine are: [2023-05-06 "The Obstacle is the Way" book notes (You are currently reading this)](./2023-05-06-the-obstacle-is-the-way-book-notes.md) [2023-07-17 "Software Developmers Career Guide and Soft Skills" book notes](./2023-07-17-career-guide-and-soft-skills-book-notes.md) [2023-11-11 "Mind Management" book notes](./2023-11-11-mind-management-book-notes.md) +[2024-05-01 "Slow Productivity" book notes](./2024-05-01-slow-productivity-book-notes.md) [More books and other resources I found useful.](../resources.md) [Back to the main site](../) diff --git a/gemfeed/2023-07-17-career-guide-and-soft-skills-book-notes.md b/gemfeed/2023-07-17-career-guide-and-soft-skills-book-notes.md index 5b6d1220..6d70da05 100644 --- a/gemfeed/2023-07-17-career-guide-and-soft-skills-book-notes.md +++ b/gemfeed/2023-07-17-career-guide-and-soft-skills-book-notes.md @@ -281,6 +281,7 @@ Other book notes of mine are: [2023-05-06 "The Obstacle is the Way" book notes](./2023-05-06-the-obstacle-is-the-way-book-notes.md) [2023-07-17 "Software Developmers Career Guide and Soft Skills" book notes (You are currently reading this)](./2023-07-17-career-guide-and-soft-skills-book-notes.md) [2023-11-11 "Mind Management" book notes](./2023-11-11-mind-management-book-notes.md) +[2024-05-01 "Slow Productivity" book notes](./2024-05-01-slow-productivity-book-notes.md) [More books and other resources I found useful.](../resources.md) [Back to the main site](../) diff --git a/gemfeed/2023-11-11-mind-management-book-notes.md b/gemfeed/2023-11-11-mind-management-book-notes.md index b0d86f16..bea77974 100644 --- a/gemfeed/2023-11-11-mind-management-book-notes.md +++ b/gemfeed/2023-11-11-mind-management-book-notes.md @@ -100,6 +100,7 @@ Other book notes of mine are: [2023-05-06 "The Obstacle is the Way" book notes](./2023-05-06-the-obstacle-is-the-way-book-notes.md) [2023-07-17 "Software Developmers Career Guide and Soft Skills" book notes](./2023-07-17-career-guide-and-soft-skills-book-notes.md) [2023-11-11 "Mind Management" book notes (You are currently reading this)](./2023-11-11-mind-management-book-notes.md) +[2024-05-01 "Slow Productivity" book notes](./2024-05-01-slow-productivity-book-notes.md) [More books and other resources I found useful.](../resources.md) [Back to the main site](../) diff --git a/gemfeed/2024-05-01-slow-productivity-book-notes.md b/gemfeed/2024-05-01-slow-productivity-book-notes.md new file mode 100644 index 00000000..910f91a4 --- /dev/null +++ b/gemfeed/2024-05-01-slow-productivity-book-notes.md @@ -0,0 +1,137 @@ +# "Slow Productivity" book notes + +> Published at 2024-04-27T14:18:51+03:00 + +These are my personal takeaways after reading "Slow Productivity - The lost Art of Accomplishment Without Burnout" by Cal Newport. + +The case studies in this book were a bit long, but they appeared to be well-researched. I will only highlight the interesting, actionable items in the book notes. + +These notes are mainly for my own use, but you may find them helpful. + +``` + ,.......... .........., + ,..,' '.' ',.., + ,' ,' : ', ', + ,' ,' : ', ', + ,' ,' : ', ', + ,' ,'............., : ,.............', ', +,' '............ '.' ............' ', + '''''''''''''''''';''';'''''''''''''''''' + ''' +``` + +"Slow productivity" does not mean being less productive. Cal Newport wants to point out that you can be much more productive with "slow productivity" than you would be without it. It is a different way of working than most of us are used to in the modern workplace, which is hyper-connected and always online. + +## Pseudo-productivity and Shallow work + +People use visible activity instead of real productivity because it's easier to measure. This is called pseudo-productivity. +Pseudo-productivity is used as a proxy for real productivity. If you don't look busy, you are dismissed as lazy or lacking a work ethic. + +There is a tendency to perform shallow work because people will otherwise dismiss you as lazy. A lot of shallow work can cause burnout, as multiple things are often being worked on in parallel. The more you have on your plate, the more stressed you will be. + +Shallow work usually doesn't help you to accomplish big things. Always have the big picture in mind. Shallow work can't be entirely eliminated, but it can be managed—for example, plan dedicated time slots for certain types of shallow work. + +## Accomplishments without burnout + +The overall perception is that if you want to accomplish something, you must put yourself on the verge of burnout. Cal Newport writes about "The lost Art of Accomplishments without Burnouts", where you can accomplish big things without all the stress usually involved. + +There are three principles for the maintenance of a sustainable work life: + +* Do fewer things +* Work at a natural pace +* Obsess over quality + +## Do fewer things + +There will always be more work. The faster you finish it, the quicker you will have something new on your plate. + +Reduce the overhead tax. The overhead tax is all the administrative work to be done. With every additional project, there will also be more administrative stuff to be done on your work plate. So, doing fewer things leads to more and better output and better quality for the projects you are working on. + +Limit the things on your plate. Limit your missions (personal goals, professional goals). Reduce your main objectives in life. More than five missions are usually not sustainable very easily, so you have to really prioritise what is important to you and your professional life. + +A mission is an overall objective/goal that can have multiple projects. Limit the projects as well. Some projects need clear endings (e.g., work in support of a never-ending flow of incoming requests). In this case, set limits (e.g., time box your support hours). You can also plan "office hours" for collaborative work with colleagues to avoid ad hoc distractions. + +The key point is that after making these commitments, you really deliver on them. This builds trust, and people will leave you alone and not ask for progress all the time. + +Doing fever things is essential for modern knowledge workers. Breathing space in your work also makes you more creative and happier overall. + +Pushing workers more work can make them less productive, so the better approach is the pull model, where workers pull in new work when the previous task is finished. + +If you can quantify how busy you are or how many other projects you already work on, then it is easier to say no to new things. For example, show what you are doing, what's in the roadmap, etc. Transparency is the key here. + +You can have your own simulated pull system if the company doesn't agree to a global one: + +* State which additional information you would need. +* Create a rough estimate of when you will be able to work on it +* Estimate how long the project would take. Double that estimate, as humans are very bad estimators. +* Respond to the requester and state that you will let him know when the estimates change. + +Sometimes, a little friction is all that is needed to combat incoming work, e.g., when your manager starts seeing the reality of your work plate, and you also request additional information for the task. If you already have too much on your plate, then decline the new project or make room for it in your calendar. If you present a large task list, others will struggle to assign more to you. + +Limit your daily goals. A good measure is to focus on one goal per day. You can time block time for deep work on your daily goal. During that time, you won't be easily available to others. + +The battle against distractions must be thought to be the master of your time. Nobody will fight this war for you. You have to do it for yourself. (Also, have a look at Cal Newport's "time block planning" method). + +Put tasks on autopilot (regular recurring tasks). + +## Work in a natural pace + +We suffer from overambitious timelines, task lists, and business. Focus on what matters. Don't rush your most important work to achieve better results. + +Don't rush. If you rush or are under pressure, you will be less effective and eventually burn out. Our brains work better then not rushy. The stress heuristic usually indicates too much work, and it is generally too late to reduce workload. That's why we all typically have dangerously too much to do. + +Have the courage to take longer to do things that are important. For example, plan on a yearly and larger scale, like 2 to 5 years. + +Find a reasonable time for a project and then double the project timeline against overconfident optimism. Humans are not great at estimating. They gravitate towards best-case estimates. If you have planned more than enough time for your project, then you will fall into a natural work pace. Otherwise, you will struggle with rushing and stress. + +Some days will still be intense and stressful, but those are exceptional cases. After those exceptions (e.g., finalizing that thing, etc.), calmer periods will follow again. + +Pace yourself over modest results over time. Simplify and reduce the daily task lists. Meetings: Certain hours are protected for work. For each meeting, add a protected block to your calendar, so you attend meetings only half a day max. + +Schedule slow seasons (e.g., when on vacation). Disconnect in the slow season. Doing nothing will not satisfy your mind, though. You could read a book on your subject matter to counteract that. + +## Obsess over quality + +Obsess over quality even if you lose short-term opportunities by rejecting other projects. Quality demands you slow down. The two previous two principles (do fewer things and work at a natural pace) are mandatory for this principle to work: + +* Focus on the core activities of your work for your obsession - you will only have the time to obsess over some things. +* Deliver solid work with good quality. +* Sharpen the focus to do the best work possible. + +Go pro to save time, and don't squeeze everything out that you can from freemium services. Professional software services eliminate administrative work: + +* Pay people who know what they are doing and focus on your stuff. +* For example, don't repair that car if you know the mechanic can do that much better than you. +* Or don't use the free version of the music streaming service if it interrupts you with commercials, hindering your ability to concentrate on your work. +* Hire an accountant for your yearly tax returns. He knows much more about that stuff than you do. And in the end, he will even be cheaper as he knows all the tax laws. +* ... + +Adjust your workplace to what you want to accomplish. You could have dedicated places in your home for different things, e.g., a place where you read and think (armchair) and a place where you collaborate (your desk or whiteboard). Surround yourself with things that inspire you (e.g., your favourite books on your shelf next to you, etc.). + +There is the concept of quiet quitting. It doesn't mean quitting your job, but it means that you don't go beyond and above the expectations people have of you. Quiet quitting became popular with modern work, which is often meaningless and full of shallow tasks. If you obsess over quality, you enjoy your craft and want to go beyond and above. + +Implement rituals and routines which shift you towards your goals: + +* For example, if you want to be a good Software Engineer, you also have to put in the work regularly. For instance, progress a bit every day in your project at hand, even if it is only one hour daily. Also, a little quality daily work will be more satisfying over time than many shallow tasks. +* Do you want to be lean and/or healthy? Schedule your daily walks and workouts. They will become habits over time. +* There's the compounding effect where every small effort made every day will yield significant results in the long run + +Deciding what not to do is as important as deciding what to do. + +It appears to be money thrown out of the window, but you get a $50 expensive paper notebook (and also a good pen). Unconsciously, it will make you take notes more seriously. You will think about what to put into the notebooks more profoundly and have thought through the ideas more intensively. If you used very cheap notebooks, you would scribble a lot of rubbish and wouldn't even recognise your handwriting after a while anymore. So choosing a high-quality notebook will help you to take higher-quality notes, too. + +Slow productivity is actionable and can be applied immediately. + +E-Mail your comments to `paul@nospam.buetow.org` :-) + +Other book notes of mine are: + +[2023-03-16 "The Pragmatic Programmer" book notes](./2023-03-16-the-pragmatic-programmer-book-notes.md) +[2023-04-01 "Never split the difference" book notes](./2023-04-01-never-split-the-difference-book-notes.md) +[2023-05-06 "The Obstacle is the Way" book notes](./2023-05-06-the-obstacle-is-the-way-book-notes.md) +[2023-07-17 "Software Developmers Career Guide and Soft Skills" book notes](./2023-07-17-career-guide-and-soft-skills-book-notes.md) +[2023-11-11 "Mind Management" book notes](./2023-11-11-mind-management-book-notes.md) +[2024-05-01 "Slow Productivity" book notes (You are currently reading this)](./2024-05-01-slow-productivity-book-notes.md) + +[More books and other resources I found useful.](../resources.md) +[Back to the main site](../) diff --git a/gemfeed/index.md b/gemfeed/index.md index d33b4992..b2a0338e 100644 --- a/gemfeed/index.md +++ b/gemfeed/index.md @@ -2,6 +2,7 @@ ## To be in the .zone! +[2024-05-01 - 'Slow Productivity' book notes](./2024-05-01-slow-productivity-book-notes.md) [2024-04-01 - KISS high-availability with OpenBSD](./2024-04-01-KISS-high-availability-with-OpenBSD.md) [2024-03-03 - A fine Fyne Android app for quickly logging ideas programmed in Go](./2024-03-03-a-fine-fyne-android-app-for-quickly-logging-ideas-programmed-in-golang.md) [2024-02-04 - From `babylon5.buetow.org` to `*.buetow.cloud`](./2024-02-04-from-babylon5.buetow.org-to-.cloud.md) -- cgit v1.2.3 From ebc896b30875699e4f12efb868021468f87748fe Mon Sep 17 00:00:00 2001 From: Paul Buetow Date: Sat, 27 Apr 2024 15:10:59 +0300 Subject: Update content for md --- gemfeed/2024-05-01-slow-productivity-book-notes.md | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) (limited to 'gemfeed') diff --git a/gemfeed/2024-05-01-slow-productivity-book-notes.md b/gemfeed/2024-05-01-slow-productivity-book-notes.md index 910f91a4..b1fcba33 100644 --- a/gemfeed/2024-05-01-slow-productivity-book-notes.md +++ b/gemfeed/2024-05-01-slow-productivity-book-notes.md @@ -70,7 +70,7 @@ Sometimes, a little friction is all that is needed to combat incoming work, e.g. Limit your daily goals. A good measure is to focus on one goal per day. You can time block time for deep work on your daily goal. During that time, you won't be easily available to others. -The battle against distractions must be thought to be the master of your time. Nobody will fight this war for you. You have to do it for yourself. (Also, have a look at Cal Newport's "time block planning" method). +The battle against distractions must be fought to be the master of your time. Nobody will fight this war for you. You have to do it for yourself. (Also, have a look at Cal Newport's "time block planning" method). Put tasks on autopilot (regular recurring tasks). -- cgit v1.2.3 From a8e3a9c099d81757bd7bf6df94b01d873e5a48b0 Mon Sep 17 00:00:00 2001 From: Paul Buetow Date: Sat, 27 Apr 2024 21:58:51 +0300 Subject: Update content for md --- gemfeed/2024-05-01-slow-productivity-book-notes.md | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) (limited to 'gemfeed') diff --git a/gemfeed/2024-05-01-slow-productivity-book-notes.md b/gemfeed/2024-05-01-slow-productivity-book-notes.md index b1fcba33..d30bd503 100644 --- a/gemfeed/2024-05-01-slow-productivity-book-notes.md +++ b/gemfeed/2024-05-01-slow-productivity-book-notes.md @@ -74,7 +74,7 @@ The battle against distractions must be fought to be the master of your time. No Put tasks on autopilot (regular recurring tasks). -## Work in a natural pace +## Work at a natural pace We suffer from overambitious timelines, task lists, and business. Focus on what matters. Don't rush your most important work to achieve better results. -- cgit v1.2.3 From 6a3be8075eb06b332597fc02ca1671c40a3a3301 Mon Sep 17 00:00:00 2001 From: Paul Buetow Date: Tue, 30 Apr 2024 13:14:10 +0300 Subject: Update content for md --- ...24-04-01-KISS-high-availability-with-OpenBSD.md | 26 ++++++++++++---------- 1 file changed, 14 insertions(+), 12 deletions(-) (limited to 'gemfeed') diff --git a/gemfeed/2024-04-01-KISS-high-availability-with-OpenBSD.md b/gemfeed/2024-04-01-KISS-high-availability-with-OpenBSD.md index 75e50778..2310f50a 100644 --- a/gemfeed/2024-04-01-KISS-high-availability-with-OpenBSD.md +++ b/gemfeed/2024-04-01-KISS-high-availability-with-OpenBSD.md @@ -28,18 +28,20 @@ _____|_:_:_| (o)-(o) |_:_:_|--'`-. ,--. ksh under-water (((\'/ ``` ``` -Table of contents: - KISS high-availability with OpenBSD - My auto-failover requirements - My HA solution - Only OpenBSD base installation required - Fairly cheap and geo-redundant - Failover time and split-brain - Failover support for multiple protocols - Let's encrypt TLS certificates - Monitoring - Rex automation - More HA +Table of contents +================= + +KISS high-availability with OpenBSD + My auto-failover requirements + My HA solution + Only OpenBSD base installation required + Fairly cheap and geo-redundant + Failover time and split-brain + Failover support for multiple protocols + Let's encrypt TLS certificates + Monitoring + Rex automation + More HA ``` I have always wanted a highly available setup for my personal websites. I could have used off-the-shelf hosting solutions or hosted my sites in an AWS S3 bucket. I have used technologies like (in unsorted and slightly unrelated order) BGP, LVS/IPVS, ldirectord, Pacemaker, STONITH, scripted VIP failover via ARP, heartbeat, heartbeat2, Corosync, keepalived, DRBD, and commercial F5 Load Balancers for high availability at work. -- cgit v1.2.3 From 16f67a688efdaa459e51eecc32e36feef26a2c46 Mon Sep 17 00:00:00 2001 From: Paul Buetow Date: Fri, 3 May 2024 16:23:42 +0300 Subject: Update content for md --- ...5-03-projects-i-currently-don-thave-time-for.md | 278 +++++++++++++++++++++ gemfeed/index.md | 1 + 2 files changed, 279 insertions(+) create mode 100644 gemfeed/2024-05-03-projects-i-currently-don-thave-time-for.md (limited to 'gemfeed') diff --git a/gemfeed/2024-05-03-projects-i-currently-don-thave-time-for.md b/gemfeed/2024-05-03-projects-i-currently-don-thave-time-for.md new file mode 100644 index 00000000..4dccf827 --- /dev/null +++ b/gemfeed/2024-05-03-projects-i-currently-don-thave-time-for.md @@ -0,0 +1,278 @@ +# Projects I currently don't have time for + +> Published at 2024-05-03T16:23:03+03:00 + +``` +Art by Laura Brown + +.'`~~~~~~~~~~~`'. +( .'11 12 1'. ) +| :10 \ 2: | +| :9 @-> 3: | +| :8 4; | +'. '..7 6 5..' .' + ~-------------~ ldb + +``` + +## Introduction + +Over the years, I have collected many ideas for my personal projects and noted them down. I am currently in the process of cleaning up all my notes and reviewing those ideas. I don’t have time for the ones listed here and won’t have any soon due to other commitments and personal projects. So, in order to "get rid of them" from my notes folder, I decided to simply put them in this blog post so that those ideas don't get lost. Maybe I will pick up one or another idea someday in the future, but for now, they are all put on ice in favor of other personal projects or family time. + +``` +Table of contents +================= + +Projects I currently don't have time for + Introduction + Hardware projects I don't have time for + I use Arch, btw! + OpenBSD home router + Infodash + Reading station + Retro station + Sound server + Project Freekat + Programming projects I don't have time for + CLI-HIVE + Enhanced KISS home photo albums + KISS file sync server with end-to-end encryption + A language that compiles to `bash` + A language that compiles to `sed` + Renovate VS-Sim + KISS ticketing system + A domain-specific language (DSL) for work + Self-hosting projects I don't have time for + My own Matrix server + Ampache music server + Librum eBook reader + Memos - Note-taking service + Bepasty server + New websites I don't have time for + Create a "Why Raku Rox" site + Research projects I don't have time for + Project secure + CPU utilisation is all wrong +``` + +## Hardware projects I don't have time for + +### I use Arch, btw! + +The idea was to build the ultimate Arch Linux setup on an old ThinkPad X200 booting with the open-source LibreBoot firmware, complete with a tiling window manager, dmenu, and all the elite tools. This is mainly for fun, as I am pretty happy (and productive) with my Fedora Linux setup. I ran EndeavourOS (close enough to Arch) on an old ThinkPad for a while, but then I switched back to Fedora because the rolling releases were annoying (there were too many updates). + +### OpenBSD home router + +In my student days, I operated a 486DX PC with OpenBSD as my home DSL internet router. I bought the setup from my brother back then. The router's hostname was `fishbone`, and it performed very well until it became too slow for larger broadband bandwidth after a few years of use. + +I had the idea to revive this concept, implement `fishbone2`, and place it in front of my proprietary ISP router to add an extra layer of security and control in my home LAN. It would serve as the default gateway for all of my devices, including a Wi-Fi access point, would run a DNS server, Pi-hole proxy, VPN client, and DynDNS client. I would also implement high availability using OpenBSD's CARP protocol. + +[https://openbsdrouterguide.net](https://openbsdrouterguide.net) +[https://pi-hole.net/](https://pi-hole.net/) +[https://www.OpenBSD.org](https://www.OpenBSD.org) +[https://www.OpenBSD.org/faq/pf/carp.html](https://www.OpenBSD.org/faq/pf/carp.html) + +However, I am putting this on hold as I have opted for an OpenWRT-based solution, which was much quicker to set up and runs well enough. + +[https://OpenWRT.org/](https://OpenWRT.org/) + +### Infodash + +The idea was to implement my smart info screen using purely open-source software. It would display information such as the health status of my personal infrastructure, my current work tracker balance (I track how much I work to prevent overworking), and my sports balance (I track my workouts to stay within my quotas for general health). The information would be displayed on a small screen in my home office, on my Pine watch, or remotely from any terminal window. + +I don't have this, and I haven't missed having it, so I guess it would have been nice to have it but not provide any value other than the "fun of tinkering." + +### Reading station + +I wanted to create the most comfortable setup possible for reading digital notes, articles, and books. This would include a comfy armchair, a silent barebone PC or Raspberry Pi computer running either Linux or *BSD, and an e-Ink display mounted on a flexible arm/stand. There would also be a small table for my paper journal for occasional note-taking. There are a bunch of open-source software available for PDF and ePub reading. It would have been neat, but I am currently using the most straightforward solution: a Kobo Elipsa, which I can use on my sofa. + +### Retro station + +I had an idea to build a computer infused with retro elements. It wouldn't use actual retro hardware but would look and feel like a retro machine. I would call this machine HAL or Retron. + +I would use an old ThinkPad laptop placed on a horizontal stand, running NetBSD, and attaching a keyboard from ModelFkeyboards. I use WindowMaker as a window manager and run terminal applications through Retro Term. For the monitor, I would use an older (black) EIZO model with large bezels. + +[https://www.NetBSD.org](https://www.NetBSD.org) +[https://www.modelfkeyboards.com](https://www.modelfkeyboards.com) +[https://github.com/Swordfish90/cool-retro-term)](https://github.com/Swordfish90/cool-retro-term)) + +The computer would occasionally be used to surf the Gemini space, take notes, blog, or do light coding. However, I have abandoned the project for now because there isn't enough space in my apartment, as my daughter will have a room for herself. + +### Sound server + +My idea involved using a barebone mini PC running FreeBSD with the Navidrome sound server software. I could remotely connect to it from my phone, workstation/laptop to listen to my music collection. The storage would be based on ZFS with at least two drives for redundancy. The app would run in a Linux Docker container under FreeBSD via Bhyve. + +[https://github.com/navidrome/navidrome](https://github.com/navidrome/navidrome) +[https://wiki.freebsd.org/bhyve](https://wiki.freebsd.org/bhyve) + +### Project Freekat + +My idea involved purchasing the Meerkat mini PC from System76 and installing FreeBSD. Like the sound-server idea (see previous idea), it would run Linux Docker through Bhyve. I would self-host a bunch of applications on it: + +* Wallabag +* Ankidroid +* Miniflux & Postgres +* Audiobookshelf +* ... + +All of this would be within my LAN, but the services would also be accessible from the internet through either Wireguard or SSH reverse tunnels to one of my OpenBSD VMs, for example: + +* `wallabag.awesome.buetow.org` +* `ankidroid.awesome.buetow.org` +* `miniflux.awesome.buetow.org` +* `audiobookshelf.awesome.buetow.org` +* ... + +I am abandoning this project for now, as I am currently hosting my apps on AWS ECS Fargate under `*.cool.buetow.org`, which is "good enough" for the time being and also offers the benefit of learning to use AWS and Terraform, knowledge that can be applied at work. + +## Programming projects I don't have time for + +### CLI-HIVE + +This was a pet project idea that my brother and I had. The concept was to collect all shell history of all servers at work in a central place, apply ML/AI, and return suggestions for commands to type or allow a fuzzy search on all the commands in the history. The recommendations for the commands on a server could be context-based (e.g., past occurrences on the same server type). + +You could decide whether to share your command history with others so they would receive better suggestions depending on which server they are on, or you could keep all the history private and secure. The plan was to add hooks into zsh and bash shells so that all commands typed would be pushed to the central location for data mining. + +### Enhanced KISS home photo albums + +I don't use third-party cloud providers such as Google Photos to store/archive my photos. Instead, they are all on a ZFS volume on my home NAS, with regular offsite backups taken. Thus, my project would involve implementing the features I miss most or finding a solution simple enough to host on my LAN: + +* A feature I miss presents me with a random day from the past and some photos from that day. This project would randomly select a day and generate a photo album for me to view and reminisce about memories. +* Another feature I miss is the ability to automatically deduplicate all the photos, as I am sure there are tons of duplicates on my NAS. +* Auto-enhancing the photos (perhaps using ImageMagick?) +* I already have a simple `photoalbum.sh` script that generates an album based on an input directory. However, it would be great also to have a timeline feature to enable browsing through different dates. + +[KISS static web photo albums with `photoalbum.sh`](./2023-10-29-kiss-static-web-photo-albums-with-photoalbum.sh.md) + +### KISS file sync server with end-to-end encryption + +I aimed to have a simple server to which I could sync notes and other documents, ensuring that the data is fully end-to-end encrypted. This way, only the clients could decrypt the data, while an encrypted copy of all the data would be stored on the server side. There are a few solutions (e.g., NextCloud), but they are bloated or complex to set up. + +I currently use Syncthing for encrypted file sync across all my devices; however, the data is not end-to-end encrypted. It's a good-enough setup, though, as my Syncthing server is in my home LAN on an encrypted file system. + +[https://syncthing.net](https://syncthing.net) + +I also had the idea of using this as a pet project for work and naming it `Cryptolake`, utilizing post-quantum-safe encryption algorithms and a distributed data store. + +### A language that compiles to `bash` + +I had an idea to implement a higher-level language with strong typing that could be compiled into native Bash code. This would make all resulting Bash scripts more robust and secure by default. The project would involve developing a parser, lexer, and a Bash code generator. I planned to implement this in Go. + +I had previously implemented a tiny scripting language called Fype (For Your Program Execution), which could have served as inspiration. + +[The Fype Programming Language](./2010-05-09-the-fype-programming-language.md) + +### A language that compiles to `sed` + +This is similar to the previous idea, but the difference is that the language would compile into a sed script. Sed has many features, but the brief syntax makes scripts challenging to read. The higher-level language would mimic sed but in a form that is easier for humans to read. + +### Renovate VS-Sim + +VS-Sim is an open-source simulator programmed in Java for distributed systems. VS-Sim stands for "Verteilte Systeme Simulator," the German translation for "Distributed Systems Simulator." The VS-Sim project was my diploma thesis at Aachen University of Applied Sciences. + +[https://codeberg.org/snonux/vs-sim](https://codeberg.org/snonux/vs-sim) + +The ideas I had was: + +* Translate the project into English. +* Modernise the Java codebase to be compatible with the latest JDK. +* Make it compile to native binaries using GraalVM. +* Distribute the project using AppImages. + +I have put this project on hold for now, as I want to do more things in Go and fewer in Java in my personal time. + +### KISS ticketing system + +My idea was to program a KISS (Keep It Simple, Stupid) ticketing system for my personal use. However, I am abandoning this project because I now use the excellent Taskwarrior software. You can learn more about it at: + +[https://taskwarrior.org/](https://taskwarrior.org/) + +### A domain-specific language (DSL) for work + +At work, an internal service allocates storage space for our customers on our storage clusters. It automates many tasks, but many tweaks are accessible through APIs. I had the idea to implement a Ruby-based DSL that would make using all those APIs for ad-hoc changes effortless, e.g.: + +```ruby +Cluster :UK, :uk01 do + Customer.C1A1.segments.volumes.each do |volume| + puts volume.usage_stats + volume.move_off! if volume.over_subscribed? + end +end +``` + +I am abandoning this project because my workplace has stopped the annual pet project competition, and I have other more important projects to work on at the moment. + +[Creative universe (Work pet project contests)](./2022-04-10-creative-universe.md) + +## Self-hosting projects I don't have time for + +### My own Matrix server + +I value privacy. It would be great to run my own Matrix server for communication within my family. I have yet to have time to look into this more closely. + +[https://matrix.org](https://matrix.org) + +### Ampache music server + +Ampache is an open-source music streaming server that allows you to host and manage your music collection online, accessible via a web interface. Setting it up involves configuring a web server, installing Ampache, and organising your music files, which can be time-consuming. + +### Librum eBook reader + +Librum is a self-hostable e-book reader that allows users to manage and read their e-book collection from a web interface. Designed to be a self-contained platform where users can upload, organise, and access their e-books, Librum emphasises privacy and control over one's digital library. + +[https://github.com/Librum-Reader/Librum](https://github.com/Librum-Reader/Librum) + +I am using my Kobo devices or my laptop to read these kinds of things for now. + +### Memos - Note-taking service + +Memos is a note-taking service that simplifies and streamlines information capture and organisation. It focuses on providing users with a minimalistic and intuitive interface, aiming to enhance productivity without the clutter commonly associated with more complex note-taking apps. + +[https://www.usememos.com](https://www.usememos.com) + +I am abandoning this idea for now, as I am currently using plain Markdown files for notes and syncing them with Syncthing across my devices. + +### Bepasty server + +Bepasty is like a Pastebin for all kinds of files (text, image, audio, video, documents, binary, etc.). It seems very neat, but I only share a little nowadays. When I do, I upload files via SCP to one of my OpenBSD VMs and serve them via vanilla httpd there, keeping it KISS. + +[https://github.com/bepasty/bepasty-server](https://github.com/bepasty/bepasty-server) + +## New websites I don't have time for + +### Create a "Why Raku Rox" site + +The website "Why Raku Rox" would showcase the unique features and benefits of the Raku programming language and highlight why it is an exceptional choice for developers. Raku, originally known as Perl 6, is a dynamic, expressive language designed for flexible and powerful software development. + +This would be similar to the "Why OpenBSD rocks" site: + +[https://why-openbsd.rocks](https://why-openbsd.rocks) +[https://raku.org](https://raku.org) + +I am not working on this for now, as I currently don’t even have time to program in Raku. + +## Research projects I don't have time for + +### Project secure + +For work: Implement a PoC that dumps Java heaps to extract secrets from memory. Based on the findings, write a Java program that encrypts secrets in the kernel using the `memfd_secret()` syscall to make it even more secure. + +[https://lwn.net/Articles/865256/](https://lwn.net/Articles/865256/) + +Due to other priorities, I am putting this on hold for now. The software we have built is pretty damn secure already! + +### CPU utilisation is all wrong + +This research project, based on Brendan Gregg's blog post, could potentially significantly impact my work. + +[https://brendangregg.com/blog/2017-05-09/cpu-utilization-is-wrong.html](https://brendangregg.com/blog/2017-05-09/cpu-utilization-is-wrong.html) + +The research project would involve setting up dashboards that display actual CPU usage and the cycles versus waiting time for memory access. + +E-Mail your comments to `paul@nospam.buetow.org` :-) + +Related and maybe interesting: + +[Sweatin the small stuff - Tiny projects of mine](./2022-06-15-sweating-the-small-stuff.md) + +[Back to the main site](../) diff --git a/gemfeed/index.md b/gemfeed/index.md index b2a0338e..ef3aea75 100644 --- a/gemfeed/index.md +++ b/gemfeed/index.md @@ -2,6 +2,7 @@ ## To be in the .zone! +[2024-05-03 - Projects I currently don't have time for](./2024-05-03-projects-i-currently-don-thave-time-for.md) [2024-05-01 - 'Slow Productivity' book notes](./2024-05-01-slow-productivity-book-notes.md) [2024-04-01 - KISS high-availability with OpenBSD](./2024-04-01-KISS-high-availability-with-OpenBSD.md) [2024-03-03 - A fine Fyne Android app for quickly logging ideas programmed in Go](./2024-03-03-a-fine-fyne-android-app-for-quickly-logging-ideas-programmed-in-golang.md) -- cgit v1.2.3 From 36ad30d383c34371a589240b99c56aad3254ec89 Mon Sep 17 00:00:00 2001 From: Paul Buetow Date: Fri, 3 May 2024 16:26:00 +0300 Subject: Update content for md --- gemfeed/2024-05-03-projects-i-currently-don-thave-time-for.md | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) (limited to 'gemfeed') diff --git a/gemfeed/2024-05-03-projects-i-currently-don-thave-time-for.md b/gemfeed/2024-05-03-projects-i-currently-don-thave-time-for.md index 4dccf827..4662496f 100644 --- a/gemfeed/2024-05-03-projects-i-currently-don-thave-time-for.md +++ b/gemfeed/2024-05-03-projects-i-currently-don-thave-time-for.md @@ -273,6 +273,6 @@ E-Mail your comments to `paul@nospam.buetow.org` :-) Related and maybe interesting: -[Sweatin the small stuff - Tiny projects of mine](./2022-06-15-sweating-the-small-stuff.md) +[Sweating the small stuff - Tiny projects of mine](./2022-06-15-sweating-the-small-stuff.md) [Back to the main site](../) -- cgit v1.2.3 From e87160e9b60cc33e87f4a4d4cfbb0eb7c80f798b Mon Sep 17 00:00:00 2001 From: Paul Buetow Date: Fri, 3 May 2024 16:38:33 +0300 Subject: Update content for md --- gemfeed/2024-05-03-projects-i-currently-don-thave-time-for.md | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) (limited to 'gemfeed') diff --git a/gemfeed/2024-05-03-projects-i-currently-don-thave-time-for.md b/gemfeed/2024-05-03-projects-i-currently-don-thave-time-for.md index 4662496f..911d3cf1 100644 --- a/gemfeed/2024-05-03-projects-i-currently-don-thave-time-for.md +++ b/gemfeed/2024-05-03-projects-i-currently-don-thave-time-for.md @@ -84,7 +84,7 @@ I don't have this, and I haven't missed having it, so I guess it would have been ### Reading station -I wanted to create the most comfortable setup possible for reading digital notes, articles, and books. This would include a comfy armchair, a silent barebone PC or Raspberry Pi computer running either Linux or *BSD, and an e-Ink display mounted on a flexible arm/stand. There would also be a small table for my paper journal for occasional note-taking. There are a bunch of open-source software available for PDF and ePub reading. It would have been neat, but I am currently using the most straightforward solution: a Kobo Elipsa, which I can use on my sofa. +I wanted to create the most comfortable setup possible for reading digital notes, articles, and books. This would include a comfy armchair, a silent barebone PC or Raspberry Pi computer running either Linux or *BSD, and an e-Ink display mounted on a flexible arm/stand. There would also be a small table for my paper journal for occasional note-taking. There are a bunch of open-source software available for PDF and ePub reading. It would have been neat, but I am currently using the most straightforward solution: a Kobo Elipsa 2E, which I can use on my sofa. ### Retro station -- cgit v1.2.3 From 42dd46986f126250effb9a16ffa2822ab0d5012c Mon Sep 17 00:00:00 2001 From: Paul Buetow Date: Fri, 3 May 2024 16:55:35 +0300 Subject: Update content for md --- ...5-03-projects-i-currently-don-thave-time-for.md | 278 -------------------- ...5-03-projects-i-currently-dont-have-time-for.md | 280 +++++++++++++++++++++ gemfeed/index.md | 2 +- 3 files changed, 281 insertions(+), 279 deletions(-) delete mode 100644 gemfeed/2024-05-03-projects-i-currently-don-thave-time-for.md create mode 100644 gemfeed/2024-05-03-projects-i-currently-dont-have-time-for.md (limited to 'gemfeed') diff --git a/gemfeed/2024-05-03-projects-i-currently-don-thave-time-for.md b/gemfeed/2024-05-03-projects-i-currently-don-thave-time-for.md deleted file mode 100644 index 911d3cf1..00000000 --- a/gemfeed/2024-05-03-projects-i-currently-don-thave-time-for.md +++ /dev/null @@ -1,278 +0,0 @@ -# Projects I currently don't have time for - -> Published at 2024-05-03T16:23:03+03:00 - -``` -Art by Laura Brown - -.'`~~~~~~~~~~~`'. -( .'11 12 1'. ) -| :10 \ 2: | -| :9 @-> 3: | -| :8 4; | -'. '..7 6 5..' .' - ~-------------~ ldb - -``` - -## Introduction - -Over the years, I have collected many ideas for my personal projects and noted them down. I am currently in the process of cleaning up all my notes and reviewing those ideas. I don’t have time for the ones listed here and won’t have any soon due to other commitments and personal projects. So, in order to "get rid of them" from my notes folder, I decided to simply put them in this blog post so that those ideas don't get lost. Maybe I will pick up one or another idea someday in the future, but for now, they are all put on ice in favor of other personal projects or family time. - -``` -Table of contents -================= - -Projects I currently don't have time for - Introduction - Hardware projects I don't have time for - I use Arch, btw! - OpenBSD home router - Infodash - Reading station - Retro station - Sound server - Project Freekat - Programming projects I don't have time for - CLI-HIVE - Enhanced KISS home photo albums - KISS file sync server with end-to-end encryption - A language that compiles to `bash` - A language that compiles to `sed` - Renovate VS-Sim - KISS ticketing system - A domain-specific language (DSL) for work - Self-hosting projects I don't have time for - My own Matrix server - Ampache music server - Librum eBook reader - Memos - Note-taking service - Bepasty server - New websites I don't have time for - Create a "Why Raku Rox" site - Research projects I don't have time for - Project secure - CPU utilisation is all wrong -``` - -## Hardware projects I don't have time for - -### I use Arch, btw! - -The idea was to build the ultimate Arch Linux setup on an old ThinkPad X200 booting with the open-source LibreBoot firmware, complete with a tiling window manager, dmenu, and all the elite tools. This is mainly for fun, as I am pretty happy (and productive) with my Fedora Linux setup. I ran EndeavourOS (close enough to Arch) on an old ThinkPad for a while, but then I switched back to Fedora because the rolling releases were annoying (there were too many updates). - -### OpenBSD home router - -In my student days, I operated a 486DX PC with OpenBSD as my home DSL internet router. I bought the setup from my brother back then. The router's hostname was `fishbone`, and it performed very well until it became too slow for larger broadband bandwidth after a few years of use. - -I had the idea to revive this concept, implement `fishbone2`, and place it in front of my proprietary ISP router to add an extra layer of security and control in my home LAN. It would serve as the default gateway for all of my devices, including a Wi-Fi access point, would run a DNS server, Pi-hole proxy, VPN client, and DynDNS client. I would also implement high availability using OpenBSD's CARP protocol. - -[https://openbsdrouterguide.net](https://openbsdrouterguide.net) -[https://pi-hole.net/](https://pi-hole.net/) -[https://www.OpenBSD.org](https://www.OpenBSD.org) -[https://www.OpenBSD.org/faq/pf/carp.html](https://www.OpenBSD.org/faq/pf/carp.html) - -However, I am putting this on hold as I have opted for an OpenWRT-based solution, which was much quicker to set up and runs well enough. - -[https://OpenWRT.org/](https://OpenWRT.org/) - -### Infodash - -The idea was to implement my smart info screen using purely open-source software. It would display information such as the health status of my personal infrastructure, my current work tracker balance (I track how much I work to prevent overworking), and my sports balance (I track my workouts to stay within my quotas for general health). The information would be displayed on a small screen in my home office, on my Pine watch, or remotely from any terminal window. - -I don't have this, and I haven't missed having it, so I guess it would have been nice to have it but not provide any value other than the "fun of tinkering." - -### Reading station - -I wanted to create the most comfortable setup possible for reading digital notes, articles, and books. This would include a comfy armchair, a silent barebone PC or Raspberry Pi computer running either Linux or *BSD, and an e-Ink display mounted on a flexible arm/stand. There would also be a small table for my paper journal for occasional note-taking. There are a bunch of open-source software available for PDF and ePub reading. It would have been neat, but I am currently using the most straightforward solution: a Kobo Elipsa 2E, which I can use on my sofa. - -### Retro station - -I had an idea to build a computer infused with retro elements. It wouldn't use actual retro hardware but would look and feel like a retro machine. I would call this machine HAL or Retron. - -I would use an old ThinkPad laptop placed on a horizontal stand, running NetBSD, and attaching a keyboard from ModelFkeyboards. I use WindowMaker as a window manager and run terminal applications through Retro Term. For the monitor, I would use an older (black) EIZO model with large bezels. - -[https://www.NetBSD.org](https://www.NetBSD.org) -[https://www.modelfkeyboards.com](https://www.modelfkeyboards.com) -[https://github.com/Swordfish90/cool-retro-term)](https://github.com/Swordfish90/cool-retro-term)) - -The computer would occasionally be used to surf the Gemini space, take notes, blog, or do light coding. However, I have abandoned the project for now because there isn't enough space in my apartment, as my daughter will have a room for herself. - -### Sound server - -My idea involved using a barebone mini PC running FreeBSD with the Navidrome sound server software. I could remotely connect to it from my phone, workstation/laptop to listen to my music collection. The storage would be based on ZFS with at least two drives for redundancy. The app would run in a Linux Docker container under FreeBSD via Bhyve. - -[https://github.com/navidrome/navidrome](https://github.com/navidrome/navidrome) -[https://wiki.freebsd.org/bhyve](https://wiki.freebsd.org/bhyve) - -### Project Freekat - -My idea involved purchasing the Meerkat mini PC from System76 and installing FreeBSD. Like the sound-server idea (see previous idea), it would run Linux Docker through Bhyve. I would self-host a bunch of applications on it: - -* Wallabag -* Ankidroid -* Miniflux & Postgres -* Audiobookshelf -* ... - -All of this would be within my LAN, but the services would also be accessible from the internet through either Wireguard or SSH reverse tunnels to one of my OpenBSD VMs, for example: - -* `wallabag.awesome.buetow.org` -* `ankidroid.awesome.buetow.org` -* `miniflux.awesome.buetow.org` -* `audiobookshelf.awesome.buetow.org` -* ... - -I am abandoning this project for now, as I am currently hosting my apps on AWS ECS Fargate under `*.cool.buetow.org`, which is "good enough" for the time being and also offers the benefit of learning to use AWS and Terraform, knowledge that can be applied at work. - -## Programming projects I don't have time for - -### CLI-HIVE - -This was a pet project idea that my brother and I had. The concept was to collect all shell history of all servers at work in a central place, apply ML/AI, and return suggestions for commands to type or allow a fuzzy search on all the commands in the history. The recommendations for the commands on a server could be context-based (e.g., past occurrences on the same server type). - -You could decide whether to share your command history with others so they would receive better suggestions depending on which server they are on, or you could keep all the history private and secure. The plan was to add hooks into zsh and bash shells so that all commands typed would be pushed to the central location for data mining. - -### Enhanced KISS home photo albums - -I don't use third-party cloud providers such as Google Photos to store/archive my photos. Instead, they are all on a ZFS volume on my home NAS, with regular offsite backups taken. Thus, my project would involve implementing the features I miss most or finding a solution simple enough to host on my LAN: - -* A feature I miss presents me with a random day from the past and some photos from that day. This project would randomly select a day and generate a photo album for me to view and reminisce about memories. -* Another feature I miss is the ability to automatically deduplicate all the photos, as I am sure there are tons of duplicates on my NAS. -* Auto-enhancing the photos (perhaps using ImageMagick?) -* I already have a simple `photoalbum.sh` script that generates an album based on an input directory. However, it would be great also to have a timeline feature to enable browsing through different dates. - -[KISS static web photo albums with `photoalbum.sh`](./2023-10-29-kiss-static-web-photo-albums-with-photoalbum.sh.md) - -### KISS file sync server with end-to-end encryption - -I aimed to have a simple server to which I could sync notes and other documents, ensuring that the data is fully end-to-end encrypted. This way, only the clients could decrypt the data, while an encrypted copy of all the data would be stored on the server side. There are a few solutions (e.g., NextCloud), but they are bloated or complex to set up. - -I currently use Syncthing for encrypted file sync across all my devices; however, the data is not end-to-end encrypted. It's a good-enough setup, though, as my Syncthing server is in my home LAN on an encrypted file system. - -[https://syncthing.net](https://syncthing.net) - -I also had the idea of using this as a pet project for work and naming it `Cryptolake`, utilizing post-quantum-safe encryption algorithms and a distributed data store. - -### A language that compiles to `bash` - -I had an idea to implement a higher-level language with strong typing that could be compiled into native Bash code. This would make all resulting Bash scripts more robust and secure by default. The project would involve developing a parser, lexer, and a Bash code generator. I planned to implement this in Go. - -I had previously implemented a tiny scripting language called Fype (For Your Program Execution), which could have served as inspiration. - -[The Fype Programming Language](./2010-05-09-the-fype-programming-language.md) - -### A language that compiles to `sed` - -This is similar to the previous idea, but the difference is that the language would compile into a sed script. Sed has many features, but the brief syntax makes scripts challenging to read. The higher-level language would mimic sed but in a form that is easier for humans to read. - -### Renovate VS-Sim - -VS-Sim is an open-source simulator programmed in Java for distributed systems. VS-Sim stands for "Verteilte Systeme Simulator," the German translation for "Distributed Systems Simulator." The VS-Sim project was my diploma thesis at Aachen University of Applied Sciences. - -[https://codeberg.org/snonux/vs-sim](https://codeberg.org/snonux/vs-sim) - -The ideas I had was: - -* Translate the project into English. -* Modernise the Java codebase to be compatible with the latest JDK. -* Make it compile to native binaries using GraalVM. -* Distribute the project using AppImages. - -I have put this project on hold for now, as I want to do more things in Go and fewer in Java in my personal time. - -### KISS ticketing system - -My idea was to program a KISS (Keep It Simple, Stupid) ticketing system for my personal use. However, I am abandoning this project because I now use the excellent Taskwarrior software. You can learn more about it at: - -[https://taskwarrior.org/](https://taskwarrior.org/) - -### A domain-specific language (DSL) for work - -At work, an internal service allocates storage space for our customers on our storage clusters. It automates many tasks, but many tweaks are accessible through APIs. I had the idea to implement a Ruby-based DSL that would make using all those APIs for ad-hoc changes effortless, e.g.: - -```ruby -Cluster :UK, :uk01 do - Customer.C1A1.segments.volumes.each do |volume| - puts volume.usage_stats - volume.move_off! if volume.over_subscribed? - end -end -``` - -I am abandoning this project because my workplace has stopped the annual pet project competition, and I have other more important projects to work on at the moment. - -[Creative universe (Work pet project contests)](./2022-04-10-creative-universe.md) - -## Self-hosting projects I don't have time for - -### My own Matrix server - -I value privacy. It would be great to run my own Matrix server for communication within my family. I have yet to have time to look into this more closely. - -[https://matrix.org](https://matrix.org) - -### Ampache music server - -Ampache is an open-source music streaming server that allows you to host and manage your music collection online, accessible via a web interface. Setting it up involves configuring a web server, installing Ampache, and organising your music files, which can be time-consuming. - -### Librum eBook reader - -Librum is a self-hostable e-book reader that allows users to manage and read their e-book collection from a web interface. Designed to be a self-contained platform where users can upload, organise, and access their e-books, Librum emphasises privacy and control over one's digital library. - -[https://github.com/Librum-Reader/Librum](https://github.com/Librum-Reader/Librum) - -I am using my Kobo devices or my laptop to read these kinds of things for now. - -### Memos - Note-taking service - -Memos is a note-taking service that simplifies and streamlines information capture and organisation. It focuses on providing users with a minimalistic and intuitive interface, aiming to enhance productivity without the clutter commonly associated with more complex note-taking apps. - -[https://www.usememos.com](https://www.usememos.com) - -I am abandoning this idea for now, as I am currently using plain Markdown files for notes and syncing them with Syncthing across my devices. - -### Bepasty server - -Bepasty is like a Pastebin for all kinds of files (text, image, audio, video, documents, binary, etc.). It seems very neat, but I only share a little nowadays. When I do, I upload files via SCP to one of my OpenBSD VMs and serve them via vanilla httpd there, keeping it KISS. - -[https://github.com/bepasty/bepasty-server](https://github.com/bepasty/bepasty-server) - -## New websites I don't have time for - -### Create a "Why Raku Rox" site - -The website "Why Raku Rox" would showcase the unique features and benefits of the Raku programming language and highlight why it is an exceptional choice for developers. Raku, originally known as Perl 6, is a dynamic, expressive language designed for flexible and powerful software development. - -This would be similar to the "Why OpenBSD rocks" site: - -[https://why-openbsd.rocks](https://why-openbsd.rocks) -[https://raku.org](https://raku.org) - -I am not working on this for now, as I currently don’t even have time to program in Raku. - -## Research projects I don't have time for - -### Project secure - -For work: Implement a PoC that dumps Java heaps to extract secrets from memory. Based on the findings, write a Java program that encrypts secrets in the kernel using the `memfd_secret()` syscall to make it even more secure. - -[https://lwn.net/Articles/865256/](https://lwn.net/Articles/865256/) - -Due to other priorities, I am putting this on hold for now. The software we have built is pretty damn secure already! - -### CPU utilisation is all wrong - -This research project, based on Brendan Gregg's blog post, could potentially significantly impact my work. - -[https://brendangregg.com/blog/2017-05-09/cpu-utilization-is-wrong.html](https://brendangregg.com/blog/2017-05-09/cpu-utilization-is-wrong.html) - -The research project would involve setting up dashboards that display actual CPU usage and the cycles versus waiting time for memory access. - -E-Mail your comments to `paul@nospam.buetow.org` :-) - -Related and maybe interesting: - -[Sweating the small stuff - Tiny projects of mine](./2022-06-15-sweating-the-small-stuff.md) - -[Back to the main site](../) diff --git a/gemfeed/2024-05-03-projects-i-currently-dont-have-time-for.md b/gemfeed/2024-05-03-projects-i-currently-dont-have-time-for.md new file mode 100644 index 00000000..f02f59ec --- /dev/null +++ b/gemfeed/2024-05-03-projects-i-currently-dont-have-time-for.md @@ -0,0 +1,280 @@ +# Projects I currently don't have time for + +> Published at 2024-05-03T16:23:03+03:00 + +``` +Art by Laura Brown + +.'`~~~~~~~~~~~`'. +( .'11 12 1'. ) +| :10 \ 2: | +| :9 @-> 3: | +| :8 4; | +'. '..7 6 5..' .' + ~-------------~ ldb + +``` + +## Introduction + +Over the years, I have collected many ideas for my personal projects and noted them down. I am currently in the process of cleaning up all my notes and reviewing those ideas. I don’t have time for the ones listed here and won’t have any soon due to other commitments and personal projects. So, in order to "get rid of them" from my notes folder, I decided to simply put them in this blog post so that those ideas don't get lost. Maybe I will pick up one or another idea someday in the future, but for now, they are all put on ice in favor of other personal projects or family time. + +``` +Table of contents +================= + +Projects I currently don't have time for + Introduction + Hardware projects I don't have time for + I use Arch, btw! + OpenBSD home router + Infodash + Reading station + Retro station + Sound server + Project Freekat + Programming projects I don't have time for + CLI-HIVE + Enhanced KISS home photo albums + KISS file sync server with end-to-end encryption + A language that compiles to `bash` + A language that compiles to `sed` + Renovate VS-Sim + KISS ticketing system + A domain-specific language (DSL) for work + Self-hosting projects I don't have time for + My own Matrix server + Ampache music server + Librum eBook reader + Memos - Note-taking service + Bepasty server + New websites I don't have time for + Create a "Why Raku Rox" site + Research projects I don't have time for + Project secure + CPU utilisation is all wrong +``` + +## Hardware projects I don't have time for + +### I use Arch, btw! + +The idea was to build the ultimate Arch Linux setup on an old ThinkPad X200 booting with the open-source LibreBoot firmware, complete with a tiling window manager, dmenu, and all the elite tools. This is mainly for fun, as I am pretty happy (and productive) with my Fedora Linux setup. I ran EndeavourOS (close enough to Arch) on an old ThinkPad for a while, but then I switched back to Fedora because the rolling releases were annoying (there were too many updates). + +### OpenBSD home router + +In my student days, I operated a 486DX PC with OpenBSD as my home DSL internet router. I bought the setup from my brother back then. The router's hostname was `fishbone`, and it performed very well until it became too slow for larger broadband bandwidth after a few years of use. + +I had the idea to revive this concept, implement `fishbone2`, and place it in front of my proprietary ISP router to add an extra layer of security and control in my home LAN. It would serve as the default gateway for all of my devices, including a Wi-Fi access point, would run a DNS server, Pi-hole proxy, VPN client, and DynDNS client. I would also implement high availability using OpenBSD's CARP protocol. + +[https://openbsdrouterguide.net](https://openbsdrouterguide.net) +[https://pi-hole.net/](https://pi-hole.net/) +[https://www.OpenBSD.org](https://www.OpenBSD.org) +[https://www.OpenBSD.org/faq/pf/carp.html](https://www.OpenBSD.org/faq/pf/carp.html) + +However, I am putting this on hold as I have opted for an OpenWRT-based solution, which was much quicker to set up and runs well enough. + +[https://OpenWRT.org/](https://OpenWRT.org/) + +### Infodash + +The idea was to implement my smart info screen using purely open-source software. It would display information such as the health status of my personal infrastructure, my current work tracker balance (I track how much I work to prevent overworking), and my sports balance (I track my workouts to stay within my quotas for general health). The information would be displayed on a small screen in my home office, on my Pine watch, or remotely from any terminal window. + +I don't have this, and I haven't missed having it, so I guess it would have been nice to have it but not provide any value other than the "fun of tinkering." + +### Reading station + +I wanted to create the most comfortable setup possible for reading digital notes, articles, and books. This would include a comfy armchair, a silent barebone PC or Raspberry Pi computer running either Linux or *BSD, and an e-Ink display mounted on a flexible arm/stand. There would also be a small table for my paper journal for occasional note-taking. There are a bunch of open-source software available for PDF and ePub reading. It would have been neat, but I am currently using the most straightforward solution: a Kobo Elipsa 2E, which I can use on my sofa. + +### Retro station + +I had an idea to build a computer infused with retro elements. It wouldn't use actual retro hardware but would look and feel like a retro machine. I would call this machine HAL or Retron. + +I would use an old ThinkPad laptop placed on a horizontal stand, running NetBSD, and attaching a keyboard from ModelFkeyboards. I use WindowMaker as a window manager and run terminal applications through Retro Term. For the monitor, I would use an older (black) EIZO model with large bezels. + +[https://www.NetBSD.org](https://www.NetBSD.org) +[https://www.modelfkeyboards.com](https://www.modelfkeyboards.com) +[https://github.com/Swordfish90/cool-retro-term)](https://github.com/Swordfish90/cool-retro-term)) + +The computer would occasionally be used to surf the Gemini space, take notes, blog, or do light coding. However, I have abandoned the project for now because there isn't enough space in my apartment, as my daughter will have a room for herself. + +### Sound server + +My idea involved using a barebone mini PC running FreeBSD with the Navidrome sound server software. I could remotely connect to it from my phone, workstation/laptop to listen to my music collection. The storage would be based on ZFS with at least two drives for redundancy. The app would run in a Linux Docker container under FreeBSD via Bhyve. + +[https://github.com/navidrome/navidrome](https://github.com/navidrome/navidrome) +[https://wiki.freebsd.org/bhyve](https://wiki.freebsd.org/bhyve) + +### Project Freekat + +My idea involved purchasing the Meerkat mini PC from System76 and installing FreeBSD. Like the sound-server idea (see previous idea), it would run Linux Docker through Bhyve. I would self-host a bunch of applications on it: + +* Wallabag +* Ankidroid +* Miniflux & Postgres +* Audiobookshelf +* ... + +All of this would be within my LAN, but the services would also be accessible from the internet through either Wireguard or SSH reverse tunnels to one of my OpenBSD VMs, for example: + +* `wallabag.awesome.buetow.org` +* `ankidroid.awesome.buetow.org` +* `miniflux.awesome.buetow.org` +* `audiobookshelf.awesome.buetow.org` +* ... + +I am abandoning this project for now, as I am currently hosting my apps on AWS ECS Fargate under `*.cool.buetow.org`, which is "good enough" for the time being and also offers the benefit of learning to use AWS and Terraform, knowledge that can be applied at work. + +[My personal AWS setup](./2024-02-04-from-babylon5.buetow.org-to-.cloud.md) + +## Programming projects I don't have time for + +### CLI-HIVE + +This was a pet project idea that my brother and I had. The concept was to collect all shell history of all servers at work in a central place, apply ML/AI, and return suggestions for commands to type or allow a fuzzy search on all the commands in the history. The recommendations for the commands on a server could be context-based (e.g., past occurrences on the same server type). + +You could decide whether to share your command history with others so they would receive better suggestions depending on which server they are on, or you could keep all the history private and secure. The plan was to add hooks into zsh and bash shells so that all commands typed would be pushed to the central location for data mining. + +### Enhanced KISS home photo albums + +I don't use third-party cloud providers such as Google Photos to store/archive my photos. Instead, they are all on a ZFS volume on my home NAS, with regular offsite backups taken. Thus, my project would involve implementing the features I miss most or finding a solution simple enough to host on my LAN: + +* A feature I miss presents me with a random day from the past and some photos from that day. This project would randomly select a day and generate a photo album for me to view and reminisce about memories. +* Another feature I miss is the ability to automatically deduplicate all the photos, as I am sure there are tons of duplicates on my NAS. +* Auto-enhancing the photos (perhaps using ImageMagick?) +* I already have a simple `photoalbum.sh` script that generates an album based on an input directory. However, it would be great also to have a timeline feature to enable browsing through different dates. + +[KISS static web photo albums with `photoalbum.sh`](./2023-10-29-kiss-static-web-photo-albums-with-photoalbum.sh.md) + +### KISS file sync server with end-to-end encryption + +I aimed to have a simple server to which I could sync notes and other documents, ensuring that the data is fully end-to-end encrypted. This way, only the clients could decrypt the data, while an encrypted copy of all the data would be stored on the server side. There are a few solutions (e.g., NextCloud), but they are bloated or complex to set up. + +I currently use Syncthing for encrypted file sync across all my devices; however, the data is not end-to-end encrypted. It's a good-enough setup, though, as my Syncthing server is in my home LAN on an encrypted file system. + +[https://syncthing.net](https://syncthing.net) + +I also had the idea of using this as a pet project for work and naming it `Cryptolake`, utilizing post-quantum-safe encryption algorithms and a distributed data store. + +### A language that compiles to `bash` + +I had an idea to implement a higher-level language with strong typing that could be compiled into native Bash code. This would make all resulting Bash scripts more robust and secure by default. The project would involve developing a parser, lexer, and a Bash code generator. I planned to implement this in Go. + +I had previously implemented a tiny scripting language called Fype (For Your Program Execution), which could have served as inspiration. + +[The Fype Programming Language](./2010-05-09-the-fype-programming-language.md) + +### A language that compiles to `sed` + +This is similar to the previous idea, but the difference is that the language would compile into a sed script. Sed has many features, but the brief syntax makes scripts challenging to read. The higher-level language would mimic sed but in a form that is easier for humans to read. + +### Renovate VS-Sim + +VS-Sim is an open-source simulator programmed in Java for distributed systems. VS-Sim stands for "Verteilte Systeme Simulator," the German translation for "Distributed Systems Simulator." The VS-Sim project was my diploma thesis at Aachen University of Applied Sciences. + +[https://codeberg.org/snonux/vs-sim](https://codeberg.org/snonux/vs-sim) + +The ideas I had was: + +* Translate the project into English. +* Modernise the Java codebase to be compatible with the latest JDK. +* Make it compile to native binaries using GraalVM. +* Distribute the project using AppImages. + +I have put this project on hold for now, as I want to do more things in Go and fewer in Java in my personal time. + +### KISS ticketing system + +My idea was to program a KISS (Keep It Simple, Stupid) ticketing system for my personal use. However, I am abandoning this project because I now use the excellent Taskwarrior software. You can learn more about it at: + +[https://taskwarrior.org/](https://taskwarrior.org/) + +### A domain-specific language (DSL) for work + +At work, an internal service allocates storage space for our customers on our storage clusters. It automates many tasks, but many tweaks are accessible through APIs. I had the idea to implement a Ruby-based DSL that would make using all those APIs for ad-hoc changes effortless, e.g.: + +```ruby +Cluster :UK, :uk01 do + Customer.C1A1.segments.volumes.each do |volume| + puts volume.usage_stats + volume.move_off! if volume.over_subscribed? + end +end +``` + +I am abandoning this project because my workplace has stopped the annual pet project competition, and I have other more important projects to work on at the moment. + +[Creative universe (Work pet project contests)](./2022-04-10-creative-universe.md) + +## Self-hosting projects I don't have time for + +### My own Matrix server + +I value privacy. It would be great to run my own Matrix server for communication within my family. I have yet to have time to look into this more closely. + +[https://matrix.org](https://matrix.org) + +### Ampache music server + +Ampache is an open-source music streaming server that allows you to host and manage your music collection online, accessible via a web interface. Setting it up involves configuring a web server, installing Ampache, and organising your music files, which can be time-consuming. + +### Librum eBook reader + +Librum is a self-hostable e-book reader that allows users to manage and read their e-book collection from a web interface. Designed to be a self-contained platform where users can upload, organise, and access their e-books, Librum emphasises privacy and control over one's digital library. + +[https://github.com/Librum-Reader/Librum](https://github.com/Librum-Reader/Librum) + +I am using my Kobo devices or my laptop to read these kinds of things for now. + +### Memos - Note-taking service + +Memos is a note-taking service that simplifies and streamlines information capture and organisation. It focuses on providing users with a minimalistic and intuitive interface, aiming to enhance productivity without the clutter commonly associated with more complex note-taking apps. + +[https://www.usememos.com](https://www.usememos.com) + +I am abandoning this idea for now, as I am currently using plain Markdown files for notes and syncing them with Syncthing across my devices. + +### Bepasty server + +Bepasty is like a Pastebin for all kinds of files (text, image, audio, video, documents, binary, etc.). It seems very neat, but I only share a little nowadays. When I do, I upload files via SCP to one of my OpenBSD VMs and serve them via vanilla httpd there, keeping it KISS. + +[https://github.com/bepasty/bepasty-server](https://github.com/bepasty/bepasty-server) + +## New websites I don't have time for + +### Create a "Why Raku Rox" site + +The website "Why Raku Rox" would showcase the unique features and benefits of the Raku programming language and highlight why it is an exceptional choice for developers. Raku, originally known as Perl 6, is a dynamic, expressive language designed for flexible and powerful software development. + +This would be similar to the "Why OpenBSD rocks" site: + +[https://why-openbsd.rocks](https://why-openbsd.rocks) +[https://raku.org](https://raku.org) + +I am not working on this for now, as I currently don’t even have time to program in Raku. + +## Research projects I don't have time for + +### Project secure + +For work: Implement a PoC that dumps Java heaps to extract secrets from memory. Based on the findings, write a Java program that encrypts secrets in the kernel using the `memfd_secret()` syscall to make it even more secure. + +[https://lwn.net/Articles/865256/](https://lwn.net/Articles/865256/) + +Due to other priorities, I am putting this on hold for now. The software we have built is pretty damn secure already! + +### CPU utilisation is all wrong + +This research project, based on Brendan Gregg's blog post, could potentially significantly impact my work. + +[https://brendangregg.com/blog/2017-05-09/cpu-utilization-is-wrong.html](https://brendangregg.com/blog/2017-05-09/cpu-utilization-is-wrong.html) + +The research project would involve setting up dashboards that display actual CPU usage and the cycles versus waiting time for memory access. + +E-Mail your comments to `paul@nospam.buetow.org` :-) + +Related and maybe interesting: + +[Sweating the small stuff - Tiny projects of mine](./2022-06-15-sweating-the-small-stuff.md) + +[Back to the main site](../) diff --git a/gemfeed/index.md b/gemfeed/index.md index ef3aea75..ba0c2b4a 100644 --- a/gemfeed/index.md +++ b/gemfeed/index.md @@ -2,7 +2,7 @@ ## To be in the .zone! -[2024-05-03 - Projects I currently don't have time for](./2024-05-03-projects-i-currently-don-thave-time-for.md) +[2024-05-03 - Projects I currently don't have time for](./2024-05-03-projects-i-currently-dont-have-time-for.md) [2024-05-01 - 'Slow Productivity' book notes](./2024-05-01-slow-productivity-book-notes.md) [2024-04-01 - KISS high-availability with OpenBSD](./2024-04-01-KISS-high-availability-with-OpenBSD.md) [2024-03-03 - A fine Fyne Android app for quickly logging ideas programmed in Go](./2024-03-03-a-fine-fyne-android-app-for-quickly-logging-ideas-programmed-in-golang.md) -- cgit v1.2.3 From b9a8f6a974b1647a26c397c45bab0a7c2df1abb6 Mon Sep 17 00:00:00 2001 From: Paul Buetow Date: Sat, 4 May 2024 17:47:20 +0300 Subject: Update content for md --- ...5-03-projects-i-currently-dont-have-time-for.md | 26 ++++++++++++++++++++++ 1 file changed, 26 insertions(+) (limited to 'gemfeed') diff --git a/gemfeed/2024-05-03-projects-i-currently-dont-have-time-for.md b/gemfeed/2024-05-03-projects-i-currently-dont-have-time-for.md index f02f59ec..b8327766 100644 --- a/gemfeed/2024-05-03-projects-i-currently-dont-have-time-for.md +++ b/gemfeed/2024-05-03-projects-i-currently-dont-have-time-for.md @@ -48,6 +48,10 @@ Projects I currently don't have time for Librum eBook reader Memos - Note-taking service Bepasty server + Books I don't have time to read + Fluent Python + Programming Ruby + Peter F. Hamilton science fiction books New websites I don't have time for Create a "Why Raku Rox" site Research projects I don't have time for @@ -240,6 +244,28 @@ Bepasty is like a Pastebin for all kinds of files (text, image, audio, video, do [https://github.com/bepasty/bepasty-server](https://github.com/bepasty/bepasty-server) +## Books I don't have time to read + +### Fluent Python + +I consider myself an advanced programmer in Ruby, Bash, and Perl. However, Python seems to be ubiquitous nowadays, and most of my colleagues prefer Python over any other languages. Thus, it makes sense for me to also learn and use Python. After conducting some research, "Fluent Python" appears to be the best book for this purpose. + +I don't have time to read this book at the moment, as I am focusing more on Go (Golang) and I know just enough Python to get by (e.g., for code reviews). Additionally, there are still enough colleagues around who can review my Ruby or Bash code. + +### Programming Ruby + +I've read a couple of Ruby books already, but "Programming Ruby," which covers up to Ruby 3.2, was just recently released. I would like to read this to deepen my Ruby knowledge further and to revisit some concepts that I may have forgotten. + +As stated in this blog post, I am currently more eager to focus on Go, so I've put the Ruby book on hold. Additionally, there wouldn't be enough colleagues who could "understand" my advanced Ruby skills anyway, as most of them are either Java developers or SREs who don't code a lot. + +## Peter F. Hamilton science fiction books + +I am a big fan of science fiction, but my reading list is currently too long anyway. So, I've put the Hamilton books on the back burner for now. You can see all the novels I've read here: + +[https://paul.buetow.org/novels.html](https://paul.buetow.org/novels.html) +[gemini://paul.buetow.org/novels.gmi](gemini://paul.buetow.org/novels.gmi) + + ## New websites I don't have time for ### Create a "Why Raku Rox" site -- cgit v1.2.3 From 60da23269dc5c8a5d04ef65d7e888dcbbebd1f2b Mon Sep 17 00:00:00 2001 From: Paul Buetow Date: Sat, 4 May 2024 17:53:26 +0300 Subject: Update content for md --- gemfeed/2024-05-03-projects-i-currently-dont-have-time-for.md | 4 ++-- 1 file changed, 2 insertions(+), 2 deletions(-) (limited to 'gemfeed') diff --git a/gemfeed/2024-05-03-projects-i-currently-dont-have-time-for.md b/gemfeed/2024-05-03-projects-i-currently-dont-have-time-for.md index b8327766..dc42b488 100644 --- a/gemfeed/2024-05-03-projects-i-currently-dont-have-time-for.md +++ b/gemfeed/2024-05-03-projects-i-currently-dont-have-time-for.md @@ -51,7 +51,7 @@ Projects I currently don't have time for Books I don't have time to read Fluent Python Programming Ruby - Peter F. Hamilton science fiction books + Peter F. Hamilton science fiction books New websites I don't have time for Create a "Why Raku Rox" site Research projects I don't have time for @@ -258,7 +258,7 @@ I've read a couple of Ruby books already, but "Programming Ruby," which covers u As stated in this blog post, I am currently more eager to focus on Go, so I've put the Ruby book on hold. Additionally, there wouldn't be enough colleagues who could "understand" my advanced Ruby skills anyway, as most of them are either Java developers or SREs who don't code a lot. -## Peter F. Hamilton science fiction books +### Peter F. Hamilton science fiction books I am a big fan of science fiction, but my reading list is currently too long anyway. So, I've put the Hamilton books on the back burner for now. You can see all the novels I've read here: -- cgit v1.2.3 From 65f9f1b9806dbd7cdeb4cf5b07e3c3d34a7f7228 Mon Sep 17 00:00:00 2001 From: Paul Buetow Date: Sun, 12 May 2024 14:48:56 +0300 Subject: Update content for md --- gemfeed/2024-05-03-projects-i-currently-dont-have-time-for.md | 7 +++++++ 1 file changed, 7 insertions(+) (limited to 'gemfeed') diff --git a/gemfeed/2024-05-03-projects-i-currently-dont-have-time-for.md b/gemfeed/2024-05-03-projects-i-currently-dont-have-time-for.md index dc42b488..5817e6ff 100644 --- a/gemfeed/2024-05-03-projects-i-currently-dont-have-time-for.md +++ b/gemfeed/2024-05-03-projects-i-currently-dont-have-time-for.md @@ -28,6 +28,7 @@ Projects I currently don't have time for Hardware projects I don't have time for I use Arch, btw! OpenBSD home router + Pi-Hole server Infodash Reading station Retro station @@ -80,6 +81,12 @@ However, I am putting this on hold as I have opted for an OpenWRT-based solution [https://OpenWRT.org/](https://OpenWRT.org/) +### Pi-Hole server + +Install Pi-hole on one of my Pis or run it in a container on Freekat. For now, I am putting this on hold as the primary use for this would be ad-blocking, and I am avoiding surfing ad-heavy sites anyway. So there's no significant use for me personally at the moment. + +[https://pi-hole.net/](https://pi-hole.net/) + ### Infodash The idea was to implement my smart info screen using purely open-source software. It would display information such as the health status of my personal infrastructure, my current work tracker balance (I track how much I work to prevent overworking), and my sports balance (I track my workouts to stay within my quotas for general health). The information would be displayed on a small screen in my home office, on my Pine watch, or remotely from any terminal window. -- cgit v1.2.3 From d613a7e92fdc95c77d4841e5d86eec3f11b7c9d9 Mon Sep 17 00:00:00 2001 From: Paul Buetow Date: Sun, 23 Jun 2024 23:07:19 +0300 Subject: Update content for md --- .../2024-06-23-terminal-multiplexing-with-tmux.md | 405 +++++++++++++++++++++ .../DRAFT-KISS-high-availability-with-OpenBSD.md | 286 --------------- gemfeed/index.md | 1 + .../tmux-session-fzf.png | Bin 0 -> 34897 bytes .../tmux-tree-view.png | Bin 0 -> 56847 bytes 5 files changed, 406 insertions(+), 286 deletions(-) create mode 100644 gemfeed/2024-06-23-terminal-multiplexing-with-tmux.md delete mode 100644 gemfeed/DRAFT-KISS-high-availability-with-OpenBSD.md create mode 100644 gemfeed/terminal-multiplexing-with-tmux/tmux-session-fzf.png create mode 100644 gemfeed/terminal-multiplexing-with-tmux/tmux-tree-view.png (limited to 'gemfeed') diff --git a/gemfeed/2024-06-23-terminal-multiplexing-with-tmux.md b/gemfeed/2024-06-23-terminal-multiplexing-with-tmux.md new file mode 100644 index 00000000..277968e1 --- /dev/null +++ b/gemfeed/2024-06-23-terminal-multiplexing-with-tmux.md @@ -0,0 +1,405 @@ +# Terminal multiplexing with `tmux` + +> Published at 2024-06-23T22:41:59+03:00 + +``` + \\\\\\\ + \\\\\\\\\\\\ + \\\\\\\\\\\\\\\ + -----------,-| |C> // )\\\\| + ,','| / || ,'/////| +---------,',' X| (, || ///// + || U | \\ ||||//''''| + || M .| ||||||| _| + ||T . |______ `````\____/ \ + || . | ,| _/_____/ \ + ||$ ,' ,' | / | + ||,' ,' | | \ | +_________|/ ,' | / | | +_____________,' ,',_____| | | | + | ,',' | | | | + | ,',' ____|_____/ / | + | ,',' __/ | / | +_____________|',' ///_/-------------/ | + |===========,' + +``` + +``` +Table of contents +================= + +Terminal multiplexing with `tmux` + Introduction + Shell aliases + The `tn` alias - Creating a new session + Cleaning up default sessions automatically + Renaming sessions + The `ta` alias - Attaching to a session + The `tr` alias - For a nested remote session + Change of the Tmux prefix for better nesting + The `ts` alias - Searching sessions with fuzzy finder + The `tssh` alias - Cluster SSH replacement + The `tmux::tssh_from_argument` helper + The `tmux::tssh_from_file` helper + `tssh` examples + Common Tmux commands I use in `tssh` + Copy and paste workflow + Tmux configurations +``` + +## Introduction + +Tmux (Terminal Multiplexer) is a powerful, terminal-based tool that manages multiple terminal sessions within a single window. Here are some of its primary features and functionalities: + +* Session management +* Window and Pane management +* Persistent Workspace +* Customization + +[https://github.com/tmux/tmux/wiki](https://github.com/tmux/tmux/wiki) + +Before continuing to read this post, I encourage you to get familiar with Tmux first (unless you already know the basics). You can go through the official getting started guide: + +[https://github.com/tmux/tmux/wiki/Getting-Started](https://github.com/tmux/tmux/wiki/Getting-Started) + +I can also recommend this book (this is the book I got started with with Tmux): + +[https://pragprog.com/titles/bhtmux2/tmux-2/](https://pragprog.com/titles/bhtmux2/tmux-2/) + +Over the years, I have built a couple of shell helper functions to optimize my workflows. Tmux is extensively integrated into my daily workflows (personal and work). I had colleagues asking me about my Tmux config and helper scripts for Tmux several times. It would be neat to blog about it so that everyone interested in it can make a copy of my configuration and scripts. + +The configuration and scripts in this blog post are only the non-work-specific parts. There are more helper scripts, which I only use for work (and aren't really useful outside of work due to the way servers and clusters are structured there). + +Tmux is highly configurable, and I think I am only scratching the surface of what is possible with it. Nevertheless, it may still be useful for you. I also love that Tmux is part of the OpenBSD base system! + +## Shell aliases + +I am a user of the Z-Shell (`zsh`), but I believe all the snippets mentioned in this blog post also work with Bash. + +[https://www.zsh.org](https://www.zsh.org) + +For the most common Tmux commands I use, I have created the following shell aliases: + +```bash +alias tm=tmux +alias tl='tmux list-sessions' +alias tn=tmux::new +alias ta=tmux::attach +alias tx=tmux::remote +alias ts=tmux::search +alias tssh=tmux::cluster_ssh +``` + +Note all `tmux::...`; those are custom shell functions doing certain things, and they aren't part of the Tmux distribution. But let's run through every aliases one by one. + +The first two are pretty straightforward. `tm` is simply a shorthand for `tmux`, so I have to type less, and `tl` lists all Tmux sessions that are currently open. No magic here. + +## The `tn` alias - Creating a new session + +The `tn` alias is referencing this function: + +```bash +# Create new session and if alread exists attach to it +tmux::new () { + readonly session=$1 + local date=date + if where gdate &>/dev/null; then + date=gdate + fi + + tmux::cleanup_default + if [ -z "$session" ]; then + tmux::new T$($date +%s) + else + tmux new-session -d -s $session + tmux -2 attach-session -t $session || tmux -2 switch-client -t $session + fi +} +alias tn=tmux::new +``` + +There is a lot going on here. Let's have a detailed look at what it is doing. As a note, the function relies on GNU Date, so MacOS is looking for the `gdate` commands to be available. Otherwise, it will fall back to `date`. You need to install GNU Date for Mac, as it isn't installed by default there. As I use Fedora Linux on my personal Laptop and a MacBook for work, I have to make it work for both. + +First, a Tmux session name can be passed to the function as a first argument. That session name is only optional. Without it, Tmux will select a session named `T$($date +%s)` as a default. Which is T followed by the UNIX epoch, e.g. `T1717133796`. + +### Cleaning up default sessions automatically + +Note also the call to `tmux::cleanup_default`; it would clean up all already opened default sessions if they aren't attached. Those sessions were only temporary, and I had too many flying around after a while. So, I decided to auto-delete the sessions if they weren't attached. If I want to keep sessions around, I will rename them with the Tmux command `prefix-key $`. This is the cleanup function: + +```bash +tmux::cleanup_default () { + local s + tmux list-sessions | grep '^T.*: ' | grep -F -v attached | + cut -d: -f1 | while read -r s; do + echo "Killing $s" + tmux kill-session -t "$s" + done +} +``` + +The cleanup function kills all open Tmux sessions that haven't been renamed properly yet—but only if they aren't attached (e.g., don't run in the foreground in any terminal). Cleaning them up automatically keeps my Tmux sessions as neat and tidy as possible. + +### Renaming sessions + +Whenever I am in a temporary session (named `T....`), I may decide that I want to keep this session around. I have to rename the session to prevent the cleanup function from doing its thing. That's, as mentioned already, easily accomplished with the standard `prefix-key $` Tmux command. + +## The `ta` alias - Attaching to a session + +This alias refers to the following function, which tries to attach to an already-running Tmux session. + +```bash +tmux::attach () { + readonly session=$1 + + if [ -z "$session" ]; then + tmux attach-session || tmux::new + else + tmux attach-session -t $session || tmux::new $session + fi +} +alias ta=tmux::attach +``` + +If no session is specified (as the argument of the function), it will try to attach to the first open session. If no Tmux server is running, it will create a new one with `tmux::new`. Otherwise, with a session name given as the argument, it will attach to it. If unsuccessful (e.g., the session doesn't exist), it will be created and attached to. + +## The `tr` alias - For a nested remote session + +This SSHs into the remote server specified and then, remotely on the server itself, starts a nested Tmux session. So we have one Tmux session on the local computer and, inside of it, an SSH connection to a remote server with a Tmux session running again. The benefit of this is that, in case my network connection breaks down, the next time I connect, I can continue my work on the remote server exactly where I left off. The session name is the name of the server being SSHed into. If a session like this already exists, it simply attaches to it. + +```bash +tmux::remote () { + readonly server=$1 + tmux new -s $server "ssh -t $server 'tmux attach-session || tmux'" || \ + tmux attach-session -d -t $server +} +alias tr=tmux::remote +``` + +### Change of the Tmux prefix for better nesting + +To make nested Tmux sessions work smoothly, one must change the Tmux prefix key locally or remotely. By default, the Tmux prefix key is `Ctrl-b`, so `Ctrl-b $`, for example, renames the current session. To change the prefix key from the standard `Ctrl-b` to, for example, `Ctrl-g`, you must add this to the `tmux.conf`: + +``` +set-option -g prefix C-g +``` + +This way, when I want to rename the remote Tmux session, I have to use `Ctrl-g $`, and when I want to rename the local Tmux session, I still have to use `Ctrl-b $`. In my case, I have this deployed to all remote servers through a configuration management system (out of scope for this blog post). + +There might also be another way around this (without reconfiguring the prefix key), but that is cumbersome to use, as far as I remember. + +## The `ts` alias - Searching sessions with fuzzy finder + +Despite the fact that with `tmux::cleanup_default`, I don't leave a huge mess with trillions of Tmux sessions flying around all the time, at times, it can become challenging to find exactly the session I am currently interested in. After a busy workday, I often end up with around twenty sessions on my laptop. This is where fuzzy searching for session names comes in handy, as I often don't remember the exact session names. + +```bash +tmux::search () { + local -r session=$(tmux list-sessions | fzf | cut -d: -f1) + if [ -z "$TMUX" ]; then + tmux attach-session -t $session + else + tmux switch -t $session + fi +} +alias ts=tmux::search +``` + +All it does is list all currently open sessions in `fzf`, where one of them can be searched and selected through fuzzy find, and then either switch (if already inside a session) to the other session or attach to the other session (if not yet in Tmux). + +You must install the `fzf` command on your computer for this to work. This is how it looks like: + +[![Tmux session fuzzy finder](./terminal-multiplexing-with-tmux/tmux-session-fzf.png "Tmux session fuzzy finder")](./terminal-multiplexing-with-tmux/tmux-session-fzf.png) + +## The `tssh` alias - Cluster SSH replacement + +Before I used Tmux, I was a heavy user of ClusterSSH, which allowed me to log in to multiple servers at once in a single terminal window and type and run commands on all of them in parallel. + +[https://github.com/duncs/clusterssh](https://github.com/duncs/clusterssh) + +However, since I started using Tmux, I retired ClusterSSH, as it came with the benefit that Tmux only needs to be run in the terminal, whereas ClusterSSH spawned terminal windows, which aren't easily portable (e.g., from a Linux desktop to macOS). The `tmux::cluster_ssh` function can have N arguments, where: + +* ...the first argument will be the session name (see `tmux::tssh_from_argument` helper function), and all remaining arguments will be server hostnames/FQDNs to connect to simultaneously. +* ...or, the first argument is a file name, and the file contains a list of hostnames/FQDNs (see `tmux::ssh_from_file` helper function) + +This is the function definition behind the `tssh` alias: + +```bash +tmux::cluster_ssh () { + if [ -f "$1" ]; then + tmux::tssh_from_file $1 + return + fi + + tmux::tssh_from_argument $@ +} +alias tssh=tmux::cluster_ssh +``` + +This function is just a wrapper around the more complex `tmux::tssh_from_file` and `tmux::tssh_from_argument` functions, as you have learned already. Most of the magic happens there. + +### The `tmux::tssh_from_argument` helper + +This is the most magic helper function we will cover in this post. It looks like this: + +```bash +tmux::tssh_from_argument () { + local -r session=$1; shift + local first_server=$1; shift + + tmux new-session -d -s $session "ssh -t $first_server" + if ! tmux list-session | grep "^$session:"; then + echo "Could not create session $session" + return 2 + fi + + for server in "${@[@]}"; do + tmux split-window -t $session "tmux select-layout tiled; ssh -t $server" + done + + tmux setw -t $session synchronize-panes on + tmux -2 attach-session -t $session | tmux -2 switch-client -t $session +} +``` + +It expects at least two arguments. The first argument is the session name to create for the clustered SSH session. All other arguments are server hostnames or FQDNs to which to connect. The first one is used to make the initial session. All remaining ones are added to that session with `tmux split-window -t $session...`. At the end, we enable synchronized panes by default, so whenever you type, the commands will be sent to every SSH connection, thus allowing the neat ClusterSSH feature to run commands on multiple servers simultaneously. Once done, we attach (or switch, if already in Tmux) to it. + +Sometimes, I don't want the synchronized panes behavior and want to switch it off temporarily. I can do that with `prefix-key p` and `prefix-key P` after adding the following to my local `tmux.conf`: + +``` +bind-key p setw synchronize-panes off +bind-key P setw synchronize-panes on +``` + +### The `tmux::tssh_from_file` helper + +This one sets the session name to the file name and then reads a list of servers from that file, passing the list of servers to `tmux::tssh_from_argument` as the arguments. So, this is a neat little wrapper that also enables me to open clustered SSH sessions from an input file. + +```bash +tmux::tssh_from_file () { + local -r serverlist=$1; shift + local -r session=$(basename $serverlist | cut -d. -f1) + + tmux::tssh_from_argument $session $(awk '{ print $1} ' $serverlist | sed 's/.lan./.lan/g') +} +``` + +### `tssh` examples + +To open a new session named `fish` and log in to 4 remote hosts, run this command (Note that it is also possible to specify the remote user): + +``` +$ tssh fish blowfish.buetow.org fishfinger.buetow.org \ + fishbone.buetow.org user@octopus.buetow.org +``` + +To open a new session named `manyservers`, put many servers (one FQDN per line) into a file called `manyservers.txt` and simply run: + +``` +$ tssh manyservers.txt +``` + +### Common Tmux commands I use in `tssh` + +These are default Tmux commands that I make heavy use of in a `tssh` session: + +* Press `prefix-key DIRECTION` to switch panes. DIRECTION is by default any of the arrow keys, but I also configured Vi keybindings. +* Press `prefix-key ` to change the pane layout (can be pressed multiple times to cycle through them). +* Press `prefix-key z` to zoom in and out of the current active pane. + +## Copy and paste workflow + +As you will see later in this blog post, I have configured a history limit of 1 million items in Tmux so that I can scroll back quite far. One main workflow of mine is to search for text in the Tmux history, select and copy it, and then switch to another window or session and paste it there (e.g., into my text editor to do something with it). + +This works by pressing `prefix-key [` to enter Tmux copy mode. From there, I can browse the Tmux history of the current window using either the arrow keys or vi-like navigation (see vi configuration later in this blog post) and the Pg-Dn and Pg-Up keys. + +I often search the history backwards with `prefix-key [` followed by a `?`, which opens the Tmux history search prompt. + +Once I have identified the terminal text to be copied, I enter visual select mode with `v`, highlight all the text to be copied (using arrow keys or Vi motions), and press `y` to yank it (sorry if this all sounds a bit complicated, but Vim/NeoVim users will know this, as it is pretty much how you do it there as well). + +For `v` and `y` to work, the following has to be added to the Tmux configuration file: + +``` +bind-key -T copy-mode-vi 'v' send -X begin-selection +bind-key -T copy-mode-vi 'y' send -X copy-selection-and-cancel +``` + +Once the text is yanked, I switch to another Tmux window or session where, for example, a text editor is running and paste the yanked text from Tmux into the editor with `prefix-key ]`. Note that when pasting into a modal text editor like Vi or Helix, you would first need to enter insert mode before `prefix-key ]` would paste anything. + +## Tmux configurations + +Some features I have configured directly in Tmux don't require an external shell alias to function correctly. Let's walk line by line through my local `~/config/tmux/tmux.conf`: + +``` +source ~/.config/tmux/tmux.local.conf + +set-option -g allow-rename off +set-option -g history-limit 100000 +set-option -g status-bg '#444444' +set-option -g status-fg '#ffa500' +set-option -s escape-time 0 +``` + +There's yet to be much magic happening here. I source a `tmux.local.conf`, which I sometimes use to override the default configuration that comes from the configuration management system. But it is mostly just an empty file, so it doesn't throw any errors on Tmux startup when I don't use it. + +I work with many terminal outputs, which I also like to search within Tmux. So, I added a large enough `history-limit`, enabling me to search backwards in Tmux for any output up to a million lines of text. + +Besides changing some colours (personal taste), I also set `escape-time` to `0`, which is just a workaround. Otherwise, my Helix text editor's `ESC` key would take ages to trigger within Tmux. I am trying to remember the gory details. You can leave it out; if everything works fine for you, leave it out. + +The next lines in the configuration file are: + +``` +set-window-option -g mode-keys vi +bind-key -T copy-mode-vi 'v' send -X begin-selection +bind-key -T copy-mode-vi 'y' send -X copy-selection-and-cancel +``` + +I navigate within Tmux using Vi keybindings, so the `mode-keys` is set to `vi`. I use the Helix modal text editor, which is close enough to Vi bindings for simple navigation to feel "native" to me. (By the way, I have been a long-time Vim and NeoVim user, but I eventually switched to Helix. It's off-topic here, but it may be worth another blog post once.) + +The two `bind-key` commands make it so that I can use `v` and `y` in copy mode, which feels more Vi-like (as already discussed earlier in this post). + +The next set of lines in the configuration file are: + +``` +bind-key h select-pane -L +bind-key j select-pane -D +bind-key k select-pane -U +bind-key l select-pane -R + +bind-key H resize-pane -L 5 +bind-key J resize-pane -D 5 +bind-key K resize-pane -U 5 +bind-key L resize-pane -R 5 +``` + +These allow me to use `prefix-key h`, `prefix-key j`, `prefix-key k`, and `prefix-key l` for switching panes and `prefix-key H`, `prefix-key J`, `prefix-key K`, and `prefix-key L` for resizing the panes. If you don't know Vi/Vim/NeoVim, the letters `hjkl` are commonly used there for left, down, up, and right, which is also the same for Helix, by the way. + +The next set of lines in the configuration file are: + +``` +bind-key c new-window -c '#{pane_current_path}' +bind-key F new-window -n "session-switcher" "tmux list-sessions | fzf | cut -d: -f1 | xargs tmux switch-client -t" +bind-key T choose-tree +``` + +The first one is that any new window starts in the current directory. The second one is more interesting. I list all open sessions in the fuzzy finder. I rely heavily on this during my daily workflow to switch between various sessions depending on the task. E.g. from a remote cluster SSH session to a local code editor. + +The third one, `choose-tree`, opens a tree view in Tmux listing all sessions and windows. This one is handy to get a better overview of what is currently running in any local Tmux session. It looks like this (it also allows me to press a hotkey to switch to a particular Tmux window): + +[![Tmux sessiont tree view](./terminal-multiplexing-with-tmux/tmux-tree-view.png "Tmux sessiont tree view")](./terminal-multiplexing-with-tmux/tmux-tree-view.png) + + +The last remaining lines in my configuration file are: + +``` +bind-key p setw synchronize-panes off +bind-key P setw synchronize-panes on +bind-key r source-file ~/.config/tmux/tmux.conf \; display-message "tmux.conf reloaded" +``` + +We discussed `synchronized panes` earlier. I use it all the time in clustered SSH sessions. When enabled, all panes (remote SSH sessions) receive the same keystrokes. This is very useful when you want to run the same commands on many servers at once, such as navigating to a common directory, restarting a couple of services at once, or running tools like `htop` to quickly monitor system resources. + +The last one reloads my Tmux configuration on the fly. + +E-Mail your comments to `paul@nospam.buetow.org` :-) + +[Back to the main site](../) diff --git a/gemfeed/DRAFT-KISS-high-availability-with-OpenBSD.md b/gemfeed/DRAFT-KISS-high-availability-with-OpenBSD.md deleted file mode 100644 index 3e388ffe..00000000 --- a/gemfeed/DRAFT-KISS-high-availability-with-OpenBSD.md +++ /dev/null @@ -1,286 +0,0 @@ -# KISS high-availability with OpenBSD - -``` -Art by Michael J. Penick (mod. by Paul B) - - __________ - / nsd tower\ ( - /____________\ (\) awk-ward - |:_:_:_:_:_| )) plant - |_:_,--.:_:| dig-bubble (\// ) - |:_:|__|_:_| relayd-castle _ ) )) (( - _ |_ _ :_:| _ _ _ (_) (((( /)\` - | |_| |_| | _| | |_| |_| | o \\)) (( ( - \_:_:_:_:/|_|_|_|\:_:_:_:_/ . (( )))) - |_,-._:_:_:_:_:_:_:_.-,_| )) ((// - |:|_|:_:_:,---,:_:_:|_|:| ,-. )/ - |_:_:_:_,'puffy `,_:_:_:_| _ o ,;'))(( - |:_:_:_/ _ | _ \_:_:_:| (_O (( )) -_____|_:_:_| (o)-(o) |_:_:_|--'`-. ,--. ksh under-water (((\'/ - ', ;|:_:_:| -( .-. )- |:_:_:| ', ; `--._\ /,---.~ goat \`)) -. ` |_:_:_| \`-'/ |_:_:_|. ` . ` /()\.__( ) .,-----'`-\(( sed-root - ', ;|:_:_:| `-' |:_:_:| ', ; ', ; `--'| \ ', ; ', ; ',')).,-- -. ` MJP ` . ` . ` . ` . httpd-soil ` . . ` . ` . ` . ` . ` - ', ; ', ; ', ; ', ; ', ; ', ; ', ; ', ; ', ; ', ; ', ; ', ; ', ; ', ; - -``` - -I have always wanted a highly available setup for my personal websites. I could have used off-the-shelf hosting solutions or hosted my sites in an AWS S3 bucket. I have used technologies like BGP, LVS/IPVS, ldirectord, Pacemaker, heartbeat, heartbeat2, Corosync, keepalived, DRBD, and commercial F5 Load Balancers for high availability at work. - -But still, my personal sites were never highly available. All those technologies are great for professional use, but I was looking for something much more straightforward for my personal space—something as KISS (keep it simple and stupid) as possible. - -It would be fine if my personal website wasn't highly available, but the geek in me wants it anyway. - -> PS: ASCII-art reflects the OpenBSD under-water world with all the tools available in the base system. - -## My auto-failover requirements - -* Be OpenBSD-based (I prefer OpenBSD because of the cleanliness and good documentation) and rely on as few external packages as possible. -* Don't rely on the hottest and newest tech (don't want to migrate everything to a new and fancier technology next month). -* It should be reasonably cheap. I want to avoid paying a premium for floating IPs or fancy Elastic Load Balancers. -* It should be geo-redundant. -* It's fine if my sites aren't reachable for five or ten minutes every other month. Due to their static nature, I don't care if there's a split-brain scenario where some requests reach one server and other requests reach another server. -* Failover should work for both HTTP/HTTPS and Gemini protocols. My self-hosted MTAs and DNS servers should also be highly available. -* Let's Encrypt TLS certificates should always work (before and after a failover). -* Have good monitoring in place so I know when a failover was performed and when something went wrong with the failover. -* Don't configure everything manually. The configuration should be automated and reproducible. - -## My HA solution - -### Only OpenBSD base installation required - -My HA solution for Web and Gemini is based on DNS (OpenBSD's `nsd`) and a simple shell script (OpenBSD's `ksh` and some little `sed` and `awk` and `grep`). All software used here is part of the OpenBSD base system and no external package needs to be installed - OpenBSD is a complete operating system. - -[https://man.OpenBSD.org/nsd.8](https://man.OpenBSD.org/nsd.8) -[https://man.OpenBSD.org/ksh](https://man.OpenBSD.org/ksh) -[https://man.OpenBSD.org/awk](https://man.OpenBSD.org/awk) -[https://man.OpenBSD.org/sed](https://man.OpenBSD.org/sed) -[https://man.OpenBSD.org/dig](https://man.OpenBSD.org/dig) -[https://man.OpenBSD.org/ftp](https://man.OpenBSD.org/ftp) - -I also used the `dig` (for DNS checks) and `ftp` (for HTTP/HTTPS checks) programs. - -The DNS failover is performed automatically between the two OpenBSD VMs involved (my setup doesn't require any quorum for a failover, so there isn't a need for a 3rd VM). The `ksh` script, executed once per minute via CRON (on both VMs), performs a health check to determine whether the current master node is available. If the current master isn't available (no HTTP response as expected), a failover is performed to the standby VM: - -```sh -#!/bin/ksh - -ZONES_DIR=/var/nsd/zones/master/ -DEFAULT_MASTER=fishfinger.buetow.org -DEFAULT_STANDBY=blowfish.buetow.org - -determine_master_and_standby () { - local master=$DEFAULT_MASTER - local standby=$DEFAULT_STANDBY - - . - . - . - - local -i health_ok=1 - if ! ftp -4 -o - https://$master/index.txt | grep -q "Welcome to $master"; then - echo "https://$master/index.txt IPv4 health check failed" - health_ok=0 - elif ! ftp -6 -o - https://$master/index.txt | grep -q "Welcome to $master"; then - echo "https://$master/index.txt IPv6 health check failed" - health_ok=0 - fi - if [ $health_ok -eq 0 ]; then - local tmp=$master - master=$standby - standby=$tmp - fi - - . - . - . -} -``` - -The failover scripts looks for the ` ; Enable failover` string in the DNS zone files and swaps the `A` and `AAAA` records of the DNS entries accordingly: - -```sh -fishfinger$ grep failover /var/nsd/zones/master/foo.zone.zone - 300 IN A 46.23.94.99 ; Enable failover - 300 IN AAAA 2a03:6000:6f67:624::99 ; Enable failover -www 300 IN A 46.23.94.99 ; Enable failover -www 300 IN AAAA 2a03:6000:6f67:624::99 ; Enable failover -standby 300 IN A 23.88.35.144 ; Enable failover -standby 300 IN AAAA 2a01:4f8:c17:20f1::42 ; Enable failover -``` - -```sh -tramsform () { - sed -E ' - /IN A .*; Enable failover/ { - /^standby/! { - s/^(.*) 300 IN A (.*) ; (.*)/\1 300 IN A '$(cat /var/nsd/run/master_a)' ; \3/; - } - /^standby/ { - s/^(.*) 300 IN A (.*) ; (.*)/\1 300 IN A '$(cat /var/nsd/run/standby_a)' ; \3/; - } - } - /IN AAAA .*; Enable failover/ { - /^standby/! { - s/^(.*) 300 IN AAAA (.*) ; (.*)/\1 300 IN AAAA '$(cat /var/nsd/run/master_aaaa)' ; \3/; - } - /^standby/ { - s/^(.*) 300 IN AAAA (.*) ; (.*)/\1 300 IN AAAA '$(cat /var/nsd/run/standby_aaaa)' ; \3/; - } - } - / ; serial/ { - s/^( +) ([0-9]+) .*; (.*)/\1 '$(date +%s)' ; \3/; - } - ' -} -``` - -After the failover, the script reloads `nsd` and performs a sanity check to see if DNS still works. If not, a rollback will be performed: - -```sh -# Race condition (e.g. script execution abored in the middle of the previous run) -if [ -f $zone_file.bak ]; then - mv $zone_file.bak $zone_file -fi - -cat $zone_file | transform > $zone_file.new.tmp - -grep -v ' ; serial' $zone_file.new.tmp > $zone_file.new.noserial.tmp -grep -v ' ; serial' $zone_file > $zone_file.old.noserial.tmp - -echo "Has zone $zone_file changed?" -if diff -u $zone_file.old.noserial.tmp $zone_file.new.noserial.tmp; then - echo "The zone $zone_file hasn't changed" - rm $zone_file.*.tmp - return 0 -fi - -cp $zone_file $zone_file.bak -mv $zone_file.new.tmp $zone_file -rm $zone_file.*.tmp -echo "Reloading nsd" -nsd-control reload - -if ! zone_is_ok $zone; then - echo "Rolling back $zone_file changes" - cp $zone_file $zone_file.invalid - mv $zone_file.bak $zone_file - echo "Reloading nsd" - nsd-control reload - zone_is_ok $zone - return 3 -fi - -for cleanup in invalid bak; do - if [ -f $zone_file.$cleanup ]; then - rm $zone_file.$cleanup - fi -done - -echo "Failover of zone $zone to $MASTER completed" -return 1 -``` - -A non-zero return code (here, 3 when a rollback and 1 when a DNS failover was performed) will cause CRON to send an E-Mail with the whole script output. - -The nameserver is running on both VMs, and both are configured to be "master" DNS servers so that they have their own individual zone files, which can be changed independently. Otherwise, my setup wouldn't work. The side effect is that under a split-brain scenario (both VMs cannot see each other), both would promote themselves to master via their local DNS entries. More about that later, but that's fine in my use case. - -Check out the whole script here: - -[https://codeberg.org/snonux/rexfiles/src/branch/master/frontends/scripts/dns-failover.ksh](https://codeberg.org/snonux/rexfiles/src/branch/master/frontends/scripts/dns-failover.ksh) - -### Fairly cheap and geo-redundant - -I am renting two small OpenBSD VMs: One at OpenBSD Amsterdam and the other at Hetzner Cloud. So, both VMs are hosted at another provider, in different IP subnets, and in different countries (the Netherlands and Germany). - -[https://openbsd.amsterdam](https://openbsd.amsterdam) -[https://www.hetzner.cloud](https://www.hetzner.cloud) - -I only have a little traffic on my sites. I could always upload the static content to AWS S3 if I suddenly had to. But this will never be required. - -A DNS-based failover is cheap, as there isn't any BGP or fancy load balancer to pay for. Small VMs also cost less than millions. - -### Failover time and split-brain - -A DNS failover doesn't happen immediately. I've configured a DNS TTL of `300` seconds, and the failover script checks once per minute whether to perform a failover or not. So, in total, a failover can take six minutes (not including other DNS caching servers somewhere in the interweb, but that's fine - eventually, all requests will resolve to the new master after a failover). - -A split-brain scenario between the old master and the new master might happen. That's OK, as my sites are static, and there's no database to synchronise other than HTML, CSS, and images when the site is updated. - -### Failover support for multiple protocols - -With the DNS failover, HTTP, HTTPS, and Gemini protocols are failovered. This works because all domain virtual hosts are configured on either VM's `httpd` (OpenBSD's HTTP server) and `relayd` (it's also part of OpenBSD and I use it to TLS offload the Gemini protocol). So, both VMs accept requests for all the hosts. It's just a matter of the DNS entry, which hosts receive the requests. - -[https://man.openbsd.org/httpd.8](https://man.openbsd.org/httpd.8) -[https://man.openbsd.org/relayd.8](https://man.openbsd.org/relayd.8) - -For example, the master is responsible for the `https://www.foo.zone` and `https://foo.zone` hosts, whereas the standby can be reached via `https://standby.foo.zone` (port 80 for plain HTTP works as well). The same principle is followed with all the other hosts, e.g. `irregular.ninja`, `paul.buetow.org` and so on. The same applies to my Gemini capsules for `gemini://foo.zone`, `gemini://standby.foo.zone`, `gemini://paul.buetow.org` and `gemini://standby.paul.buetow.org`. - -On DNS failover, master and standby swap roles without config changes other than the DNS entries. That's KISS (keep it simple and stupid)! - -### Let's encrypt TLS certificates - -All my hosts use TLS certificates from Let's Encrypt. The ACME automation for requesting and keeping the certificates valid (up to date) requires that the host requesting a certificate from Let's Encrypt is also the host using that certificate. - -If the master always serves `foo.zone` and the standby always `standby.foo.zone`, then there would be a problem after the failover, as the new master wouldn't have a valid certificate for `foo.zone` and the new standby wouldn't have a valid certificate for `standby.foo.zone` which would lead to TLS errors on the clients. - -As a solution, the CRON job responsible for the DNS failover also checks for the current week number of the year so that: - -* In an odd week number, the first server is the default master -* In an even week number, the second server is the default master. - -Which translates to: - -```sh -# Weekly auto-failover for Let's Encrypt automation -local -i -r week_of_the_year=$(date +%U) -if [ $(( week_of_the_year % 2 )) -eq 0 ]; then - local tmp=$master - master=$standby - standby=$tmp -fi -``` - -This way, a DNS failover is performed weekly so that the ACME automation can update the Let's Encrypt certificates (for master and standby) before they expire on each VM. - -The ACME automation is yet another daily CRON script `/usr/local/bin/acme.sh`. It iterates over all of my Let's Encrypt hosts, checks whether they resolve to the same IP address as the current VM, and only then invokes the ACME client to request or renew the TLS certificates. So, there are always correct requests made to Let's Encrypt. - -Let's encrypt certificates usually expire after 3 months, so a weekly failover of my VMs is plenty. - -[`acme.sh.tpl` - Rex template for the `acme.sh` script of mine.](https://codeberg.org/snonux/rexfiles/src/branch/master/frontends/scripts/acme.sh.tpl) -[https://man.openbsd.org/acme-client.1](https://man.openbsd.org/acme-client.1) -[Let's Encrypt with OpenBSD and Rex](./2022-07-30-lets-encrypt-with-openbsd-and-rex.md) - -### Monitoring - -CRON is sending me an E-Mail whenever a failover is performed (or whenever a failover failed). Furthermore, I am monitoring my DNS servers and hosts through Gogios, the monitoring system I have developed. - -[https://codeberg.org/snonux/gogios](https://codeberg.org/snonux/gogios) -[KISS server monitoring with Gogios](./2023-06-01-kiss-server-monitoring-with-gogios.md) - -### Rex automation - -I use Rexify, a friendly configuration management system that allows automatic deployment and configuration. - -[https://www.rexify.org](https://www.rexify.org) -[https://codeberg.org/snonux/rexfiles/src/branch/master/frontends](https://codeberg.org/snonux/rexfiles/src/branch/master/frontends) - -## More HA - -Other high-available services running on my OpenBSD VMs are my MTAs for mail forwarding (OpenSMTPD) and the authoritative DNS servers (`nsd`) for all my domains. No particular HA setup is required, though, as the protocols (SMTP and DNS) already take care of the failover to the next available host! - -As a password manager, I use `geheim`, a command-line tool I wrote in Ruby with encrypted files in a git repository (I even have it installed in Termux on my Phone). For HA reasons, I simply updated the client code so that it always synchronises the database with both servers when I run the `sync` command there. - -[https://codeberg.org/snonux/geheim](https://codeberg.org/snonux/geheim) - -E-Mail your comments to `paul@nospam.buetow.org` :-) - -Other *BSD and KISS related posts are: - -[2016-04-09 Jails and ZFS with Puppet on FreeBSD](./2016-04-09-jails-and-zfs-on-freebsd-with-puppet.md) -[2022-07-30 Let's Encrypt with OpenBSD and Rex](./2022-07-30-lets-encrypt-with-openbsd-and-rex.md) -[2022-10-30 Installing DTail on OpenBSD](./2022-10-30-installing-dtail-on-openbsd.md) -[2023-06-01 KISS server monitoring with Gogios](./2023-06-01-kiss-server-monitoring-with-gogios.md) -[2023-10-29 KISS static web photo albums with `photoalbum.sh`](./2023-10-29-kiss-static-web-photo-albums-with-photoalbum.sh.md) -[2024-01-13 One reason why I love OpenBSD](./2024-01-13-one-reason-why-i-love-openbsd.md) - -[Back to the main site](../) diff --git a/gemfeed/index.md b/gemfeed/index.md index ba0c2b4a..d192bfbd 100644 --- a/gemfeed/index.md +++ b/gemfeed/index.md @@ -2,6 +2,7 @@ ## To be in the .zone! +[2024-06-23 - Terminal multiplexing with `tmux`](./2024-06-23-terminal-multiplexing-with-tmux.md) [2024-05-03 - Projects I currently don't have time for](./2024-05-03-projects-i-currently-dont-have-time-for.md) [2024-05-01 - 'Slow Productivity' book notes](./2024-05-01-slow-productivity-book-notes.md) [2024-04-01 - KISS high-availability with OpenBSD](./2024-04-01-KISS-high-availability-with-OpenBSD.md) diff --git a/gemfeed/terminal-multiplexing-with-tmux/tmux-session-fzf.png b/gemfeed/terminal-multiplexing-with-tmux/tmux-session-fzf.png new file mode 100644 index 00000000..7a2e9440 Binary files /dev/null and b/gemfeed/terminal-multiplexing-with-tmux/tmux-session-fzf.png differ diff --git a/gemfeed/terminal-multiplexing-with-tmux/tmux-tree-view.png b/gemfeed/terminal-multiplexing-with-tmux/tmux-tree-view.png new file mode 100644 index 00000000..672859c5 Binary files /dev/null and b/gemfeed/terminal-multiplexing-with-tmux/tmux-tree-view.png differ -- cgit v1.2.3 From 32d011ed4defd6f77fdcc66668a6f739785d2700 Mon Sep 17 00:00:00 2001 From: Paul Buetow Date: Sun, 23 Jun 2024 23:14:32 +0300 Subject: Update content for md --- .../2024-06-23-terminal-multiplexing-with-tmux.md | 29 +++++++--------------- 1 file changed, 9 insertions(+), 20 deletions(-) (limited to 'gemfeed') diff --git a/gemfeed/2024-06-23-terminal-multiplexing-with-tmux.md b/gemfeed/2024-06-23-terminal-multiplexing-with-tmux.md index 277968e1..4cb4f369 100644 --- a/gemfeed/2024-06-23-terminal-multiplexing-with-tmux.md +++ b/gemfeed/2024-06-23-terminal-multiplexing-with-tmux.md @@ -3,26 +3,15 @@ > Published at 2024-06-23T22:41:59+03:00 ``` - \\\\\\\ - \\\\\\\\\\\\ - \\\\\\\\\\\\\\\ - -----------,-| |C> // )\\\\| - ,','| / || ,'/////| ----------,',' X| (, || ///// - || U | \\ ||||//''''| - || M .| ||||||| _| - ||T . |______ `````\____/ \ - || . | ,| _/_____/ \ - ||$ ,' ,' | / | - ||,' ,' | | \ | -_________|/ ,' | / | | -_____________,' ,',_____| | | | - | ,',' | | | | - | ,',' ____|_____/ / | - | ,',' __/ | / | -_____________|',' ///_/-------------/ | - |===========,' - + _______ + |.-----.| + || Tmux|| + ||_.-._|| + `--)-(--` + __[=== o]___ + |:::::::::::|\ +jgs `-=========-`() + mod. by Paul B. ``` ``` -- cgit v1.2.3 From c3f8dd7eefa667bac0320fc18f433c9e8d511bd4 Mon Sep 17 00:00:00 2001 From: Paul Buetow Date: Sun, 23 Jun 2024 23:44:45 +0300 Subject: Update content for md --- gemfeed/2024-06-23-terminal-multiplexing-with-tmux.md | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) (limited to 'gemfeed') diff --git a/gemfeed/2024-06-23-terminal-multiplexing-with-tmux.md b/gemfeed/2024-06-23-terminal-multiplexing-with-tmux.md index 4cb4f369..472cb022 100644 --- a/gemfeed/2024-06-23-terminal-multiplexing-with-tmux.md +++ b/gemfeed/2024-06-23-terminal-multiplexing-with-tmux.md @@ -316,7 +316,7 @@ Once the text is yanked, I switch to another Tmux window or session where, for e ## Tmux configurations -Some features I have configured directly in Tmux don't require an external shell alias to function correctly. Let's walk line by line through my local `~/config/tmux/tmux.conf`: +Some features I have configured directly in Tmux don't require an external shell alias to function correctly. Let's walk line by line through my local `~/.config/tmux/tmux.conf`: ``` source ~/.config/tmux/tmux.local.conf -- cgit v1.2.3 From 953750b60342b3d763939237875cc4227119aa96 Mon Sep 17 00:00:00 2001 From: Paul Buetow Date: Fri, 5 Jul 2024 11:11:33 +0300 Subject: Update content for md --- gemfeed/2024-07-05-random-weird-things.md | 332 ++++++++++++++++++++++++++++++ gemfeed/index.md | 1 + 2 files changed, 333 insertions(+) create mode 100644 gemfeed/2024-07-05-random-weird-things.md (limited to 'gemfeed') diff --git a/gemfeed/2024-07-05-random-weird-things.md b/gemfeed/2024-07-05-random-weird-things.md new file mode 100644 index 00000000..4b28ac93 --- /dev/null +++ b/gemfeed/2024-07-05-random-weird-things.md @@ -0,0 +1,332 @@ +# Random Weird Things + +> Published at 2024-07-05T10:59:59+03:00 + +Every so often, I come across random, weird, and unexpected things on the internet. I thought it would be neat to share them here from time to time. As a start, here are ten of them. + +``` + /\_/\ +WHOA!! ( o.o ) + > ^ < + / - \ + / \ + /______\ \ +``` + +## 1. `bad.horse` traceroute + +Run traceroute to get the poem (or song). + +```bash +% traceroute bad.horse +traceroute to bad.horse (162.252.205.157), 30 hops max, 60 byte packets + 1 dsldevice.lan (192.168.1.1) 5.712 ms 5.800 ms 6.466 ms + 2 87-243-116-2.ip.btc-net.bg (87.243.116.2) 8.017 ms 7.506 ms 8.432 ms + 3 * * * + 4 * * * + 5 xe-1-2-0.mpr1.fra4.de.above.net (80.81.194.26) 39.952 ms 40.155 ms 40.139 ms + 6 ae12.cs1.fra6.de.eth.zayo.com (64.125.26.172) 128.014 ms * * + 7 * * * + 8 * * * + 9 ae10.cs1.lhr15.uk.eth.zayo.com (64.125.29.17) 120.625 ms 121.117 ms 121.050 ms +10 * * * +11 * * * +12 * * * +13 ae5.mpr1.tor3.ca.zip.zayo.com (64.125.23.118) 192.605 ms 205.741 ms 203.607 ms +14 64.124.217.237.IDIA-265104-ZYO.zip.zayo.com (64.124.217.237) 204.673 ms 134.674 ms 131.442 ms +15 * * * +16 67.223.96.90 (67.223.96.90) 128.245 ms 127.844 ms 127.843 ms +17 bad.horse (162.252.205.130) 128.194 ms 122.854 ms 121.786 ms +18 bad.horse (162.252.205.131) 128.831 ms 128.341 ms 186.559 ms +19 bad.horse (162.252.205.132) 185.716 ms 180.121 ms 180.042 ms +20 bad.horse (162.252.205.133) 203.170 ms 203.076 ms 203.168 ms +21 he.rides.across.the.nation (162.252.205.134) 203.115 ms 141.830 ms 141.799 ms +22 the.thoroughbred.of.sin (162.252.205.135) 147.965 ms 148.230 ms 170.478 ms +23 he.got.the.application (162.252.205.136) 165.161 ms 164.939 ms 159.085 ms +24 that.you.just.sent.in (162.252.205.137) 162.310 ms 158.569 ms 158.896 ms +25 it.needs.evaluation (162.252.205.138) 162.927 ms 163.046 ms 163.085 ms +26 so.let.the.games.begin (162.252.205.139) 233.363 ms 233.545 ms 233.317 ms +27 a.heinous.crime (162.252.205.140) 237.745 ms 233.614 ms 233.740 ms +28 a.show.of.force (162.252.205.141) 237.974 ms 176.085 ms 175.927 ms +29 a.murder.would.be.nice.of.course (162.252.205.142) 181.838 ms 181.858 ms 182.059 ms +30 bad.horse (162.252.205.143) 187.731 ms 187.416 ms 187.532 ms +``` + +## 2. ASCII cinema + +Fancy watching Star Wars Episode IV in ASCII? Head to the ASCII cinema: + +[https://asciinema.org/a/569727](https://asciinema.org/a/569727) + +## 3. Netflix's Hello World application + +Netflix has got the Hello World application run in production 😱 + +* https://www.Netflix.com/helloworld + +> By the time this is posted, it seems that Netflix has taken it offline... I should have created a screenshot! + +## C programming + +### 4. Indexing an array + +In C, you can index an array like this: `array[i]` (not surprising). But this works as well and is valid C code: `i[array]`, 🤯 It's because after the spec `A[B]` is equivalent to `*(A + B)` and the ordering doesn't matter for the `+` operator. All 3 loops are producing the same output. Would be funny to use `i[array]` in a merge request of some code base on April Fool's day! + +```c +#include + +int main(void) { + int array[5] = { 1, 2, 3, 4, 5 }; + + for (int i = 0; i < 5; i++) + printf("%d\n", array[i]); + + for (int i = 0; i < 5; i++) + printf("%d\n", i[array]); + + for (int i = 0; i < 5; i++) + printf("%d\n", *(i + array)); +} +``` + +### 5. Variables with prefix `$` + +In C you can prefix variables with `$`! E.g. the following is valid C code 🫠: + +```c +#include + +int main(void) { + int $array[5] = { 1, 2, 3, 4, 5 }; + + for (int $i = 0; $i < 5; $i++) + printf("%d\n", $array[$i]); + + for (int $i = 0; $i < 5; $i++) + printf("%d\n", $i[$array]); + + for (int $i = 0; $i < 5; $i++) + printf("%d\n", *($i + $array)); +} +``` + +## 6. Object oriented shell scripts using `ksh` + +Experienced software developers are aware that scripting languages like Python, Perl, Ruby, and JavaScript support object-oriented programming (OOP) concepts such as classes and inheritance. However, many might be surprised to learn that the latest version of the Korn shell (Version 93t+) also supports OOP. In ksh93, OOP is implemented using user-defined types: + +```ksh +#!/usr/bin/ksh93 + +typeset -T Point_t=( + integer -h 'x coordinate' x=0 + integer -h 'y coordinate' y=0 + typeset -h 'point color' color="red" + + function getcolor { + print -r ${_.color} + } + + function setcolor { + _.color=$1 + } + + setxy() { + _.x=$1; _.y=$2 + } + + getxy() { + print -r "(${_.x},${_.y})" + } +) + +Point_t point + +echo "Initial coordinates are (${point.x},${point.y}). Color is ${point.color}" + +point.setxy 5 6 +point.setcolor blue + +echo "New coordinates are ${point.getxy}. Color is ${point.getcolor}" + +exit 0 +``` + +[Using types to create object oriented Korn shell 93 scripts](https://blog.fpmurphy.com/2010/05/ksh93-using-types-to-create-object-orientated-scripts.html) + +## 7. This works in Go + +There is no pointer arithmetic in Go like in C, but it is still possible to do some brain teasers with pointers 😧: + +```go +package main + +import "fmt" + +func main() { + var i int + f := func() *int { + return &i + } + *f()++ + fmt.Println(i) +} +``` + +[Go playground](https://go.dev/play/p/sPRdyDvXefK?__s=mk8u899owb9yurl256gw) + +## 8. "I am a Teapot" HTTP response code + +Defined in 1998 as one of the IETF's traditional April Fools' jokes (RFC 2324), the Hyper Text Coffee Pot Control Protocol specifies an HTTP status code that is not intended for actual HTTP server implementation. According to the RFC, this code should be returned by teapots when asked to brew coffee. This status code also serves as an Easter egg on some websites, such as Google.com's "I'm a teapot" feature. Occasionally, it is used to respond to a blocked request, even though the more appropriate response would be the 403 Forbidden status code. + +[https://en.wikipedia.org/wiki/List_of_HTTP_status_codes#418](https://en.wikipedia.org/wiki/List_of_HTTP_status_codes#418) + +## 9. `jq` is a functional programming language + +Many know of `jq`, the handy small tool and swiss army knife for JSON parsing. + +[https://github.com/jqlang/jq](https://github.com/jqlang/jq) + +What many don't know that `jq` is actually a full blown functional programming language `jqlang`, have a look at the language description: + +[https://github.com/jqlang/jq/wiki/jq-Language-Description](https://github.com/jqlang/jq/wiki/jq-Language-Description) + +As a matter of fact, the language is so powerful, that there exists an implementation of `jq` in `jq` itself: + +[https://github.com/wader/jqjq](https://github.com/wader/jqjq) + +Here some snipped from `jqjq`, to get a feel of `jqlang`: + +``` +def _token: + def _re($re; f): + ( . as {$remain, $string_stack} + | $remain + | match($re; "m").string + | f as $token + | { result: ($token | del(.string_stack)) + , remain: $remain[length:] + , string_stack: + ( if $token.string_stack == null then $string_stack + else $token.string_stack + end + ) + } + ); + if .remain == "" then empty + else + ( . as {$string_stack} + | _re("^\\s+"; {whitespace: .}) + // _re("^#[^\n]*"; {comment: .}) + // _re("^\\.[_a-zA-Z][_a-zA-Z0-9]*"; {index: .[1:]}) + // _re("^[_a-zA-Z][_a-zA-Z0-9]*"; {ident: .}) + // _re("^@[_a-zA-Z][_a-zA-Z0-9]*"; {at_ident: .}) + // _re("^\\$[_a-zA-Z][_a-zA-Z0-9]*"; {binding: .}) + # 1.23, .123, 123e2, 1.23e2, 123E2, 1.23e+2, 1.23E-2 or 123 + // _re("^(?:[0-9]*\\.[0-9]+|[0-9]+)(?:[eE][-\\+]?[0-9]+)?"; {number: .}) + // _re("^\"(?:[^\"\\\\]|\\\\.)*?\\\\\\("; + ( .[1:-2] + | _unescape + | {string_start: ., string_stack: ($string_stack+["\\("])} + ) + ) + . + . + . +``` + +## 10. Regular expression to verify email addresses + +This is a pretty old meme, but still worth posting here (as some may be unaware). The RFC822 Perl regex to validate email addresses is 😱: + +``` +(?:(?:\r\n)?[ \t])*(?:(?:(?:[^()<>@,;:\\".\[\] \000-\031]+(?:(?:(?:\r\n)?[ \t] +)+|\Z|(?=[\["()<>@,;:\\".\[\]]))|"(?:[^\"\r\\]|\\.|(?:(?:\r\n)?[ \t]))*"(?:(?: +\r\n)?[ \t])*)(?:\.(?:(?:\r\n)?[ \t])*(?:[^()<>@,;:\\".\[\] \000-\031]+(?:(?:( +?:\r\n)?[ \t])+|\Z|(?=[\["()<>@,;:\\".\[\]]))|"(?:[^\"\r\\]|\\.|(?:(?:\r\n)?[ +\t]))*"(?:(?:\r\n)?[ \t])*))*@(?:(?:\r\n)?[ \t])*(?:[^()<>@,;:\\".\[\] \000-\0 +31]+(?:(?:(?:\r\n)?[ \t])+|\Z|(?=[\["()<>@,;:\\".\[\]]))|\[([^\[\]\r\\]|\\.)*\ +](?:(?:\r\n)?[ \t])*)(?:\.(?:(?:\r\n)?[ \t])*(?:[^()<>@,;:\\".\[\] \000-\031]+ +(?:(?:(?:\r\n)?[ \t])+|\Z|(?=[\["()<>@,;:\\".\[\]]))|\[([^\[\]\r\\]|\\.)*\](?: +(?:\r\n)?[ \t])*))*|(?:[^()<>@,;:\\".\[\] \000-\031]+(?:(?:(?:\r\n)?[ \t])+|\Z +|(?=[\["()<>@,;:\\".\[\]]))|"(?:[^\"\r\\]|\\.|(?:(?:\r\n)?[ \t]))*"(?:(?:\r\n) +?[ \t])*)*\<(?:(?:\r\n)?[ \t])*(?:@(?:[^()<>@,;:\\".\[\] \000-\031]+(?:(?:(?:\ +r\n)?[ \t])+|\Z|(?=[\["()<>@,;:\\".\[\]]))|\[([^\[\]\r\\]|\\.)*\](?:(?:\r\n)?[ + \t])*)(?:\.(?:(?:\r\n)?[ \t])*(?:[^()<>@,;:\\".\[\] \000-\031]+(?:(?:(?:\r\n) +?[ \t])+|\Z|(?=[\["()<>@,;:\\".\[\]]))|\[([^\[\]\r\\]|\\.)*\](?:(?:\r\n)?[ \t] +)*))*(?:,@(?:(?:\r\n)?[ \t])*(?:[^()<>@,;:\\".\[\] \000-\031]+(?:(?:(?:\r\n)?[ + \t])+|\Z|(?=[\["()<>@,;:\\".\[\]]))|\[([^\[\]\r\\]|\\.)*\](?:(?:\r\n)?[ \t])* +)(?:\.(?:(?:\r\n)?[ \t])*(?:[^()<>@,;:\\".\[\] \000-\031]+(?:(?:(?:\r\n)?[ \t] +)+|\Z|(?=[\["()<>@,;:\\".\[\]]))|\[([^\[\]\r\\]|\\.)*\](?:(?:\r\n)?[ \t])*))*) +*:(?:(?:\r\n)?[ \t])*)?(?:[^()<>@,;:\\".\[\] \000-\031]+(?:(?:(?:\r\n)?[ \t])+ +|\Z|(?=[\["()<>@,;:\\".\[\]]))|"(?:[^\"\r\\]|\\.|(?:(?:\r\n)?[ \t]))*"(?:(?:\r +\n)?[ \t])*)(?:\.(?:(?:\r\n)?[ \t])*(?:[^()<>@,;:\\".\[\] \000-\031]+(?:(?:(?: +\r\n)?[ \t])+|\Z|(?=[\["()<>@,;:\\".\[\]]))|"(?:[^\"\r\\]|\\.|(?:(?:\r\n)?[ \t +]))*"(?:(?:\r\n)?[ \t])*))*@(?:(?:\r\n)?[ \t])*(?:[^()<>@,;:\\".\[\] \000-\031 +]+(?:(?:(?:\r\n)?[ \t])+|\Z|(?=[\["()<>@,;:\\".\[\]]))|\[([^\[\]\r\\]|\\.)*\]( +?:(?:\r\n)?[ \t])*)(?:\.(?:(?:\r\n)?[ \t])*(?:[^()<>@,;:\\".\[\] \000-\031]+(? +:(?:(?:\r\n)?[ \t])+|\Z|(?=[\["()<>@,;:\\".\[\]]))|\[([^\[\]\r\\]|\\.)*\](?:(? +:\r\n)?[ \t])*))*\>(?:(?:\r\n)?[ \t])*)|(?:[^()<>@,;:\\".\[\] \000-\031]+(?:(? +:(?:\r\n)?[ \t])+|\Z|(?=[\["()<>@,;:\\".\[\]]))|"(?:[^\"\r\\]|\\.|(?:(?:\r\n)? +[ \t]))*"(?:(?:\r\n)?[ \t])*)*:(?:(?:\r\n)?[ \t])*(?:(?:(?:[^()<>@,;:\\".\[\] +\000-\031]+(?:(?:(?:\r\n)?[ \t])+|\Z|(?=[\["()<>@,;:\\".\[\]]))|"(?:[^\"\r\\]| +\\.|(?:(?:\r\n)?[ \t]))*"(?:(?:\r\n)?[ \t])*)(?:\.(?:(?:\r\n)?[ \t])*(?:[^()<> +@,;:\\".\[\] \000-\031]+(?:(?:(?:\r\n)?[ \t])+|\Z|(?=[\["()<>@,;:\\".\[\]]))|" +(?:[^\"\r\\]|\\.|(?:(?:\r\n)?[ \t]))*"(?:(?:\r\n)?[ \t])*))*@(?:(?:\r\n)?[ \t] +)*(?:[^()<>@,;:\\".\[\] \000-\031]+(?:(?:(?:\r\n)?[ \t])+|\Z|(?=[\["()<>@,;:\\ +".\[\]]))|\[([^\[\]\r\\]|\\.)*\](?:(?:\r\n)?[ \t])*)(?:\.(?:(?:\r\n)?[ \t])*(? +:[^()<>@,;:\\".\[\] \000-\031]+(?:(?:(?:\r\n)?[ \t])+|\Z|(?=[\["()<>@,;:\\".\[ +\]]))|\[([^\[\]\r\\]|\\.)*\](?:(?:\r\n)?[ \t])*))*|(?:[^()<>@,;:\\".\[\] \000- +\031]+(?:(?:(?:\r\n)?[ \t])+|\Z|(?=[\["()<>@,;:\\".\[\]]))|"(?:[^\"\r\\]|\\.|( +?:(?:\r\n)?[ \t]))*"(?:(?:\r\n)?[ \t])*)*\<(?:(?:\r\n)?[ \t])*(?:@(?:[^()<>@,; +:\\".\[\] \000-\031]+(?:(?:(?:\r\n)?[ \t])+|\Z|(?=[\["()<>@,;:\\".\[\]]))|\[([ +^\[\]\r\\]|\\.)*\](?:(?:\r\n)?[ \t])*)(?:\.(?:(?:\r\n)?[ \t])*(?:[^()<>@,;:\\" +.\[\] \000-\031]+(?:(?:(?:\r\n)?[ \t])+|\Z|(?=[\["()<>@,;:\\".\[\]]))|\[([^\[\ +]\r\\]|\\.)*\](?:(?:\r\n)?[ \t])*))*(?:,@(?:(?:\r\n)?[ \t])*(?:[^()<>@,;:\\".\ +[\] \000-\031]+(?:(?:(?:\r\n)?[ \t])+|\Z|(?=[\["()<>@,;:\\".\[\]]))|\[([^\[\]\ +r\\]|\\.)*\](?:(?:\r\n)?[ \t])*)(?:\.(?:(?:\r\n)?[ \t])*(?:[^()<>@,;:\\".\[\] +\000-\031]+(?:(?:(?:\r\n)?[ \t])+|\Z|(?=[\["()<>@,;:\\".\[\]]))|\[([^\[\]\r\\] +|\\.)*\](?:(?:\r\n)?[ \t])*))*)*:(?:(?:\r\n)?[ \t])*)?(?:[^()<>@,;:\\".\[\] \0 +00-\031]+(?:(?:(?:\r\n)?[ \t])+|\Z|(?=[\["()<>@,;:\\".\[\]]))|"(?:[^\"\r\\]|\\ +.|(?:(?:\r\n)?[ \t]))*"(?:(?:\r\n)?[ \t])*)(?:\.(?:(?:\r\n)?[ \t])*(?:[^()<>@, +;:\\".\[\] \000-\031]+(?:(?:(?:\r\n)?[ \t])+|\Z|(?=[\["()<>@,;:\\".\[\]]))|"(? +:[^\"\r\\]|\\.|(?:(?:\r\n)?[ \t]))*"(?:(?:\r\n)?[ \t])*))*@(?:(?:\r\n)?[ \t])* +(?:[^()<>@,;:\\".\[\] \000-\031]+(?:(?:(?:\r\n)?[ \t])+|\Z|(?=[\["()<>@,;:\\". +\[\]]))|\[([^\[\]\r\\]|\\.)*\](?:(?:\r\n)?[ \t])*)(?:\.(?:(?:\r\n)?[ \t])*(?:[ +^()<>@,;:\\".\[\] \000-\031]+(?:(?:(?:\r\n)?[ \t])+|\Z|(?=[\["()<>@,;:\\".\[\] +]))|\[([^\[\]\r\\]|\\.)*\](?:(?:\r\n)?[ \t])*))*\>(?:(?:\r\n)?[ \t])*)(?:,\s*( +?:(?:[^()<>@,;:\\".\[\] \000-\031]+(?:(?:(?:\r\n)?[ \t])+|\Z|(?=[\["()<>@,;:\\ +".\[\]]))|"(?:[^\"\r\\]|\\.|(?:(?:\r\n)?[ \t]))*"(?:(?:\r\n)?[ \t])*)(?:\.(?:( +?:\r\n)?[ \t])*(?:[^()<>@,;:\\".\[\] \000-\031]+(?:(?:(?:\r\n)?[ \t])+|\Z|(?=[ +\["()<>@,;:\\".\[\]]))|"(?:[^\"\r\\]|\\.|(?:(?:\r\n)?[ \t]))*"(?:(?:\r\n)?[ \t +])*))*@(?:(?:\r\n)?[ \t])*(?:[^()<>@,;:\\".\[\] \000-\031]+(?:(?:(?:\r\n)?[ \t +])+|\Z|(?=[\["()<>@,;:\\".\[\]]))|\[([^\[\]\r\\]|\\.)*\](?:(?:\r\n)?[ \t])*)(? +:\.(?:(?:\r\n)?[ \t])*(?:[^()<>@,;:\\".\[\] \000-\031]+(?:(?:(?:\r\n)?[ \t])+| +\Z|(?=[\["()<>@,;:\\".\[\]]))|\[([^\[\]\r\\]|\\.)*\](?:(?:\r\n)?[ \t])*))*|(?: +[^()<>@,;:\\".\[\] \000-\031]+(?:(?:(?:\r\n)?[ \t])+|\Z|(?=[\["()<>@,;:\\".\[\ +]]))|"(?:[^\"\r\\]|\\.|(?:(?:\r\n)?[ \t]))*"(?:(?:\r\n)?[ \t])*)*\<(?:(?:\r\n) +?[ \t])*(?:@(?:[^()<>@,;:\\".\[\] \000-\031]+(?:(?:(?:\r\n)?[ \t])+|\Z|(?=[\[" +()<>@,;:\\".\[\]]))|\[([^\[\]\r\\]|\\.)*\](?:(?:\r\n)?[ \t])*)(?:\.(?:(?:\r\n) +?[ \t])*(?:[^()<>@,;:\\".\[\] \000-\031]+(?:(?:(?:\r\n)?[ \t])+|\Z|(?=[\["()<> +@,;:\\".\[\]]))|\[([^\[\]\r\\]|\\.)*\](?:(?:\r\n)?[ \t])*))*(?:,@(?:(?:\r\n)?[ + \t])*(?:[^()<>@,;:\\".\[\] \000-\031]+(?:(?:(?:\r\n)?[ \t])+|\Z|(?=[\["()<>@, +;:\\".\[\]]))|\[([^\[\]\r\\]|\\.)*\](?:(?:\r\n)?[ \t])*)(?:\.(?:(?:\r\n)?[ \t] +)*(?:[^()<>@,;:\\".\[\] \000-\031]+(?:(?:(?:\r\n)?[ \t])+|\Z|(?=[\["()<>@,;:\\ +".\[\]]))|\[([^\[\]\r\\]|\\.)*\](?:(?:\r\n)?[ \t])*))*)*:(?:(?:\r\n)?[ \t])*)? +(?:[^()<>@,;:\\".\[\] \000-\031]+(?:(?:(?:\r\n)?[ \t])+|\Z|(?=[\["()<>@,;:\\". +\[\]]))|"(?:[^\"\r\\]|\\.|(?:(?:\r\n)?[ \t]))*"(?:(?:\r\n)?[ \t])*)(?:\.(?:(?: +\r\n)?[ \t])*(?:[^()<>@,;:\\".\[\] \000-\031]+(?:(?:(?:\r\n)?[ \t])+|\Z|(?=[\[ +"()<>@,;:\\".\[\]]))|"(?:[^\"\r\\]|\\.|(?:(?:\r\n)?[ \t]))*"(?:(?:\r\n)?[ \t]) +*))*@(?:(?:\r\n)?[ \t])*(?:[^()<>@,;:\\".\[\] \000-\031]+(?:(?:(?:\r\n)?[ \t]) ++|\Z|(?=[\["()<>@,;:\\".\[\]]))|\[([^\[\]\r\\]|\\.)*\](?:(?:\r\n)?[ \t])*)(?:\ +.(?:(?:\r\n)?[ \t])*(?:[^()<>@,;:\\".\[\] \000-\031]+(?:(?:(?:\r\n)?[ \t])+|\Z +|(?=[\["()<>@,;:\\".\[\]]))|\[([^\[\]\r\\]|\\.)*\](?:(?:\r\n)?[ \t])*))*\>(?:( +?:\r\n)?[ \t])*))*)?;\s*) +``` + +[https://pdw.ex-parrot.com/Mail-RFC822-Address.html](https://pdw.ex-parrot.com/Mail-RFC822-Address.html) + +I hope you had some fun. E-Mail your comments to `paul@nospam.buetow.org` :-) + +other related posts are: + +[Back to the main site](../) diff --git a/gemfeed/index.md b/gemfeed/index.md index d192bfbd..5ddd17d8 100644 --- a/gemfeed/index.md +++ b/gemfeed/index.md @@ -2,6 +2,7 @@ ## To be in the .zone! +[2024-07-05 - Random Weird Things](./2024-07-05-random-weird-things.md) [2024-06-23 - Terminal multiplexing with `tmux`](./2024-06-23-terminal-multiplexing-with-tmux.md) [2024-05-03 - Projects I currently don't have time for](./2024-05-03-projects-i-currently-dont-have-time-for.md) [2024-05-01 - 'Slow Productivity' book notes](./2024-05-01-slow-productivity-book-notes.md) -- cgit v1.2.3 From 1deb2ac65af0bc9cedbe46459d44df8f6f3ce2b6 Mon Sep 17 00:00:00 2001 From: Paul Buetow Date: Sun, 7 Jul 2024 12:47:33 +0300 Subject: Update content for md --- ...23-03-16-the-pragmatic-programmer-book-notes.md | 1 + ...-04-01-never-split-the-difference-book-notes.md | 1 + ...023-05-06-the-obstacle-is-the-way-book-notes.md | 1 + ...7-17-career-guide-and-soft-skills-book-notes.md | 1 + gemfeed/2023-11-11-mind-management-book-notes.md | 1 + gemfeed/2024-05-01-slow-productivity-book-notes.md | 1 + .../2024-07-07-the-stoic-challenge-book-notes.md | 60 ++++++++++++++++++++++ gemfeed/index.md | 1 + 8 files changed, 67 insertions(+) create mode 100644 gemfeed/2024-07-07-the-stoic-challenge-book-notes.md (limited to 'gemfeed') diff --git a/gemfeed/2023-03-16-the-pragmatic-programmer-book-notes.md b/gemfeed/2023-03-16-the-pragmatic-programmer-book-notes.md index b6c5784a..045eb4ee 100644 --- a/gemfeed/2023-03-16-the-pragmatic-programmer-book-notes.md +++ b/gemfeed/2023-03-16-the-pragmatic-programmer-book-notes.md @@ -86,6 +86,7 @@ Other book notes of mine are: [2023-07-17 "Software Developmers Career Guide and Soft Skills" book notes](./2023-07-17-career-guide-and-soft-skills-book-notes.md) [2023-11-11 "Mind Management" book notes](./2023-11-11-mind-management-book-notes.md) [2024-05-01 "Slow Productivity" book notes](./2024-05-01-slow-productivity-book-notes.md) +[2024-07-07 "The Stoic Challenge" book notes](./2024-07-07-the-stoic-challenge-book-notes.md) [More books and other resources I found useful.](../resources.md) [Back to the main site](../) diff --git a/gemfeed/2023-04-01-never-split-the-difference-book-notes.md b/gemfeed/2023-04-01-never-split-the-difference-book-notes.md index 946601fc..171d357b 100644 --- a/gemfeed/2023-04-01-never-split-the-difference-book-notes.md +++ b/gemfeed/2023-04-01-never-split-the-difference-book-notes.md @@ -130,5 +130,6 @@ Other book notes of mine are: [2023-07-17 "Software Developmers Career Guide and Soft Skills" book notes](./2023-07-17-career-guide-and-soft-skills-book-notes.md) [2023-11-11 "Mind Management" book notes](./2023-11-11-mind-management-book-notes.md) [2024-05-01 "Slow Productivity" book notes](./2024-05-01-slow-productivity-book-notes.md) +[2024-07-07 "The Stoic Challenge" book notes](./2024-07-07-the-stoic-challenge-book-notes.md) [Back to the main site](../) diff --git a/gemfeed/2023-05-06-the-obstacle-is-the-way-book-notes.md b/gemfeed/2023-05-06-the-obstacle-is-the-way-book-notes.md index 72bb0233..9c10dc32 100644 --- a/gemfeed/2023-05-06-the-obstacle-is-the-way-book-notes.md +++ b/gemfeed/2023-05-06-the-obstacle-is-the-way-book-notes.md @@ -92,6 +92,7 @@ Other book notes of mine are: [2023-07-17 "Software Developmers Career Guide and Soft Skills" book notes](./2023-07-17-career-guide-and-soft-skills-book-notes.md) [2023-11-11 "Mind Management" book notes](./2023-11-11-mind-management-book-notes.md) [2024-05-01 "Slow Productivity" book notes](./2024-05-01-slow-productivity-book-notes.md) +[2024-07-07 "The Stoic Challenge" book notes](./2024-07-07-the-stoic-challenge-book-notes.md) [More books and other resources I found useful.](../resources.md) [Back to the main site](../) diff --git a/gemfeed/2023-07-17-career-guide-and-soft-skills-book-notes.md b/gemfeed/2023-07-17-career-guide-and-soft-skills-book-notes.md index 6d70da05..cab2e3ff 100644 --- a/gemfeed/2023-07-17-career-guide-and-soft-skills-book-notes.md +++ b/gemfeed/2023-07-17-career-guide-and-soft-skills-book-notes.md @@ -282,6 +282,7 @@ Other book notes of mine are: [2023-07-17 "Software Developmers Career Guide and Soft Skills" book notes (You are currently reading this)](./2023-07-17-career-guide-and-soft-skills-book-notes.md) [2023-11-11 "Mind Management" book notes](./2023-11-11-mind-management-book-notes.md) [2024-05-01 "Slow Productivity" book notes](./2024-05-01-slow-productivity-book-notes.md) +[2024-07-07 "The Stoic Challenge" book notes](./2024-07-07-the-stoic-challenge-book-notes.md) [More books and other resources I found useful.](../resources.md) [Back to the main site](../) diff --git a/gemfeed/2023-11-11-mind-management-book-notes.md b/gemfeed/2023-11-11-mind-management-book-notes.md index bea77974..be1250aa 100644 --- a/gemfeed/2023-11-11-mind-management-book-notes.md +++ b/gemfeed/2023-11-11-mind-management-book-notes.md @@ -101,6 +101,7 @@ Other book notes of mine are: [2023-07-17 "Software Developmers Career Guide and Soft Skills" book notes](./2023-07-17-career-guide-and-soft-skills-book-notes.md) [2023-11-11 "Mind Management" book notes (You are currently reading this)](./2023-11-11-mind-management-book-notes.md) [2024-05-01 "Slow Productivity" book notes](./2024-05-01-slow-productivity-book-notes.md) +[2024-07-07 "The Stoic Challenge" book notes](./2024-07-07-the-stoic-challenge-book-notes.md) [More books and other resources I found useful.](../resources.md) [Back to the main site](../) diff --git a/gemfeed/2024-05-01-slow-productivity-book-notes.md b/gemfeed/2024-05-01-slow-productivity-book-notes.md index d30bd503..0365ca66 100644 --- a/gemfeed/2024-05-01-slow-productivity-book-notes.md +++ b/gemfeed/2024-05-01-slow-productivity-book-notes.md @@ -132,6 +132,7 @@ Other book notes of mine are: [2023-07-17 "Software Developmers Career Guide and Soft Skills" book notes](./2023-07-17-career-guide-and-soft-skills-book-notes.md) [2023-11-11 "Mind Management" book notes](./2023-11-11-mind-management-book-notes.md) [2024-05-01 "Slow Productivity" book notes (You are currently reading this)](./2024-05-01-slow-productivity-book-notes.md) +[2024-07-07 "The Stoic Challenge" book notes](./2024-07-07-the-stoic-challenge-book-notes.md) [More books and other resources I found useful.](../resources.md) [Back to the main site](../) diff --git a/gemfeed/2024-07-07-the-stoic-challenge-book-notes.md b/gemfeed/2024-07-07-the-stoic-challenge-book-notes.md new file mode 100644 index 00000000..1859ebf0 --- /dev/null +++ b/gemfeed/2024-07-07-the-stoic-challenge-book-notes.md @@ -0,0 +1,60 @@ +# "The Stoic Challenge" book notes + +> Published at 2024-07-07T12:46:55+03:00 + +These are my personal takeaways after reading "The Stoic Challenge: A Philosopher's Guide to Becoming Tougher, Calmer, and More Resilient" by William B. Irvine. + +``` + ,.......... .........., + ,..,' '.' ',.., + ,' ,' : ', ', + ,' ,' : ', ', + ,' ,' : ', ', + ,' ,'............., : ,.............', ', +,' '............ '.' ............' ', + '''''''''''''''''';''';'''''''''''''''''' + ''' +``` + +Gods set you up for a challenge to see how resilient you are. Is getting angry worth the price? If you stay calm then you can find the optimal workaround for the obstacle. Stay calm even with big setbacks. Practice minimalism of negative emotions. + +Put a positive spin on everything. What should you do if someone wrong you? Don't get angry, there is no point in that, it just makes you suffer. Do the best what you got now and keep calm and carry on. A resilient person will refuse to play the role of a victim. You can develop the setback response skills. Turn a setback. e.g. a handycap, into a personal triumph. + +It is not the things done to you or happen to you what matters but how you take the things and react to these things. + +Don't row against the other boats but against your own lazy bill. It doesn't matter if you are first or last, as long as you defeat your lazy self. + +Stoics are thankful that they are mortal. As then you can get reminded of how great it is to be alive at all. In dying we are more alive we have ever been as every thing you do could be the last time you do it. Rather than fighting your death you should embrace it if there are no workarounds. Embrace a good death. + +## Negative visualization + +It is easy what we have to take for granted. + +* Imagine the negative and then think that things are actually much better than they seem to be. +* Close your eyes and imagine you are color blind for a minute, then open the eyes again and see all the colours. You will be grateful for being able to see the colours. +* Now close your eyes for a minute and imagine you would be blind, so that you will never be able to experience the world again and let it sink in. When you open your eyes again you will feel a lot of gratefulness. +* Last time meditation. Lets you appreciate the life as it is now. Life gets vitalised again. + +## Oh, nice trick, you stoic "god"! ;-) + +Take setbacks as a challenge. Also take it with some humor. + +* A setback in a setback, how Genius :-) +* A setback in a setback in a setback: the stoic god's work overtime, eh? :-) + +What would the stoic god's do next? This is just a test strategy by them. Don't be frustrated at all but be astonished of what comes next. Thank the stoic gods of testing you. This is comfort zone extension of the stoics aka toughness Training. + +E-Mail your comments to `paul@nospam.buetow.org` :-) + +Other book notes of mine are: + +[2023-03-16 "The Pragmatic Programmer" book notes](./2023-03-16-the-pragmatic-programmer-book-notes.md) +[2023-04-01 "Never split the difference" book notes](./2023-04-01-never-split-the-difference-book-notes.md) +[2023-05-06 "The Obstacle is the Way" book notes](./2023-05-06-the-obstacle-is-the-way-book-notes.md) +[2023-07-17 "Software Developmers Career Guide and Soft Skills" book notes](./2023-07-17-career-guide-and-soft-skills-book-notes.md) +[2023-11-11 "Mind Management" book notes](./2023-11-11-mind-management-book-notes.md) +[2024-05-01 "Slow Productivity" book notes](./2024-05-01-slow-productivity-book-notes.md) +[2024-07-07 "The Stoic Challenge" book notes (You are currently reading this)](./2024-07-07-the-stoic-challenge-book-notes.md) + +[More books and other resources I found useful.](../resources.md) +[Back to the main site](../) diff --git a/gemfeed/index.md b/gemfeed/index.md index 5ddd17d8..5b19eb61 100644 --- a/gemfeed/index.md +++ b/gemfeed/index.md @@ -2,6 +2,7 @@ ## To be in the .zone! +[2024-07-07 - 'The Stoic Challenge' book notes](./2024-07-07-the-stoic-challenge-book-notes.md) [2024-07-05 - Random Weird Things](./2024-07-05-random-weird-things.md) [2024-06-23 - Terminal multiplexing with `tmux`](./2024-06-23-terminal-multiplexing-with-tmux.md) [2024-05-03 - Projects I currently don't have time for](./2024-05-03-projects-i-currently-dont-have-time-for.md) -- cgit v1.2.3 From ceaf027da17c9214199086f90751b05e4e9abbd4 Mon Sep 17 00:00:00 2001 From: Paul Buetow Date: Wed, 24 Jul 2024 22:38:10 +0300 Subject: Update content for md --- ...2008-12-29-using-my-nokia-n95-for-fixing-my-mta.md | 2 +- .../nokia-n95.jpg | Bin 379578 -> 0 bytes ...015-12-05-run-debian-on-your-phone-with-debroid.md | 2 +- .../Deboroid.png | Bin 576510 -> 0 bytes ...01-realistic-load-testing-with-ioriot-for-linux.md | 12 ++++++------ .../figure1-ioriot-io-recording.png | Bin 220247 -> 0 bytes .../figure2-ioriot-test-preparation.png | Bin 208235 -> 0 bytes .../figure3-ioriot-replay.png | Bin 417034 -> 0 bytes .../figure4-ioriot-read-latency.png | Bin 39552 -> 0 bytes .../figure5-ioriot-write-latency.png | Bin 26547 -> 0 bytes .../figure6-iostat.png | Bin 294346 -> 0 bytes ...21-04-22-dtail-the-distributed-log-tail-program.md | 6 +++--- .../dgrep.gif | Bin 142329 -> 0 bytes .../dtail.gif | Bin 1984520 -> 0 bytes .../title.png | Bin 84933 -> 0 bytes gemfeed/2021-04-24-welcome-to-the-geminispace.md | 4 ++-- .../amfora-screenshot.png | Bin 154951 -> 0 bytes .../lagrange-screenshot.png | Bin 104677 -> 0 bytes ...-06-05-gemtexter-one-bash-script-to-rule-it-all.md | 2 +- .../blog-engine.jpg | Bin 41291 -> 0 bytes gemfeed/2021-07-04-the-well-grounded-rubyist.md | 4 ++-- .../book-backside.jpg | Bin 179996 -> 0 bytes .../book-cover.jpg | Bin 140259 -> 0 bytes gemfeed/2022-05-27-perl-is-still-a-great-choice.md | 4 ++-- .../googletrendsperl.jpg | Bin 18537 -> 0 bytes .../regular_expressions.png | Bin 107151 -> 0 bytes gemfeed/2022-06-15-sweating-the-small-stuff.md | 4 ++-- .../2022-06-15-sweating-the-small-stuff/jsmstrade.png | Bin 13636 -> 0 bytes gemfeed/2022-06-15-sweating-the-small-stuff/ninja.jpg | Bin 302772 -> 0 bytes .../2022-12-24-ultrarelearning-java-my-takeaways.md | 4 ++-- .../effective-java.jpg | Bin 187342 -> 0 bytes .../learnjava.jpg | Bin 69628 -> 0 bytes .../2023-06-01-kiss-server-monitoring-with-gogios.md | 2 +- .../gogios-small.png | Bin 56698 -> 0 bytes gemfeed/2023-12-10-bash-golf-part-3.md | 2 +- .../2023-12-10-bash-golf-part-3/bash-fork-bomb.jpg | Bin 209399 -> 0 bytes ...-for-quickly-logging-ideas-programmed-in-golang.md | 4 ++-- .../logo-small.png | Bin 63314 -> 0 bytes .../screenshot-android.png | Bin 45089 -> 0 bytes .../logo-small.png | Bin 0 -> 63314 bytes .../screenshot-android.png | Bin 0 -> 45089 bytes gemfeed/bash-golf-part-3/bash-fork-bomb.jpg | Bin 0 -> 209399 bytes .../dtail-the-distributed-log-tail-program/dgrep.gif | Bin 0 -> 142329 bytes .../dtail-the-distributed-log-tail-program/dtail.gif | Bin 0 -> 1984520 bytes .../dtail-the-distributed-log-tail-program/title.png | Bin 0 -> 84933 bytes .../blog-engine.jpg | Bin 0 -> 41291 bytes .../gogios-small.png | Bin 0 -> 56698 bytes .../perl-is-still-a-great-choice/googletrendsperl.jpg | Bin 0 -> 18537 bytes .../regular_expressions.png | Bin 0 -> 107151 bytes .../figure1-ioriot-io-recording.png | Bin 0 -> 220247 bytes .../figure2-ioriot-test-preparation.png | Bin 0 -> 208235 bytes .../figure3-ioriot-replay.png | Bin 0 -> 417034 bytes .../figure4-ioriot-read-latency.png | Bin 0 -> 39552 bytes .../figure5-ioriot-write-latency.png | Bin 0 -> 26547 bytes .../figure6-iostat.png | Bin 0 -> 294346 bytes .../Deboroid.png | Bin 0 -> 576510 bytes gemfeed/sweating-the-small-stuff/jsmstrade.png | Bin 0 -> 13636 bytes gemfeed/sweating-the-small-stuff/ninja.jpg | Bin 0 -> 302772 bytes gemfeed/the-well-grounded-rubyist/book-backside.jpg | Bin 0 -> 179996 bytes gemfeed/the-well-grounded-rubyist/book-cover.jpg | Bin 0 -> 140259 bytes .../effective-java.jpg | Bin 0 -> 187342 bytes .../ultrarelearning-java-my-takeaways/learnjava.jpg | Bin 0 -> 69628 bytes .../nokia-n95.jpg | Bin 0 -> 379578 bytes .../welcome-to-the-geminispace/amfora-screenshot.png | Bin 0 -> 154951 bytes .../lagrange-screenshot.png | Bin 0 -> 104677 bytes 65 files changed, 26 insertions(+), 26 deletions(-) delete mode 100644 gemfeed/2008-12-29-using-my-nokia-n95-for-fixing-my-mta/nokia-n95.jpg delete mode 100644 gemfeed/2015-12-05-run-debian-on-your-phone-with-debroid/Deboroid.png delete mode 100644 gemfeed/2018-06-01-realistic-load-testing-with-ioriot-for-linux/figure1-ioriot-io-recording.png delete mode 100644 gemfeed/2018-06-01-realistic-load-testing-with-ioriot-for-linux/figure2-ioriot-test-preparation.png delete mode 100644 gemfeed/2018-06-01-realistic-load-testing-with-ioriot-for-linux/figure3-ioriot-replay.png delete mode 100644 gemfeed/2018-06-01-realistic-load-testing-with-ioriot-for-linux/figure4-ioriot-read-latency.png delete mode 100644 gemfeed/2018-06-01-realistic-load-testing-with-ioriot-for-linux/figure5-ioriot-write-latency.png delete mode 100644 gemfeed/2018-06-01-realistic-load-testing-with-ioriot-for-linux/figure6-iostat.png delete mode 100644 gemfeed/2021-04-22-dtail-the-distributed-log-tail-program/dgrep.gif delete mode 100644 gemfeed/2021-04-22-dtail-the-distributed-log-tail-program/dtail.gif delete mode 100644 gemfeed/2021-04-22-dtail-the-distributed-log-tail-program/title.png delete mode 100644 gemfeed/2021-04-24-welcome-to-the-geminispace/amfora-screenshot.png delete mode 100644 gemfeed/2021-04-24-welcome-to-the-geminispace/lagrange-screenshot.png delete mode 100644 gemfeed/2021-06-05-gemtexter-one-bash-script-to-rule-it-all/blog-engine.jpg delete mode 100644 gemfeed/2021-07-04-the-well-grounded-rubyist/book-backside.jpg delete mode 100644 gemfeed/2021-07-04-the-well-grounded-rubyist/book-cover.jpg delete mode 100644 gemfeed/2022-05-27-perl-is-still-a-great-choice/googletrendsperl.jpg delete mode 100644 gemfeed/2022-05-27-perl-is-still-a-great-choice/regular_expressions.png delete mode 100644 gemfeed/2022-06-15-sweating-the-small-stuff/jsmstrade.png delete mode 100644 gemfeed/2022-06-15-sweating-the-small-stuff/ninja.jpg delete mode 100644 gemfeed/2022-12-24-ultrarelearning-java-my-takeaways/effective-java.jpg delete mode 100644 gemfeed/2022-12-24-ultrarelearning-java-my-takeaways/learnjava.jpg delete mode 100644 gemfeed/2023-06-01-kiss-server-monitoring-with-gogios/gogios-small.png delete mode 100644 gemfeed/2023-12-10-bash-golf-part-3/bash-fork-bomb.jpg delete mode 100644 gemfeed/2024-03-03-a-fine-fyne-android-app-for-quickly-logging-ideas-programmed-in-golang/logo-small.png delete mode 100644 gemfeed/2024-03-03-a-fine-fyne-android-app-for-quickly-logging-ideas-programmed-in-golang/screenshot-android.png create mode 100644 gemfeed/a-fine-fyne-android-app-for-quickly-logging-ideas-programmed-in-golang/logo-small.png create mode 100644 gemfeed/a-fine-fyne-android-app-for-quickly-logging-ideas-programmed-in-golang/screenshot-android.png create mode 100644 gemfeed/bash-golf-part-3/bash-fork-bomb.jpg create mode 100644 gemfeed/dtail-the-distributed-log-tail-program/dgrep.gif create mode 100644 gemfeed/dtail-the-distributed-log-tail-program/dtail.gif create mode 100644 gemfeed/dtail-the-distributed-log-tail-program/title.png create mode 100644 gemfeed/gemtexter-one-bash-script-to-rule-it-all/blog-engine.jpg create mode 100644 gemfeed/kiss-server-monitoring-with-gogios/gogios-small.png create mode 100644 gemfeed/perl-is-still-a-great-choice/googletrendsperl.jpg create mode 100644 gemfeed/perl-is-still-a-great-choice/regular_expressions.png create mode 100644 gemfeed/realistic-load-testing-with-ioriot-for-linux/figure1-ioriot-io-recording.png create mode 100644 gemfeed/realistic-load-testing-with-ioriot-for-linux/figure2-ioriot-test-preparation.png create mode 100644 gemfeed/realistic-load-testing-with-ioriot-for-linux/figure3-ioriot-replay.png create mode 100644 gemfeed/realistic-load-testing-with-ioriot-for-linux/figure4-ioriot-read-latency.png create mode 100644 gemfeed/realistic-load-testing-with-ioriot-for-linux/figure5-ioriot-write-latency.png create mode 100644 gemfeed/realistic-load-testing-with-ioriot-for-linux/figure6-iostat.png create mode 100644 gemfeed/run-debian-on-your-phone-with-debroid/Deboroid.png create mode 100644 gemfeed/sweating-the-small-stuff/jsmstrade.png create mode 100644 gemfeed/sweating-the-small-stuff/ninja.jpg create mode 100644 gemfeed/the-well-grounded-rubyist/book-backside.jpg create mode 100644 gemfeed/the-well-grounded-rubyist/book-cover.jpg create mode 100644 gemfeed/ultrarelearning-java-my-takeaways/effective-java.jpg create mode 100644 gemfeed/ultrarelearning-java-my-takeaways/learnjava.jpg create mode 100644 gemfeed/using-my-nokia-n95-for-fixing-my-mta/nokia-n95.jpg create mode 100644 gemfeed/welcome-to-the-geminispace/amfora-screenshot.png create mode 100644 gemfeed/welcome-to-the-geminispace/lagrange-screenshot.png (limited to 'gemfeed') diff --git a/gemfeed/2008-12-29-using-my-nokia-n95-for-fixing-my-mta.md b/gemfeed/2008-12-29-using-my-nokia-n95-for-fixing-my-mta.md index acb2a67e..7f92733b 100644 --- a/gemfeed/2008-12-29-using-my-nokia-n95-for-fixing-my-mta.md +++ b/gemfeed/2008-12-29-using-my-nokia-n95-for-fixing-my-mta.md @@ -23,7 +23,7 @@ The last week I was in Vidin, Bulgaria with no internet access and I had to fix My first attempt to find an internet café, which was working during Christmastime, failed. However, I found with my N95 phone lots of free WLAN hotspots. The hotspots refused me logging into my server using SSH as I have configured a non-standard port for SSH for security reasons. Without knowing the costs, I used the GPRS internet access of my German phone provider (yes, I had to pay roaming fees). -[![Picture of a Nokia N95](./2008-12-29-using-my-nokia-n95-for-fixing-my-mta/nokia-n95.jpg "Picture of a Nokia N95")](./2008-12-29-using-my-nokia-n95-for-fixing-my-mta/nokia-n95.jpg) +[![Picture of a Nokia N95](./using-my-nokia-n95-for-fixing-my-mta/nokia-n95.jpg "Picture of a Nokia N95")](./using-my-nokia-n95-for-fixing-my-mta/nokia-n95.jpg) With Putty for N95 and configuring Postfix with Vim and the T9 input mechanism, I managed to fix the problem. But it took half of an hour: diff --git a/gemfeed/2008-12-29-using-my-nokia-n95-for-fixing-my-mta/nokia-n95.jpg b/gemfeed/2008-12-29-using-my-nokia-n95-for-fixing-my-mta/nokia-n95.jpg deleted file mode 100644 index 6a11be8b..00000000 Binary files a/gemfeed/2008-12-29-using-my-nokia-n95-for-fixing-my-mta/nokia-n95.jpg and /dev/null differ diff --git a/gemfeed/2015-12-05-run-debian-on-your-phone-with-debroid.md b/gemfeed/2015-12-05-run-debian-on-your-phone-with-debroid.md index ccb9113b..fd54242c 100644 --- a/gemfeed/2015-12-05-run-debian-on-your-phone-with-debroid.md +++ b/gemfeed/2015-12-05-run-debian-on-your-phone-with-debroid.md @@ -13,7 +13,7 @@ You can use the following tutorial to install a full-blown Debian GNU/Linux Chroot on an LG G3 D855 CyanogenMod 13 (Android 6). First of all, you need to have root permissions on your phone, and you also need to have the developer mode activated. The following steps have been tested on Linux (Fedora 23). -[![./2015-12-05-run-debian-on-your-phone-with-debroid/Deboroid.png](./2015-12-05-run-debian-on-your-phone-with-debroid/Deboroid.png)](./2015-12-05-run-debian-on-your-phone-with-debroid/Deboroid.png) +[![./run-debian-on-your-phone-with-debroid/Deboroid.png](./run-debian-on-your-phone-with-debroid/Deboroid.png)](./run-debian-on-your-phone-with-debroid/Deboroid.png) ## Foreword diff --git a/gemfeed/2015-12-05-run-debian-on-your-phone-with-debroid/Deboroid.png b/gemfeed/2015-12-05-run-debian-on-your-phone-with-debroid/Deboroid.png deleted file mode 100644 index f76cf226..00000000 Binary files a/gemfeed/2015-12-05-run-debian-on-your-phone-with-debroid/Deboroid.png and /dev/null differ diff --git a/gemfeed/2018-06-01-realistic-load-testing-with-ioriot-for-linux.md b/gemfeed/2018-06-01-realistic-load-testing-with-ioriot-for-linux.md index 4b03f475..3c876f60 100644 --- a/gemfeed/2018-06-01-realistic-load-testing-with-ioriot-for-linux.md +++ b/gemfeed/2018-06-01-realistic-load-testing-with-ioriot-for-linux.md @@ -81,7 +81,7 @@ During recording, ioriot acts as a wrapper and executes all relevant Systemtap c % sudo ioriot -c io.capture ``` -[![Screenshot I/O recording](./2018-06-01-realistic-load-testing-with-ioriot-for-linux/figure1-ioriot-io-recording.png "Screenshot I/O recording")](./2018-06-01-realistic-load-testing-with-ioriot-for-linux/figure1-ioriot-io-recording.png) +[![Screenshot I/O recording](./realistic-load-testing-with-ioriot-for-linux/figure1-ioriot-io-recording.png "Screenshot I/O recording")](./realistic-load-testing-with-ioriot-for-linux/figure1-ioriot-io-recording.png) A Ctrl-C (SIGINT) stops recording prematurely. Otherwise, ioriot terminates itself automatically after 1 hour. Depending on the system load, the output file can grow to several gigabytes. Only metadata is logged, not the read and written data itself. When replaying later, only random data is used. Under certain circumstances, Systemtap may omit some system calls and issue warnings. This is to ensure that Systemtap does not consume too many resources. @@ -105,7 +105,7 @@ The test will most likely want to access existing files. These are files the tes To avoid any damage to the running system, ioreplay only works in special directories. The tool creates a separate subdirectory for each file system mount point (e.g. /, /usr/local, /store/00,...) (here: /.ioriot/TESTNAME, /usr/local/.ioriot/TESTNAME, /store/00/.ioriot/TESTNAME,...). By default, the working directory of ioriot is /usr/local/ioriot/TESTNAME. -[![Screenshot test preparation](./2018-06-01-realistic-load-testing-with-ioriot-for-linux/figure2-ioriot-test-preparation.png "Screenshot test preparation")](./2018-06-01-realistic-load-testing-with-ioriot-for-linux/figure2-ioriot-test-preparation.png) +[![Screenshot test preparation](./realistic-load-testing-with-ioriot-for-linux/figure2-ioriot-test-preparation.png "Screenshot test preparation")](./realistic-load-testing-with-ioriot-for-linux/figure2-ioriot-test-preparation.png) You must re-initialize the environment before each run. Data from previous tests will be moved to a trash directory automatically, which can be finally deleted with "sudo ioriot -P". @@ -115,7 +115,7 @@ After initialization, you can replay the log with -r. You can use -R to initiate You can also influence the playback speed: "-s 0" is interpreted as "Playback as fast as possible" and is the default setting. With "-s 1" all operations are performed at original speed. "-s 2" would double the playback speed and "-s 0.5" would halve it. -[![Screenshot replaying I/O](./2018-06-01-realistic-load-testing-with-ioriot-for-linux/figure3-ioriot-replay.png "Screenshot replaying I/O")](./2018-06-01-realistic-load-testing-with-ioriot-for-linux/figure3-ioriot-replay.png) +[![Screenshot replaying I/O](./realistic-load-testing-with-ioriot-for-linux/figure3-ioriot-replay.png "Screenshot replaying I/O")](./realistic-load-testing-with-ioriot-for-linux/figure3-ioriot-replay.png) As an initial test, for example, you could compare the two Linux I/O schedulers CFQ and Deadline and check which scheduler the test runs the fastest. They run the test separately for each scheduler. The following shell loop iterates through all attached block devices of the system and changes their I/O scheduler to the one specified in variable $new_scheduler (in this case either cfq or deadline). Subsequently, all I/O events from the io.replay protocol are played back. At the end, an output file with statistics is generated: @@ -157,13 +157,13 @@ Total time: 1213.00s In any case, you should also set up a time series database, such as Graphite, where the I/O throughput can be plotted. Figures 4 and 5 show the read and write access times of both tests. The break-in makes it clear when the CFQ test ended and the deadline test was started. The reading latency of both tests is similar. Write latency is dramatically improved using the Deadline Scheduler. -[![Graphite visualization of the mean read access times in ms with CFQ and Deadline Scheduler.](./2018-06-01-realistic-load-testing-with-ioriot-for-linux/figure4-ioriot-read-latency.png "Graphite visualization of the mean read access times in ms with CFQ and Deadline Scheduler.")](./2018-06-01-realistic-load-testing-with-ioriot-for-linux/figure4-ioriot-read-latency.png) +[![Graphite visualization of the mean read access times in ms with CFQ and Deadline Scheduler.](./realistic-load-testing-with-ioriot-for-linux/figure4-ioriot-read-latency.png "Graphite visualization of the mean read access times in ms with CFQ and Deadline Scheduler.")](./realistic-load-testing-with-ioriot-for-linux/figure4-ioriot-read-latency.png) -[![Graphite visualization of the average write access times in ms with CFQ and Deadline Scheduler.](./2018-06-01-realistic-load-testing-with-ioriot-for-linux/figure5-ioriot-write-latency.png "Graphite visualization of the average write access times in ms with CFQ and Deadline Scheduler.")](./2018-06-01-realistic-load-testing-with-ioriot-for-linux/figure5-ioriot-write-latency.png) +[![Graphite visualization of the average write access times in ms with CFQ and Deadline Scheduler.](./realistic-load-testing-with-ioriot-for-linux/figure5-ioriot-write-latency.png "Graphite visualization of the average write access times in ms with CFQ and Deadline Scheduler.")](./realistic-load-testing-with-ioriot-for-linux/figure5-ioriot-write-latency.png) You should also take a look at the iostat tool. The iostat screenshot shows the output of iostat -x 10 during a test run. As you can see, a block device is fully loaded with 99% utilization, while all other block devices still have sufficient buffer. This could be an indication of poor data distribution in the storage system and is worth pursuing. It is not uncommon for I/O Riot to reveal software problems. -[![Output of iostat. The block device sdy seems to be almost fully utilized by 99%.](./2018-06-01-realistic-load-testing-with-ioriot-for-linux/figure6-iostat.png "Output of iostat. The block device sdy seems to be almost fully utilized by 99%.")](./2018-06-01-realistic-load-testing-with-ioriot-for-linux/figure6-iostat.png) +[![Output of iostat. The block device sdy seems to be almost fully utilized by 99%.](./realistic-load-testing-with-ioriot-for-linux/figure6-iostat.png "Output of iostat. The block device sdy seems to be almost fully utilized by 99%.")](./realistic-load-testing-with-ioriot-for-linux/figure6-iostat.png) ## I/O Riot is Open Source diff --git a/gemfeed/2018-06-01-realistic-load-testing-with-ioriot-for-linux/figure1-ioriot-io-recording.png b/gemfeed/2018-06-01-realistic-load-testing-with-ioriot-for-linux/figure1-ioriot-io-recording.png deleted file mode 100644 index 43ac852f..00000000 Binary files a/gemfeed/2018-06-01-realistic-load-testing-with-ioriot-for-linux/figure1-ioriot-io-recording.png and /dev/null differ diff --git a/gemfeed/2018-06-01-realistic-load-testing-with-ioriot-for-linux/figure2-ioriot-test-preparation.png b/gemfeed/2018-06-01-realistic-load-testing-with-ioriot-for-linux/figure2-ioriot-test-preparation.png deleted file mode 100644 index 709d7490..00000000 Binary files a/gemfeed/2018-06-01-realistic-load-testing-with-ioriot-for-linux/figure2-ioriot-test-preparation.png and /dev/null differ diff --git a/gemfeed/2018-06-01-realistic-load-testing-with-ioriot-for-linux/figure3-ioriot-replay.png b/gemfeed/2018-06-01-realistic-load-testing-with-ioriot-for-linux/figure3-ioriot-replay.png deleted file mode 100644 index 3bd66b6f..00000000 Binary files a/gemfeed/2018-06-01-realistic-load-testing-with-ioriot-for-linux/figure3-ioriot-replay.png and /dev/null differ diff --git a/gemfeed/2018-06-01-realistic-load-testing-with-ioriot-for-linux/figure4-ioriot-read-latency.png b/gemfeed/2018-06-01-realistic-load-testing-with-ioriot-for-linux/figure4-ioriot-read-latency.png deleted file mode 100644 index 160b2305..00000000 Binary files a/gemfeed/2018-06-01-realistic-load-testing-with-ioriot-for-linux/figure4-ioriot-read-latency.png and /dev/null differ diff --git a/gemfeed/2018-06-01-realistic-load-testing-with-ioriot-for-linux/figure5-ioriot-write-latency.png b/gemfeed/2018-06-01-realistic-load-testing-with-ioriot-for-linux/figure5-ioriot-write-latency.png deleted file mode 100644 index e30efdbb..00000000 Binary files a/gemfeed/2018-06-01-realistic-load-testing-with-ioriot-for-linux/figure5-ioriot-write-latency.png and /dev/null differ diff --git a/gemfeed/2018-06-01-realistic-load-testing-with-ioriot-for-linux/figure6-iostat.png b/gemfeed/2018-06-01-realistic-load-testing-with-ioriot-for-linux/figure6-iostat.png deleted file mode 100644 index 0d3fc0d8..00000000 Binary files a/gemfeed/2018-06-01-realistic-load-testing-with-ioriot-for-linux/figure6-iostat.png and /dev/null differ diff --git a/gemfeed/2021-04-22-dtail-the-distributed-log-tail-program.md b/gemfeed/2021-04-22-dtail-the-distributed-log-tail-program.md index 8adf5491..ecfdcfd7 100644 --- a/gemfeed/2021-04-22-dtail-the-distributed-log-tail-program.md +++ b/gemfeed/2021-04-22-dtail-the-distributed-log-tail-program.md @@ -2,7 +2,7 @@ > Published at 2021-04-22T19:28:41+01:00; Updated at 2021-04-26 -[![DTail logo image](./2021-04-22-dtail-the-distributed-log-tail-program/title.png "DTail logo image")](./2021-04-22-dtail-the-distributed-log-tail-program/title.png) +[![DTail logo image](./dtail-the-distributed-log-tail-program/title.png "DTail logo image")](./dtail-the-distributed-log-tail-program/title.png) This article first appeared at the Mimecast Engineering Blog but I made it available here in my personal internet site too. @@ -30,7 +30,7 @@ Why not just use a full-blown log management system? There are various Open-Sour DTail does not aim to replace any of the log management tools already available but is rather an additional tool crafted especially for ad-hoc debugging and troubleshooting purposes. DTail is cheap to operate as it does not require any dedicated hardware for log storage as it operates directly on the source of the logs. It means that there is a DTail server installed on all server boxes producing logs. This decentralized comes with the direct advantages that there is no introduced delay because the logs are not shipped to a central log storage device. The reduced complexity also makes it more robust against outages. You won’t be able to troubleshoot your distributed application very well if the log management infrastructure isn’t working either. -[![DTail sample session animated gif](./2021-04-22-dtail-the-distributed-log-tail-program/dtail.gif "DTail sample session animated gif")](./2021-04-22-dtail-the-distributed-log-tail-program/dtail.gif) +[![DTail sample session animated gif](./dtail-the-distributed-log-tail-program/dtail.gif "DTail sample session animated gif")](./dtail-the-distributed-log-tail-program/dtail.gif) As a downside, you won’t be able to access any logs with DTail when the server is down. Furthermore, a server can store logs only up to a certain capacity as disks will fill up. For the purpose of ad-hoc debugging, these are not typically issues. Usually, it’s the application you want to debug and not the server. And disk space is rarely an issue for bare metal and VM-based systems these days, with sufficient space for several weeks’ worth of log storage being available. DTail also supports reading compressed logs. The currently supported compression algorithms are gzip and zstd. @@ -54,7 +54,7 @@ Following the UNIX philosophy, DTail includes multiple command-line commands eac * dgrep: The distributed grep client for searching text files for a regular expression pattern. * dmap: The distributed map-reduce client for aggregating stats from log files. -[![DGrep sample session animated gif](./2021-04-22-dtail-the-distributed-log-tail-program/dgrep.gif "DGrep sample session animated gif")](./2021-04-22-dtail-the-distributed-log-tail-program/dgrep.gif) +[![DGrep sample session animated gif](./dtail-the-distributed-log-tail-program/dgrep.gif "DGrep sample session animated gif")](./dtail-the-distributed-log-tail-program/dgrep.gif) ## Usage example diff --git a/gemfeed/2021-04-22-dtail-the-distributed-log-tail-program/dgrep.gif b/gemfeed/2021-04-22-dtail-the-distributed-log-tail-program/dgrep.gif deleted file mode 100644 index e2f2ac64..00000000 Binary files a/gemfeed/2021-04-22-dtail-the-distributed-log-tail-program/dgrep.gif and /dev/null differ diff --git a/gemfeed/2021-04-22-dtail-the-distributed-log-tail-program/dtail.gif b/gemfeed/2021-04-22-dtail-the-distributed-log-tail-program/dtail.gif deleted file mode 100644 index 8f6b56bf..00000000 Binary files a/gemfeed/2021-04-22-dtail-the-distributed-log-tail-program/dtail.gif and /dev/null differ diff --git a/gemfeed/2021-04-22-dtail-the-distributed-log-tail-program/title.png b/gemfeed/2021-04-22-dtail-the-distributed-log-tail-program/title.png deleted file mode 100644 index 4e343c4f..00000000 Binary files a/gemfeed/2021-04-22-dtail-the-distributed-log-tail-program/title.png and /dev/null differ diff --git a/gemfeed/2021-04-24-welcome-to-the-geminispace.md b/gemfeed/2021-04-24-welcome-to-the-geminispace.md index a7231f44..e8443ea3 100644 --- a/gemfeed/2021-04-24-welcome-to-the-geminispace.md +++ b/gemfeed/2021-04-24-welcome-to-the-geminispace.md @@ -48,8 +48,8 @@ Around the same time, I discovered a relatively new, more lightweight protocol n The "downside" is that due to the limited capabilities of the Gemini protocol, all sites look very old and spartan. But that is not a downside; that is, in fact, a design choice people made. It is up to the client software how your capsule looks. For example, you could use a graphical client, such as Lagrange, with nice font renderings and colours to improve the appearance. Or you could use a very minimalistic command line black-and-white Gemini client. It's your (the user's) choice. -[![Screenshot Amfora Gemini terminal client surfing this site](./2021-04-24-welcome-to-the-geminispace/amfora-screenshot.png "Screenshot Amfora Gemini terminal client surfing this site")](./2021-04-24-welcome-to-the-geminispace/amfora-screenshot.png) -[![Screenshot graphical Lagrange Gemini client surfing this site](./2021-04-24-welcome-to-the-geminispace/lagrange-screenshot.png "Screenshot graphical Lagrange Gemini client surfing this site")](./2021-04-24-welcome-to-the-geminispace/lagrange-screenshot.png) +[![Screenshot Amfora Gemini terminal client surfing this site](./welcome-to-the-geminispace/amfora-screenshot.png "Screenshot Amfora Gemini terminal client surfing this site")](./welcome-to-the-geminispace/amfora-screenshot.png) +[![Screenshot graphical Lagrange Gemini client surfing this site](./welcome-to-the-geminispace/lagrange-screenshot.png "Screenshot graphical Lagrange Gemini client surfing this site")](./welcome-to-the-geminispace/lagrange-screenshot.png) Why is there a need for a new protocol? As the modern web is a superset of Gemini, can't we use simple HTML 1.0 instead? That's a good and valid question. It is not a technical problem but a human problem. We tend to abuse the features once they are available. You can ensure that things stay efficient and straightforward as long as you are using the Gemini protocol. On the other hand, you can't force every website on the modern web to only create plain and straightforward-looking HTML pages. diff --git a/gemfeed/2021-04-24-welcome-to-the-geminispace/amfora-screenshot.png b/gemfeed/2021-04-24-welcome-to-the-geminispace/amfora-screenshot.png deleted file mode 100644 index 093aec79..00000000 Binary files a/gemfeed/2021-04-24-welcome-to-the-geminispace/amfora-screenshot.png and /dev/null differ diff --git a/gemfeed/2021-04-24-welcome-to-the-geminispace/lagrange-screenshot.png b/gemfeed/2021-04-24-welcome-to-the-geminispace/lagrange-screenshot.png deleted file mode 100644 index 478d2fdd..00000000 Binary files a/gemfeed/2021-04-24-welcome-to-the-geminispace/lagrange-screenshot.png and /dev/null differ diff --git a/gemfeed/2021-06-05-gemtexter-one-bash-script-to-rule-it-all.md b/gemfeed/2021-06-05-gemtexter-one-bash-script-to-rule-it-all.md index 41b23f71..86878339 100644 --- a/gemfeed/2021-06-05-gemtexter-one-bash-script-to-rule-it-all.md +++ b/gemfeed/2021-06-05-gemtexter-one-bash-script-to-rule-it-all.md @@ -51,7 +51,7 @@ This comes with the benefit that I can write content in my favourite text editor Another benefit of using Gemini is that the Gemtext markup language is easy to parse. As my site is dual-hosted (Gemini+HTTP), I could, in theory, just write a shell script to deal with the conversion from Gemtext to HTML; there is no need for a full-featured programming language here. I have done a lot of Bash in the past, but I am also often revisiting old tools and techniques for refreshing and keeping the knowledge up to date here. -[![Motivational comic strip](./2021-06-05-gemtexter-one-bash-script-to-rule-it-all/blog-engine.jpg "Motivational comic strip")](./2021-06-05-gemtexter-one-bash-script-to-rule-it-all/blog-engine.jpg) +[![Motivational comic strip](./gemtexter-one-bash-script-to-rule-it-all/blog-engine.jpg "Motivational comic strip")](./gemtexter-one-bash-script-to-rule-it-all/blog-engine.jpg) I have exactly done that - I wrote a Bash script, named Gemtexter, for that: diff --git a/gemfeed/2021-06-05-gemtexter-one-bash-script-to-rule-it-all/blog-engine.jpg b/gemfeed/2021-06-05-gemtexter-one-bash-script-to-rule-it-all/blog-engine.jpg deleted file mode 100644 index 844bc9fc..00000000 Binary files a/gemfeed/2021-06-05-gemtexter-one-bash-script-to-rule-it-all/blog-engine.jpg and /dev/null differ diff --git a/gemfeed/2021-07-04-the-well-grounded-rubyist.md b/gemfeed/2021-07-04-the-well-grounded-rubyist.md index 290b6518..0e2b2def 100644 --- a/gemfeed/2021-07-04-the-well-grounded-rubyist.md +++ b/gemfeed/2021-07-04-the-well-grounded-rubyist.md @@ -6,11 +6,11 @@ When I was a Linux System Administrator, I have been programming in Perl for yea You should learn or try out one new programming language once yearly anyway. If you end up not using the new language, that's not a problem. You will learn new techniques with each new programming language and this also helps you to improve your overall programming skills even for other languages. Also, having some background in a similar programming language makes it reasonably easy to get started. Besides that, learning a new programming language is kick-a** fun! -[![./2021-07-04-the-well-grounded-rubyist/book-cover.jpg](./2021-07-04-the-well-grounded-rubyist/book-cover.jpg)](./2021-07-04-the-well-grounded-rubyist/book-cover.jpg) +[![./the-well-grounded-rubyist/book-cover.jpg](./the-well-grounded-rubyist/book-cover.jpg)](./the-well-grounded-rubyist/book-cover.jpg) Superficially, Perl seems to have many similarities to Ruby (but, of course, it is entirely different to Perl when you look closer), which pushed me towards Ruby instead of Python. I have tried Python a couple of times before, and I managed to write good code, but I never felt satisfied with the language. I didn't love the syntax, especially the indentations used; they always confused me. I don't dislike Python, but I don't prefer to program in it if I have a choice, especially when there are more propelling alternatives available. Personally, it's so much more fun to program in Ruby than in Python. -[![./2021-07-04-the-well-grounded-rubyist/book-backside.jpg](./2021-07-04-the-well-grounded-rubyist/book-backside.jpg)](./2021-07-04-the-well-grounded-rubyist/book-backside.jpg) +[![./the-well-grounded-rubyist/book-backside.jpg](./the-well-grounded-rubyist/book-backside.jpg)](./the-well-grounded-rubyist/book-backside.jpg) Yukihiro Matsumoto, the inventor of Ruby, said: "I wanted a scripting language that was more powerful than Perl and more object-oriented than Python" - So I can see where some of the similarities come from. I personally don't believe that Ruby is more powerful than Perl, though, especially when you take CPAN and/or Perl 6 (now known as Raku) into the equation. Well, it all depends on what you mean with "more powerful". But I want to stay pragmatic and use what's already used at my workplace. diff --git a/gemfeed/2021-07-04-the-well-grounded-rubyist/book-backside.jpg b/gemfeed/2021-07-04-the-well-grounded-rubyist/book-backside.jpg deleted file mode 100644 index 2190e679..00000000 Binary files a/gemfeed/2021-07-04-the-well-grounded-rubyist/book-backside.jpg and /dev/null differ diff --git a/gemfeed/2021-07-04-the-well-grounded-rubyist/book-cover.jpg b/gemfeed/2021-07-04-the-well-grounded-rubyist/book-cover.jpg deleted file mode 100644 index b5a00063..00000000 Binary files a/gemfeed/2021-07-04-the-well-grounded-rubyist/book-cover.jpg and /dev/null differ diff --git a/gemfeed/2022-05-27-perl-is-still-a-great-choice.md b/gemfeed/2022-05-27-perl-is-still-a-great-choice.md index 4462b862..e56858e6 100644 --- a/gemfeed/2022-05-27-perl-is-still-a-great-choice.md +++ b/gemfeed/2022-05-27-perl-is-still-a-great-choice.md @@ -2,13 +2,13 @@ > Published at 2022-05-27T07:50:12+01:00; Updated at 2023-01-28 -[![Comic source: XKCD](./2022-05-27-perl-is-still-a-great-choice/regular_expressions.png "Comic source: XKCD")](./2022-05-27-perl-is-still-a-great-choice/regular_expressions.png) +[![Comic source: XKCD](./perl-is-still-a-great-choice/regular_expressions.png "Comic source: XKCD")](./perl-is-still-a-great-choice/regular_expressions.png) Perl (the Practical Extraction and Report Language) is a battle-tested, mature, multi-paradigm dynamic programming language. Note that it's not called PERL, neither P.E.R.L. nor Pearl. "Perl" is the name of the language and `perl` the name of the interpreter or the interpreter command. Unfortunately (it makes me sad), Perl's popularity has been declining over the last years as Google trends shows: -[![./2022-05-27-perl-is-still-a-great-choice/googletrendsperl.jpg](./2022-05-27-perl-is-still-a-great-choice/googletrendsperl.jpg)](./2022-05-27-perl-is-still-a-great-choice/googletrendsperl.jpg) +[![./perl-is-still-a-great-choice/googletrendsperl.jpg](./perl-is-still-a-great-choice/googletrendsperl.jpg)](./perl-is-still-a-great-choice/googletrendsperl.jpg) So why is that? Once the de-facto standard super-glue language for the web nowadays seems to have a bad reputation. Often, people state: diff --git a/gemfeed/2022-05-27-perl-is-still-a-great-choice/googletrendsperl.jpg b/gemfeed/2022-05-27-perl-is-still-a-great-choice/googletrendsperl.jpg deleted file mode 100644 index 397c9f29..00000000 Binary files a/gemfeed/2022-05-27-perl-is-still-a-great-choice/googletrendsperl.jpg and /dev/null differ diff --git a/gemfeed/2022-05-27-perl-is-still-a-great-choice/regular_expressions.png b/gemfeed/2022-05-27-perl-is-still-a-great-choice/regular_expressions.png deleted file mode 100644 index acbc2437..00000000 Binary files a/gemfeed/2022-05-27-perl-is-still-a-great-choice/regular_expressions.png and /dev/null differ diff --git a/gemfeed/2022-06-15-sweating-the-small-stuff.md b/gemfeed/2022-06-15-sweating-the-small-stuff.md index bf4b2549..cbc0311f 100644 --- a/gemfeed/2022-06-15-sweating-the-small-stuff.md +++ b/gemfeed/2022-06-15-sweating-the-small-stuff.md @@ -47,7 +47,7 @@ But now, let's continue with the small projects worth mentioning :-) Photography is one of my casual hobbies. I love to capture interesting perspectives and motifs. I love to walk new streets and neighbourhoods I never walked before so I can capture those unexpected motifs, colours and moments. Unfortunately, because of time constraints (and sometime weather constraints), I do that on a pretty infrequent basis. -[![./2022-06-15-sweating-the-small-stuff/ninja.jpg](./2022-06-15-sweating-the-small-stuff/ninja.jpg)](./2022-06-15-sweating-the-small-stuff/ninja.jpg) +[![./sweating-the-small-stuff/ninja.jpg](./sweating-the-small-stuff/ninja.jpg)](./sweating-the-small-stuff/ninja.jpg) More than 10 years ago I wrote the bespoke small static photo album generator in Bash `photoalbum.sh` which I recently refactored to a modern Bash coding style and also freshened up the Cascading Style Sheets. Last but not least, the new domain name `irregular.ninja` has been registered. @@ -229,7 +229,7 @@ This is a shell script for the Mutt email client for delaying sending out E-Mail `jsmstrade` is a minimalistic graphical Java swing client for sending SMS messages over the SMStrade service. -[![./2022-06-15-sweating-the-small-stuff/jsmstrade.png](./2022-06-15-sweating-the-small-stuff/jsmstrade.png)](./2022-06-15-sweating-the-small-stuff/jsmstrade.png) +[![./sweating-the-small-stuff/jsmstrade.png](./sweating-the-small-stuff/jsmstrade.png)](./sweating-the-small-stuff/jsmstrade.png) [https://codeberg.org/snonux/jsmstrade](https://codeberg.org/snonux/jsmstrade) [https://smstrade.de](https://smstrade.de) diff --git a/gemfeed/2022-06-15-sweating-the-small-stuff/jsmstrade.png b/gemfeed/2022-06-15-sweating-the-small-stuff/jsmstrade.png deleted file mode 100644 index ce5276f8..00000000 Binary files a/gemfeed/2022-06-15-sweating-the-small-stuff/jsmstrade.png and /dev/null differ diff --git a/gemfeed/2022-06-15-sweating-the-small-stuff/ninja.jpg b/gemfeed/2022-06-15-sweating-the-small-stuff/ninja.jpg deleted file mode 100644 index 8a036323..00000000 Binary files a/gemfeed/2022-06-15-sweating-the-small-stuff/ninja.jpg and /dev/null differ diff --git a/gemfeed/2022-12-24-ultrarelearning-java-my-takeaways.md b/gemfeed/2022-12-24-ultrarelearning-java-my-takeaways.md index 220401a4..90f57d05 100644 --- a/gemfeed/2022-12-24-ultrarelearning-java-my-takeaways.md +++ b/gemfeed/2022-12-24-ultrarelearning-java-my-takeaways.md @@ -2,7 +2,7 @@ > Published at 2022-12-24T23:18:40+02:00 -[![./2022-12-24-ultrarelearning-java-my-takeaways/learnjava.jpg](./2022-12-24-ultrarelearning-java-my-takeaways/learnjava.jpg)](./2022-12-24-ultrarelearning-java-my-takeaways/learnjava.jpg) +[![./ultrarelearning-java-my-takeaways/learnjava.jpg](./ultrarelearning-java-my-takeaways/learnjava.jpg)](./ultrarelearning-java-my-takeaways/learnjava.jpg) As a regular participant in the annual Pet Project competition at work, I always try to find a project where I can learn something new. In this post, I would like to share my takeaways after revisiting Java. You can read about my motivations in my "Creative universe" post: @@ -26,7 +26,7 @@ Over time, I had been missing out on many new features that were added to the la This book was recommended by my brother and also by at least another colleague at work to be one of the best, if not the best, book about Java programming. I read the whole book from the beginning to the end and immersed myself in it. I fully agree; this is a great book. Every Java developer or Java software engineer should read it! -[![./2022-12-24-ultrarelearning-java-my-takeaways/effective-java.jpg](./2022-12-24-ultrarelearning-java-my-takeaways/effective-java.jpg)](./2022-12-24-ultrarelearning-java-my-takeaways/effective-java.jpg) +[![./ultrarelearning-java-my-takeaways/effective-java.jpg](./ultrarelearning-java-my-takeaways/effective-java.jpg)](./ultrarelearning-java-my-takeaways/effective-java.jpg) I recommend reading the 90-part effective Java Series on `dev.to`. It's a perfect companion to the book as it explains all the chapters again but from a slightly different perspective and helps you to really understand the content. diff --git a/gemfeed/2022-12-24-ultrarelearning-java-my-takeaways/effective-java.jpg b/gemfeed/2022-12-24-ultrarelearning-java-my-takeaways/effective-java.jpg deleted file mode 100644 index 213c6e03..00000000 Binary files a/gemfeed/2022-12-24-ultrarelearning-java-my-takeaways/effective-java.jpg and /dev/null differ diff --git a/gemfeed/2022-12-24-ultrarelearning-java-my-takeaways/learnjava.jpg b/gemfeed/2022-12-24-ultrarelearning-java-my-takeaways/learnjava.jpg deleted file mode 100644 index 4c3b9e7b..00000000 Binary files a/gemfeed/2022-12-24-ultrarelearning-java-my-takeaways/learnjava.jpg and /dev/null differ diff --git a/gemfeed/2023-06-01-kiss-server-monitoring-with-gogios.md b/gemfeed/2023-06-01-kiss-server-monitoring-with-gogios.md index 981a63a8..a9a6393b 100644 --- a/gemfeed/2023-06-01-kiss-server-monitoring-with-gogios.md +++ b/gemfeed/2023-06-01-kiss-server-monitoring-with-gogios.md @@ -2,7 +2,7 @@ > Published at 2023-06-01T21:10:17+03:00 -[![Gogios logo](./2023-06-01-kiss-server-monitoring-with-gogios/gogios-small.png "Gogios logo")](./2023-06-01-kiss-server-monitoring-with-gogios/gogios-small.png) +[![Gogios logo](./kiss-server-monitoring-with-gogios/gogios-small.png "Gogios logo")](./kiss-server-monitoring-with-gogios/gogios-small.png) ## Introduction diff --git a/gemfeed/2023-06-01-kiss-server-monitoring-with-gogios/gogios-small.png b/gemfeed/2023-06-01-kiss-server-monitoring-with-gogios/gogios-small.png deleted file mode 100644 index aebe695c..00000000 Binary files a/gemfeed/2023-06-01-kiss-server-monitoring-with-gogios/gogios-small.png and /dev/null differ diff --git a/gemfeed/2023-12-10-bash-golf-part-3.md b/gemfeed/2023-12-10-bash-golf-part-3.md index 570793a7..5efbb1e8 100644 --- a/gemfeed/2023-12-10-bash-golf-part-3.md +++ b/gemfeed/2023-12-10-bash-golf-part-3.md @@ -73,7 +73,7 @@ So, it's a fork bomb. If you run it, your computer will run out of resources eve And here is the cute illustration: -[![Bash fork bomb](./2023-12-10-bash-golf-part-3/bash-fork-bomb.jpg "Bash fork bomb")](./2023-12-10-bash-golf-part-3/bash-fork-bomb.jpg) +[![Bash fork bomb](./bash-golf-part-3/bash-fork-bomb.jpg "Bash fork bomb")](./bash-golf-part-3/bash-fork-bomb.jpg) ## Inner functions diff --git a/gemfeed/2023-12-10-bash-golf-part-3/bash-fork-bomb.jpg b/gemfeed/2023-12-10-bash-golf-part-3/bash-fork-bomb.jpg deleted file mode 100644 index 6967c03a..00000000 Binary files a/gemfeed/2023-12-10-bash-golf-part-3/bash-fork-bomb.jpg and /dev/null differ diff --git a/gemfeed/2024-03-03-a-fine-fyne-android-app-for-quickly-logging-ideas-programmed-in-golang.md b/gemfeed/2024-03-03-a-fine-fyne-android-app-for-quickly-logging-ideas-programmed-in-golang.md index 5665b5e9..9da20108 100644 --- a/gemfeed/2024-03-03-a-fine-fyne-android-app-for-quickly-logging-ideas-programmed-in-golang.md +++ b/gemfeed/2024-03-03-a-fine-fyne-android-app-for-quickly-logging-ideas-programmed-in-golang.md @@ -6,7 +6,7 @@ I am an ideas person. I find myself frequently somewhere on the streets with an I have tried many note apps for my Android (I use GrapheneOS) phone. Most of them either don't do what I want, are proprietary software, require Google Play services (I have the main profile on my phone de-googled) or are too bloated. I was never into mobile app development, as I'm not too fond of the complexity of the developer toolchains. I don't want to use Android Studio (as a NeoVim user), and I don't want to use Java or Kotlin. I want to use a language I know (and like) for mobile app development. Go would be one of those languages. -[![Quick logger Logo](2024-03-03-a-fine-fyne-android-app-for-quickly-logging-ideas-programmed-in-golang/logo-small.png "Quick logger Logo")](2024-03-03-a-fine-fyne-android-app-for-quickly-logging-ideas-programmed-in-golang/logo-small.png) +[![Quick logger Logo](a-fine-fyne-android-app-for-quickly-logging-ideas-programmed-in-golang/logo-small.png "Quick logger Logo")](a-fine-fyne-android-app-for-quickly-logging-ideas-programmed-in-golang/logo-small.png) Enter Quick logger – a compact GUI Android (well, cross-platform due to Fyne) app I've crafted using Go and the nifty Fyne framework. With Fyne, the app can be compiled easily into an Android APK. As of this writing, this app's whole Go source code is only 75 lines short!! This little tool is designed for spontaneous moments, allowing me to quickly log my thoughts as plain text files on my Android phone. There are no fancy file formats. Just plain text! @@ -26,7 +26,7 @@ Quick logger's user interface is as minimal as it gets. When I launch Quick logg For the code-savvy folks out there, Quick logger is a neat example of what you can achieve with Go and Fyne. It's a testament to building functional, cross-platform apps without getting bogged down in the nitty-gritty of platform-specific details. Thanks to Fyne, I am pleased with how easy it is to make mobile Android apps in Go. -[![Quick logger running on Android](2024-03-03-a-fine-fyne-android-app-for-quickly-logging-ideas-programmed-in-golang/screenshot-android.png "Quick logger running on Android")](2024-03-03-a-fine-fyne-android-app-for-quickly-logging-ideas-programmed-in-golang/screenshot-android.png) +[![Quick logger running on Android](a-fine-fyne-android-app-for-quickly-logging-ideas-programmed-in-golang/screenshot-android.png "Quick logger running on Android")](a-fine-fyne-android-app-for-quickly-logging-ideas-programmed-in-golang/screenshot-android.png) My Android apps will never be polished, but they will get the job done, and this is precisely how I want them to be. Minimalistic but functional. I could spend more time polishing Quick logger, but my Quick logger app then may be the same as any other notes app out there (complicated or bloated). diff --git a/gemfeed/2024-03-03-a-fine-fyne-android-app-for-quickly-logging-ideas-programmed-in-golang/logo-small.png b/gemfeed/2024-03-03-a-fine-fyne-android-app-for-quickly-logging-ideas-programmed-in-golang/logo-small.png deleted file mode 100644 index dc29011c..00000000 Binary files a/gemfeed/2024-03-03-a-fine-fyne-android-app-for-quickly-logging-ideas-programmed-in-golang/logo-small.png and /dev/null differ diff --git a/gemfeed/2024-03-03-a-fine-fyne-android-app-for-quickly-logging-ideas-programmed-in-golang/screenshot-android.png b/gemfeed/2024-03-03-a-fine-fyne-android-app-for-quickly-logging-ideas-programmed-in-golang/screenshot-android.png deleted file mode 100644 index a8a604e3..00000000 Binary files a/gemfeed/2024-03-03-a-fine-fyne-android-app-for-quickly-logging-ideas-programmed-in-golang/screenshot-android.png and /dev/null differ diff --git a/gemfeed/a-fine-fyne-android-app-for-quickly-logging-ideas-programmed-in-golang/logo-small.png b/gemfeed/a-fine-fyne-android-app-for-quickly-logging-ideas-programmed-in-golang/logo-small.png new file mode 100644 index 00000000..dc29011c Binary files /dev/null and b/gemfeed/a-fine-fyne-android-app-for-quickly-logging-ideas-programmed-in-golang/logo-small.png differ diff --git a/gemfeed/a-fine-fyne-android-app-for-quickly-logging-ideas-programmed-in-golang/screenshot-android.png b/gemfeed/a-fine-fyne-android-app-for-quickly-logging-ideas-programmed-in-golang/screenshot-android.png new file mode 100644 index 00000000..a8a604e3 Binary files /dev/null and b/gemfeed/a-fine-fyne-android-app-for-quickly-logging-ideas-programmed-in-golang/screenshot-android.png differ diff --git a/gemfeed/bash-golf-part-3/bash-fork-bomb.jpg b/gemfeed/bash-golf-part-3/bash-fork-bomb.jpg new file mode 100644 index 00000000..6967c03a Binary files /dev/null and b/gemfeed/bash-golf-part-3/bash-fork-bomb.jpg differ diff --git a/gemfeed/dtail-the-distributed-log-tail-program/dgrep.gif b/gemfeed/dtail-the-distributed-log-tail-program/dgrep.gif new file mode 100644 index 00000000..e2f2ac64 Binary files /dev/null and b/gemfeed/dtail-the-distributed-log-tail-program/dgrep.gif differ diff --git a/gemfeed/dtail-the-distributed-log-tail-program/dtail.gif b/gemfeed/dtail-the-distributed-log-tail-program/dtail.gif new file mode 100644 index 00000000..8f6b56bf Binary files /dev/null and b/gemfeed/dtail-the-distributed-log-tail-program/dtail.gif differ diff --git a/gemfeed/dtail-the-distributed-log-tail-program/title.png b/gemfeed/dtail-the-distributed-log-tail-program/title.png new file mode 100644 index 00000000..4e343c4f Binary files /dev/null and b/gemfeed/dtail-the-distributed-log-tail-program/title.png differ diff --git a/gemfeed/gemtexter-one-bash-script-to-rule-it-all/blog-engine.jpg b/gemfeed/gemtexter-one-bash-script-to-rule-it-all/blog-engine.jpg new file mode 100644 index 00000000..844bc9fc Binary files /dev/null and b/gemfeed/gemtexter-one-bash-script-to-rule-it-all/blog-engine.jpg differ diff --git a/gemfeed/kiss-server-monitoring-with-gogios/gogios-small.png b/gemfeed/kiss-server-monitoring-with-gogios/gogios-small.png new file mode 100644 index 00000000..aebe695c Binary files /dev/null and b/gemfeed/kiss-server-monitoring-with-gogios/gogios-small.png differ diff --git a/gemfeed/perl-is-still-a-great-choice/googletrendsperl.jpg b/gemfeed/perl-is-still-a-great-choice/googletrendsperl.jpg new file mode 100644 index 00000000..397c9f29 Binary files /dev/null and b/gemfeed/perl-is-still-a-great-choice/googletrendsperl.jpg differ diff --git a/gemfeed/perl-is-still-a-great-choice/regular_expressions.png b/gemfeed/perl-is-still-a-great-choice/regular_expressions.png new file mode 100644 index 00000000..acbc2437 Binary files /dev/null and b/gemfeed/perl-is-still-a-great-choice/regular_expressions.png differ diff --git a/gemfeed/realistic-load-testing-with-ioriot-for-linux/figure1-ioriot-io-recording.png b/gemfeed/realistic-load-testing-with-ioriot-for-linux/figure1-ioriot-io-recording.png new file mode 100644 index 00000000..43ac852f Binary files /dev/null and b/gemfeed/realistic-load-testing-with-ioriot-for-linux/figure1-ioriot-io-recording.png differ diff --git a/gemfeed/realistic-load-testing-with-ioriot-for-linux/figure2-ioriot-test-preparation.png b/gemfeed/realistic-load-testing-with-ioriot-for-linux/figure2-ioriot-test-preparation.png new file mode 100644 index 00000000..709d7490 Binary files /dev/null and b/gemfeed/realistic-load-testing-with-ioriot-for-linux/figure2-ioriot-test-preparation.png differ diff --git a/gemfeed/realistic-load-testing-with-ioriot-for-linux/figure3-ioriot-replay.png b/gemfeed/realistic-load-testing-with-ioriot-for-linux/figure3-ioriot-replay.png new file mode 100644 index 00000000..3bd66b6f Binary files /dev/null and b/gemfeed/realistic-load-testing-with-ioriot-for-linux/figure3-ioriot-replay.png differ diff --git a/gemfeed/realistic-load-testing-with-ioriot-for-linux/figure4-ioriot-read-latency.png b/gemfeed/realistic-load-testing-with-ioriot-for-linux/figure4-ioriot-read-latency.png new file mode 100644 index 00000000..160b2305 Binary files /dev/null and b/gemfeed/realistic-load-testing-with-ioriot-for-linux/figure4-ioriot-read-latency.png differ diff --git a/gemfeed/realistic-load-testing-with-ioriot-for-linux/figure5-ioriot-write-latency.png b/gemfeed/realistic-load-testing-with-ioriot-for-linux/figure5-ioriot-write-latency.png new file mode 100644 index 00000000..e30efdbb Binary files /dev/null and b/gemfeed/realistic-load-testing-with-ioriot-for-linux/figure5-ioriot-write-latency.png differ diff --git a/gemfeed/realistic-load-testing-with-ioriot-for-linux/figure6-iostat.png b/gemfeed/realistic-load-testing-with-ioriot-for-linux/figure6-iostat.png new file mode 100644 index 00000000..0d3fc0d8 Binary files /dev/null and b/gemfeed/realistic-load-testing-with-ioriot-for-linux/figure6-iostat.png differ diff --git a/gemfeed/run-debian-on-your-phone-with-debroid/Deboroid.png b/gemfeed/run-debian-on-your-phone-with-debroid/Deboroid.png new file mode 100644 index 00000000..f76cf226 Binary files /dev/null and b/gemfeed/run-debian-on-your-phone-with-debroid/Deboroid.png differ diff --git a/gemfeed/sweating-the-small-stuff/jsmstrade.png b/gemfeed/sweating-the-small-stuff/jsmstrade.png new file mode 100644 index 00000000..ce5276f8 Binary files /dev/null and b/gemfeed/sweating-the-small-stuff/jsmstrade.png differ diff --git a/gemfeed/sweating-the-small-stuff/ninja.jpg b/gemfeed/sweating-the-small-stuff/ninja.jpg new file mode 100644 index 00000000..8a036323 Binary files /dev/null and b/gemfeed/sweating-the-small-stuff/ninja.jpg differ diff --git a/gemfeed/the-well-grounded-rubyist/book-backside.jpg b/gemfeed/the-well-grounded-rubyist/book-backside.jpg new file mode 100644 index 00000000..2190e679 Binary files /dev/null and b/gemfeed/the-well-grounded-rubyist/book-backside.jpg differ diff --git a/gemfeed/the-well-grounded-rubyist/book-cover.jpg b/gemfeed/the-well-grounded-rubyist/book-cover.jpg new file mode 100644 index 00000000..b5a00063 Binary files /dev/null and b/gemfeed/the-well-grounded-rubyist/book-cover.jpg differ diff --git a/gemfeed/ultrarelearning-java-my-takeaways/effective-java.jpg b/gemfeed/ultrarelearning-java-my-takeaways/effective-java.jpg new file mode 100644 index 00000000..213c6e03 Binary files /dev/null and b/gemfeed/ultrarelearning-java-my-takeaways/effective-java.jpg differ diff --git a/gemfeed/ultrarelearning-java-my-takeaways/learnjava.jpg b/gemfeed/ultrarelearning-java-my-takeaways/learnjava.jpg new file mode 100644 index 00000000..4c3b9e7b Binary files /dev/null and b/gemfeed/ultrarelearning-java-my-takeaways/learnjava.jpg differ diff --git a/gemfeed/using-my-nokia-n95-for-fixing-my-mta/nokia-n95.jpg b/gemfeed/using-my-nokia-n95-for-fixing-my-mta/nokia-n95.jpg new file mode 100644 index 00000000..6a11be8b Binary files /dev/null and b/gemfeed/using-my-nokia-n95-for-fixing-my-mta/nokia-n95.jpg differ diff --git a/gemfeed/welcome-to-the-geminispace/amfora-screenshot.png b/gemfeed/welcome-to-the-geminispace/amfora-screenshot.png new file mode 100644 index 00000000..093aec79 Binary files /dev/null and b/gemfeed/welcome-to-the-geminispace/amfora-screenshot.png differ diff --git a/gemfeed/welcome-to-the-geminispace/lagrange-screenshot.png b/gemfeed/welcome-to-the-geminispace/lagrange-screenshot.png new file mode 100644 index 00000000..478d2fdd Binary files /dev/null and b/gemfeed/welcome-to-the-geminispace/lagrange-screenshot.png differ -- cgit v1.2.3 From f7c84abad5c7905c240fbea1cd8e058b2055a594 Mon Sep 17 00:00:00 2001 From: Paul Buetow Date: Mon, 5 Aug 2024 17:48:10 +0300 Subject: Update content for md --- .../2024-08-05-typing-127.1-words-per-minute.md | 197 +++++++++++++++++++++ gemfeed/index.md | 1 + .../all-time-stats.png | Bin 0 -> 39542 bytes gemfeed/typing-127.1-words-per-minute/glove80.jpg | Bin 0 -> 226313 bytes gemfeed/typing-127.1-words-per-minute/kinesis1.jpg | Bin 0 -> 179598 bytes gemfeed/typing-127.1-words-per-minute/kinesis2.jpg | Bin 0 -> 164451 bytes .../typing-speed-over-lessons.png | Bin 0 -> 107464 bytes 7 files changed, 198 insertions(+) create mode 100644 gemfeed/2024-08-05-typing-127.1-words-per-minute.md create mode 100644 gemfeed/typing-127.1-words-per-minute/all-time-stats.png create mode 100644 gemfeed/typing-127.1-words-per-minute/glove80.jpg create mode 100644 gemfeed/typing-127.1-words-per-minute/kinesis1.jpg create mode 100644 gemfeed/typing-127.1-words-per-minute/kinesis2.jpg create mode 100644 gemfeed/typing-127.1-words-per-minute/typing-speed-over-lessons.png (limited to 'gemfeed') diff --git a/gemfeed/2024-08-05-typing-127.1-words-per-minute.md b/gemfeed/2024-08-05-typing-127.1-words-per-minute.md new file mode 100644 index 00000000..779d193d --- /dev/null +++ b/gemfeed/2024-08-05-typing-127.1-words-per-minute.md @@ -0,0 +1,197 @@ +# Typing `127.1` words per minute (`>100wpm average`) + +> Published at 2024-08-05T17:39:30+03:00 + +``` +,---,---,---,---,---,---,---,---,---,---,---,---,---,-------, +|1/2| 1 | 2 | 3 | 4 | 5 | 6 | 7 | 8 | 9 | 0 | + | ' | <- | +|---'-,-'-,-'-,-'-,-'-,-'-,-'-,-'-,-'-,-'-,-'-,-'-,-'-,-----| +| ->| | Q | W | E | R | T | Y | U | I | O | P | ] | ^ | | +|-----',--',--',--',--',--',--',--',--',--',--',--',--'| | +| Caps | A | S | D | F | G | H | J | K | L | \ | [ | * | | +|----,-'-,-'-,-'-,-'-,-'-,-'-,-'-,-'-,-'-,-'-,-'-,-'---'----| +| | < | Z | X | C | V | B | N | M | , | . | - | | +|----'-,-',--'--,'---'---'---'---'---'---'-,-'---',--,------| +| ctrl | | alt | |altgr | | ctrl | +'------' '-----'--------------------------'------' '------' + Nieminen Mika +``` + +After work one day, I noticed some discomfort in my right wrist. Upon research, it appeared to be a mild case of Repetitive Strain Injury (RSI). Initially, I thought that this would go away after a while, but after a week it became even worse. This led me to consider potential causes such as poor posture or keyboard use habits. As an enthusiast of keyboards, I experimented with ergonomic concave ortholinear split keyboards. Wait, what?... + +* Concave: Some fingers are longer than others. A concave keyboard makes it so that the keycaps meant to be pressed by the longer fingers are further down (e.g., left middle finger for `e` on a Qwerty layout), and keycaps meant to be pressed by shorter fingers are further up (e.g., right pinky finger for the letter `p`). +* Ortholinear: The keys are arranged in a straight vertical line, unlike most conventional keyboards. The conventional keyboards still resemble the old typewriters, where the placement of the keys was optimized so that the typewriter would not jam. There is no such requirement anymore. +* Split: The keyboard is split into two halves (left and right), allowing one to place either hand where it is most ergonomic. + +After discovering ThePrimagen (I found him long ago, but I never bothered buying the same Keyboard he is on) on YouTube and reading/watching a couple of reviews, I thought that as a computer professional, the equipment could be expensive anyway (laptop, adjustable desk, comfortable chair), so why not invest a bit more into the Keyboard? I purchased myself the Kinesis Advantage360 Professional keyboard. +## Kinesis review + +For an in-depth review, have a look at this great article: + +[Review of the Kinesis Advantage360 Professional Keyboard](https://arslan.io/2022/10/22/review-of-the-kinesis-advantage360-professional) + +### Top build quality + +Overall, the keyboard feels excellent quality and robust. It has got some weight to it. Because of that, it is not ideally suited for travel, though. But I have a different keyboard to solve this (see later in this post). Overall, I love how it is built and how it feels. + +[![Kinesis Adv.360 Pro at home](./typing-127.1-words-per-minute/kinesis2.jpg "Kinesis Adv.360 Pro at home")](./typing-127.1-words-per-minute/kinesis2.jpg) + +### Bluetooth connectivity + +Despite encountering concerns about Bluetooth connectivity issues with the Kinesis keyboard during my research, I purchased one anyway as I intended to use it only via USB. However, I discovered that the firmware updates available afterwards had addressed these reported Bluetooth issues, and as a result, I did not experience any difficulties with the Bluetooth functionality. This positive outcome allowed me to enjoy using the keyboard also wirelessly. +### Gateron Browm key switches + +Many voices on the internet seem to dislike the Gateron Brown switches, the only official choice for non-clicky tactile switches in the Kinesis, so I was also a bit concerned. I almost went with Cherry MX Browns for my Kinesis (a custom build from a 3rd party provider that is partnershipping with Kinesis). Still, I decided on Gateron Browns to try different switches than the Cherry MX Browns I already have on my ZSA Moonlander keyboard (another ortho-linear split keyboard, but without a concave keycap layout). + +I was disappointed by the Gaterons, as they initially felt a bit meshy compared to the Cherries. Still, over the weeks I grew to prefer them because of their smoothness. Over time, the tactile bumps also became more noticeable (as my perception of them improved). Because of their less pronounced tactile feedback, the Gaterons are less tiring for long typing sessions and better suited for a relaxed typing experience. + +So, the Cherry MX feel sharper but are more tiring in the long run, and the Gaterons are easier to write on and the tactile Feedback is slightly less pronounced. + +### Keycaps + +If you ever purchase a Kinesis keyboard, go with the PCB keycaps. They upgrade the typing experience a lot. The only thing you will lose is that the backlighting won't shine through them. But that is a reasonable tradeoff. When do I need backlighting? I am supposed to look at the screen and not the keyboard while typing. + +I went with the blank keycaps, by the way. + +[![Kinesis Adv.360 Pro at home](./typing-127.1-words-per-minute/kinesis1.jpg "Kinesis Adv.360 Pro at home")](./typing-127.1-words-per-minute/kinesis1.jpg) + +### Keymap editor + +There is no official keymap editor. You have to edit a configuration file manually, build the firmware from scratch, and upload the firmware with the new keymap to both keyboard halves. The Professional version of his keyboard, by the way, runs on the ZMK open-source firmware. + +Many users find the need for an easy-to-use keymap editor an issue. But this is the Pro model. You can also go with the non-Pro, which runs on non-open-source firmware and has no Bluetooth (it must be operated entirely on USB). They should have called it 'Advanced' and not 'Professional'. + +There is a 3rd party solution which is supposed to configure the keymap for the Professional model as bliss, but I have never used it. As a part-time programmer and full-time Site Reliability Engineer, I am okay configuring the keymap in my text editor and building it in a local docker container. This is one of the standard ways of doing it here. You could also use a GitHub pipeline for the firmware build, but I prefer building it locally on my machine. This all seems natural to me, but this may be an issue for others, those job is not to be a programmer. + +## First steps + +I didn't measure the usual words per minute (wpm) on my previous keyboard, the ZSA Moonlander, but I guess that it was around 40-50wp,. Once the Kinesis arrived, I started practising. The experience was quite different due to the concave keycaps, so I barely managed 10wpm on the first day. + +I quickly noticed that I could not continue using the freestyle 6-finger typing system I was used to on my Moonlander or any previous keyboards I worked with. I learned ten-finger touch typing from scratch to be more efficient with the Kinesis keyboard. The keyboard forces you to embrace touch typing. + +Sometimes, there were brain farts, and I couldn't type at all. The trick was not to freak out about it, but to move on. If your average goes down a bit for a day, it doesn't matter; the long-term trend over several days and weeks matters, not the one-off wpm high score. + +Although my wrist pain seemed to go away during the first week of using the Kinesis, my fingers became tired of adjusting to the new way of typing. My hands were stiff, as if I had been training for the Olympics. Only after three weeks did I start to feel comfortable with it. If it weren't for the comments I read online, I would have sent it back after week 2. + +I also had a problem with the left pinky finger, where I could not comfortably reach the `p` key. This involved moving the whole hand. An easy fix was to swap `p` with `;` on the keyboard layout. + +## Considering alternate layouts + +As I was going to learn 10-finger touch typing from scratch, I also played with the thought of switching from the Qwerty to the Dvorak or Colemak keymap, but after reading some comments on the internet, I decided against it: +* These layouts (Dvorak and Colemak) will minimize the finger travel for the most commonly used English words, but they necessarily don't give you a better wpm score. +* One comment on Redit also mentioned that getting stiffer fingers with these layouts is more likely than with Qwerty, as in Qwerty, he had to stretch out his fingers more often, which helps here. +* There are also many applications and websites with keyboard shortcuts and are Qwerty-optimized. +* You won't be able to use someone else's computer as there will be likely Qwerty. Some report that after using an alternative layout for a while, they forget how to use Qwerty. + +## Training how to type + +### Tools + +One of the most influential tools in my touch typing journey has been `keybr.com`. This site/app helped me learn 10-finger touch typing, and I practice daily for 30 minutes (in the first two weeks, up to an hour every day). The key is persistence and focus on technique rather than speed; the latter naturally improves with regular practice. Precision matters, too, so I always correct my errors using the backspace key. + +[https://keybr.com](https://keybr.com) + +I also used a command-line tool called `tt`, which is written in Go. It has a feature that I found very helpful: the ability to practice typing by piping custom text into it. Additionally, I appreciated its customization options, such as choosing a colour theme and specifying how statistics are displayed. + +[https://github.com/lemnos/tt](https://github.com/lemnos/tt) + +I wrote myself a small Ruby script that would randomly select a paragraph from one of my eBooks or book notes and pipe it to `tt`. This helped me remember some of the books I read and also practice touch typing. + +## My `keybr.com` statistics + +Overall, I trained for around 4 months in more than 5,000 sessions. My top speed in a session was 127.1wpm (up from barely 10wpm at the beginning). + +[![./typing-127.1-words-per-minute/all-time-stats.png](./typing-127.1-words-per-minute/all-time-stats.png)](./typing-127.1-words-per-minute/all-time-stats.png) + +My overall average speed over those 5,000 sessions was 80wpm. The average speed over the last week was over 100wpm. The green line represents the wpm average (increasing trend), the purple line represents the number of keys in the practices (not much movement there, as all keys are unlocked), and the red line represents the average typing accuracy. + +[![./typing-127.1-words-per-minute/typing-speed-over-lessons.png](./typing-127.1-words-per-minute/typing-speed-over-lessons.png)](./typing-127.1-words-per-minute/typing-speed-over-lessons.png) + +Around the middle, you see a break-in of the wpm average value. This was where I swapped the `p` and `;` keys, but after some retraining, I came back to the previous level and beyond. + +## Tips and tricks + +These are some tips and tricks I learned along the way to improve my typing speed: + +### Relax + +It's easy to get cramped when trying to hit this new wpm mark, but this is just holding you back. Relax and type at a natural pace. Now I also understand why my Katate Sensei back in London kept screaming "RELAAAX" at me during practice.... It didn't help much back then, though, as it is difficult to relax while someone screams at you! + +### Focus on accuracy first + +This goes with the previous point. Instead of trying to speed through sessions as quickly as possible, slow down and try to type the words correctly—so don't rush it. If you aren't fast yet, the reason is that your brain hasn't trained enough. It will come over time, and you will be faster. + +### Chording + +A trick to getting faster is to type by word and pause between each word so you learn the words by chords. From 80wpm and beyond, this makes a real difference. + +### Punctuation and Capitalization + +I included 10% punctuation and 20% capital letters in my `keybr.com` practice sessions to simulate real typing conditions, which improved my overall working efficiency. I guess I would have gone to 120wpm in average if I didn't include this options... + +### Reverse shifting + +Reverse shifting aka left-right shifting is to is to... + +* ...use the left shift key for letters on the right keyboard side. +* ...use the right shift key for letters on the left keyboard side. + +This makes using the shift key a blaze. + +### Enter the flow state + +Listening to music helps me enter a flow state during practice sessions, which makes typing training a bit addictive (which is good, or isn't it?). + +### Repeat every word + +There's a setting on `keybr.com` that makes it so that every word is always repeated, having you type every word twice in a row. I liked this feature very much, and I think it also helped to improve my practice. + +### Don't use the same finger for two consecutive keystrokes + +Apparently, if you want to type fast, avoid using the same finger for two consecutive keystrokes. This means you don't always need to use the same finger for the same keys. + +However, there are no hard and fast rules. Thus, everyone develops their system for typing word combinations. An exception would be if you are typing the very same letter in a row (e.g., t in letter)—here, you are using the same finger for both ts. + +### Warm-up + +You can't reach your average typing speed first ting the morning. It would help if you warmed up before the exercise or practice later during the day. Also, some days are good, others not so, e.g., after a bad night's sleep. What matters is the mid- and long-term trend, not the fluctuations here, though. + +## Travel keyboard + +As mentioned, the Kinesis is a great keyboard, but it is not meant for travel. + +I guess keyboards will always be my expensive hobby, so I also purchased another ergonomic, ortho-linear, concave split keyboard, the Glove80 (with the Red Pro low-profile switches). This keyboard is much lighter and, in my opinion, much better suited for travel than the Kinesis. It also comes with a great travel case. + +Here is a photo of me using it with my Surface Go 2 (it runs Linux, by the way) while waiting for the baggage drop at the airport: + +[![Traveling with the Glove80 using my Surface Go 2](./typing-127.1-words-per-minute/glove80.jpg "Traveling with the Glove80 using my Surface Go 2")](./typing-127.1-words-per-minute/glove80.jpg) + +For everyday work, I prefer the tactile Browns on the Kinesis over the Red Pro I have on the Glove80 (normal profile vs. low profile). However, the Kinesis feels much more premium. + +The F-key row is odd at the Glove80. I would have preferred more keys on the sides like the Kinesis, and I use them for `[]` `{}` `()`, which is pretty handy there. However, I like the thumb cluster of the Glove80 more than the one on the Kinesis. + +The good thing is that I can switch between both Keyboards instantly without retraining my typing memories. I've configured (as much as possible) the same keymaps on both my Kinesis and Glove80, making it easy to switch between them at any occasion. + +Interested in the Glove80? I suggest also reading this review: + +[Review of the Glove80 Keyboard](https://arslan.io/2024/04/22/review-of-the-moergo-glove80-keyboard/) + +## Upcoming custom Kinesis built + +As I mentioned, Keyboards will remain an expensive hobby of mine. I don't regret anything here, though. After all, I use keyboards at my day job. I've ordered a Kinesis custom build with the Gateron Kangaroo switches, and I'm excited to see how that compares to my current setup. I'm still deciding whether to keep my Gateron Brown-equipped Kinesis as a secondary keyboard or possibly leave it at my in-laws for use when visiting. + +## Conclusion + +When I traveled with the Glove80 for work to the London office, a colleague stared at my keyboard and made jokes that it might be broken (split into two halves). But other than that... + +Ten-finger touch typing has improved my efficiency and has become a rewarding discipline. Whether it's the keyboards I use, the tools I practice with, or the techniques I've adopted, each step has been a learning experience. I hope sharing my journey provides valuable insights and inspiration for anyone looking to improve their touch typing skills. + +I also accidentally started using a 10-finger-like system (maybe still 6 fingers, but better than before) on my regular laptop keyboard. I could be more efficient on the laptop keyboard. The form is different there (not ortholinear, not concave keycaps, etc.), but my typing has improved there too (even if it is only by a little bit). + +I don't want to return to a non-concave keyboard as my default. I will use other keyboards still once in a while but only for short periods or when I have to (e.g. travelling with my Laptop and when there is no space to put an external keyboard) + +Learning to touch type has been an eye-opening experience for me, not just for work but also for personal projects. Now, writing documentation is so much fun; who could believe that? Furthermore, working with Slack (communicating with colleagues) is more fun now as well. + +E-Mail your comments to `paul@nospam.buetow.org` :-) + +[Back to the main site](../) diff --git a/gemfeed/index.md b/gemfeed/index.md index 5b19eb61..54339766 100644 --- a/gemfeed/index.md +++ b/gemfeed/index.md @@ -2,6 +2,7 @@ ## To be in the .zone! +[2024-08-05 - Typing `127.1` words per minute (`>100wpm average`)](./2024-08-05-typing-127.1-words-per-minute.md) [2024-07-07 - 'The Stoic Challenge' book notes](./2024-07-07-the-stoic-challenge-book-notes.md) [2024-07-05 - Random Weird Things](./2024-07-05-random-weird-things.md) [2024-06-23 - Terminal multiplexing with `tmux`](./2024-06-23-terminal-multiplexing-with-tmux.md) diff --git a/gemfeed/typing-127.1-words-per-minute/all-time-stats.png b/gemfeed/typing-127.1-words-per-minute/all-time-stats.png new file mode 100644 index 00000000..4d8a5a8f Binary files /dev/null and b/gemfeed/typing-127.1-words-per-minute/all-time-stats.png differ diff --git a/gemfeed/typing-127.1-words-per-minute/glove80.jpg b/gemfeed/typing-127.1-words-per-minute/glove80.jpg new file mode 100644 index 00000000..80b9c4fb Binary files /dev/null and b/gemfeed/typing-127.1-words-per-minute/glove80.jpg differ diff --git a/gemfeed/typing-127.1-words-per-minute/kinesis1.jpg b/gemfeed/typing-127.1-words-per-minute/kinesis1.jpg new file mode 100644 index 00000000..1edffb84 Binary files /dev/null and b/gemfeed/typing-127.1-words-per-minute/kinesis1.jpg differ diff --git a/gemfeed/typing-127.1-words-per-minute/kinesis2.jpg b/gemfeed/typing-127.1-words-per-minute/kinesis2.jpg new file mode 100644 index 00000000..d6ae665d Binary files /dev/null and b/gemfeed/typing-127.1-words-per-minute/kinesis2.jpg differ diff --git a/gemfeed/typing-127.1-words-per-minute/typing-speed-over-lessons.png b/gemfeed/typing-127.1-words-per-minute/typing-speed-over-lessons.png new file mode 100644 index 00000000..f9f85417 Binary files /dev/null and b/gemfeed/typing-127.1-words-per-minute/typing-speed-over-lessons.png differ -- cgit v1.2.3 From 1852e29665773374a7f901a31a7008d69f2ad7de Mon Sep 17 00:00:00 2001 From: Paul Buetow Date: Mon, 5 Aug 2024 18:02:10 +0300 Subject: Update content for md --- gemfeed/2024-08-05-typing-127.1-words-per-minute.md | 2 ++ 1 file changed, 2 insertions(+) (limited to 'gemfeed') diff --git a/gemfeed/2024-08-05-typing-127.1-words-per-minute.md b/gemfeed/2024-08-05-typing-127.1-words-per-minute.md index 779d193d..17189bad 100644 --- a/gemfeed/2024-08-05-typing-127.1-words-per-minute.md +++ b/gemfeed/2024-08-05-typing-127.1-words-per-minute.md @@ -24,6 +24,7 @@ After work one day, I noticed some discomfort in my right wrist. Upon research, * Split: The keyboard is split into two halves (left and right), allowing one to place either hand where it is most ergonomic. After discovering ThePrimagen (I found him long ago, but I never bothered buying the same Keyboard he is on) on YouTube and reading/watching a couple of reviews, I thought that as a computer professional, the equipment could be expensive anyway (laptop, adjustable desk, comfortable chair), so why not invest a bit more into the Keyboard? I purchased myself the Kinesis Advantage360 Professional keyboard. + ## Kinesis review For an in-depth review, have a look at this great article: @@ -39,6 +40,7 @@ Overall, the keyboard feels excellent quality and robust. It has got some weight ### Bluetooth connectivity Despite encountering concerns about Bluetooth connectivity issues with the Kinesis keyboard during my research, I purchased one anyway as I intended to use it only via USB. However, I discovered that the firmware updates available afterwards had addressed these reported Bluetooth issues, and as a result, I did not experience any difficulties with the Bluetooth functionality. This positive outcome allowed me to enjoy using the keyboard also wirelessly. + ### Gateron Browm key switches Many voices on the internet seem to dislike the Gateron Brown switches, the only official choice for non-clicky tactile switches in the Kinesis, so I was also a bit concerned. I almost went with Cherry MX Browns for my Kinesis (a custom build from a 3rd party provider that is partnershipping with Kinesis). Still, I decided on Gateron Browns to try different switches than the Cherry MX Browns I already have on my ZSA Moonlander keyboard (another ortho-linear split keyboard, but without a concave keycap layout). -- cgit v1.2.3 From 6edd61fe6c0e3edf958a0b8f1bbe873d542bd526 Mon Sep 17 00:00:00 2001 From: Paul Buetow Date: Mon, 5 Aug 2024 18:11:14 +0300 Subject: Update content for md --- gemfeed/2024-08-05-typing-127.1-words-per-minute.md | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) (limited to 'gemfeed') diff --git a/gemfeed/2024-08-05-typing-127.1-words-per-minute.md b/gemfeed/2024-08-05-typing-127.1-words-per-minute.md index 17189bad..28a65ae5 100644 --- a/gemfeed/2024-08-05-typing-127.1-words-per-minute.md +++ b/gemfeed/2024-08-05-typing-127.1-words-per-minute.md @@ -168,7 +168,7 @@ Here is a photo of me using it with my Surface Go 2 (it runs Linux, by the way) [![Traveling with the Glove80 using my Surface Go 2](./typing-127.1-words-per-minute/glove80.jpg "Traveling with the Glove80 using my Surface Go 2")](./typing-127.1-words-per-minute/glove80.jpg) -For everyday work, I prefer the tactile Browns on the Kinesis over the Red Pro I have on the Glove80 (normal profile vs. low profile). However, the Kinesis feels much more premium. +For everyday work, I prefer the tactile Browns on the Kinesis over the Red Pro I have on the Glove80 (normal profile vs. low profile). The Kinesis feels much more premium, whereas the Glove80 is much lighter and easier to store away in a rucksack (the official travel case is a bit bulky, so I wrapped it simply in bubble plastic). The F-key row is odd at the Glove80. I would have preferred more keys on the sides like the Kinesis, and I use them for `[]` `{}` `()`, which is pretty handy there. However, I like the thumb cluster of the Glove80 more than the one on the Kinesis. -- cgit v1.2.3 From 2cbd2c4ec8b59cf1b4bb77c790ed091c5609c19c Mon Sep 17 00:00:00 2001 From: Paul Buetow Date: Mon, 5 Aug 2024 22:08:53 +0300 Subject: Update content for md --- .../2024-08-05-typing-127.1-words-per-minute.md | 27 +++++++++++----------- 1 file changed, 13 insertions(+), 14 deletions(-) (limited to 'gemfeed') diff --git a/gemfeed/2024-08-05-typing-127.1-words-per-minute.md b/gemfeed/2024-08-05-typing-127.1-words-per-minute.md index 28a65ae5..85aca65b 100644 --- a/gemfeed/2024-08-05-typing-127.1-words-per-minute.md +++ b/gemfeed/2024-08-05-typing-127.1-words-per-minute.md @@ -23,13 +23,13 @@ After work one day, I noticed some discomfort in my right wrist. Upon research, * Ortholinear: The keys are arranged in a straight vertical line, unlike most conventional keyboards. The conventional keyboards still resemble the old typewriters, where the placement of the keys was optimized so that the typewriter would not jam. There is no such requirement anymore. * Split: The keyboard is split into two halves (left and right), allowing one to place either hand where it is most ergonomic. -After discovering ThePrimagen (I found him long ago, but I never bothered buying the same Keyboard he is on) on YouTube and reading/watching a couple of reviews, I thought that as a computer professional, the equipment could be expensive anyway (laptop, adjustable desk, comfortable chair), so why not invest a bit more into the Keyboard? I purchased myself the Kinesis Advantage360 Professional keyboard. +After discovering ThePrimagen (I found him long ago, but I never bothered buying the same keyboard he is on) on YouTube and reading/watching a couple of reviews, I thought that as a computer professional, the equipment could be expensive anyway (laptop, adjustable desk, comfortable chair), so why not invest a bit more into the keyboard? I purchased myself the Kinesis Advantage360 Professional keyboard. ## Kinesis review For an in-depth review, have a look at this great article: -[Review of the Kinesis Advantage360 Professional Keyboard](https://arslan.io/2022/10/22/review-of-the-kinesis-advantage360-professional) +[Review of the Kinesis Advantage360 Professional keyboard](https://arslan.io/2022/10/22/review-of-the-kinesis-advantage360-professional) ### Top build quality @@ -45,7 +45,7 @@ Despite encountering concerns about Bluetooth connectivity issues with the Kines Many voices on the internet seem to dislike the Gateron Brown switches, the only official choice for non-clicky tactile switches in the Kinesis, so I was also a bit concerned. I almost went with Cherry MX Browns for my Kinesis (a custom build from a 3rd party provider that is partnershipping with Kinesis). Still, I decided on Gateron Browns to try different switches than the Cherry MX Browns I already have on my ZSA Moonlander keyboard (another ortho-linear split keyboard, but without a concave keycap layout). -I was disappointed by the Gaterons, as they initially felt a bit meshy compared to the Cherries. Still, over the weeks I grew to prefer them because of their smoothness. Over time, the tactile bumps also became more noticeable (as my perception of them improved). Because of their less pronounced tactile feedback, the Gaterons are less tiring for long typing sessions and better suited for a relaxed typing experience. +At first, I was disappointed by the Gaterons, as they initially felt a bit meshy compared to the Cherries. Still, over the weeks I grew to prefer them because of their smoothness. Over time, the tactile bumps also became more noticeable (as my perception of them improved). Because of their less pronounced tactile feedback, the Gaterons are less tiring for long typing sessions and better suited for a relaxed typing experience. So, the Cherry MX feel sharper but are more tiring in the long run, and the Gaterons are easier to write on and the tactile Feedback is slightly less pronounced. @@ -61,25 +61,26 @@ I went with the blank keycaps, by the way. There is no official keymap editor. You have to edit a configuration file manually, build the firmware from scratch, and upload the firmware with the new keymap to both keyboard halves. The Professional version of his keyboard, by the way, runs on the ZMK open-source firmware. -Many users find the need for an easy-to-use keymap editor an issue. But this is the Pro model. You can also go with the non-Pro, which runs on non-open-source firmware and has no Bluetooth (it must be operated entirely on USB). They should have called it 'Advanced' and not 'Professional'. +Many users find the need for an easy-to-use keymap editor an issue. But this is the Pro model. You can also go with the non-Pro, which runs on non-open-source firmware and has no Bluetooth (it must be operated entirely on USB). -There is a 3rd party solution which is supposed to configure the keymap for the Professional model as bliss, but I have never used it. As a part-time programmer and full-time Site Reliability Engineer, I am okay configuring the keymap in my text editor and building it in a local docker container. This is one of the standard ways of doing it here. You could also use a GitHub pipeline for the firmware build, but I prefer building it locally on my machine. This all seems natural to me, but this may be an issue for others, those job is not to be a programmer. +There is a 3rd party solution which is supposed to configure the keymap for the Professional model as bliss, but I have never used it. As a part-time programmer and full-time Site Reliability Engineer, I am okay configuring the keymap in my text editor and building it in a local docker container. This is one of the standard ways of doing it here. You could also use a GitHub pipeline for the firmware build, but I prefer building it locally on my machine. This all seems natural to me, but this may be an issue for "the average Joe" user. ## First steps -I didn't measure the usual words per minute (wpm) on my previous keyboard, the ZSA Moonlander, but I guess that it was around 40-50wp,. Once the Kinesis arrived, I started practising. The experience was quite different due to the concave keycaps, so I barely managed 10wpm on the first day. +I didn't measure the usual words per minute (wpm) on my previous keyboard, the ZSA Moonlander, but I guess that it was around 40-50wpm. Once the Kinesis arrived, I started practising. The experience was quite different due to the concave keycaps, so I barely managed 10wpm on the first day. I quickly noticed that I could not continue using the freestyle 6-finger typing system I was used to on my Moonlander or any previous keyboards I worked with. I learned ten-finger touch typing from scratch to be more efficient with the Kinesis keyboard. The keyboard forces you to embrace touch typing. Sometimes, there were brain farts, and I couldn't type at all. The trick was not to freak out about it, but to move on. If your average goes down a bit for a day, it doesn't matter; the long-term trend over several days and weeks matters, not the one-off wpm high score. -Although my wrist pain seemed to go away during the first week of using the Kinesis, my fingers became tired of adjusting to the new way of typing. My hands were stiff, as if I had been training for the Olympics. Only after three weeks did I start to feel comfortable with it. If it weren't for the comments I read online, I would have sent it back after week 2. +Although my wrist pain seemed to go away aftre the first week of using the Kinesis, my fingers became tired of adjusting to the new way of typing. My hands were stiff, as if I had been training for the Olympics. Only after three weeks did I start to feel comfortable with it. If it weren't for the comments I read online, I would have sent it back after week 2. I also had a problem with the left pinky finger, where I could not comfortably reach the `p` key. This involved moving the whole hand. An easy fix was to swap `p` with `;` on the keyboard layout. ## Considering alternate layouts As I was going to learn 10-finger touch typing from scratch, I also played with the thought of switching from the Qwerty to the Dvorak or Colemak keymap, but after reading some comments on the internet, I decided against it: + * These layouts (Dvorak and Colemak) will minimize the finger travel for the most commonly used English words, but they necessarily don't give you a better wpm score. * One comment on Redit also mentioned that getting stiffer fingers with these layouts is more likely than with Qwerty, as in Qwerty, he had to stretch out his fingers more often, which helps here. * There are also many applications and websites with keyboard shortcuts and are Qwerty-optimized. @@ -118,7 +119,6 @@ These are some tips and tricks I learned along the way to improve my typing spee ### Relax It's easy to get cramped when trying to hit this new wpm mark, but this is just holding you back. Relax and type at a natural pace. Now I also understand why my Katate Sensei back in London kept screaming "RELAAAX" at me during practice.... It didn't help much back then, though, as it is difficult to relax while someone screams at you! - ### Focus on accuracy first This goes with the previous point. Instead of trying to speed through sessions as quickly as possible, slow down and try to type the words correctly—so don't rush it. If you aren't fast yet, the reason is that your brain hasn't trained enough. It will come over time, and you will be faster. @@ -133,7 +133,7 @@ I included 10% punctuation and 20% capital letters in my `keybr.com` practice se ### Reverse shifting -Reverse shifting aka left-right shifting is to is to... +Reverse shifting aka left-right shifting is to... * ...use the left shift key for letters on the right keyboard side. * ...use the right shift key for letters on the left keyboard side. @@ -151,7 +151,6 @@ There's a setting on `keybr.com` that makes it so that every word is always repe ### Don't use the same finger for two consecutive keystrokes Apparently, if you want to type fast, avoid using the same finger for two consecutive keystrokes. This means you don't always need to use the same finger for the same keys. - However, there are no hard and fast rules. Thus, everyone develops their system for typing word combinations. An exception would be if you are typing the very same letter in a row (e.g., t in letter)—here, you are using the same finger for both ts. ### Warm-up @@ -172,15 +171,15 @@ For everyday work, I prefer the tactile Browns on the Kinesis over the Red Pro I The F-key row is odd at the Glove80. I would have preferred more keys on the sides like the Kinesis, and I use them for `[]` `{}` `()`, which is pretty handy there. However, I like the thumb cluster of the Glove80 more than the one on the Kinesis. -The good thing is that I can switch between both Keyboards instantly without retraining my typing memories. I've configured (as much as possible) the same keymaps on both my Kinesis and Glove80, making it easy to switch between them at any occasion. +The good thing is that I can switch between both keyboards instantly without retraining my typing memories. I've configured (as much as possible) the same keymaps on both my Kinesis and Glove80, making it easy to switch between them at any occasion. Interested in the Glove80? I suggest also reading this review: -[Review of the Glove80 Keyboard](https://arslan.io/2024/04/22/review-of-the-moergo-glove80-keyboard/) +[Review of the Glove80 keyboard](https://arslan.io/2024/04/22/review-of-the-moergo-glove80-keyboard/) -## Upcoming custom Kinesis built +## Upcoming custom Kinesis build -As I mentioned, Keyboards will remain an expensive hobby of mine. I don't regret anything here, though. After all, I use keyboards at my day job. I've ordered a Kinesis custom build with the Gateron Kangaroo switches, and I'm excited to see how that compares to my current setup. I'm still deciding whether to keep my Gateron Brown-equipped Kinesis as a secondary keyboard or possibly leave it at my in-laws for use when visiting. +As I mentioned, keyboards will remain an expensive hobby of mine. I don't regret anything here, though. After all, I use keyboards at my day job. I've ordered a Kinesis custom build with the Gateron Kangaroo switches, and I'm excited to see how that compares to my current setup. I'm still deciding whether to keep my Gateron Brown-equipped Kinesis as a secondary keyboard or possibly leave it at my in-laws for use when visiting or to sell it. ## Conclusion -- cgit v1.2.3 From 20f05013c94cf211e01da84d16a5a6a3122e2942 Mon Sep 17 00:00:00 2001 From: Paul Buetow Date: Sun, 18 Aug 2024 18:58:37 +0300 Subject: Update content for md --- gemfeed/2024-08-05-typing-127.1-words-per-minute.md | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) (limited to 'gemfeed') diff --git a/gemfeed/2024-08-05-typing-127.1-words-per-minute.md b/gemfeed/2024-08-05-typing-127.1-words-per-minute.md index 85aca65b..40f2e594 100644 --- a/gemfeed/2024-08-05-typing-127.1-words-per-minute.md +++ b/gemfeed/2024-08-05-typing-127.1-words-per-minute.md @@ -41,7 +41,7 @@ Overall, the keyboard feels excellent quality and robust. It has got some weight Despite encountering concerns about Bluetooth connectivity issues with the Kinesis keyboard during my research, I purchased one anyway as I intended to use it only via USB. However, I discovered that the firmware updates available afterwards had addressed these reported Bluetooth issues, and as a result, I did not experience any difficulties with the Bluetooth functionality. This positive outcome allowed me to enjoy using the keyboard also wirelessly. -### Gateron Browm key switches +### Gateron Brown key switches Many voices on the internet seem to dislike the Gateron Brown switches, the only official choice for non-clicky tactile switches in the Kinesis, so I was also a bit concerned. I almost went with Cherry MX Browns for my Kinesis (a custom build from a 3rd party provider that is partnershipping with Kinesis). Still, I decided on Gateron Browns to try different switches than the Cherry MX Browns I already have on my ZSA Moonlander keyboard (another ortho-linear split keyboard, but without a concave keycap layout). -- cgit v1.2.3 From 408bd2fe1f1566d16f5b380cf4410205170657f9 Mon Sep 17 00:00:00 2001 From: Paul Buetow Date: Sun, 18 Aug 2024 22:23:41 +0300 Subject: Update content for md --- ...23-08-18-site-reliability-engineering-part-1.md | 20 +++++++++--------- ...23-11-19-site-reliability-engineering-part-2.md | 19 ++++++++--------- ...24-01-09-site-reliability-engineering-part-3.md | 24 ++++++++++++---------- gemfeed/index.md | 2 +- 4 files changed, 33 insertions(+), 32 deletions(-) (limited to 'gemfeed') diff --git a/gemfeed/2023-08-18-site-reliability-engineering-part-1.md b/gemfeed/2023-08-18-site-reliability-engineering-part-1.md index 7d1d098c..1c1632ad 100644 --- a/gemfeed/2023-08-18-site-reliability-engineering-part-1.md +++ b/gemfeed/2023-08-18-site-reliability-engineering-part-1.md @@ -2,7 +2,7 @@ > Published at 2023-08-18T22:43:47+03:00 -The universe of Site Reliability Engineering (SRE) is like an intricate tapestry woven with diverse technology, culture, and personal grit threads. Site Reliability Engineering is one of the most demanding jobs. With all the facets, it's impossible to get bored. There is always a new challenge to master, and there is always a new technology to tinker with. It's not just technical; it's also about communication, collaboration and teamwork. I am currently employed as a Site Reliability Engineer and will try to share what SRE is about in this blog series. +Being a Site Reliability Engineer (SRE) is like stepping into a lively, ever-evolving universe. The world of SRE mixes together different tech, a unique culture, and a whole lot of determination. It’s one of the toughest but most exciting jobs out there. There's zero chance of getting bored because there's always a fresh challenge to tackle and new technology to play around with. It's not just about the tech side of things either; it's heavily rooted in communication, collaboration, and teamwork. As someone currently working as an SRE, I’m here to break it all down for you in this blog series. Let's dive into what SRE is really all about! [2023-08-18 Site Reliability Engineering - Part 1: SRE and Organizational Culture (You are currently reading this)](./2023-08-18-site-reliability-engineering-part-1.md) [2023-11-19 Site Reliability Engineering - Part 2: Operational Balance in SRE](./2023-11-19-site-reliability-engineering-part-2.md) @@ -32,23 +32,23 @@ DC on fire: ## SRE and Organizational Culture: Navigating the Nexus -At the heart of SRE lies the proactive mindset of "prevention over cure." Traditional IT models focused predominantly on reactive solutions, but SRE mandates a shift towards foresight. By adopting Service Level Indicators (SLIs) and Service Level Objectives (SLOs), teams are equipped with clear metrics and goals that guide them toward ensuring reliability and user satisfaction. They reflect an organisational culture prioritising user experience and constant system alignment with user needs. +At the core of SRE is the principle of "prevention over cure." Unlike traditional IT setups that mostly react to problems, SRE focuses on spotting issues before they happen. This proactive approach involves using Service Level Indicators (SLIs) and Service Level Objectives (SLOs). These tools give teams specific metrics and targets to aim for, helping them keep systems reliable and users happy. It's all about creating a culture that prioritizes user experience and makes sure everything runs smoothly to meet their needs. -Another defining SRE idea concept the "error budget." This ingenious framework accepts that no system is flawless. Failures are inevitable. However, instead of being punitive, the culture here is to accept, learn, and iterate. By providing teams with a "budget" for errors, organisations create an environment where innovation is encouraged, and failures are viewed as learning opportunities. +Another key concept in SRE is the "error budget." It’s a clever approach that recognizes no system is perfect and that failures will happen. Instead of punishing mistakes, SRE culture embraces them as chances to learn and improve. The idea is to give teams a "budget" for errors, creating a space where innovation can thrive and failures are simply seen as lessons learned. -But SRE isn't just about technology and metrics; it's also human. It challenges the "hero culture" that plagues many IT teams. While individual heroics might occasionally save the day, a sustainable model requires collective expertise. An SRE culture recognises that heroes achieve their best within teams, negating the need for a hero-centric environment. This philosophy promotes a balanced on-call experience, emphasising the importance of trust, ownership, effective communication, and collaboration as cornerstones of team success. I personally have fallen into the hero trap, and know it's unsustainable to be the only go-to person for every arising problem. +SRE isn't just about tech and metrics; it's also about people. It tackles the "hero culture" that often ends up burning out IT teams. Sure, having a hero swoop in to save the day can be great, but relying on that all the time just isn’t sustainable. Instead, SRE focuses on collective expertise and teamwork. It recognizes that heroes are at their best within a solid team, making the need for constant heroics unnecessary. This way of thinking promotes a balanced on-call experience and highlights trust, ownership, good communication, and collaboration as key to success. I've been there myself, falling into the hero trap, and I know firsthand that it's just not feasible to be the go-to person for every problem that comes up. -Additionally, the SRE model requires good documentation. However, it's essential ensuring that this documentation undergoes the same quality checks as code, reinforcing effective onboarding, training and communication. +Also, the SRE model puts a big emphasis on good documentation. It's not enough to just have docs; they need to be top-notch and go through the same quality checks as code. This really helps with onboarding new team members, training, and keeping everyone on the same page. -Organisations might face a significant challenge when adopting SRE. Some might feel SRE principles counter their goals. They might prioritise feature rollouts over reliability or view SRE practices as cumbersome. Hence, creating an SRE culture often demands patient explanations and showcasing benefits, such as increased release velocity and improved user experience. +Adopting SRE can be a big challenge for some organizations. They might think the SRE approach goes against their goals, like preferring to roll out new features quickly rather than focusing on reliability, or seeing SRE practices as too much hassle. Building an SRE culture often means taking the time to explain things patiently and showing the benefits, like faster release cycles and a better user experience. -Monitoring and observability form another SRE aspect, emphasising the need for high-quality tools to query and analyse data. This ties back to the cultural emphasis on continuous learning and adaptability. SREs, by nature, need to be curious, ready to delve into anomalies, and keen on adopting new tools and practices. +Monitoring and observability are also big parts of SRE, highlighting the need for top-notch tools to query and analyze data. This aligns with the SRE focus on continuous learning and being adaptable. SREs naturally need to be curious, ready to dive into any strange issues, and always open to picking up new tools and practices. -The success of SRE within any organisation depends on the broader acceptance of its principles. It demands a move away from siloed operations, where SRE acts as a bandage on flawed systems, to a model where reliability is everyone's responsibility. +For SRE to really work in any organization, everyone needs to buy into its principles. It's about moving away from working in isolated silos and relying on SRE to just patch things up. Instead, it’s about making reliability a shared responsibility across the whole team. -In essence, the integration of SRE principles transcends technical practices. It paves the way for a shift in organisational culture that values proactive prevention, continuous learning, collaboration, and transparent communication. The successful melding of SRE and corporate culture promises not just reliable systems but also a robust, resilient, and progressive work environment. +In short, bringing SRE principles into the mix goes beyond just the technical stuff. It helps shift the whole organizational culture to value things like preventing issues before they happen, always learning, working together, and being open with communication. When SRE and corporate culture blend well, you end up with not just reliable systems but also a strong, resilient, and forward-thinking workplace. -Organisations with the implementation of SLIs, SLOs and error budgets are already advanced in their SRE journey. It takes a lot of communication, convincing, and patience until that point is reached. +Organizations that have SLIs, SLOs, and error budgets in place are already pretty far along in their SRE journey. Getting there takes a lot of communication, convincing people, and patience. Continue with the second part of this series: diff --git a/gemfeed/2023-11-19-site-reliability-engineering-part-2.md b/gemfeed/2023-11-19-site-reliability-engineering-part-2.md index 0db86f50..3fd48c9c 100644 --- a/gemfeed/2023-11-19-site-reliability-engineering-part-2.md +++ b/gemfeed/2023-11-19-site-reliability-engineering-part-2.md @@ -23,23 +23,22 @@ This is the second part of my Site Reliability Engineering (SRE) series. I am cu ⠀⠀⠀⠀⠀⠀⠴⠶⠿⠿⠿⠿⠿⠿⠿⠿⠿⠿⠿⠿⠿⠿⠶⠦⠀⠀ ``` -## Operational Balance in SRE: Finding the Equilibrium in Reliability and Velocity +## Operational Balance in SRE: Striking the Right Balance Between Reliability and Speed -Site Reliability Engineering has established itself as more than just a set of best practices or methodologies. Instead, it stands as a beacon of operational excellence, which guides engineering teams through the turbulent waters of modern software development and system management. +Site Reliability Engineering is more than just a bunch of best practices or methods. It's a guiding light for engineering teams, helping them navigate the tricky waters of modern software development and system management. +In the world of software production, there are two big forces that often clash: the push for fast feature releases (velocity) and the need for reliable systems. Traditionally, moving faster meant more risk. SRE helps balance these opposing goals with things like error budgets and SLIs/SLOs. These tools give teams a clear way to measure how much they can push changes without hurting system health. So, the error budget becomes a balancing act, helping teams trade off between innovation and reliability. -In the universe of software production, two fundamental forces are often at odds: The drive for rapid feature release (velocity) and the need for system reliability. Traditionally, the faster teams moved, the more risk was introduced into systems. SRE offers a approach to mitigate these conflicting drives through concepts like error budgets and SLIs/SLOs. These mechanisms offer a tangible metric, allowing teams to quantify how much they can push changes while ensuring they don't compromise system health. Thus, the error budget becomes a balancing act, where teams weigh the trade-offs between innovation and reliability. +Finding the right balance in SRE means juggling operations and coding. Ideally, engineers should split their time 50/50 between these tasks. This isn't just a random rule; it highlights how much SRE values both maintaining smooth operations and driving innovation. This way, SREs not only handle today's problems but also prepare for tomorrow's challenges. -An important part of this balance is the dichotomy between operations and coding. According to SRE principles, an engineer should ideally spend an equal amount of time on operations work and coding - 50% on each. This isn't just a random metric; it's a reflection of the value SRE places on both maintaining operational excellence and progressing forward with innovations. This balance ensures that while SREs are solving today's problems, they are also preparing for tomorrow's challenges. +But not all operations tasks are the same. SRE makes a clear distinction between "ops work" and "toil." Ops work is essential for maintaining systems and adds value, while toil is the repetitive, boring stuff that doesn’t. It's super important to recognize and minimize toil because a culture that lets engineers get bogged down in it will kill innovation and growth. The way an organization handles toil says a lot about its operational health and commitment to balance. -However, not all operational tasks are equal. SRE differentiates between "ops work" and "toil". While ops work is integral to system maintenance and can provide value, toil represents repetitive, mundane tasks which offer little value in the long run. Recognising and minimising toil is crucial. A culture that allows engineers to drown in toil stifles innovation and growth. Hence, an organisation's approach to toil indicates its operational health and commitment to balance. +A key part of finding operational balance is the tools and processes that SREs use. Great monitoring and observability tools, especially those that can handle lots of complex data, are essential. This isn’t just about having the right tech—it shows that the organization values proactive problem-solving. With systems that can spot potential issues early, SREs can keep things stable while still pushing forward. -A cornerstone of achieving operational balance lies in the tools and processes SREs use. Effective monitoring, observability tools, and ensuring that tools can handle high cardinality data are foundational. These aren't just technical requisites but reflective of an organisational culture prioritising proactive problem-solving. By having systems that effectively flag potential issues before they escalate, SREs can maintain the balance between system stability and forward momentum. +Operational balance isn't just about tech or processes; it's also about people. The well-being of on-call engineers is just as important as the health of the services they manage. Doing postmortems after incidents, having continuous feedback loops, and identifying gaps in tools, skills, or resources all help make sure the human side of operations gets the attention it deserves. -Moreover, operational balance isn't just a technological or process challenge; it's a human one. The health of on-call engineers is as crucial as the health of the services they manage. On-call postmortems, continuous feedback loops, and recognising gaps (be it tooling, operational expertise, or resources) ensure that the human elements of operations are noticed. +In the end, finding operational balance in SRE is an ongoing journey, not a one-time thing. Companies need to keep reassessing their practices, tools, and especially their culture. When they get this balance right, they can keep innovating without sacrificing the reliability of their systems, leading to long-term success. -In conclusion, operational balance in SRE isn't static thing but an ongoing journey. It requires organisations to constantly evaluate their practices, tools, and, most importantly, their culture. By achieving this balance, organisations can ensure that they have time for innovation while maintaining the robustness and reliability of their systems, resulting in sustainable long-term success. - -That all sounds very romantic. The truth is, it's brutal to archive the perfect balance. No system will ever be perfect. But at least we should aim for it! +That all sounds pretty idealistic. The reality is that getting the perfect balance is really tough. No system is ever going to be perfect. But hey, we should still strive for it! Continue with the third part of this series: diff --git a/gemfeed/2024-01-09-site-reliability-engineering-part-3.md b/gemfeed/2024-01-09-site-reliability-engineering-part-3.md index d53c083f..1030cc21 100644 --- a/gemfeed/2024-01-09-site-reliability-engineering-part-3.md +++ b/gemfeed/2024-01-09-site-reliability-engineering-part-3.md @@ -1,8 +1,8 @@ -# Site Reliability Engineering - Part 3: On-Call Culture and the Human Aspect +# Site Reliability Engineering - Part 3: On-Call Culture and the Human Side > Published at 2024-01-09T18:35:48+02:00 -This is the third part of my Site Reliability Engineering (SRE) series. I am currently employed as a Site Reliability Engineer and will try to share what SRE is about in this blog series. +Welcome to Part 3 of my Site Reliability Engineering (SRE) series. I'm currently working as a Site Reliability Engineer, and I’m here to share what SRE is all about in this blog series. [2023-08-18 Site Reliability Engineering - Part 1: SRE and Organizational Culture](./2023-08-18-site-reliability-engineering-part-1.md) [2023-11-19 Site Reliability Engineering - Part 2: Operational Balance in SRE](./2023-11-19-site-reliability-engineering-part-2.md) @@ -34,23 +34,25 @@ This is the third part of my Site Reliability Engineering (SRE) series. I am cur ``` -## On-Call Culture and the Human Aspect: Prioritising Well-being in the Realm of Reliability +## On-Call Culture and the Human Side: Putting Well-being First in the World of Reliability -Site Reliability Engineering is synonymous with ensuring system reliability, but the human factor is an often-underestimated part of this discipline. Ensuring an healthy on-call culture is as critical as any technical solution. The well-being of the engineers is an important factor. +Site Reliability Engineering is all about keeping systems reliable, but we often forget how important the human side is. A healthy on-call culture is just as crucial as any technical fix. The well-being of the engineers really matters. -Firstly, a healthy on-call rotation is about more than just managing and responding to incidents. It's about the entire ecosystem that supports this practice. This involves reducing pain points, offering mentorship, rapid iteration, and ensuring that engineers have the right tools and processes. One ceavat is, that engineers should be willing to learn. Especially in on-call rotation embedding SREs with other engineers (for example Software Engineers or QA Engineers), it's difficult to motivate everyone to engage. QA Engineers want to test the software, Software Engineers want to implement new features; they don't want to troubleshoot and debug production incidents. It can be depressing for the mentoring SRE. +First off, a healthy on-call rotation is about more than just handling incidents. It's about creating a supportive ecosystem. This means cutting down on pain points, offering mentorship, quickly iterating on processes, and making sure engineers have the right tools. But there's a catch—engineers need to be willing to learn. Especially in on-call rotations where SREs work with Software Engineers or QA Engineers, it can be tough to get everyone motivated. QA Engineers want to test, Software Engineers want to build new features; they don’t want to deal with production issues. This can be really frustrating for the SREs trying to mentor them. -Furthermore, the metrics that measure the success of an on-call experience are only sometimes straightforward. While one might assume that fewer pages translate to better on-call expertise (which is true to a degree, as who wants to receive a page out of office hours?), it's not always the volume of pages that matters most. Trust, ownership, accountability, and effective communication play the important roles. +Plus, measuring a good on-call experience isn't always clear-cut. You might think fewer pages mean a better on-call setup—and yeah, no one wants to get paged after hours—but it's not just about the number of pages. Trust, ownership, accountability, and solid communication are what really matter. -An important part is giving feedback about the on-call experience to ensure continuous learning. If alerts are mostly noise, they should be tuned or even eliminated. If alerts are actionable, can recurring tasks be automated? If there are knowledge gaps, is the documentation not good enough? Continuous retrospection ensures that not only do systems evolve, but the experience for the on-call engineers becomes progressively better. +A key part is giving feedback about the on-call experience to keep learning and improving. If alerts are mostly noise, they need to be tweaked or even ditched. If alerts are helpful, can we automate the repetitive tasks? If there are knowledge gaps, is the documentation lacking? Regular retrospectives ensure that the systems get better over time and the on-call experience improves for the engineers. -Onboarding for on-call duties is a crucial aspect of ensuring the reliability and efficiency of systems. This process involves equipping new team members with the knowledge, tools, and support to handle incidents confidently. It begins with an overview of the system architecture and common challenges, followed by training on monitoring tools, alerting mechanisms, and incident response protocols. Shadowing experienced on-call engineers can offer practical exposure. Too often, new engineers are thrown into the cold water without proper onboarding and training because the more experienced engineers are too busy fire-fighting production issues in the first place. +Getting new team members ready for on-call duties is super important for keeping systems reliable and efficient. This means giving them the knowledge, tools, and support they need to handle incidents with confidence. It starts with a rundown of the system architecture and common issues, then training on monitoring tools, alerting systems, and incident response protocols. Watching experienced on-call engineers in action can provide some hands-on learning. Too often, though, new engineers get thrown into the deep end without proper onboarding because the more experienced engineers are too busy dealing with ongoing production issues. -An always-on, always-alert culture can lead to burnout. Engineers should be encouraged to recognise their limits, take breaks, and seek support when needed. This isn't just about individual health; a burnt-out engineer can have cascading effects on the entire team and the systems they manage. A successful on-call culture ensures that while systems are kept running, the engineers are kept happy, healthy, and supported. The more experienced engineers should take time to mentor the junior engineers, but the junior engineers should also be fully engaged, try to investigate and learn new things by themselves. +A culture where everyone's always on and alert can cause burnout. Engineers need to know their limits, take breaks, and ask for help when they need it. This isn't just about personal health; a burnt-out engineer can drag down the whole team and the systems they manage. A good on-call culture keeps systems running while making sure engineers are happy, healthy, and supported. Experienced engineers should take the time to mentor juniors, but junior engineers should also stay engaged, investigate issues, and learn new things on their own. -For the junior engineer, it's too easy to fall back and ask the experts in the team every time an issue arises. This seems reasonable, but serving recipes for solving production issues on a silver tablet won't scale forever, as there are infinite scenarios of how production systems can break. So every engineer should learn to debug, troubleshoot and resolve production incidents independently. The experts will still be there for guidance and step in when the junior gets stuck after trying, but the experts should also learn to step down so that lesser experienced engineers can step up and learn. But mistakes can always happen here; that's why having a blameless on-call culture is essential. +For junior engineers, it's tempting to always ask the experts for help whenever something goes wrong. While that might seem reasonable, constantly handing out solutions doesn't scale—there are endless ways for production systems to break. So, every engineer needs to learn how to debug, troubleshoot, and resolve incidents on their own. The experts should be there for guidance and can step in when a junior gets really stuck, but they also need to give space for less experienced engineers to grow and learn. -A blameless on-call culture is a must for a safe and collaborative environment where engineers can effectively respond to incidents without fear of retribution. This approach acknowledges that mistakes are a natural part of the learning and innovation process. When individuals are assured they won't be punished for errors, they're more likely to openly discuss mistakes, allowing the entire team to learn and grow from each incident. Furthermore, a blameless culture promotes psychological safety, enhances job satisfaction, reduces burnout, and ensures that talent remains committed and engaged. +A blameless on-call culture is essential for creating a safe and collaborative environment where engineers can handle incidents without worrying about getting blamed. It recognizes that mistakes are just part of learning and innovating. When people know they won’t be punished for errors, they’re more likely to talk openly about what went wrong, which helps the whole team learn and improve. Plus, a blameless culture boosts psychological safety, job satisfaction, and reduces burnout, keeping everyone committed and engaged. + +Mistakes are gonna happen, which is why having a blameless on-call culture is so important. E-Mail your comments to `paul@nospam.buetow.org` :-) diff --git a/gemfeed/index.md b/gemfeed/index.md index 54339766..58464a0a 100644 --- a/gemfeed/index.md +++ b/gemfeed/index.md @@ -12,7 +12,7 @@ [2024-03-03 - A fine Fyne Android app for quickly logging ideas programmed in Go](./2024-03-03-a-fine-fyne-android-app-for-quickly-logging-ideas-programmed-in-golang.md) [2024-02-04 - From `babylon5.buetow.org` to `*.buetow.cloud`](./2024-02-04-from-babylon5.buetow.org-to-.cloud.md) [2024-01-13 - One reason why I love OpenBSD](./2024-01-13-one-reason-why-i-love-openbsd.md) -[2024-01-09 - Site Reliability Engineering - Part 3: On-Call Culture and the Human Aspect](./2024-01-09-site-reliability-engineering-part-3.md) +[2024-01-09 - Site Reliability Engineering - Part 3: On-Call Culture and the Human Side](./2024-01-09-site-reliability-engineering-part-3.md) [2023-12-10 - Bash Golf Part 3](./2023-12-10-bash-golf-part-3.md) [2023-11-19 - Site Reliability Engineering - Part 2: Operational Balance in SRE](./2023-11-19-site-reliability-engineering-part-2.md) [2023-11-11 - 'Mind Management' book notes](./2023-11-11-mind-management-book-notes.md) -- cgit v1.2.3 From 0250aeb04e7b383b213827fa15b055818b7113e0 Mon Sep 17 00:00:00 2001 From: Paul Buetow Date: Sat, 24 Aug 2024 19:42:39 +0300 Subject: Update content for md --- ...23-08-18-site-reliability-engineering-part-1.md | 2 +- ...23-11-19-site-reliability-engineering-part-2.md | 4 +- ...24-01-09-site-reliability-engineering-part-3.md | 2 +- ...24-04-01-KISS-high-availability-with-OpenBSD.md | 29 ++++---- ...5-03-projects-i-currently-dont-have-time-for.md | 77 +++++++++++----------- .../2024-06-23-terminal-multiplexing-with-tmux.md | 41 ++++++------ 6 files changed, 73 insertions(+), 82 deletions(-) (limited to 'gemfeed') diff --git a/gemfeed/2023-08-18-site-reliability-engineering-part-1.md b/gemfeed/2023-08-18-site-reliability-engineering-part-1.md index 1c1632ad..37976a18 100644 --- a/gemfeed/2023-08-18-site-reliability-engineering-part-1.md +++ b/gemfeed/2023-08-18-site-reliability-engineering-part-1.md @@ -6,7 +6,7 @@ Being a Site Reliability Engineer (SRE) is like stepping into a lively, ever-evo [2023-08-18 Site Reliability Engineering - Part 1: SRE and Organizational Culture (You are currently reading this)](./2023-08-18-site-reliability-engineering-part-1.md) [2023-11-19 Site Reliability Engineering - Part 2: Operational Balance in SRE](./2023-11-19-site-reliability-engineering-part-2.md) -[2024-01-09 Site Reliability Engineering - Part 3: On-Call Culture and the Human Aspect](./2024-01-09-site-reliability-engineering-part-3.md) +[2024-01-09 Site Reliability Engineering - Part 3: On-Call Culture and the Human Side](./2024-01-09-site-reliability-engineering-part-3.md) ``` ▓▓▓▓░░ diff --git a/gemfeed/2023-11-19-site-reliability-engineering-part-2.md b/gemfeed/2023-11-19-site-reliability-engineering-part-2.md index 3fd48c9c..9bddfbcc 100644 --- a/gemfeed/2023-11-19-site-reliability-engineering-part-2.md +++ b/gemfeed/2023-11-19-site-reliability-engineering-part-2.md @@ -6,7 +6,7 @@ This is the second part of my Site Reliability Engineering (SRE) series. I am cu [2023-08-18 Site Reliability Engineering - Part 1: SRE and Organizational Culture](./2023-08-18-site-reliability-engineering-part-1.md) [2023-11-19 Site Reliability Engineering - Part 2: Operational Balance in SRE (You are currently reading this)](./2023-11-19-site-reliability-engineering-part-2.md) -[2024-01-09 Site Reliability Engineering - Part 3: On-Call Culture and the Human Aspect](./2024-01-09-site-reliability-engineering-part-3.md) +[2024-01-09 Site Reliability Engineering - Part 3: On-Call Culture and the Human Side](./2024-01-09-site-reliability-engineering-part-3.md) ``` ⠀⠀⠀⠀⠀⠀⠀⠀⠀⠀⠀⠀⢀⣠⣾⣷⣄⡀⠀⠀⠀⠀⠀⠀⠀⠀⠀⠀⠀⠀ @@ -42,7 +42,7 @@ That all sounds pretty idealistic. The reality is that getting the perfect balan Continue with the third part of this series: -[2024-01-09 Site Reliability Engineering - Part 3: On-Call Culture and the Human Aspect](./2024-01-09-site-reliability-engineering-part-3.md) +[2024-01-09 Site Reliability Engineering - Part 3: On-Call Culture and the Human Side](./2024-01-09-site-reliability-engineering-part-3.md) E-Mail your comments to `paul@nospam.buetow.org` :-) diff --git a/gemfeed/2024-01-09-site-reliability-engineering-part-3.md b/gemfeed/2024-01-09-site-reliability-engineering-part-3.md index 1030cc21..314f50e0 100644 --- a/gemfeed/2024-01-09-site-reliability-engineering-part-3.md +++ b/gemfeed/2024-01-09-site-reliability-engineering-part-3.md @@ -6,7 +6,7 @@ Welcome to Part 3 of my Site Reliability Engineering (SRE) series. I'm currently [2023-08-18 Site Reliability Engineering - Part 1: SRE and Organizational Culture](./2023-08-18-site-reliability-engineering-part-1.md) [2023-11-19 Site Reliability Engineering - Part 2: Operational Balance in SRE](./2023-11-19-site-reliability-engineering-part-2.md) -[2024-01-09 Site Reliability Engineering - Part 3: On-Call Culture and the Human Aspect (You are currently reading this)](./2024-01-09-site-reliability-engineering-part-3.md) +[2024-01-09 Site Reliability Engineering - Part 3: On-Call Culture and the Human Side (You are currently reading this)](./2024-01-09-site-reliability-engineering-part-3.md) ``` ..--""""----.. diff --git a/gemfeed/2024-04-01-KISS-high-availability-with-OpenBSD.md b/gemfeed/2024-04-01-KISS-high-availability-with-OpenBSD.md index 2310f50a..0b1680d8 100644 --- a/gemfeed/2024-04-01-KISS-high-availability-with-OpenBSD.md +++ b/gemfeed/2024-04-01-KISS-high-availability-with-OpenBSD.md @@ -27,22 +27,19 @@ _____|_:_:_| (o)-(o) |_:_:_|--'`-. ,--. ksh under-water (((\'/ ``` -``` -Table of contents -================= - -KISS high-availability with OpenBSD - My auto-failover requirements - My HA solution - Only OpenBSD base installation required - Fairly cheap and geo-redundant - Failover time and split-brain - Failover support for multiple protocols - Let's encrypt TLS certificates - Monitoring - Rex automation - More HA -``` +## Table of Contents + +* [⇢ KISS high-availability with OpenBSD](#kiss-high-availability-with-openbsd) +* [⇢ ⇢ My auto-failover requirements](#my-auto-failover-requirements) +* [⇢ ⇢ My HA solution](#my-ha-solution) +* [⇢ ⇢ ⇢ Only OpenBSD base installation required](#only-openbsd-base-installation-required) +* [⇢ ⇢ ⇢ Fairly cheap and geo-redundant](#fairly-cheap-and-geo-redundant) +* [⇢ ⇢ ⇢ Failover time and split-brain](#failover-time-and-split-brain) +* [⇢ ⇢ ⇢ Failover support for multiple protocols](#failover-support-for-multiple-protocols) +* [⇢ ⇢ ⇢ Let's encrypt TLS certificates](#lets-encrypt-tls-certificates) +* [⇢ ⇢ ⇢ Monitoring](#monitoring) +* [⇢ ⇢ ⇢ Rex automation](#rex-automation) +* [⇢ ⇢ More HA](#more-ha) I have always wanted a highly available setup for my personal websites. I could have used off-the-shelf hosting solutions or hosted my sites in an AWS S3 bucket. I have used technologies like (in unsorted and slightly unrelated order) BGP, LVS/IPVS, ldirectord, Pacemaker, STONITH, scripted VIP failover via ARP, heartbeat, heartbeat2, Corosync, keepalived, DRBD, and commercial F5 Load Balancers for high availability at work. diff --git a/gemfeed/2024-05-03-projects-i-currently-dont-have-time-for.md b/gemfeed/2024-05-03-projects-i-currently-dont-have-time-for.md index 5817e6ff..984f3c3d 100644 --- a/gemfeed/2024-05-03-projects-i-currently-dont-have-time-for.md +++ b/gemfeed/2024-05-03-projects-i-currently-dont-have-time-for.md @@ -19,46 +19,43 @@ Art by Laura Brown Over the years, I have collected many ideas for my personal projects and noted them down. I am currently in the process of cleaning up all my notes and reviewing those ideas. I don’t have time for the ones listed here and won’t have any soon due to other commitments and personal projects. So, in order to "get rid of them" from my notes folder, I decided to simply put them in this blog post so that those ideas don't get lost. Maybe I will pick up one or another idea someday in the future, but for now, they are all put on ice in favor of other personal projects or family time. -``` -Table of contents -================= - -Projects I currently don't have time for - Introduction - Hardware projects I don't have time for - I use Arch, btw! - OpenBSD home router - Pi-Hole server - Infodash - Reading station - Retro station - Sound server - Project Freekat - Programming projects I don't have time for - CLI-HIVE - Enhanced KISS home photo albums - KISS file sync server with end-to-end encryption - A language that compiles to `bash` - A language that compiles to `sed` - Renovate VS-Sim - KISS ticketing system - A domain-specific language (DSL) for work - Self-hosting projects I don't have time for - My own Matrix server - Ampache music server - Librum eBook reader - Memos - Note-taking service - Bepasty server - Books I don't have time to read - Fluent Python - Programming Ruby - Peter F. Hamilton science fiction books - New websites I don't have time for - Create a "Why Raku Rox" site - Research projects I don't have time for - Project secure - CPU utilisation is all wrong -``` +## Table of Contents + +* [⇢ Projects I currently don't have time for](#projects-i-currently-dont-have-time-for) +* [⇢ ⇢ Introduction](#introduction) +* [⇢ ⇢ Hardware projects I don't have time for](#hardware-projects-i-dont-have-time-for) +* [⇢ ⇢ ⇢ I use Arch, btw!](#i-use-arch-btw) +* [⇢ ⇢ ⇢ OpenBSD home router](#openbsd-home-router) +* [⇢ ⇢ ⇢ Pi-Hole server](#pi-hole-server) +* [⇢ ⇢ ⇢ Infodash](#infodash) +* [⇢ ⇢ ⇢ Reading station](#reading-station) +* [⇢ ⇢ ⇢ Retro station](#retro-station) +* [⇢ ⇢ ⇢ Sound server](#sound-server) +* [⇢ ⇢ ⇢ Project Freekat](#project-freekat) +* [⇢ ⇢ Programming projects I don't have time for](#programming-projects-i-dont-have-time-for) +* [⇢ ⇢ ⇢ CLI-HIVE](#cli-hive) +* [⇢ ⇢ ⇢ Enhanced KISS home photo albums](#enhanced-kiss-home-photo-albums) +* [⇢ ⇢ ⇢ KISS file sync server with end-to-end encryption](#kiss-file-sync-server-with-end-to-end-encryption) +* [⇢ ⇢ ⇢ A language that compiles to `bash`](#a-language-that-compiles-to-bash) +* [⇢ ⇢ ⇢ A language that compiles to `sed`](#a-language-that-compiles-to-sed) +* [⇢ ⇢ ⇢ Renovate VS-Sim](#renovate-vs-sim) +* [⇢ ⇢ ⇢ KISS ticketing system](#kiss-ticketing-system) +* [⇢ ⇢ ⇢ A domain-specific language (DSL) for work](#a-domain-specific-language-dsl-for-work) +* [⇢ ⇢ Self-hosting projects I don't have time for](#self-hosting-projects-i-dont-have-time-for) +* [⇢ ⇢ ⇢ My own Matrix server](#my-own-matrix-server) +* [⇢ ⇢ ⇢ Ampache music server](#ampache-music-server) +* [⇢ ⇢ ⇢ Librum eBook reader](#librum-ebook-reader) +* [⇢ ⇢ ⇢ Memos - Note-taking service](#memos---note-taking-service) +* [⇢ ⇢ ⇢ Bepasty server](#bepasty-server) +* [⇢ ⇢ Books I don't have time to read](#books-i-dont-have-time-to-read) +* [⇢ ⇢ ⇢ Fluent Python](#fluent-python) +* [⇢ ⇢ ⇢ Programming Ruby](#programming-ruby) +* [⇢ ⇢ ⇢ Peter F. Hamilton science fiction books](#peter-f-hamilton-science-fiction-books) +* [⇢ ⇢ New websites I don't have time for](#new-websites-i-dont-have-time-for) +* [⇢ ⇢ ⇢ Create a "Why Raku Rox" site](#create-a-why-raku-rox-site) +* [⇢ ⇢ Research projects I don't have time for](#research-projects-i-dont-have-time-for) +* [⇢ ⇢ ⇢ Project secure](#project-secure) +* [⇢ ⇢ ⇢ CPU utilisation is all wrong](#cpu-utilisation-is-all-wrong) ## Hardware projects I don't have time for diff --git a/gemfeed/2024-06-23-terminal-multiplexing-with-tmux.md b/gemfeed/2024-06-23-terminal-multiplexing-with-tmux.md index 472cb022..142d059a 100644 --- a/gemfeed/2024-06-23-terminal-multiplexing-with-tmux.md +++ b/gemfeed/2024-06-23-terminal-multiplexing-with-tmux.md @@ -14,28 +14,25 @@ jgs `-=========-`() mod. by Paul B. ``` -``` -Table of contents -================= - -Terminal multiplexing with `tmux` - Introduction - Shell aliases - The `tn` alias - Creating a new session - Cleaning up default sessions automatically - Renaming sessions - The `ta` alias - Attaching to a session - The `tr` alias - For a nested remote session - Change of the Tmux prefix for better nesting - The `ts` alias - Searching sessions with fuzzy finder - The `tssh` alias - Cluster SSH replacement - The `tmux::tssh_from_argument` helper - The `tmux::tssh_from_file` helper - `tssh` examples - Common Tmux commands I use in `tssh` - Copy and paste workflow - Tmux configurations -``` +## Table of Contents + +* [⇢ Terminal multiplexing with `tmux`](#terminal-multiplexing-with-tmux) +* [⇢ ⇢ Introduction](#introduction) +* [⇢ ⇢ Shell aliases](#shell-aliases) +* [⇢ ⇢ The `tn` alias - Creating a new session](#the-tn-alias---creating-a-new-session) +* [⇢ ⇢ ⇢ Cleaning up default sessions automatically](#cleaning-up-default-sessions-automatically) +* [⇢ ⇢ ⇢ Renaming sessions](#renaming-sessions) +* [⇢ ⇢ The `ta` alias - Attaching to a session](#the-ta-alias---attaching-to-a-session) +* [⇢ ⇢ The `tr` alias - For a nested remote session](#the-tr-alias---for-a-nested-remote-session) +* [⇢ ⇢ ⇢ Change of the Tmux prefix for better nesting](#change-of-the-tmux-prefix-for-better-nesting) +* [⇢ ⇢ The `ts` alias - Searching sessions with fuzzy finder](#the-ts-alias---searching-sessions-with-fuzzy-finder) +* [⇢ ⇢ The `tssh` alias - Cluster SSH replacement](#the-tssh-alias---cluster-ssh-replacement) +* [⇢ ⇢ ⇢ The `tmux::tssh_from_argument` helper](#the-tmuxtsshfromargument-helper) +* [⇢ ⇢ ⇢ The `tmux::tssh_from_file` helper](#the-tmuxtsshfromfile-helper) +* [⇢ ⇢ ⇢ `tssh` examples](#tssh-examples) +* [⇢ ⇢ ⇢ Common Tmux commands I use in `tssh`](#common-tmux-commands-i-use-in-tssh) +* [⇢ ⇢ Copy and paste workflow](#copy-and-paste-workflow) +* [⇢ ⇢ Tmux configurations](#tmux-configurations) ## Introduction -- cgit v1.2.3 From 113ff70ba3a1d828933a2d69a533f1124363a0bd Mon Sep 17 00:00:00 2001 From: Paul Buetow Date: Sat, 24 Aug 2024 19:59:33 +0300 Subject: Update content for md --- gemfeed/2008-06-26-perl-poetry.md | 11 ++++++ .../2011-05-07-perl-daemon-service-framework.md | 16 ++++++++ ...6-04-09-jails-and-zfs-on-freebsd-with-puppet.md | 11 ++++++ ...04-22-dtail-the-distributed-log-tail-program.md | 16 ++++++++ gemfeed/2021-04-24-welcome-to-the-geminispace.md | 11 ++++++ .../2021-05-16-personal-bash-coding-style-guide.md | 24 ++++++++++++ ...-05-gemtexter-one-bash-script-to-rule-it-all.md | 21 ++++++++++- gemfeed/2021-09-12-keep-it-simple-and-stupid.md | 44 ++++++++++++++++------ gemfeed/2021-11-29-bash-golf-part-1.md | 15 ++++++++ gemfeed/2022-01-01-bash-golf-part-2.md | 14 +++++++ gemfeed/2022-03-06-the-release-of-dtail-4.0.0.md | 20 ++++++++++ gemfeed/2022-05-27-perl-is-still-a-great-choice.md | 12 ++++++ ...2022-07-30-lets-encrypt-with-openbsd-and-rex.md | 21 ++++++++++- ...022-08-27-gemtexter-1.1.0-lets-gemtext-again.md | 16 ++++++++ gemfeed/2022-10-30-installing-dtail-on-openbsd.md | 17 +++++++++ ...3-03-25-gemtexter-2.0.0-lets-gemtext-again-2.md | 13 +++++++ ...orithms-and-data-structures-in-golang-part-1.md | 12 ++++++ ...veiling-guprecords:-uptime-records-with-raku.md | 10 ++++- ...023-05-06-the-obstacle-is-the-way-book-notes.md | 20 +++++++++- ...023-06-01-kiss-server-monitoring-with-gogios.md | 18 +++++++++ ...7-17-career-guide-and-soft-skills-book-notes.md | 35 +++++++++++++++++ ...3-07-21-gemtexter-2.1.0-lets-gemtext-again-3.md | 14 +++++++ gemfeed/2023-09-25-dtail-usage-examples.md | 16 ++++++++ ...s-static-web-photo-albums-with-photoalbum.sh.md | 12 ++++++ gemfeed/2023-11-11-mind-management-book-notes.md | 15 ++++++++ gemfeed/2023-12-10-bash-golf-part-3.md | 15 ++++++++ ...r-quickly-logging-ideas-programmed-in-golang.md | 8 ++++ ...24-04-01-KISS-high-availability-with-OpenBSD.md | 3 ++ gemfeed/2024-05-01-slow-productivity-book-notes.md | 12 ++++++ ...5-03-projects-i-currently-dont-have-time-for.md | 8 ++-- .../2024-07-07-the-stoic-challenge-book-notes.md | 9 +++++ .../2024-08-05-typing-127.1-words-per-minute.md | 31 +++++++++++++++ 32 files changed, 500 insertions(+), 20 deletions(-) (limited to 'gemfeed') diff --git a/gemfeed/2008-06-26-perl-poetry.md b/gemfeed/2008-06-26-perl-poetry.md index 9d6c6c02..0de1bdaf 100644 --- a/gemfeed/2008-06-26-perl-poetry.md +++ b/gemfeed/2008-06-26-perl-poetry.md @@ -25,6 +25,17 @@ _~~|~/_|_|__/|~~~~~~~ | / ~~~~~ | | ~~~~~~~~ (__) (____) ``` +## Table of Contents + +* [⇢ Perl Poetry](#perl-poetry) +* [⇢ ⇢ Introduction](#introduction) +* [⇢ ⇢ math.pl](#mathpl) +* [⇢ ⇢ christmas.pl](#christmaspl) +* [⇢ ⇢ shopping.pl](#shoppingpl) +* [⇢ ⇢ More...](#more) + +## Introduction + Here are some Perl Poems I wrote. They don't do anything useful when you run them, but they don't produce a compiler error either. They only exist for fun and demonstrate what you can do with Perl syntax. Wikipedia: "Perl poetry is the practice of writing poems that can be compiled as legal Perl code, for example the piece known as Black Perl. Perl poetry is made possible by the large number of English words that are used in the Perl language. New poems are regularly submitted to the community at PerlMonks." diff --git a/gemfeed/2011-05-07-perl-daemon-service-framework.md b/gemfeed/2011-05-07-perl-daemon-service-framework.md index 183a3de1..e393a1ea 100644 --- a/gemfeed/2011-05-07-perl-daemon-service-framework.md +++ b/gemfeed/2011-05-07-perl-daemon-service-framework.md @@ -9,6 +9,22 @@ //\ //\\ //\ //\\ //\ //\\jrei ``` +## Table of Contents + +* [⇢ Perl Daemon (Service Framework)](#perl-daemon-service-framework) +* [⇢ ⇢ Introduction](#introduction) +* [⇢ ⇢ Features](#features) +* [⇢ ⇢ Quick Guide](#quick-guide) +* [⇢ ⇢ How to configure](#how-to-configure) +* [⇢ ⇢ Example ](#example-) +* [⇢ ⇢ HiRes event loop](#hires-event-loop) +* [⇢ ⇢ Writing your own modules](#writing-your-own-modules) +* [⇢ ⇢ ⇢ Example module](#example-module) +* [⇢ ⇢ ⇢ Your own module](#your-own-module) +* [⇢ ⇢ May the source be with you](#may-the-source-be-with-you) + +## Introduction + PerlDaemon is a minimal daemon for Linux and other Unix like operating systems programmed in Perl. It is a minimal but pretty functional and fairly generic service framework. This means that it does not do anything useful other than providing a framework for starting, stopping, configuring and logging. To do something useful, a module (written in Perl) must be provided. ## Features diff --git a/gemfeed/2016-04-09-jails-and-zfs-on-freebsd-with-puppet.md b/gemfeed/2016-04-09-jails-and-zfs-on-freebsd-with-puppet.md index ff7e2413..3879df57 100644 --- a/gemfeed/2016-04-09-jails-and-zfs-on-freebsd-with-puppet.md +++ b/gemfeed/2016-04-09-jails-and-zfs-on-freebsd-with-puppet.md @@ -22,6 +22,17 @@ \ `. ``` +## Table of Contents + +* [⇢ Jails and ZFS with Puppet on FreeBSD](#jails-and-zfs-with-puppet-on-freebsd) +* [⇢ ⇢ Introduction](#introduction) +* [⇢ ⇢ ZFS](#zfs) +* [⇢ ⇢ Jails](#jails) +* [⇢ ⇢ Inside-Jail Puppet](#inside-jail-puppet) +* [⇢ ⇢ Managing multiple Jails](#managing-multiple-jails) + +## Introduction + Over the last couple of years I wrote quite a few Puppet modules in order to manage my personal server infrastructure. One of them manages FreeBSD Jails and another one ZFS file systems. I thought I would give a brief overview in how it looks and feels. ## ZFS diff --git a/gemfeed/2021-04-22-dtail-the-distributed-log-tail-program.md b/gemfeed/2021-04-22-dtail-the-distributed-log-tail-program.md index ecfdcfd7..b0a2bf0f 100644 --- a/gemfeed/2021-04-22-dtail-the-distributed-log-tail-program.md +++ b/gemfeed/2021-04-22-dtail-the-distributed-log-tail-program.md @@ -4,6 +4,22 @@ [![DTail logo image](./dtail-the-distributed-log-tail-program/title.png "DTail logo image")](./dtail-the-distributed-log-tail-program/title.png) +## Table of Contents + +* [⇢ DTail - The distributed log tail program](#dtail---the-distributed-log-tail-program) +* [⇢ ⇢ Introduction](#introduction) +* [⇢ ⇢ A Mimecast Pet Project](#a-mimecast-pet-project) +* [⇢ ⇢ Differentiating from log management systems](#differentiating-from-log-management-systems) +* [⇢ ⇢ Combining simplicity, security and efficiency](#combining-simplicity-security-and-efficiency) +* [⇢ ⇢ The DTail family of commands](#the-dtail-family-of-commands) +* [⇢ ⇢ Usage example](#usage-example) +* [⇢ ⇢ Fitting it in](#fitting-it-in) +* [⇢ ⇢ Advanced features](#advanced-features) +* [⇢ ⇢ For the future](#for-the-future) +* [⇢ ⇢ Open Source](#open-source) + +## Introduction + This article first appeared at the Mimecast Engineering Blog but I made it available here in my personal internet site too. [Original Mimecast Engineering Blog post at Medium](https://medium.com/mimecast-engineering/dtail-the-distributed-log-tail-program-79b8087904bb) diff --git a/gemfeed/2021-04-24-welcome-to-the-geminispace.md b/gemfeed/2021-04-24-welcome-to-the-geminispace.md index e8443ea3..27f82c24 100644 --- a/gemfeed/2021-04-24-welcome-to-the-geminispace.md +++ b/gemfeed/2021-04-24-welcome-to-the-geminispace.md @@ -30,6 +30,17 @@ However, if you still use HTTP, you are just surfing the fallback HTML version o ``` +## Table of Contents + +* [⇢ Welcome to the Geminispace](#welcome-to-the-geminispace) +* [⇢ ⇢ Motivation](#motivation) +* [⇢ ⇢ ⇢ My urge to revamp my personal website](#my-urge-to-revamp-my-personal-website) +* [⇢ ⇢ ⇢ My still great Laptop running hot](#my-still-great-laptop-running-hot) +* [⇢ ⇢ Discovering the Gemini internet protocol](#discovering-the-gemini-internet-protocol) +* [⇢ ⇢ My own Gemini capsule](#my-own-gemini-capsule) +* [⇢ ⇢ Gemini advantages summarised](#gemini-advantages-summarised) +* [⇢ ⇢ Dive into deep Gemini space](#dive-into-deep-gemini-space) + ## Motivation ### My urge to revamp my personal website diff --git a/gemfeed/2021-05-16-personal-bash-coding-style-guide.md b/gemfeed/2021-05-16-personal-bash-coding-style-guide.md index 1389be26..43b93229 100644 --- a/gemfeed/2021-05-16-personal-bash-coding-style-guide.md +++ b/gemfeed/2021-05-16-personal-bash-coding-style-guide.md @@ -15,6 +15,30 @@ "\__/"---------------"\__/"-+---+' ``` +## Table of Contents + +* [⇢ Personal Bash coding style guide](#personal-bash-coding-style-guide) +* [⇢ ⇢ Introduction](#introduction) +* [⇢ ⇢ My modifications](#my-modifications) +* [⇢ ⇢ ⇢ Shebang](#shebang) +* [⇢ ⇢ ⇢ Two space soft-tabs indentation](#two-space-soft-tabs-indentation) +* [⇢ ⇢ ⇢ Breaking long pipes](#breaking-long-pipes) +* [⇢ ⇢ ⇢ Quoting your variables](#quoting-your-variables) +* [⇢ ⇢ ⇢ Prefer built-in commands over external commands](#prefer-built-in-commands-over-external-commands) +* [⇢ ⇢ My additions](#my-additions) +* [⇢ ⇢ ⇢ Use of 'yes' and 'no'](#use-of-yes-and-no) +* [⇢ ⇢ ⇢ Non-evil alternative to variable assignments via eval](#non-evil-alternative-to-variable-assignments-via-eval) +* [⇢ ⇢ ⇢ Prefer pipes over arrays for list processing](#prefer-pipes-over-arrays-for-list-processing) +* [⇢ ⇢ ⇢ Assign-then-shift](#assign-then-shift) +* [⇢ ⇢ ⇢ Paranoid mode](#paranoid-mode) +* [⇢ ⇢ Learned](#learned) +* [⇢ ⇢ ⇢ Unintended lexicographical comparison.](#unintended-lexicographical-comparison) +* [⇢ ⇢ ⇢ PIPESTATUS](#pipestatus) +* [⇢ ⇢ Use common sense and BE CONSISTENT.](#use-common-sense-and-be-consistent) +* [⇢ ⇢ Advanced Bash learning pro tip](#advanced-bash-learning-pro-tip) + +## Introduction + Lately, I have been polishing and writing a lot of Bash code. Not that I never wrote a lot of Bash, but now as I also looked through the Google Shell Style Guide, I thought it is time also to write my thoughts on that. I agree with that guide in most, but not in all points. [Google Shell Style Guide](https://google.github.io/styleguide/shellguide.html) diff --git a/gemfeed/2021-06-05-gemtexter-one-bash-script-to-rule-it-all.md b/gemfeed/2021-06-05-gemtexter-one-bash-script-to-rule-it-all.md index 86878339..580aceab 100644 --- a/gemfeed/2021-06-05-gemtexter-one-bash-script-to-rule-it-all.md +++ b/gemfeed/2021-06-05-gemtexter-one-bash-script-to-rule-it-all.md @@ -43,11 +43,30 @@ `+a:f:......jrei''' ``` +## Table of Contents + +* [⇢ Gemtexter - One Bash script to rule it all](#gemtexter---one-bash-script-to-rule-it-all) +* [⇢ ⇢ Introduction](#introduction) +* [⇢ ⇢ ⇢ Motivation](#motivation) +* [⇢ ⇢ Output formats](#output-formats) +* [⇢ ⇢ Taking it as far as I should, but no farther](#taking-it-as-far-as-i-should-but-no-farther) +* [⇢ ⇢ ⇢ Modularization ](#modularization-) +* [⇢ ⇢ ⇢ Bash best practises and ShellCheck](#bash-best-practises-and-shellcheck) +* [⇢ ⇢ ⇢ Unit testing](#unit-testing) +* [⇢ ⇢ ⇢ HTML unit test example](#html-unit-test-example) +* [⇢ ⇢ ⇢ Markdown unit test example](#markdown-unit-test-example) +* [⇢ ⇢ Handcrafted HTML styles](#handcrafted-html-styles) +* [⇢ ⇢ Configurability](#configurability) +* [⇢ ⇢ Future features](#future-features) +* [⇢ ⇢ Conclusion](#conclusion) + +## Introduction + You might have read my previous blog posts about entering the Geminispace, where I pointed out the benefits of having and maintaining an internet presence there. This whole site (the blog and all other pages) is composed in the Gemtext markup language. This comes with the benefit that I can write content in my favourite text editor (Vim). -## Motivation +### Motivation Another benefit of using Gemini is that the Gemtext markup language is easy to parse. As my site is dual-hosted (Gemini+HTTP), I could, in theory, just write a shell script to deal with the conversion from Gemtext to HTML; there is no need for a full-featured programming language here. I have done a lot of Bash in the past, but I am also often revisiting old tools and techniques for refreshing and keeping the knowledge up to date here. diff --git a/gemfeed/2021-09-12-keep-it-simple-and-stupid.md b/gemfeed/2021-09-12-keep-it-simple-and-stupid.md index 4948944f..35215a19 100644 --- a/gemfeed/2021-09-12-keep-it-simple-and-stupid.md +++ b/gemfeed/2021-09-12-keep-it-simple-and-stupid.md @@ -17,25 +17,45 @@ -------------------- -------------------- ``` +## Table of Contents + +* [⇢ Keep it simple and stupid](#keep-it-simple-and-stupid) +* [⇢ ⇢ Introduction](#introduction) +* [⇢ ⇢ Need faster hardware](#need-faster-hardware) +* [⇢ ⇢ Too complex to be replaced](#too-complex-to-be-replaced) +* [⇢ ⇢ ⇢ On COBOL](#on-cobol) +* [⇢ ⇢ ⇢ On Kubernetes](#on-kubernetes) +* [⇢ ⇢ ⇢ The younger generation of IT professionals](#the-younger-generation-of-it-professionals) +* [⇢ ⇢ The bloated web](#the-bloated-web) +* [⇢ ⇢ Fancy log-management solutions](#fancy-log-management-solutions) +* [⇢ ⇢ More KISS](#more-kiss) +* [⇢ ⇢ ⇢ The Adslowbe PDF Reader](#the-adslowbe-pdf-reader) +* [⇢ ⇢ ⇢ The power of plain text files](#the-power-of-plain-text-files) +* [⇢ ⇢ ⇢ KISS for programmers](#kiss-for-programmers) +* [⇢ ⇢ When KISS is not KISS anymore](#when-kiss-is-not-kiss-anymore) +* [⇢ ⇢ Other relevant readings](#other-relevant-readings) + +## Introduction + A robust computer system must be kept simple and stupid (KISS). The fancier the system is, the more can break. Unfortunately, most systems tend to become complex and challenging to maintain in today's world. In the early days, so I was told, engineers understood every part of the system, but nowadays, we see more of the "lasagna" stack. One layer or framework is built on top of another layer, and in the end, nobody has got a clue what's going on. -# Need faster hardware +## Need faster hardware This not just makes the system much more complex, difficult to maintain and challenging to troubleshoot, but also slow. So more experts are needed to support it. Also, newer and faster hardware is required to make it run smoothly. Often, it's so much easier to buy speedier hardware than rewrite a whole system from scratch from the bottom-up. The latter would require much more resources in the short run, but in the long run, it should pay off. Unfortunately, many project owners scare away from it as they only want to get their project done and then move on. -# Too complex to be replaced +## Too complex to be replaced -## On COBOL +### On COBOL Have a look at COBOL, a prevalent programming language of the past. No one is learning COBOL in college or university anymore, but many legacy systems still require COBOL experts. Why is this? It's just too scary to write everything from scratch. There's too much COBOL code out there that can't be replaced from today to tomorrow. [https://nymag.com/intelligencer/2020/04/what-is-cobol-what-does-it-have-to-do-with-the-coronavirus.html](https://nymag.com/intelligencer/2020/04/what-is-cobol-what-does-it-have-to-do-with-the-coronavirus.html) -## On Kubernetes +### On Kubernetes Now have a look at Kubernetes (k8s), the current trendy infrastructure thing to use nowadays. Of course, there are many benefits of using k8s (auto-scaling, reproducible deployments, dynamic resource allocation and resource sharing, saving of hardware costs, good commercial for potential employees as it is the current hot sauce of infrastructure). But all of this also comes with costs: You need experts operating the k8s cluster (or you need to pay extra for a managed cluster in the cloud), increased complexity of the system (k8s comes with a steep learning curve). The latter not only applies to the engineers managing the k8s cluster - it also applies to the software engineers, who now have to develop 'cloud native' applications and, therefore, have to change how they developed software how they used to. They all need to be re-educated on what cloud-native means, and they also need to understand the key concepts of k8s for writing optimal software for it. -## The younger generation of IT professionals +### The younger generation of IT professionals Maybe the younger generation knows all of this already after graduation, but then they are missing other critical parts of the system for sure. I have seen engineers who knew about containers and how to configure resource restrictions for a Docker container managed via k8s but have never heard the terms Linux control groups and Linux namespaces. So obviously, there is some knowledge gap of the underlying architecture. This can be a big problem when you have to troubleshoot such a system during a production incident and k8s adds a lot of abstraction to the mix which doesn't make it easier. @@ -51,7 +71,7 @@ And here is something to smile about: [https://christine.website/blog/theres-a-node-2021-10-02](https://christine.website/blog/theres-a-node-2021-10-02) -# The bloated web +## The bloated web Another example is the modern web. Have you ever wondered why the internet becomes slower and slower nowadays? The modern web is so much like lasagna that I decided to use Gemini to be the primary protocol of my website. The HTML version of this website is just a fallback as many visitors don't know what Gemini is and don't have any compatible software installed for surfing the Geminispace: @@ -59,7 +79,7 @@ Another example is the modern web. Have you ever wondered why the internet becom The Gemtext protocol is KISS. There's no way to do other formattings than headings, links, paragraphs, lists, quotes, and bare text blocks (e.g., ASCII art or code snippets). There's no way to create bloated Gemini sites, and due to its limited capabilities, there's also no way to commercialise it (e.g. there's no good way to track the site visitors as things like cookies don't exist). By design, the Gemini protocol can't be extended, so there is no chance to abuse it even in the future. Gemini sites will stay KISS forever, and there won't be any fancy HTML/JavaScript frameworks like we see on the modern web. -# Fancy log-management solutions +## Fancy log-management solutions Yet another example I want to bring up is DTail, the distributed log tail program I wrote. There are many great and fancy log-management solutions available to choose from, and they all seem complex to set up and maintain. The ELK stack, for example, requires you to operate an ElasticSearch cluster (or multiple, if you are geo-redundant), Logstash (different configurations and instances, depending on your infrastructure) and a Kibana web-frontend (which also needs to be highly available). I have operated ElasticSearch clusters on multiple occasions, and I must say that it is not an easy task to optimise it for the particular workload you might encounter. I also have seen many ES clusters operated by other people, and I have seen these clusters failing a lot (so it's not just me). The reduced complexity of DTail also makes it more robust against outages. You won't troubleshoot your distributed application very well if the log management infrastructure isn't working either. @@ -67,23 +87,23 @@ Yet another example I want to bring up is DTail, the distributed log tail progra I don't say that the ELK stack doesn't work, but it requires experts and additional hardware resources to support it. But instead, if you keep your infrastructure simple (e.g. only use DTail), it will maintain pretty much by itself. -# More KISS +## More KISS -## The Adslowbe PDF Reader +### The Adslowbe PDF Reader Another perfect example is the Adobe PDF reader. How can it be that the inventor of the PDF format creates such a terrible user experience with its official reader? The reader is awful bloated, and slow. There are much better alternatives around (especially for Linux and other UNIX like operating systems, look at Zathura for example). I believe the reason Adobe's reader is like this is featuritis, and 90% of the users don't use 90% of all available features. Less is more; keep it simple and stupid. -## The power of plain text files +### The power of plain text files Speaking of file formats, never underestimate the power of plain text files. Plain text files don't require any special software to be opened, and they outlive the software which created them in the first place. You will still be able to read a plain text file on a modern computer system ten (or twenty) years from now, but you probably won't be able to read such an old version of an Adobe Photoshop image file if the software required for reading that format isn't supported anymore and doesn't run anymore on modern computers. -## KISS for programmers +### KISS for programmers Not to mention, keeping things simple and stupid also reduces the potential malicious attack surface. It's not just about the software and services you use and operate. It's also about the software you write. Here is a nice article about the KISS principle in software development: [https://thevaluable.dev/kiss-principle-explained/](https://thevaluable.dev/kiss-principle-explained/) -# When KISS is not KISS anymore +## When KISS is not KISS anymore There is, however, a trap. The more you spend time with things, the more these things feel natural to you and you become an expert. The more you become an expert, the more you introduce more abstractions and other clever ways of doing things. For you, things seem to be KISS still, but another person may not be an expert and might not understand what you do. One of the fundamental challenges is to keep things really KISS. You might add abstraction upon abstraction to a system and don't even notice it until it is too late. diff --git a/gemfeed/2021-11-29-bash-golf-part-1.md b/gemfeed/2021-11-29-bash-golf-part-1.md index 062a7cfd..d0e4fb26 100644 --- a/gemfeed/2021-11-29-bash-golf-part-1.md +++ b/gemfeed/2021-11-29-bash-golf-part-1.md @@ -14,6 +14,21 @@ jgs^^^^^^^`^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^ Art by Joan Stark ``` +## Table of Contents + +* [⇢ Bash Golf Part 1](#bash-golf-part-1) +* [⇢ ⇢ Introduction](#introduction) +* [⇢ ⇢ TCP/IP networking](#tcpip-networking) +* [⇢ ⇢ Process substitution](#process-substitution) +* [⇢ ⇢ Grouping](#grouping) +* [⇢ ⇢ Expansions](#expansions) +* [⇢ ⇢ - aka stdin and stdout placeholder](#--aka-stdin-and-stdout-placeholder) +* [⇢ ⇢ Alternative argument passing](#alternative-argument-passing) +* [⇢ ⇢ : aka the null command](#-aka-the-null-command) +* [⇢ ⇢ (No) floating point support](#no-floating-point-support) + +## Introduction + This is the first blog post about my Bash Golf series. This series is about random Bash tips, tricks and weirdnesses I came across. It's a collection of smaller articles I wrote in an older (in German language) blog, which I translated and refreshed with some new content. [2021-11-29 Bash Golf Part 1 (You are currently reading this)](./2021-11-29-bash-golf-part-1.md) diff --git a/gemfeed/2022-01-01-bash-golf-part-2.md b/gemfeed/2022-01-01-bash-golf-part-2.md index e7d11702..5f6df763 100644 --- a/gemfeed/2022-01-01-bash-golf-part-2.md +++ b/gemfeed/2022-01-01-bash-golf-part-2.md @@ -14,6 +14,20 @@ jgs^^^^^^^`^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^ Art by Joan Stark, mod. by Paul Buetow ``` +## Table of Contents + +* [⇢ Bash Golf Part 2](#bash-golf-part-2) +* [⇢ ⇢ Introduction](#introduction) +* [⇢ ⇢ Redirection](#redirection) +* [⇢ ⇢ HERE](#here) +* [⇢ ⇢ RANDOM](#random) +* [⇢ ⇢ set -x and set -e and pipefile](#set--x-and-set--e-and-pipefile) +* [⇢ ⇢ ⇢ -x](#-x) +* [⇢ ⇢ ⇢ -e](#-e) +* [⇢ ⇢ ⇢ pipefail](#pipefail) + +## Introduction + This is the second blog post about my Bash Golf series. This series is random Bash tips, tricks and weirdnesses I came across. It's a collection of smaller articles I wrote in an older (in German language) blog, which I translated and refreshed with some new content. [2021-11-29 Bash Golf Part 1](./2021-11-29-bash-golf-part-1.md) diff --git a/gemfeed/2022-03-06-the-release-of-dtail-4.0.0.md b/gemfeed/2022-03-06-the-release-of-dtail-4.0.0.md index eb50d81a..2474830e 100644 --- a/gemfeed/2022-03-06-the-release-of-dtail-4.0.0.md +++ b/gemfeed/2022-03-06-the-release-of-dtail-4.0.0.md @@ -16,6 +16,26 @@ | | ``` +## Table of Contents + +* [⇢ The release of DTail 4.0.0](#the-release-of-dtail-400) +* [⇢ ⇢ Introduction](#introduction) +* [⇢ ⇢ So, what's new in 4.0.0?](#so-whats-new-in-400) +* [⇢ ⇢ ⇢ Rewritten logging](#rewritten-logging) +* [⇢ ⇢ ⇢ Configurable terminal color codes](#configurable-terminal-color-codes) +* [⇢ ⇢ ⇢ Serverless mode](#serverless-mode) +* [⇢ ⇢ ⇢ Shorthand flags](#shorthand-flags) +* [⇢ ⇢ ⇢ Spartan (aka plain) mode](#spartan-aka-plain-mode) +* [⇢ ⇢ ⇢ Standard input pipe](#standard-input-pipe) +* [⇢ ⇢ ⇢ New command dtailhealth](#new-command-dtailhealth) +* [⇢ ⇢ ⇢ Improved documentation](#improved-documentation) +* [⇢ ⇢ ⇢ Integration testing suite](#integration-testing-suite) +* [⇢ ⇢ ⇢ Improved code](#improved-code) +* [⇢ ⇢ ⇢ Use of memory pools](#use-of-memory-pools) +* [⇢ ⇢ What's next](#whats-next) + +## Introduction + I have recently released DTail 4.0.0 and this blog post goes through all the new goodies. If you want to jump directly to DTail, do it here (there are nice animated gifs which demonstrates the usage pretty well): [https://dtail.dev](https://dtail.dev) diff --git a/gemfeed/2022-05-27-perl-is-still-a-great-choice.md b/gemfeed/2022-05-27-perl-is-still-a-great-choice.md index e56858e6..2849a07f 100644 --- a/gemfeed/2022-05-27-perl-is-still-a-great-choice.md +++ b/gemfeed/2022-05-27-perl-is-still-a-great-choice.md @@ -4,6 +4,18 @@ [![Comic source: XKCD](./perl-is-still-a-great-choice/regular_expressions.png "Comic source: XKCD")](./perl-is-still-a-great-choice/regular_expressions.png) +## Table of Contents + +* [⇢ Perl is still a great choice](#perl-is-still-a-great-choice) +* [⇢ ⇢ Introduction](#introduction) +* [⇢ ⇢ Write-only language](#write-only-language) +* [⇢ ⇢ Is Perl abandoned?](#is-perl-abandoned) +* [⇢ ⇢ Why use Perl as there are better alternatives?](#why-use-perl-as-there-are-better-alternatives) +* [⇢ ⇢ Why all the sigils? It looks like an exploding ASCII factory!!](#why-all-the-sigils-it-looks-like-an-exploding-ascii-factory) +* [⇢ ⇢ Where do I personally still use perl?](#where-do-i-personally-still-use-perl) + +## Introduction + Perl (the Practical Extraction and Report Language) is a battle-tested, mature, multi-paradigm dynamic programming language. Note that it's not called PERL, neither P.E.R.L. nor Pearl. "Perl" is the name of the language and `perl` the name of the interpreter or the interpreter command. Unfortunately (it makes me sad), Perl's popularity has been declining over the last years as Google trends shows: diff --git a/gemfeed/2022-07-30-lets-encrypt-with-openbsd-and-rex.md b/gemfeed/2022-07-30-lets-encrypt-with-openbsd-and-rex.md index b25f8669..409223fe 100644 --- a/gemfeed/2022-07-30-lets-encrypt-with-openbsd-and-rex.md +++ b/gemfeed/2022-07-30-lets-encrypt-with-openbsd-and-rex.md @@ -29,9 +29,28 @@ ASCII Art by John Savard ``` +## Table of Contents + +* [⇢ Let's Encrypt with OpenBSD and Rex](#lets-encrypt-with-openbsd-and-rex) +* [⇢ ⇢ Introduction](#introduction) +* [⇢ ⇢ ⇢ What's Let's Encrypt?](#whats-lets-encrypt) +* [⇢ ⇢ Meet `acme-client`](#meet-acme-client) +* [⇢ ⇢ Configuration](#configuration) +* [⇢ ⇢ ⇢ acme-client.conf](#acme-clientconf) +* [⇢ ⇢ ⇢ httpd.conf](#httpdconf) +* [⇢ ⇢ ⇢ CRON job](#cron-job) +* [⇢ ⇢ relayd.conf and smtpd.conf](#relaydconf-and-smtpdconf) +* [⇢ ⇢ Rexification](#rexification) +* [⇢ ⇢ ⇢ General ACME client configuration](#general-acme-client-configuration) +* [⇢ ⇢ ⇢ Service rexification ](#service-rexification-) +* [⇢ ⇢ All pieces together](#all-pieces-together) +* [⇢ ⇢ Conclusion](#conclusion) + +## Introduction + I was amazed at how easy it is to automatically generate and update Let's Encrypt certificates with OpenBSD. -## What's Let's Encrypt? +### What's Let's Encrypt? > Let's Encrypt is a non-profit certificate authority run by Internet Security Research Group that provides X.509 certificates for Transport Layer Security (TLS) encryption at no charge. It is the world's largest certificate authority, used by more than 265 million websites, with the goal of all websites being secure and using HTTPS. diff --git a/gemfeed/2022-08-27-gemtexter-1.1.0-lets-gemtext-again.md b/gemfeed/2022-08-27-gemtexter-1.1.0-lets-gemtext-again.md index 358c5866..5a1c9ad0 100644 --- a/gemfeed/2022-08-27-gemtexter-1.1.0-lets-gemtext-again.md +++ b/gemfeed/2022-08-27-gemtexter-1.1.0-lets-gemtext-again.md @@ -14,6 +14,22 @@ jgs `"""""""""` ``` +## Table of Contents + +* [⇢ Gemtexter 1.1.0 - Let's Gemtext again](#gemtexter-110---lets-gemtext-again) +* [⇢ ⇢ Introduction](#introduction) +* [⇢ ⇢ What's new?](#whats-new) +* [⇢ ⇢ ⇢ Automatic check for GNU version requirements](#automatic-check-for-gnu-version-requirements) +* [⇢ ⇢ ⇢ Backticks now produce `inline code blocks` in the HTML output](#backticks-now-produce-inline-code-blocks-in-the-html-output) +* [⇢ ⇢ ⇢ Cache for Atom feed generation](#cache-for-atom-feed-generation) +* [⇢ ⇢ ⇢ Input filter support](#input-filter-support) +* [⇢ ⇢ ⇢ Revamped `git` support](#revamped-git-support) +* [⇢ ⇢ ⇢ Addition of `htmlextras` and web font support](#addition-of-htmlextras-and-web-font-support) +* [⇢ ⇢ ⇢ Sub-section support](#sub-section-support) +* [⇢ ⇢ ⇢ More](#more) + +## Introduction + I proudly announce that I've released Gemtexter version `1.1.0`. What is Gemtexter? It's my minimalist static site generator for Gemini Gemtext, HTML and Markdown written in GNU Bash. [https://codeberg.org/snonux/gemtexter](https://codeberg.org/snonux/gemtexter) diff --git a/gemfeed/2022-10-30-installing-dtail-on-openbsd.md b/gemfeed/2022-10-30-installing-dtail-on-openbsd.md index 849f0407..bf3d9a96 100644 --- a/gemfeed/2022-10-30-installing-dtail-on-openbsd.md +++ b/gemfeed/2022-10-30-installing-dtail-on-openbsd.md @@ -39,6 +39,23 @@ ' ' ``` +## Table of Contents + +* [⇢ Installing DTail on OpenBSD](#installing-dtail-on-openbsd) +* [⇢ ⇢ Introduction](#introduction) +* [⇢ ⇢ Compile it](#compile-it) +* [⇢ ⇢ Install it](#install-it) +* [⇢ ⇢ ⇢ Rexification](#rexification) +* [⇢ ⇢ Configure it](#configure-it) +* [⇢ ⇢ ⇢ Rexification](#rexification) +* [⇢ ⇢ Update the key cache for it](#update-the-key-cache-for-it) +* [⇢ ⇢ ⇢ Rexification](#rexification) +* [⇢ ⇢ Start it](#start-it) +* [⇢ ⇢ Use it](#use-it) +* [⇢ ⇢ Conclusions](#conclusions) + +## Introduction + This will be a quick blog post, as I am busy with my personal life now. I have relocated to a different country and am still busy arranging things. So bear with me :-) In this post, I want to give a quick overview (or how-to) about installing DTail on OpenBSD, as the official documentation only covers Red Hat and Fedora Linux! And this blog post will also be used as my reference! diff --git a/gemfeed/2023-03-25-gemtexter-2.0.0-lets-gemtext-again-2.md b/gemfeed/2023-03-25-gemtexter-2.0.0-lets-gemtext-again-2.md index 422932e5..8b737689 100644 --- a/gemfeed/2023-03-25-gemtexter-2.0.0-lets-gemtext-again-2.md +++ b/gemfeed/2023-03-25-gemtexter-2.0.0-lets-gemtext-again-2.md @@ -15,6 +15,19 @@ mod. by Paul Buetow `"""""""""` ``` +## Table of Contents + +* [⇢ Gemtexter 2.0.0 - Let's Gemtext again²](#gemtexter-200---lets-gemtext-again) +* [⇢ ⇢ Introduction](#introduction) +* [⇢ ⇢ Minimal template engine](#minimal-template-engine) +* [⇢ ⇢ Added hooks](#added-hooks) +* [⇢ ⇢ Use of safer Bash options](#use-of-safer-bash-options) +* [⇢ ⇢ Meta cache made obsolete](#meta-cache-made-obsolete) +* [⇢ ⇢ XMLLint support](#xmllint-support) +* [⇢ ⇢ More](#more) + +## Introduction + I proudly announce that I've released Gemtexter version `2.0.0`. What is Gemtexter? It's my minimalist static site generator for Gemini Gemtext, HTML and Markdown written in GNU Bash. [https://codeberg.org/snonux/gemtexter](https://codeberg.org/snonux/gemtexter) diff --git a/gemfeed/2023-04-09-algorithms-and-data-structures-in-golang-part-1.md b/gemfeed/2023-04-09-algorithms-and-data-structures-in-golang-part-1.md index 9fd31bff..dd8fc38a 100644 --- a/gemfeed/2023-04-09-algorithms-and-data-structures-in-golang-part-1.md +++ b/gemfeed/2023-04-09-algorithms-and-data-structures-in-golang-part-1.md @@ -16,6 +16,18 @@ | | ``` +## Table of Contents + +* [⇢ Algorithms and Data Structures in Go - Part 1](#algorithms-and-data-structures-in-go---part-1) +* [⇢ ⇢ Introduction](#introduction) +* [⇢ ⇢ Type constraints](#type-constraints) +* [⇢ ⇢ ArrayList](#arraylist) +* [⇢ ⇢ Helper methods](#helper-methods) +* [⇢ ⇢ Sleep sort](#sleep-sort) +* [⇢ ⇢ ⇢ Testing](#testing) + +## Introduction + This is the first blog post about my Algorithms and Data Structures in Go series. I am not a Software Developer in my day job. In my current role, programming and scripting skills are desirable but not mandatory. I have been learning about Data Structures and Algorithms many years ago at University. I thought it would be fun to revisit/refresh my knowledge here and implement many of the algorithms in Go. [2023-04-09 Algorithms and Data Structures in Go - Part 1 (You are currently reading this)](./2023-04-09-algorithms-and-data-structures-in-golang-part-1.md) diff --git a/gemfeed/2023-05-01-unveiling-guprecords:-uptime-records-with-raku.md b/gemfeed/2023-05-01-unveiling-guprecords:-uptime-records-with-raku.md index b4fe170e..c1136931 100644 --- a/gemfeed/2023-05-01-unveiling-guprecords:-uptime-records-with-raku.md +++ b/gemfeed/2023-05-01-unveiling-guprecords:-uptime-records-with-raku.md @@ -19,7 +19,15 @@ +-----+-----------------+-----------------------------+ ``` -# Introduction +## Table of Contents + +* [⇢ Unveiling `guprecords.raku`: Global Uptime Records with Raku](#unveiling-guprecordsraku-global-uptime-records-with-raku) +* [⇢ ⇢ Introduction](#introduction) +* [⇢ ⇢ How Guprecords works](#how-guprecords-works) +* [⇢ ⇢ Example](#example) +* [⇢ ⇢ Conclusion](#conclusion) + +## Introduction For fun, I am tracking the uptime of various personal machines (servers, laptops, workstations...). I have been doing this for over ten years now, so I have a lot of statistics collected. diff --git a/gemfeed/2023-05-06-the-obstacle-is-the-way-book-notes.md b/gemfeed/2023-05-06-the-obstacle-is-the-way-book-notes.md index 9c10dc32..8a2e31a9 100644 --- a/gemfeed/2023-05-06-the-obstacle-is-the-way-book-notes.md +++ b/gemfeed/2023-05-06-the-obstacle-is-the-way-book-notes.md @@ -2,6 +2,25 @@ > Published at 2023-05-06T17:23:16+03:00 +## Table of Contents + +* [⇢ "The Obstacle is the Way" book notes](#the-obstacle-is-the-way-book-notes) +* [⇢ ⇢ Introduction](#introduction) +* [⇢ ⇢ Reframe your perspective](#reframe-your-perspective) +* [⇢ ⇢ Embrace rationality](#embrace-rationality) +* [⇢ ⇢ Control your response](#control-your-response) +* [⇢ ⇢ Practice emotional and physical resilience](#practice-emotional-and-physical-resilience) +* [⇢ ⇢ Persistence and patience](#persistence-and-patience) +* [⇢ ⇢ Embrace failure](#embrace-failure) +* [⇢ ⇢ Be adaptable](#be-adaptable) +* [⇢ ⇢ Embrace non-action](#embrace-non-action) +* [⇢ ⇢ Leverage crisis](#leverage-crisis) +* [⇢ ⇢ Build your inner citadel](#build-your-inner-citadel) +* [⇢ ⇢ Love everything that happens](#love-everything-that-happens) +* [⇢ ⇢ Conclusion](#conclusion) + +## Introduction + These are my personal takeaways after reading "The Obstacle Is the Way" by Ryan Holiday. This is mainly for my own use, but you might find it helpful too. @@ -27,7 +46,6 @@ We spend a lot of time trying to get things perfect and look at the rules, but w Don't always try to use the front door; a backdoor could open. It's nonsense. Don't fight the judo master with judo. Non-action can be action, exposing the weaknesses of others. - ## Embrace rationality It is a superpower to see things rationally when others are fearful. Focus on the reality of the situation without letting emotions, such as anger, cloud your judgment. This ability will enable you to make better decisions in adversity. Ability to see things what they really are. E.g. wine is old fermented grapes, or other people behaving like animals during a fight. Show the middle finger if someone persists on the stupid rules occasionally. diff --git a/gemfeed/2023-06-01-kiss-server-monitoring-with-gogios.md b/gemfeed/2023-06-01-kiss-server-monitoring-with-gogios.md index a9a6393b..d9a34b54 100644 --- a/gemfeed/2023-06-01-kiss-server-monitoring-with-gogios.md +++ b/gemfeed/2023-06-01-kiss-server-monitoring-with-gogios.md @@ -4,6 +4,24 @@ [![Gogios logo](./kiss-server-monitoring-with-gogios/gogios-small.png "Gogios logo")](./kiss-server-monitoring-with-gogios/gogios-small.png) +## Table of Contents + +* [⇢ KISS server monitoring with Gogios](#kiss-server-monitoring-with-gogios) +* [⇢ ⇢ Introduction](#introduction) +* [⇢ ⇢ Motivation](#motivation) +* [⇢ ⇢ Features](#features) +* [⇢ ⇢ Example alert](#example-alert) +* [⇢ ⇢ Installation](#installation) +* [⇢ ⇢ ⇢ Compiling and installing Gogios](#compiling-and-installing-gogios) +* [⇢ ⇢ ⇢ Setting up user, group and directories](#setting-up-user-group-and-directories) +* [⇢ ⇢ ⇢ Installing monitoring plugins](#installing-monitoring-plugins) +* [⇢ ⇢ Configuration](#configuration) +* [⇢ ⇢ ⇢ MTA](#mta) +* [⇢ ⇢ ⇢ Configuring Gogios](#configuring-gogios) +* [⇢ ⇢ Running Gogios](#running-gogios) +* [⇢ ⇢ ⇢ High-availability](#high-availability) +* [⇢ ⇢ Conclusion:](#conclusion) + ## Introduction Gogios is a minimalistic and easy-to-use monitoring tool I programmed in Google Go designed specifically for small-scale self-hosted servers and virtual machines. The primary purpose of Gogios is to monitor my personal server infrastructure for `foo.zone`, my MTAs, my authoritative DNS servers, my NextCloud, Wallabag and Anki sync server installations, etc. diff --git a/gemfeed/2023-07-17-career-guide-and-soft-skills-book-notes.md b/gemfeed/2023-07-17-career-guide-and-soft-skills-book-notes.md index cab2e3ff..9cd6ca62 100644 --- a/gemfeed/2023-07-17-career-guide-and-soft-skills-book-notes.md +++ b/gemfeed/2023-07-17-career-guide-and-soft-skills-book-notes.md @@ -2,6 +2,41 @@ > Published at 2023-07-17T04:56:20+03:00 +## Table of Contents + +* [⇢ "Software Developmers Career Guide and Soft Skills" book notes](#software-developmers-career-guide-and-soft-skills-book-notes) +* [⇢ Introduction](#introduction) +* [⇢ Improve](#improve) +* [⇢ ⇢ Always learn new things](#always-learn-new-things) +* [⇢ ⇢ Set goals](#set-goals) +* [⇢ ⇢ Ratings](#ratings) +* [⇢ ⇢ Promotions](#promotions) +* [⇢ ⇢ Finish things](#finish-things) +* [⇢ ⇢ Expand the empire](#expand-the-empire) +* [⇢ ⇢ Be pragmatic and also manage your time](#be-pragmatic-and-also-manage-your-time) +* [⇢ ⇢ ⇢ The quota system](#the-quota-system) +* [⇢ ⇢ ⇢ Don't waste time](#dont-waste-time) +* [⇢ ⇢ ⇢ Habits](#habits) +* [⇢ Work-life balance](#work-life-balance) +* [⇢ ⇢ Mental health](#mental-health) +* [⇢ ⇢ Physical health](#physical-health) +* [⇢ ⇢ No drama](#no-drama) +* [⇢ Personal brand](#personal-brand) +* [⇢ ⇢ Market yourself](#market-yourself) +* [⇢ ⇢ Networking](#networking) +* [⇢ ⇢ Public speaking](#public-speaking) +* [⇢ New job](#new-job) +* [⇢ ⇢ For the interview](#for-the-interview) +* [⇢ ⇢ Find the right type of company](#find-the-right-type-of-company) +* [⇢ ⇢ Apply for the new job](#apply-for-the-new-job) +* [⇢ ⇢ Negotiation](#negotiation) +* [⇢ ⇢ Leaving the old job](#leaving-the-old-job) +* [⇢ Other things](#other-things) +* [⇢ ⇢ Testing](#testing) +* [⇢ ⇢ Books to read](#books-to-read) + +# Introduction + These notes are of two books by "John Sommez" I found helpful. I also added some of my own keypoints to it. These notes are mainly for my own use, but you might find them helpful, too. ``` diff --git a/gemfeed/2023-07-21-gemtexter-2.1.0-lets-gemtext-again-3.md b/gemfeed/2023-07-21-gemtexter-2.1.0-lets-gemtext-again-3.md index 9d3e58f2..427acce8 100644 --- a/gemfeed/2023-07-21-gemtexter-2.1.0-lets-gemtext-again-3.md +++ b/gemfeed/2023-07-21-gemtexter-2.1.0-lets-gemtext-again-3.md @@ -15,6 +15,20 @@ mod. by Paul Buetow `"""""""""` ``` +## Table of Contents + +* [⇢ Gemtexter 2.1.0 - Let's Gemtext again³](#gemtexter-210---lets-gemtext-again) +* [⇢ ⇢ Introduction](#introduction) +* [⇢ ⇢ Why Bash?](#why-bash) +* [⇢ ⇢ Switch to GPL3 license](#switch-to-gpl3-license) +* [⇢ ⇢ Source code highlighting support](#source-code-highlighting-support) +* [⇢ ⇢ HTML exact variant](#html-exact-variant) +* [⇢ ⇢ Use of Hack webfont by default](#use-of-hack-webfont-by-default) +* [⇢ ⇢ HTML Mastodon verification support](#html-mastodon-verification-support) +* [⇢ ⇢ More](#more) + +## Introduction + I proudly announce that I've released Gemtexter version `2.1.0`. What is Gemtexter? It's my minimalist static site generator for Gemini Gemtext, HTML and Markdown, written in GNU Bash. [https://codeberg.org/snonux/gemtexter](https://codeberg.org/snonux/gemtexter) diff --git a/gemfeed/2023-09-25-dtail-usage-examples.md b/gemfeed/2023-09-25-dtail-usage-examples.md index 6b85775e..6eeb4521 100644 --- a/gemfeed/2023-09-25-dtail-usage-examples.md +++ b/gemfeed/2023-09-25-dtail-usage-examples.md @@ -2,6 +2,22 @@ > Published at 2023-09-25T14:57:42+03:00 +## Table of Contents + +* [⇢ DTail usage examples](#dtail-usage-examples) +* [⇢ ⇢ Introduction](#introduction) +* [⇢ ⇢ Following logs](#following-logs) +* [⇢ ⇢ Aggregating logs](#aggregating-logs) +* [⇢ ⇢ How to use `dcat`](#how-to-use-dcat) +* [⇢ ⇢ How to use `dgrep`](#how-to-use-dgrep) +* [⇢ ⇢ How to use `dmap`](#how-to-use-dmap) +* [⇢ ⇢ How to use the DTail serverless mode](#how-to-use-the-dtail-serverless-mode) +* [⇢ ⇢ ⇢ Serverless map-reduce query](#serverless-map-reduce-query) +* [⇢ ⇢ ⇢ Aggregating CSV files](#aggregating-csv-files) +* [⇢ ⇢ ⇢ Other serverless commands](#other-serverless-commands) + +## Introduction + Hey there. As I am pretty busy this month personally (I am now on Paternity Leave) and as I still want to post once monthly, the blog post of this month will only be some DTail usage examples. They're from the DTail documentation, but not all readers of my blog may be aware of those! DTail is a distributed DevOps tool for tailing, grepping, catting logs and other text files on many remote machines at once which I programmed in Go. diff --git a/gemfeed/2023-10-29-kiss-static-web-photo-albums-with-photoalbum.sh.md b/gemfeed/2023-10-29-kiss-static-web-photo-albums-with-photoalbum.sh.md index ad26ab09..e9321c24 100644 --- a/gemfeed/2023-10-29-kiss-static-web-photo-albums-with-photoalbum.sh.md +++ b/gemfeed/2023-10-29-kiss-static-web-photo-albums-with-photoalbum.sh.md @@ -19,6 +19,18 @@ '._____________________________________________.' ``` +## Table of Contents + +* [⇢ KISS static web photo albums with `photoalbum.sh`](#kiss-static-web-photo-albums-with-photoalbumsh) +* [⇢ ⇢ Motivation](#motivation) +* [⇢ ⇢ Introducing `photoalbum.sh`](#introducing-photoalbumsh) +* [⇢ ⇢ Installation](#installation) +* [⇢ ⇢ Setting it up](#setting-it-up) +* [⇢ ⇢ Generating the static photo album](#generating-the-static-photo-album) +* [⇢ ⇢ Cleaning it up](#cleaning-it-up) +* [⇢ ⇢ HTML templates](#html-templates) +* [⇢ ⇢ Conclusion](#conclusion) + ## Motivation Once in a while, I share photos on the inter-web with either family and friends or on my The Irregular Ninja photo site. One hobby of mine is photography (even though I don't have enough time for it - so I am primarily a point-and-shoot photographer). diff --git a/gemfeed/2023-11-11-mind-management-book-notes.md b/gemfeed/2023-11-11-mind-management-book-notes.md index be1250aa..9efc6f85 100644 --- a/gemfeed/2023-11-11-mind-management-book-notes.md +++ b/gemfeed/2023-11-11-mind-management-book-notes.md @@ -2,6 +2,21 @@ > Published at 2023-11-11T22:21:47+02:00 +## Table of Contents + +* [⇢ "Mind Management" book notes](#mind-management-book-notes) +* [⇢ ⇢ Introduction](#introduction) +* [⇢ ⇢ Empty slots in the calendar](#empty-slots-in-the-calendar) +* [⇢ ⇢ When you safe time...](#when-you-safe-time) +* [⇢ ⇢ Follow your mood](#follow-your-mood) +* [⇢ ⇢ Boosting creativity](#boosting-creativity) +* [⇢ ⇢ The right mood for the task at hand](#the-right-mood-for-the-task-at-hand) +* [⇢ ⇢ Creativity hacks](#creativity-hacks) +* [⇢ ⇢ Planning and strategizing](#planning-and-strategizing) +* [⇢ ⇢ Fake it until you make it. ](#fake-it-until-you-make-it-) + +## Introduction + These are my personal takeaways after reading "Mind Management" by David Kadavy. Note that the book contains much more knowledge wisdom and that these notes only contain points I personally found worth writing down. This is mainly for my own use, but you might find it helpful too. ``` diff --git a/gemfeed/2023-12-10-bash-golf-part-3.md b/gemfeed/2023-12-10-bash-golf-part-3.md index 5efbb1e8..d4619f9b 100644 --- a/gemfeed/2023-12-10-bash-golf-part-3.md +++ b/gemfeed/2023-12-10-bash-golf-part-3.md @@ -14,6 +14,21 @@ jgs^^^^^^^`^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^ Art by Joan Stark, mod. by Paul Buetow ``` +## Table of Contents + +* [⇢ Bash Golf Part 3](#bash-golf-part-3) +* [⇢ ⇢ Introduction](#introduction) +* [⇢ ⇢ `FUNCNAME`](#funcname) +* [⇢ ⇢ `:(){ :|:& };:`](#--) +* [⇢ ⇢ Inner functions](#inner-functions) +* [⇢ ⇢ Exporting functions](#exporting-functions) +* [⇢ ⇢ Dynamic variables with `local`](#dynamic-variables-with-local) +* [⇢ ⇢ `if` conditionals](#if-conditionals) +* [⇢ ⇢ Multi-line comments](#multi-line-comments) +* [⇢ ⇢ Don't change it while it's executed](#dont-change-it-while-its-executed) + +## Introduction + This is the third blog post about my Bash Golf series. This series is random Bash tips, tricks, and weirdnesses I have encountered over time. [2021-11-29 Bash Golf Part 1](./2021-11-29-bash-golf-part-1.md) diff --git a/gemfeed/2024-03-03-a-fine-fyne-android-app-for-quickly-logging-ideas-programmed-in-golang.md b/gemfeed/2024-03-03-a-fine-fyne-android-app-for-quickly-logging-ideas-programmed-in-golang.md index 9da20108..6c0421df 100644 --- a/gemfeed/2024-03-03-a-fine-fyne-android-app-for-quickly-logging-ideas-programmed-in-golang.md +++ b/gemfeed/2024-03-03-a-fine-fyne-android-app-for-quickly-logging-ideas-programmed-in-golang.md @@ -2,6 +2,14 @@ > Published at 2024-03-03T00:07:21+02:00 +## Table of Contents + +* [⇢ A fine Fyne Android app for quickly logging ideas programmed in Go](#a-fine-fyne-android-app-for-quickly-logging-ideas-programmed-in-go) +* [⇢ ⇢ Introduction](#introduction) +* [⇢ ⇢ All easy-peasy?](#all-easy-peasy) + +## Introduction + I am an ideas person. I find myself frequently somewhere on the streets with an idea in my head but no paper journal noting it down. I have tried many note apps for my Android (I use GrapheneOS) phone. Most of them either don't do what I want, are proprietary software, require Google Play services (I have the main profile on my phone de-googled) or are too bloated. I was never into mobile app development, as I'm not too fond of the complexity of the developer toolchains. I don't want to use Android Studio (as a NeoVim user), and I don't want to use Java or Kotlin. I want to use a language I know (and like) for mobile app development. Go would be one of those languages. diff --git a/gemfeed/2024-04-01-KISS-high-availability-with-OpenBSD.md b/gemfeed/2024-04-01-KISS-high-availability-with-OpenBSD.md index 0b1680d8..6402b1de 100644 --- a/gemfeed/2024-04-01-KISS-high-availability-with-OpenBSD.md +++ b/gemfeed/2024-04-01-KISS-high-availability-with-OpenBSD.md @@ -30,6 +30,7 @@ _____|_:_:_| (o)-(o) |_:_:_|--'`-. ,--. ksh under-water (((\'/ ## Table of Contents * [⇢ KISS high-availability with OpenBSD](#kiss-high-availability-with-openbsd) +* [⇢ ⇢ Introduction](#introduction) * [⇢ ⇢ My auto-failover requirements](#my-auto-failover-requirements) * [⇢ ⇢ My HA solution](#my-ha-solution) * [⇢ ⇢ ⇢ Only OpenBSD base installation required](#only-openbsd-base-installation-required) @@ -41,6 +42,8 @@ _____|_:_:_| (o)-(o) |_:_:_|--'`-. ,--. ksh under-water (((\'/ * [⇢ ⇢ ⇢ Rex automation](#rex-automation) * [⇢ ⇢ More HA](#more-ha) +## Introduction + I have always wanted a highly available setup for my personal websites. I could have used off-the-shelf hosting solutions or hosted my sites in an AWS S3 bucket. I have used technologies like (in unsorted and slightly unrelated order) BGP, LVS/IPVS, ldirectord, Pacemaker, STONITH, scripted VIP failover via ARP, heartbeat, heartbeat2, Corosync, keepalived, DRBD, and commercial F5 Load Balancers for high availability at work. But still, my personal sites were never highly available. All those technologies are great for professional use, but I was looking for something much more straightforward for my personal space - something as KISS (keep it simple and stupid) as possible. diff --git a/gemfeed/2024-05-01-slow-productivity-book-notes.md b/gemfeed/2024-05-01-slow-productivity-book-notes.md index 0365ca66..138cec50 100644 --- a/gemfeed/2024-05-01-slow-productivity-book-notes.md +++ b/gemfeed/2024-05-01-slow-productivity-book-notes.md @@ -2,6 +2,18 @@ > Published at 2024-04-27T14:18:51+03:00 +## Table of Contents + +* [⇢ "Slow Productivity" book notes](#slow-productivity-book-notes) +* [⇢ ⇢ Introduction](#introduction) +* [⇢ ⇢ Pseudo-productivity and Shallow work](#pseudo-productivity-and-shallow-work) +* [⇢ ⇢ Accomplishments without burnout](#accomplishments-without-burnout) +* [⇢ ⇢ Do fewer things](#do-fewer-things) +* [⇢ ⇢ Work at a natural pace](#work-at-a-natural-pace) +* [⇢ ⇢ Obsess over quality ](#obsess-over-quality-) + +## Introduction + These are my personal takeaways after reading "Slow Productivity - The lost Art of Accomplishment Without Burnout" by Cal Newport. The case studies in this book were a bit long, but they appeared to be well-researched. I will only highlight the interesting, actionable items in the book notes. diff --git a/gemfeed/2024-05-03-projects-i-currently-dont-have-time-for.md b/gemfeed/2024-05-03-projects-i-currently-dont-have-time-for.md index 984f3c3d..4d9f1586 100644 --- a/gemfeed/2024-05-03-projects-i-currently-dont-have-time-for.md +++ b/gemfeed/2024-05-03-projects-i-currently-dont-have-time-for.md @@ -15,10 +15,6 @@ Art by Laura Brown ``` -## Introduction - -Over the years, I have collected many ideas for my personal projects and noted them down. I am currently in the process of cleaning up all my notes and reviewing those ideas. I don’t have time for the ones listed here and won’t have any soon due to other commitments and personal projects. So, in order to "get rid of them" from my notes folder, I decided to simply put them in this blog post so that those ideas don't get lost. Maybe I will pick up one or another idea someday in the future, but for now, they are all put on ice in favor of other personal projects or family time. - ## Table of Contents * [⇢ Projects I currently don't have time for](#projects-i-currently-dont-have-time-for) @@ -57,6 +53,10 @@ Over the years, I have collected many ideas for my personal projects and noted t * [⇢ ⇢ ⇢ Project secure](#project-secure) * [⇢ ⇢ ⇢ CPU utilisation is all wrong](#cpu-utilisation-is-all-wrong) +## Introduction + +Over the years, I have collected many ideas for my personal projects and noted them down. I am currently in the process of cleaning up all my notes and reviewing those ideas. I don’t have time for the ones listed here and won’t have any soon due to other commitments and personal projects. So, in order to "get rid of them" from my notes folder, I decided to simply put them in this blog post so that those ideas don't get lost. Maybe I will pick up one or another idea someday in the future, but for now, they are all put on ice in favor of other personal projects or family time. + ## Hardware projects I don't have time for ### I use Arch, btw! diff --git a/gemfeed/2024-07-07-the-stoic-challenge-book-notes.md b/gemfeed/2024-07-07-the-stoic-challenge-book-notes.md index 1859ebf0..ba326c66 100644 --- a/gemfeed/2024-07-07-the-stoic-challenge-book-notes.md +++ b/gemfeed/2024-07-07-the-stoic-challenge-book-notes.md @@ -2,6 +2,15 @@ > Published at 2024-07-07T12:46:55+03:00 +## Table of Contents + +* [⇢ "The Stoic Challenge" book notes](#the-stoic-challenge-book-notes) +* [⇢ ⇢ Introduction](#introduction) +* [⇢ ⇢ Negative visualization](#negative-visualization) +* [⇢ ⇢ Oh, nice trick, you stoic "god"! ;-)](#oh-nice-trick-you-stoic-god--) + +## Introduction + These are my personal takeaways after reading "The Stoic Challenge: A Philosopher's Guide to Becoming Tougher, Calmer, and More Resilient" by William B. Irvine. ``` diff --git a/gemfeed/2024-08-05-typing-127.1-words-per-minute.md b/gemfeed/2024-08-05-typing-127.1-words-per-minute.md index 40f2e594..eb03a43a 100644 --- a/gemfeed/2024-08-05-typing-127.1-words-per-minute.md +++ b/gemfeed/2024-08-05-typing-127.1-words-per-minute.md @@ -17,6 +17,37 @@ Nieminen Mika ``` +## Table of Contents + +* [⇢ Typing `127.1` words per minute (`>100wpm average`)](#typing-1271-words-per-minute-100wpm-average) +* [⇢ ⇢ Introduction](#introduction) +* [⇢ ⇢ Kinesis review](#kinesis-review) +* [⇢ ⇢ ⇢ Top build quality](#top-build-quality) +* [⇢ ⇢ ⇢ Bluetooth connectivity](#bluetooth-connectivity) +* [⇢ ⇢ ⇢ Gateron Brown key switches](#gateron-brown-key-switches) +* [⇢ ⇢ ⇢ Keycaps](#keycaps) +* [⇢ ⇢ ⇢ Keymap editor](#keymap-editor) +* [⇢ ⇢ First steps](#first-steps) +* [⇢ ⇢ Considering alternate layouts](#considering-alternate-layouts) +* [⇢ ⇢ Training how to type](#training-how-to-type) +* [⇢ ⇢ ⇢ Tools](#tools) +* [⇢ ⇢ My `keybr.com` statistics](#my-keybrcom-statistics) +* [⇢ ⇢ Tips and tricks](#tips-and-tricks) +* [⇢ ⇢ ⇢ Relax](#relax) +* [⇢ ⇢ ⇢ Focus on accuracy first](#focus-on-accuracy-first) +* [⇢ ⇢ ⇢ Chording](#chording) +* [⇢ ⇢ ⇢ Punctuation and Capitalization](#punctuation-and-capitalization) +* [⇢ ⇢ ⇢ Reverse shifting](#reverse-shifting) +* [⇢ ⇢ ⇢ Enter the flow state](#enter-the-flow-state) +* [⇢ ⇢ ⇢ Repeat every word](#repeat-every-word) +* [⇢ ⇢ ⇢ Don't use the same finger for two consecutive keystrokes](#dont-use-the-same-finger-for-two-consecutive-keystrokes) +* [⇢ ⇢ ⇢ Warm-up](#warm-up) +* [⇢ ⇢ Travel keyboard](#travel-keyboard) +* [⇢ ⇢ Upcoming custom Kinesis build](#upcoming-custom-kinesis-build) +* [⇢ ⇢ Conclusion](#conclusion) + +## Introduction + After work one day, I noticed some discomfort in my right wrist. Upon research, it appeared to be a mild case of Repetitive Strain Injury (RSI). Initially, I thought that this would go away after a while, but after a week it became even worse. This led me to consider potential causes such as poor posture or keyboard use habits. As an enthusiast of keyboards, I experimented with ergonomic concave ortholinear split keyboards. Wait, what?... * Concave: Some fingers are longer than others. A concave keyboard makes it so that the keycaps meant to be pressed by the longer fingers are further down (e.g., left middle finger for `e` on a Qwerty layout), and keycaps meant to be pressed by shorter fingers are further up (e.g., right pinky finger for the letter `p`). -- cgit v1.2.3 From da0afc2c4c562709f4f29372493ad0bb12a11e78 Mon Sep 17 00:00:00 2001 From: Paul Buetow Date: Sun, 25 Aug 2024 23:05:22 +0300 Subject: Update content for md --- gemfeed/2024-08-05-typing-127.1-words-per-minute.md | 5 +++-- 1 file changed, 3 insertions(+), 2 deletions(-) (limited to 'gemfeed') diff --git a/gemfeed/2024-08-05-typing-127.1-words-per-minute.md b/gemfeed/2024-08-05-typing-127.1-words-per-minute.md index eb03a43a..7173ce37 100644 --- a/gemfeed/2024-08-05-typing-127.1-words-per-minute.md +++ b/gemfeed/2024-08-05-typing-127.1-words-per-minute.md @@ -135,11 +135,11 @@ I wrote myself a small Ruby script that would randomly select a paragraph from o Overall, I trained for around 4 months in more than 5,000 sessions. My top speed in a session was 127.1wpm (up from barely 10wpm at the beginning). -[![./typing-127.1-words-per-minute/all-time-stats.png](./typing-127.1-words-per-minute/all-time-stats.png)](./typing-127.1-words-per-minute/all-time-stats.png) +[![All time stats](./typing-127.1-words-per-minute/all-time-stats.png "All time stats")](./typing-127.1-words-per-minute/all-time-stats.png) My overall average speed over those 5,000 sessions was 80wpm. The average speed over the last week was over 100wpm. The green line represents the wpm average (increasing trend), the purple line represents the number of keys in the practices (not much movement there, as all keys are unlocked), and the red line represents the average typing accuracy. -[![./typing-127.1-words-per-minute/typing-speed-over-lessons.png](./typing-127.1-words-per-minute/typing-speed-over-lessons.png)](./typing-127.1-words-per-minute/typing-speed-over-lessons.png) +[![Typing speed over leson](./typing-127.1-words-per-minute/typing-speed-over-lessons.png "Typing speed over leson")](./typing-127.1-words-per-minute/typing-speed-over-lessons.png) Around the middle, you see a break-in of the wpm average value. This was where I swapped the `p` and `;` keys, but after some retraining, I came back to the previous level and beyond. @@ -150,6 +150,7 @@ These are some tips and tricks I learned along the way to improve my typing spee ### Relax It's easy to get cramped when trying to hit this new wpm mark, but this is just holding you back. Relax and type at a natural pace. Now I also understand why my Katate Sensei back in London kept screaming "RELAAAX" at me during practice.... It didn't help much back then, though, as it is difficult to relax while someone screams at you! + ### Focus on accuracy first This goes with the previous point. Instead of trying to speed through sessions as quickly as possible, slow down and try to type the words correctly—so don't rush it. If you aren't fast yet, the reason is that your brain hasn't trained enough. It will come over time, and you will be faster. -- cgit v1.2.3 From dbeb611de4607e39de7880e2e9ca36ff1237c444 Mon Sep 17 00:00:00 2001 From: Paul Buetow Date: Sun, 25 Aug 2024 23:08:27 +0300 Subject: test --- gemfeed/2024-05-03-projects-i-currently-dont-have-time-for.md | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) (limited to 'gemfeed') diff --git a/gemfeed/2024-05-03-projects-i-currently-dont-have-time-for.md b/gemfeed/2024-05-03-projects-i-currently-dont-have-time-for.md index 4d9f1586..7161f7e2 100644 --- a/gemfeed/2024-05-03-projects-i-currently-dont-have-time-for.md +++ b/gemfeed/2024-05-03-projects-i-currently-dont-have-time-for.md @@ -19,7 +19,7 @@ Art by Laura Brown * [⇢ Projects I currently don't have time for](#projects-i-currently-dont-have-time-for) * [⇢ ⇢ Introduction](#introduction) -* [⇢ ⇢ Hardware projects I don't have time for](#hardware-projects-i-dont-have-time-for) +* [⇢ ⇢ Hardware projects I don't have time for](#hardware-projects-i-don't-have-time-for) * [⇢ ⇢ ⇢ I use Arch, btw!](#i-use-arch-btw) * [⇢ ⇢ ⇢ OpenBSD home router](#openbsd-home-router) * [⇢ ⇢ ⇢ Pi-Hole server](#pi-hole-server) -- cgit v1.2.3 From b58592661096a793959d79750907a08a086b7d65 Mon Sep 17 00:00:00 2001 From: Paul Buetow Date: Sun, 25 Aug 2024 23:08:52 +0300 Subject: test --- gemfeed/2024-05-03-projects-i-currently-dont-have-time-for.md | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) (limited to 'gemfeed') diff --git a/gemfeed/2024-05-03-projects-i-currently-dont-have-time-for.md b/gemfeed/2024-05-03-projects-i-currently-dont-have-time-for.md index 7161f7e2..feb08a94 100644 --- a/gemfeed/2024-05-03-projects-i-currently-dont-have-time-for.md +++ b/gemfeed/2024-05-03-projects-i-currently-dont-have-time-for.md @@ -19,7 +19,7 @@ Art by Laura Brown * [⇢ Projects I currently don't have time for](#projects-i-currently-dont-have-time-for) * [⇢ ⇢ Introduction](#introduction) -* [⇢ ⇢ Hardware projects I don't have time for](#hardware-projects-i-don't-have-time-for) +* [⇢ ⇢ Hardware projects I don't have time for](#hardware-projects-i-don-t-have-time-for) * [⇢ ⇢ ⇢ I use Arch, btw!](#i-use-arch-btw) * [⇢ ⇢ ⇢ OpenBSD home router](#openbsd-home-router) * [⇢ ⇢ ⇢ Pi-Hole server](#pi-hole-server) -- cgit v1.2.3 From 9bbc5b37d3b525b54f705567a4db3243d8c4449e Mon Sep 17 00:00:00 2001 From: Paul Buetow Date: Sun, 25 Aug 2024 23:17:20 +0300 Subject: Update content for md --- gemfeed/2021-05-16-personal-bash-coding-style-guide.md | 2 +- gemfeed/2022-03-06-the-release-of-dtail-4.0.0.md | 4 ++-- gemfeed/2022-07-30-lets-encrypt-with-openbsd-and-rex.md | 4 ++-- gemfeed/2022-08-27-gemtexter-1.1.0-lets-gemtext-again.md | 4 ++-- gemfeed/2023-03-25-gemtexter-2.0.0-lets-gemtext-again-2.md | 2 +- .../2023-07-17-career-guide-and-soft-skills-book-notes.md | 2 +- gemfeed/2023-07-21-gemtexter-2.1.0-lets-gemtext-again-3.md | 2 +- gemfeed/2023-12-10-bash-golf-part-3.md | 2 +- gemfeed/2024-04-01-KISS-high-availability-with-OpenBSD.md | 2 +- .../2024-05-03-projects-i-currently-dont-have-time-for.md | 12 ++++++------ gemfeed/2024-08-05-typing-127.1-words-per-minute.md | 2 +- 11 files changed, 19 insertions(+), 19 deletions(-) (limited to 'gemfeed') diff --git a/gemfeed/2021-05-16-personal-bash-coding-style-guide.md b/gemfeed/2021-05-16-personal-bash-coding-style-guide.md index 43b93229..87f8ccb0 100644 --- a/gemfeed/2021-05-16-personal-bash-coding-style-guide.md +++ b/gemfeed/2021-05-16-personal-bash-coding-style-guide.md @@ -26,7 +26,7 @@ * [⇢ ⇢ ⇢ Quoting your variables](#quoting-your-variables) * [⇢ ⇢ ⇢ Prefer built-in commands over external commands](#prefer-built-in-commands-over-external-commands) * [⇢ ⇢ My additions](#my-additions) -* [⇢ ⇢ ⇢ Use of 'yes' and 'no'](#use-of-yes-and-no) +* [⇢ ⇢ ⇢ Use of 'yes' and 'no'](#use-of--yes--and--no-) * [⇢ ⇢ ⇢ Non-evil alternative to variable assignments via eval](#non-evil-alternative-to-variable-assignments-via-eval) * [⇢ ⇢ ⇢ Prefer pipes over arrays for list processing](#prefer-pipes-over-arrays-for-list-processing) * [⇢ ⇢ ⇢ Assign-then-shift](#assign-then-shift) diff --git a/gemfeed/2022-03-06-the-release-of-dtail-4.0.0.md b/gemfeed/2022-03-06-the-release-of-dtail-4.0.0.md index 2474830e..42527f51 100644 --- a/gemfeed/2022-03-06-the-release-of-dtail-4.0.0.md +++ b/gemfeed/2022-03-06-the-release-of-dtail-4.0.0.md @@ -20,7 +20,7 @@ * [⇢ The release of DTail 4.0.0](#the-release-of-dtail-400) * [⇢ ⇢ Introduction](#introduction) -* [⇢ ⇢ So, what's new in 4.0.0?](#so-whats-new-in-400) +* [⇢ ⇢ So, what's new in 4.0.0?](#so-what-s-new-in-400) * [⇢ ⇢ ⇢ Rewritten logging](#rewritten-logging) * [⇢ ⇢ ⇢ Configurable terminal color codes](#configurable-terminal-color-codes) * [⇢ ⇢ ⇢ Serverless mode](#serverless-mode) @@ -32,7 +32,7 @@ * [⇢ ⇢ ⇢ Integration testing suite](#integration-testing-suite) * [⇢ ⇢ ⇢ Improved code](#improved-code) * [⇢ ⇢ ⇢ Use of memory pools](#use-of-memory-pools) -* [⇢ ⇢ What's next](#whats-next) +* [⇢ ⇢ What's next](#what-s-next) ## Introduction diff --git a/gemfeed/2022-07-30-lets-encrypt-with-openbsd-and-rex.md b/gemfeed/2022-07-30-lets-encrypt-with-openbsd-and-rex.md index 409223fe..746dab78 100644 --- a/gemfeed/2022-07-30-lets-encrypt-with-openbsd-and-rex.md +++ b/gemfeed/2022-07-30-lets-encrypt-with-openbsd-and-rex.md @@ -31,9 +31,9 @@ ## Table of Contents -* [⇢ Let's Encrypt with OpenBSD and Rex](#lets-encrypt-with-openbsd-and-rex) +* [⇢ Let's Encrypt with OpenBSD and Rex](#let-s-encrypt-with-openbsd-and-rex) * [⇢ ⇢ Introduction](#introduction) -* [⇢ ⇢ ⇢ What's Let's Encrypt?](#whats-lets-encrypt) +* [⇢ ⇢ ⇢ What's Let's Encrypt?](#what-s-let-s-encrypt) * [⇢ ⇢ Meet `acme-client`](#meet-acme-client) * [⇢ ⇢ Configuration](#configuration) * [⇢ ⇢ ⇢ acme-client.conf](#acme-clientconf) diff --git a/gemfeed/2022-08-27-gemtexter-1.1.0-lets-gemtext-again.md b/gemfeed/2022-08-27-gemtexter-1.1.0-lets-gemtext-again.md index 5a1c9ad0..8e7a2464 100644 --- a/gemfeed/2022-08-27-gemtexter-1.1.0-lets-gemtext-again.md +++ b/gemfeed/2022-08-27-gemtexter-1.1.0-lets-gemtext-again.md @@ -16,9 +16,9 @@ ## Table of Contents -* [⇢ Gemtexter 1.1.0 - Let's Gemtext again](#gemtexter-110---lets-gemtext-again) +* [⇢ Gemtexter 1.1.0 - Let's Gemtext again](#gemtexter-110---let-s-gemtext-again) * [⇢ ⇢ Introduction](#introduction) -* [⇢ ⇢ What's new?](#whats-new) +* [⇢ ⇢ What's new?](#what-s-new) * [⇢ ⇢ ⇢ Automatic check for GNU version requirements](#automatic-check-for-gnu-version-requirements) * [⇢ ⇢ ⇢ Backticks now produce `inline code blocks` in the HTML output](#backticks-now-produce-inline-code-blocks-in-the-html-output) * [⇢ ⇢ ⇢ Cache for Atom feed generation](#cache-for-atom-feed-generation) diff --git a/gemfeed/2023-03-25-gemtexter-2.0.0-lets-gemtext-again-2.md b/gemfeed/2023-03-25-gemtexter-2.0.0-lets-gemtext-again-2.md index 8b737689..f8b31a17 100644 --- a/gemfeed/2023-03-25-gemtexter-2.0.0-lets-gemtext-again-2.md +++ b/gemfeed/2023-03-25-gemtexter-2.0.0-lets-gemtext-again-2.md @@ -17,7 +17,7 @@ ## Table of Contents -* [⇢ Gemtexter 2.0.0 - Let's Gemtext again²](#gemtexter-200---lets-gemtext-again) +* [⇢ Gemtexter 2.0.0 - Let's Gemtext again²](#gemtexter-200---let-s-gemtext-again) * [⇢ ⇢ Introduction](#introduction) * [⇢ ⇢ Minimal template engine](#minimal-template-engine) * [⇢ ⇢ Added hooks](#added-hooks) diff --git a/gemfeed/2023-07-17-career-guide-and-soft-skills-book-notes.md b/gemfeed/2023-07-17-career-guide-and-soft-skills-book-notes.md index 9cd6ca62..67439538 100644 --- a/gemfeed/2023-07-17-career-guide-and-soft-skills-book-notes.md +++ b/gemfeed/2023-07-17-career-guide-and-soft-skills-book-notes.md @@ -15,7 +15,7 @@ * [⇢ ⇢ Expand the empire](#expand-the-empire) * [⇢ ⇢ Be pragmatic and also manage your time](#be-pragmatic-and-also-manage-your-time) * [⇢ ⇢ ⇢ The quota system](#the-quota-system) -* [⇢ ⇢ ⇢ Don't waste time](#dont-waste-time) +* [⇢ ⇢ ⇢ Don't waste time](#don-t-waste-time) * [⇢ ⇢ ⇢ Habits](#habits) * [⇢ Work-life balance](#work-life-balance) * [⇢ ⇢ Mental health](#mental-health) diff --git a/gemfeed/2023-07-21-gemtexter-2.1.0-lets-gemtext-again-3.md b/gemfeed/2023-07-21-gemtexter-2.1.0-lets-gemtext-again-3.md index 427acce8..92531bbb 100644 --- a/gemfeed/2023-07-21-gemtexter-2.1.0-lets-gemtext-again-3.md +++ b/gemfeed/2023-07-21-gemtexter-2.1.0-lets-gemtext-again-3.md @@ -17,7 +17,7 @@ ## Table of Contents -* [⇢ Gemtexter 2.1.0 - Let's Gemtext again³](#gemtexter-210---lets-gemtext-again) +* [⇢ Gemtexter 2.1.0 - Let's Gemtext again³](#gemtexter-210---let-s-gemtext-again) * [⇢ ⇢ Introduction](#introduction) * [⇢ ⇢ Why Bash?](#why-bash) * [⇢ ⇢ Switch to GPL3 license](#switch-to-gpl3-license) diff --git a/gemfeed/2023-12-10-bash-golf-part-3.md b/gemfeed/2023-12-10-bash-golf-part-3.md index d4619f9b..6e58a05e 100644 --- a/gemfeed/2023-12-10-bash-golf-part-3.md +++ b/gemfeed/2023-12-10-bash-golf-part-3.md @@ -25,7 +25,7 @@ jgs^^^^^^^`^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^ * [⇢ ⇢ Dynamic variables with `local`](#dynamic-variables-with-local) * [⇢ ⇢ `if` conditionals](#if-conditionals) * [⇢ ⇢ Multi-line comments](#multi-line-comments) -* [⇢ ⇢ Don't change it while it's executed](#dont-change-it-while-its-executed) +* [⇢ ⇢ Don't change it while it's executed](#don-t-change-it-while-it-s-executed) ## Introduction diff --git a/gemfeed/2024-04-01-KISS-high-availability-with-OpenBSD.md b/gemfeed/2024-04-01-KISS-high-availability-with-OpenBSD.md index 6402b1de..f45b5c14 100644 --- a/gemfeed/2024-04-01-KISS-high-availability-with-OpenBSD.md +++ b/gemfeed/2024-04-01-KISS-high-availability-with-OpenBSD.md @@ -37,7 +37,7 @@ _____|_:_:_| (o)-(o) |_:_:_|--'`-. ,--. ksh under-water (((\'/ * [⇢ ⇢ ⇢ Fairly cheap and geo-redundant](#fairly-cheap-and-geo-redundant) * [⇢ ⇢ ⇢ Failover time and split-brain](#failover-time-and-split-brain) * [⇢ ⇢ ⇢ Failover support for multiple protocols](#failover-support-for-multiple-protocols) -* [⇢ ⇢ ⇢ Let's encrypt TLS certificates](#lets-encrypt-tls-certificates) +* [⇢ ⇢ ⇢ Let's encrypt TLS certificates](#let-s-encrypt-tls-certificates) * [⇢ ⇢ ⇢ Monitoring](#monitoring) * [⇢ ⇢ ⇢ Rex automation](#rex-automation) * [⇢ ⇢ More HA](#more-ha) diff --git a/gemfeed/2024-05-03-projects-i-currently-dont-have-time-for.md b/gemfeed/2024-05-03-projects-i-currently-dont-have-time-for.md index feb08a94..8230e707 100644 --- a/gemfeed/2024-05-03-projects-i-currently-dont-have-time-for.md +++ b/gemfeed/2024-05-03-projects-i-currently-dont-have-time-for.md @@ -17,7 +17,7 @@ Art by Laura Brown ## Table of Contents -* [⇢ Projects I currently don't have time for](#projects-i-currently-dont-have-time-for) +* [⇢ Projects I currently don't have time for](#projects-i-currently-don-t-have-time-for) * [⇢ ⇢ Introduction](#introduction) * [⇢ ⇢ Hardware projects I don't have time for](#hardware-projects-i-don-t-have-time-for) * [⇢ ⇢ ⇢ I use Arch, btw!](#i-use-arch-btw) @@ -28,7 +28,7 @@ Art by Laura Brown * [⇢ ⇢ ⇢ Retro station](#retro-station) * [⇢ ⇢ ⇢ Sound server](#sound-server) * [⇢ ⇢ ⇢ Project Freekat](#project-freekat) -* [⇢ ⇢ Programming projects I don't have time for](#programming-projects-i-dont-have-time-for) +* [⇢ ⇢ Programming projects I don't have time for](#programming-projects-i-don-t-have-time-for) * [⇢ ⇢ ⇢ CLI-HIVE](#cli-hive) * [⇢ ⇢ ⇢ Enhanced KISS home photo albums](#enhanced-kiss-home-photo-albums) * [⇢ ⇢ ⇢ KISS file sync server with end-to-end encryption](#kiss-file-sync-server-with-end-to-end-encryption) @@ -37,19 +37,19 @@ Art by Laura Brown * [⇢ ⇢ ⇢ Renovate VS-Sim](#renovate-vs-sim) * [⇢ ⇢ ⇢ KISS ticketing system](#kiss-ticketing-system) * [⇢ ⇢ ⇢ A domain-specific language (DSL) for work](#a-domain-specific-language-dsl-for-work) -* [⇢ ⇢ Self-hosting projects I don't have time for](#self-hosting-projects-i-dont-have-time-for) +* [⇢ ⇢ Self-hosting projects I don't have time for](#self-hosting-projects-i-don-t-have-time-for) * [⇢ ⇢ ⇢ My own Matrix server](#my-own-matrix-server) * [⇢ ⇢ ⇢ Ampache music server](#ampache-music-server) * [⇢ ⇢ ⇢ Librum eBook reader](#librum-ebook-reader) * [⇢ ⇢ ⇢ Memos - Note-taking service](#memos---note-taking-service) * [⇢ ⇢ ⇢ Bepasty server](#bepasty-server) -* [⇢ ⇢ Books I don't have time to read](#books-i-dont-have-time-to-read) +* [⇢ ⇢ Books I don't have time to read](#books-i-don-t-have-time-to-read) * [⇢ ⇢ ⇢ Fluent Python](#fluent-python) * [⇢ ⇢ ⇢ Programming Ruby](#programming-ruby) * [⇢ ⇢ ⇢ Peter F. Hamilton science fiction books](#peter-f-hamilton-science-fiction-books) -* [⇢ ⇢ New websites I don't have time for](#new-websites-i-dont-have-time-for) +* [⇢ ⇢ New websites I don't have time for](#new-websites-i-don-t-have-time-for) * [⇢ ⇢ ⇢ Create a "Why Raku Rox" site](#create-a-why-raku-rox-site) -* [⇢ ⇢ Research projects I don't have time for](#research-projects-i-dont-have-time-for) +* [⇢ ⇢ Research projects I don't have time for](#research-projects-i-don-t-have-time-for) * [⇢ ⇢ ⇢ Project secure](#project-secure) * [⇢ ⇢ ⇢ CPU utilisation is all wrong](#cpu-utilisation-is-all-wrong) diff --git a/gemfeed/2024-08-05-typing-127.1-words-per-minute.md b/gemfeed/2024-08-05-typing-127.1-words-per-minute.md index 7173ce37..94900c69 100644 --- a/gemfeed/2024-08-05-typing-127.1-words-per-minute.md +++ b/gemfeed/2024-08-05-typing-127.1-words-per-minute.md @@ -40,7 +40,7 @@ * [⇢ ⇢ ⇢ Reverse shifting](#reverse-shifting) * [⇢ ⇢ ⇢ Enter the flow state](#enter-the-flow-state) * [⇢ ⇢ ⇢ Repeat every word](#repeat-every-word) -* [⇢ ⇢ ⇢ Don't use the same finger for two consecutive keystrokes](#dont-use-the-same-finger-for-two-consecutive-keystrokes) +* [⇢ ⇢ ⇢ Don't use the same finger for two consecutive keystrokes](#don-t-use-the-same-finger-for-two-consecutive-keystrokes) * [⇢ ⇢ ⇢ Warm-up](#warm-up) * [⇢ ⇢ Travel keyboard](#travel-keyboard) * [⇢ ⇢ Upcoming custom Kinesis build](#upcoming-custom-kinesis-build) -- cgit v1.2.3 From 7899ff9353c2ba2c1f22c56eaa803e00bcc6398c Mon Sep 17 00:00:00 2001 From: Paul Buetow Date: Mon, 26 Aug 2024 22:09:09 +0300 Subject: Update content for md --- gemfeed/2024-07-05-random-weird-things.md | 34 +++++++++++++++++++++++-------- 1 file changed, 26 insertions(+), 8 deletions(-) (limited to 'gemfeed') diff --git a/gemfeed/2024-07-05-random-weird-things.md b/gemfeed/2024-07-05-random-weird-things.md index 4b28ac93..cbe595ae 100644 --- a/gemfeed/2024-07-05-random-weird-things.md +++ b/gemfeed/2024-07-05-random-weird-things.md @@ -2,6 +2,24 @@ > Published at 2024-07-05T10:59:59+03:00 +## Table of Contents + +* [⇢ Random Weird Things](#random-weird-things) +* [⇢ ⇢ Introduction](#introduction) +* [⇢ ⇢ 1. `bad.horse` traceroute](#1-badhorse-traceroute) +* [⇢ ⇢ 2. ASCII cinema](#2-ascii-cinema) +* [⇢ ⇢ 3. Netflix's Hello World application](#3-netflix-s-hello-world-application) +* [⇢ ⇢ C programming](#c-programming) +* [⇢ ⇢ ⇢ 4. Indexing an array](#4-indexing-an-array) +* [⇢ ⇢ ⇢ 5. Variables with prefix `$`](#5-variables-with-prefix-) +* [⇢ ⇢ 6. Object oriented shell scripts using `ksh`](#6-object-oriented-shell-scripts-using-ksh) +* [⇢ ⇢ 7. This works in Go](#7-this-works-in-go) +* [⇢ ⇢ 8. "I am a Teapot" HTTP response code](#8-i-am-a-teapot-http-response-code) +* [⇢ ⇢ 9. `jq` is a functional programming language](#9-jq-is-a-functional-programming-language) +* [⇢ ⇢ 10. Regular expression to verify email addresses](#10-regular-expression-to-verify-email-addresses) + +## Introduction + Every so often, I come across random, weird, and unexpected things on the internet. I thought it would be neat to share them here from time to time. As a start, here are ten of them. ``` @@ -245,7 +263,7 @@ This is a pretty old meme, but still worth posting here (as some may be unaware) ?:\r\n)?[ \t])+|\Z|(?=[\["()<>@,;:\\".\[\]]))|"(?:[^\"\r\\]|\\.|(?:(?:\r\n)?[ \t]))*"(?:(?:\r\n)?[ \t])*))*@(?:(?:\r\n)?[ \t])*(?:[^()<>@,;:\\".\[\] \000-\0 31]+(?:(?:(?:\r\n)?[ \t])+|\Z|(?=[\["()<>@,;:\\".\[\]]))|\[([^\[\]\r\\]|\\.)*\ -](?:(?:\r\n)?[ \t])*)(?:\.(?:(?:\r\n)?[ \t])*(?:[^()<>@,;:\\".\[\] \000-\031]+ +>(?:(?:\r\n)?[ \t])*)(?:\.(?:(?:\r\n)?[ \t])*(?:[^()<>@,;:\\".\[\] \000-\031]+ (?:(?:(?:\r\n)?[ \t])+|\Z|(?=[\["()<>@,;:\\".\[\]]))|\[([^\[\]\r\\]|\\.)*\](?: (?:\r\n)?[ \t])*))*|(?:[^()<>@,;:\\".\[\] \000-\031]+(?:(?:(?:\r\n)?[ \t])+|\Z |(?=[\["()<>@,;:\\".\[\]]))|"(?:[^\"\r\\]|\\.|(?:(?:\r\n)?[ \t]))*"(?:(?:\r\n) @@ -261,8 +279,8 @@ r\n)?[ \t])+|\Z|(?=[\["()<>@,;:\\".\[\]]))|\[([^\[\]\r\\]|\\.)*\](?:(?:\r\n)?[ |\Z|(?=[\["()<>@,;:\\".\[\]]))|"(?:[^\"\r\\]|\\.|(?:(?:\r\n)?[ \t]))*"(?:(?:\r \n)?[ \t])*)(?:\.(?:(?:\r\n)?[ \t])*(?:[^()<>@,;:\\".\[\] \000-\031]+(?:(?:(?: \r\n)?[ \t])+|\Z|(?=[\["()<>@,;:\\".\[\]]))|"(?:[^\"\r\\]|\\.|(?:(?:\r\n)?[ \t -]))*"(?:(?:\r\n)?[ \t])*))*@(?:(?:\r\n)?[ \t])*(?:[^()<>@,;:\\".\[\] \000-\031 -]+(?:(?:(?:\r\n)?[ \t])+|\Z|(?=[\["()<>@,;:\\".\[\]]))|\[([^\[\]\r\\]|\\.)*\]( +>))*"(?:(?:\r\n)?[ \t])*))*@(?:(?:\r\n)?[ \t])*(?:[^()<>@,;:\\".\[\] \000-\031 +>+(?:(?:(?:\r\n)?[ \t])+|\Z|(?=[\["()<>@,;:\\".\[\]]))|\[([^\[\]\r\\]|\\.)*\]( ?:(?:\r\n)?[ \t])*)(?:\.(?:(?:\r\n)?[ \t])*(?:[^()<>@,;:\\".\[\] \000-\031]+(? :(?:(?:\r\n)?[ \t])+|\Z|(?=[\["()<>@,;:\\".\[\]]))|\[([^\[\]\r\\]|\\.)*\](?:(? :\r\n)?[ \t])*))*\>(?:(?:\r\n)?[ \t])*)|(?:[^()<>@,;:\\".\[\] \000-\031]+(?:(? @@ -281,7 +299,7 @@ r\n)?[ \t])+|\Z|(?=[\["()<>@,;:\\".\[\]]))|\[([^\[\]\r\\]|\\.)*\](?:(?:\r\n)?[ :\\".\[\] \000-\031]+(?:(?:(?:\r\n)?[ \t])+|\Z|(?=[\["()<>@,;:\\".\[\]]))|\[([ ^\[\]\r\\]|\\.)*\](?:(?:\r\n)?[ \t])*)(?:\.(?:(?:\r\n)?[ \t])*(?:[^()<>@,;:\\" .\[\] \000-\031]+(?:(?:(?:\r\n)?[ \t])+|\Z|(?=[\["()<>@,;:\\".\[\]]))|\[([^\[\ -]\r\\]|\\.)*\](?:(?:\r\n)?[ \t])*))*(?:,@(?:(?:\r\n)?[ \t])*(?:[^()<>@,;:\\".\ +>\r\\]|\\.)*\](?:(?:\r\n)?[ \t])*))*(?:,@(?:(?:\r\n)?[ \t])*(?:[^()<>@,;:\\".\ [\] \000-\031]+(?:(?:(?:\r\n)?[ \t])+|\Z|(?=[\["()<>@,;:\\".\[\]]))|\[([^\[\]\ r\\]|\\.)*\](?:(?:\r\n)?[ \t])*)(?:\.(?:(?:\r\n)?[ \t])*(?:[^()<>@,;:\\".\[\] \000-\031]+(?:(?:(?:\r\n)?[ \t])+|\Z|(?=[\["()<>@,;:\\".\[\]]))|\[([^\[\]\r\\] @@ -293,17 +311,17 @@ r\\]|\\.)*\](?:(?:\r\n)?[ \t])*)(?:\.(?:(?:\r\n)?[ \t])*(?:[^()<>@,;:\\".\[\] (?:[^()<>@,;:\\".\[\] \000-\031]+(?:(?:(?:\r\n)?[ \t])+|\Z|(?=[\["()<>@,;:\\". \[\]]))|\[([^\[\]\r\\]|\\.)*\](?:(?:\r\n)?[ \t])*)(?:\.(?:(?:\r\n)?[ \t])*(?:[ ^()<>@,;:\\".\[\] \000-\031]+(?:(?:(?:\r\n)?[ \t])+|\Z|(?=[\["()<>@,;:\\".\[\] -]))|\[([^\[\]\r\\]|\\.)*\](?:(?:\r\n)?[ \t])*))*\>(?:(?:\r\n)?[ \t])*)(?:,\s*( +>))|\[([^\[\]\r\\]|\\.)*\](?:(?:\r\n)?[ \t])*))*\>(?:(?:\r\n)?[ \t])*)(?:,\s*( ?:(?:[^()<>@,;:\\".\[\] \000-\031]+(?:(?:(?:\r\n)?[ \t])+|\Z|(?=[\["()<>@,;:\\ ".\[\]]))|"(?:[^\"\r\\]|\\.|(?:(?:\r\n)?[ \t]))*"(?:(?:\r\n)?[ \t])*)(?:\.(?:( ?:\r\n)?[ \t])*(?:[^()<>@,;:\\".\[\] \000-\031]+(?:(?:(?:\r\n)?[ \t])+|\Z|(?=[ \["()<>@,;:\\".\[\]]))|"(?:[^\"\r\\]|\\.|(?:(?:\r\n)?[ \t]))*"(?:(?:\r\n)?[ \t -])*))*@(?:(?:\r\n)?[ \t])*(?:[^()<>@,;:\\".\[\] \000-\031]+(?:(?:(?:\r\n)?[ \t -])+|\Z|(?=[\["()<>@,;:\\".\[\]]))|\[([^\[\]\r\\]|\\.)*\](?:(?:\r\n)?[ \t])*)(? +>)*))*@(?:(?:\r\n)?[ \t])*(?:[^()<>@,;:\\".\[\] \000-\031]+(?:(?:(?:\r\n)?[ \t +>)+|\Z|(?=[\["()<>@,;:\\".\[\]]))|\[([^\[\]\r\\]|\\.)*\](?:(?:\r\n)?[ \t])*)(? :\.(?:(?:\r\n)?[ \t])*(?:[^()<>@,;:\\".\[\] \000-\031]+(?:(?:(?:\r\n)?[ \t])+| \Z|(?=[\["()<>@,;:\\".\[\]]))|\[([^\[\]\r\\]|\\.)*\](?:(?:\r\n)?[ \t])*))*|(?: [^()<>@,;:\\".\[\] \000-\031]+(?:(?:(?:\r\n)?[ \t])+|\Z|(?=[\["()<>@,;:\\".\[\ -]]))|"(?:[^\"\r\\]|\\.|(?:(?:\r\n)?[ \t]))*"(?:(?:\r\n)?[ \t])*)*\<(?:(?:\r\n) +>]))|"(?:[^\"\r\\]|\\.|(?:(?:\r\n)?[ \t]))*"(?:(?:\r\n)?[ \t])*)*\<(?:(?:\r\n) ?[ \t])*(?:@(?:[^()<>@,;:\\".\[\] \000-\031]+(?:(?:(?:\r\n)?[ \t])+|\Z|(?=[\[" ()<>@,;:\\".\[\]]))|\[([^\[\]\r\\]|\\.)*\](?:(?:\r\n)?[ \t])*)(?:\.(?:(?:\r\n) ?[ \t])*(?:[^()<>@,;:\\".\[\] \000-\031]+(?:(?:(?:\r\n)?[ \t])+|\Z|(?=[\["()<> -- cgit v1.2.3 From 238eb92c1f28ecb4d44089b230f3345eecdc1af0 Mon Sep 17 00:00:00 2001 From: Paul Buetow Date: Mon, 26 Aug 2024 22:12:48 +0300 Subject: Update content for md --- .../2022-02-04-computer-operating-systems-i-use.md | 27 ++++++++++++++++++++++ 1 file changed, 27 insertions(+) (limited to 'gemfeed') diff --git a/gemfeed/2022-02-04-computer-operating-systems-i-use.md b/gemfeed/2022-02-04-computer-operating-systems-i-use.md index 67f068f6..d19adeb9 100644 --- a/gemfeed/2022-02-04-computer-operating-systems-i-use.md +++ b/gemfeed/2022-02-04-computer-operating-systems-i-use.md @@ -23,6 +23,33 @@ `--{__________) \/ "Berkeley Unix Daemon" ``` +## Table of Contents + +* [⇢ Computer operating systems I use(d)](#computer-operating-systems-i-used) +* [⇢ ⇢ Introduction](#introduction) +* [⇢ ⇢ Fedora Linux](#fedora-linux) +* [⇢ ⇢ EndeavourOS](#endeavouros) +* [⇢ ⇢ FreeBSD](#freebsd) +* [⇢ ⇢ CentOS 7](#centos-7) +* [⇢ ⇢ OpenBSD](#openbsd) +* [⇢ ⇢ macOS (proprietary)](#macos-proprietary) +* [⇢ ⇢ LineageOS (mobile)](#lineageos-mobile) +* [⇢ ⇢ Samsung's Stock Android (mobile proprietary)](#samsung-s-stock-android-mobile-proprietary) +* [⇢ ⇢ iOS (mobile proprietary)](#ios-mobile-proprietary) +* [⇢ ⇢ Other OSes](#other-oses) +* [⇢ ⇢ ⇢ InfinyTime (smartwatch)](#infinytime-smartwatch) +* [⇢ ⇢ ⇢ motionEyeOS](#motioneyeos) +* [⇢ ⇢ ⇢ Kobo OS (proprietary)](#kobo-os-proprietary) +* [⇢ ⇢ ⇢ Android TV (proprietary)](#android-tv-proprietary) +* [⇢ ⇢ Other OSes..](#other-oses) +* [⇢ ⇢ ⇢ NetBSD](#netbsd) +* [⇢ ⇢ ⇢ Other OSes in use...](#other-oses-in-use) +* [⇢ ⇢ ⇢ Other OSes not used any more...](#other-oses-not-used-any-more) +* [⇢ ⇢ ⇢ Other OSes I only had a glance at...](#other-oses-i-only-had-a-glance-at) +* [⇢ ⇢ ⇢ Other OSes which seem interesting...](#other-oses-which-seem-interesting) + +## Introduction + This is a list of Operating Systems I currently use. This list is in no particular order and also will be updated over time. The very first operating system I used was MS-DOS (mainly for games) and the very first Unix like operating system I used was SuSE Linux 5.3. My first smartphone OS was Symbian on a clunky Sony Ericsson device. ## Fedora Linux -- cgit v1.2.3 From 9bb115af8b870e1171356ef3a7b3ddfff8dedd4f Mon Sep 17 00:00:00 2001 From: Paul Buetow Date: Mon, 26 Aug 2024 23:07:44 +0300 Subject: Update content for md --- gemfeed/2008-06-26-perl-poetry.md | 15 +++--- gemfeed/2010-04-09-standard-ml-and-haskell.md | 10 ++++ .../2010-05-09-the-fype-programming-language.md | 38 +++++++++++++-- .../2011-05-07-perl-daemon-service-framework.md | 7 +-- ...-12-05-run-debian-on-your-phone-with-debroid.md | 21 ++++++--- ...6-04-09-jails-and-zfs-on-freebsd-with-puppet.md | 7 +-- ...spinning-up-my-own-authoritative-dns-servers.md | 12 ++++- ...realistic-load-testing-with-ioriot-for-linux.md | 36 +++++++++----- ...04-22-dtail-the-distributed-log-tail-program.md | 27 +++++------ .../2021-05-16-personal-bash-coding-style-guide.md | 11 ++--- ...-05-gemtexter-one-bash-script-to-rule-it-all.md | 15 +++--- gemfeed/2021-07-04-the-well-grounded-rubyist.md | 14 ++++++ ...21-08-01-on-being-pedantic-about-open-source.md | 20 +++++++- gemfeed/2021-09-12-keep-it-simple-and-stupid.md | 7 +-- gemfeed/2021-10-22-defensive-devops.md | 30 ++++++++---- gemfeed/2021-11-29-bash-golf-part-1.md | 15 +++--- ...21-12-26-how-to-stay-sane-as-a-devops-person.md | 32 ++++++++++--- gemfeed/2022-01-01-bash-golf-part-2.md | 15 +++--- .../2022-02-04-computer-operating-systems-i-use.md | 7 +-- gemfeed/2022-03-06-the-release-of-dtail-4.0.0.md | 11 ++--- gemfeed/2022-04-10-creative-universe.md | 45 +++++++++++------- gemfeed/2022-05-27-perl-is-still-a-great-choice.md | 25 +++++----- gemfeed/2022-06-15-sweating-the-small-stuff.md | 41 ++++++++++++---- ...2022-07-30-lets-encrypt-with-openbsd-and-rex.md | 7 +-- ...022-08-27-gemtexter-1.1.0-lets-gemtext-again.md | 15 +++--- gemfeed/2022-09-30-after-a-bad-nights-sleep.md | 21 ++++++++- gemfeed/2022-10-30-installing-dtail-on-openbsd.md | 27 +++++------ ...-i-tried-emacs-but-i-switched-back-to-neovim.md | 31 ++++++++---- ...2022-12-24-ultrarelearning-java-my-takeaways.md | 19 +++++++- gemfeed/2023-01-23-why-grapheneos-rox.md | 36 +++++++++----- gemfeed/2023-02-26-how-to-shut-down-after-work.md | 13 ++++- ...3-03-25-gemtexter-2.0.0-lets-gemtext-again-2.md | 19 ++++---- ...-04-01-never-split-the-difference-book-notes.md | 15 ++++++ ...orithms-and-data-structures-in-golang-part-1.md | 15 +++--- gemfeed/2023-05-01-unveiling-guprecords | 1 + ...023-05-06-the-obstacle-is-the-way-book-notes.md | 32 ++++++------- ...023-06-01-kiss-server-monitoring-with-gogios.md | 15 +++--- ...7-17-career-guide-and-soft-skills-book-notes.md | 55 ++++++++++------------ ...3-07-21-gemtexter-2.1.0-lets-gemtext-again-3.md | 11 ++--- gemfeed/2023-09-25-dtail-usage-examples.md | 32 ++++++------- ...s-static-web-photo-albums-with-photoalbum.sh.md | 15 +++--- gemfeed/2023-11-11-mind-management-book-notes.md | 30 ++++++------ gemfeed/2023-12-10-bash-golf-part-3.md | 15 +++--- ...024-02-04-from-babylon5.buetow.org-to-.cloud.md | 17 +++++++ ...r-quickly-logging-ideas-programmed-in-golang.md | 16 +++---- ...24-04-01-KISS-high-availability-with-OpenBSD.md | 19 ++++---- gemfeed/2024-05-01-slow-productivity-book-notes.md | 24 +++++----- ...5-03-projects-i-currently-dont-have-time-for.md | 7 +-- .../2024-06-23-terminal-multiplexing-with-tmux.md | 22 ++++----- gemfeed/2024-07-05-random-weird-things.md | 25 +++++----- .../2024-07-07-the-stoic-challenge-book-notes.md | 18 +++---- .../2024-08-05-typing-127.1-words-per-minute.md | 19 ++++---- 52 files changed, 619 insertions(+), 433 deletions(-) (limited to 'gemfeed') diff --git a/gemfeed/2008-06-26-perl-poetry.md b/gemfeed/2008-06-26-perl-poetry.md index 0de1bdaf..e64cd0f4 100644 --- a/gemfeed/2008-06-26-perl-poetry.md +++ b/gemfeed/2008-06-26-perl-poetry.md @@ -2,6 +2,12 @@ > Published at 2008-06-26T21:43:51+01:00; Updated at 2021-05-04 +Here are some Perl Poems I wrote. They don't do anything useful when you run them, but they don't produce a compiler error either. They only exist for fun and demonstrate what you can do with Perl syntax. + +Wikipedia: "Perl poetry is the practice of writing poems that can be compiled as legal Perl code, for example the piece known as Black Perl. Perl poetry is made possible by the large number of English words that are used in the Perl language. New poems are regularly submitted to the community at PerlMonks." + +[https://en.wikipedia.org/wiki/Perl](https://en.wikipedia.org/wiki/Perl) + ``` '\|/' * -- * ----- @@ -28,20 +34,11 @@ _~~|~/_|_|__/|~~~~~~~ | / ~~~~~ | | ~~~~~~~~ ## Table of Contents * [⇢ Perl Poetry](#perl-poetry) -* [⇢ ⇢ Introduction](#introduction) * [⇢ ⇢ math.pl](#mathpl) * [⇢ ⇢ christmas.pl](#christmaspl) * [⇢ ⇢ shopping.pl](#shoppingpl) * [⇢ ⇢ More...](#more) -## Introduction - -Here are some Perl Poems I wrote. They don't do anything useful when you run them, but they don't produce a compiler error either. They only exist for fun and demonstrate what you can do with Perl syntax. - -Wikipedia: "Perl poetry is the practice of writing poems that can be compiled as legal Perl code, for example the piece known as Black Perl. Perl poetry is made possible by the large number of English words that are used in the Perl language. New poems are regularly submitted to the community at PerlMonks." - -[https://en.wikipedia.org/wiki/Perl](https://en.wikipedia.org/wiki/Perl) - ## math.pl ```perl diff --git a/gemfeed/2010-04-09-standard-ml-and-haskell.md b/gemfeed/2010-04-09-standard-ml-and-haskell.md index daad07b5..cdf4c5d5 100644 --- a/gemfeed/2010-04-09-standard-ml-and-haskell.md +++ b/gemfeed/2010-04-09-standard-ml-and-haskell.md @@ -8,6 +8,16 @@ As you will see, SML and Haskell are very similar (at least when it comes to the Haskell is also a "pure functional" programming language, whereas SML also makes explicit use of imperative concepts. I am by far not a specialist in either of these languages, but here are a few functions implemented in both SML and Haskell: +## Table of Contents + +* [⇢ Standard ML and Haskell](#standard-ml-and-haskell) +* [⇢ ⇢ Defining a multi-data type](#defining-a-multi-data-type) +* [⇢ ⇢ Processing a multi](#processing-a-multi) +* [⇢ ⇢ Simplify function](#simplify-function) +* [⇢ ⇢ Delete all](#delete-all) +* [⇢ ⇢ Delete one](#delete-one) +* [⇢ ⇢ Higher-order functions](#higher-order-functions) + ## Defining a multi-data type Standard ML: diff --git a/gemfeed/2010-05-09-the-fype-programming-language.md b/gemfeed/2010-05-09-the-fype-programming-language.md index c7f8850d..3885a031 100644 --- a/gemfeed/2010-05-09-the-fype-programming-language.md +++ b/gemfeed/2010-05-09-the-fype-programming-language.md @@ -2,6 +2,12 @@ > Published at 2010-05-09T12:48:29+01:00; Updated at 2021-05-05 +Fype is an interpreted programming language created by me for learning and fun. The interpreter is written in C. It has been tested on FreeBSD and NetBSD and may also work on other Unix like operating systems such as Linux based ones. Besides learning and fun, there is no other use case of why Fype exists as many other programming languages are much faster and more powerful. + +The Fype syntax is straightforward and uses a maximum look ahead of 1 and an effortless top-down parsing mechanism. Fype is parsing and interpreting its code simultaneously. This means that syntax errors are only detected during program runtime. + +Fype is a recursive acronym and means "Fype is For Your Program Execution" or "Fype is Free Yak Programmed for ELF". You could also say, "It's not a hype - it's Fype!". + ``` ____ _ __ / / _|_ _ _ __ ___ _ _ ___ __ _| |__ / _|_ _ @@ -11,11 +17,33 @@ |___/|_| |___/ |___/ ``` -Fype is an interpreted programming language created by me for learning and fun. The interpreter is written in C. It has been tested on FreeBSD and NetBSD and may also work on other Unix like operating systems such as Linux based ones. Besides learning and fun, there is no other use case of why Fype exists as many other programming languages are much faster and more powerful. - -The Fype syntax is straightforward and uses a maximum look ahead of 1 and an effortless top-down parsing mechanism. Fype is parsing and interpreting its code simultaneously. This means that syntax errors are only detected during program runtime. - -Fype is a recursive acronym and means "Fype is For Your Program Execution" or "Fype is Free Yak Programmed for ELF". You could also say, "It's not a hype - it's Fype!". +## Table of Contents + +* [⇢ The Fype Programming Language](#the-fype-programming-language) +* [⇢ ⇢ Object-oriented C style](#object-oriented-c-style) +* [⇢ ⇢ Data types](#data-types) +* [⇢ ⇢ Syntax](#syntax) +* [⇢ ⇢ ⇢ Comments](#comments) +* [⇢ ⇢ ⇢ Variables](#variables) +* [⇢ ⇢ ⇢ Synonyms](#synonyms) +* [⇢ ⇢ Statements and expressions](#statements-and-expressions) +* [⇢ ⇢ ⇢ Parenthesis](#parenthesis) +* [⇢ ⇢ ⇢ Basic expressions](#basic-expressions) +* [⇢ ⇢ ⇢ Bitwise expressions](#bitwise-expressions) +* [⇢ ⇢ ⇢ Numeric expressions](#numeric-expressions) +* [⇢ ⇢ Control statements](#control-statements) +* [⇢ ⇢ Scopes](#scopes) +* [⇢ ⇢ Definedness ](#definedness-) +* [⇢ ⇢ System ](#system-) +* [⇢ ⇢ ⇢ I/O ](#io-) +* [⇢ ⇢ Procedures and functions](#procedures-and-functions) +* [⇢ ⇢ ⇢ Procedures](#procedures) +* [⇢ ⇢ ⇢ Nested procedures](#nested-procedures) +* [⇢ ⇢ ⇢ Functions](#functions) +* [⇢ ⇢ ⇢ Nested functions](#nested-functions) +* [⇢ ⇢ Arrays](#arrays) +* [⇢ ⇢ Fancy stuff](#fancy-stuff) +* [⇢ ⇢ May the source be with you](#may-the-source-be-with-you) ## Object-oriented C style diff --git a/gemfeed/2011-05-07-perl-daemon-service-framework.md b/gemfeed/2011-05-07-perl-daemon-service-framework.md index e393a1ea..7364826f 100644 --- a/gemfeed/2011-05-07-perl-daemon-service-framework.md +++ b/gemfeed/2011-05-07-perl-daemon-service-framework.md @@ -2,6 +2,8 @@ > Published at 2011-05-07T22:26:02+01:00; Updated at 2021-05-07 +PerlDaemon is a minimal daemon for Linux and other Unix like operating systems programmed in Perl. It is a minimal but pretty functional and fairly generic service framework. This means that it does not do anything useful other than providing a framework for starting, stopping, configuring and logging. To do something useful, a module (written in Perl) must be provided. + ``` a'! _,,_ a'! _,,_ a'! _,,_ \\_/ \ \\_/ \ \\_/ \.-, @@ -12,7 +14,6 @@ ## Table of Contents * [⇢ Perl Daemon (Service Framework)](#perl-daemon-service-framework) -* [⇢ ⇢ Introduction](#introduction) * [⇢ ⇢ Features](#features) * [⇢ ⇢ Quick Guide](#quick-guide) * [⇢ ⇢ How to configure](#how-to-configure) @@ -23,10 +24,6 @@ * [⇢ ⇢ ⇢ Your own module](#your-own-module) * [⇢ ⇢ May the source be with you](#may-the-source-be-with-you) -## Introduction - -PerlDaemon is a minimal daemon for Linux and other Unix like operating systems programmed in Perl. It is a minimal but pretty functional and fairly generic service framework. This means that it does not do anything useful other than providing a framework for starting, stopping, configuring and logging. To do something useful, a module (written in Perl) must be provided. - ## Features PerlDaemon supports: diff --git a/gemfeed/2015-12-05-run-debian-on-your-phone-with-debroid.md b/gemfeed/2015-12-05-run-debian-on-your-phone-with-debroid.md index fd54242c..f0c1af25 100644 --- a/gemfeed/2015-12-05-run-debian-on-your-phone-with-debroid.md +++ b/gemfeed/2015-12-05-run-debian-on-your-phone-with-debroid.md @@ -2,6 +2,12 @@ > Published at 2015-12-05T16:12:57+00:00; Updated at 2021-05-16 +You can use the following tutorial to install a full-blown Debian GNU/Linux Chroot on an LG G3 D855 CyanogenMod 13 (Android 6). First of all, you need to have root permissions on your phone, and you also need to have the developer mode activated. The following steps have been tested on Linux (Fedora 23). + +[![./run-debian-on-your-phone-with-debroid/Deboroid.png](./run-debian-on-your-phone-with-debroid/Deboroid.png)](./run-debian-on-your-phone-with-debroid/Deboroid.png) + +A couple of years have passed since I last worked on Debroid. Currently, I am using the Termux app on Android, which is less sophisticated than a fully blown Debian installation but sufficient for my current requirements. The content of this site may be still relevant, and it would also work with more recent versions of Debian and Android. I would expect that some minor modifications need to be made, though. + ``` ____ _ _ _ | _ \ ___| |__ _ __ ___ (_) __| | @@ -11,13 +17,16 @@ ``` -You can use the following tutorial to install a full-blown Debian GNU/Linux Chroot on an LG G3 D855 CyanogenMod 13 (Android 6). First of all, you need to have root permissions on your phone, and you also need to have the developer mode activated. The following steps have been tested on Linux (Fedora 23). - -[![./run-debian-on-your-phone-with-debroid/Deboroid.png](./run-debian-on-your-phone-with-debroid/Deboroid.png)](./run-debian-on-your-phone-with-debroid/Deboroid.png) +## Table of Contents -## Foreword - -A couple of years have passed since I last worked on Debroid. Currently, I am using the Termux app on Android, which is less sophisticated than a fully blown Debian installation but sufficient for my current requirements. The content of this site may be still relevant, and it would also work with more recent versions of Debian and Android. I would expect that some minor modifications need to be made, though. +* [⇢ Run Debian on your phone with Debroid](#run-debian-on-your-phone-with-debroid) +* [⇢ ⇢ Step by step guide](#step-by-step-guide) +* [⇢ ⇢ ⇢ First debootstrap stage](#first-debootstrap-stage) +* [⇢ ⇢ ⇢ Copy Debian image to the phone](#copy-debian-image-to-the-phone) +* [⇢ ⇢ ⇢ Second debootstrap stage](#second-debootstrap-stage) +* [⇢ ⇢ ⇢ Setup of various scripts](#setup-of-various-scripts) +* [⇢ ⇢ ⇢ Entering Debroid and enable a service](#entering-debroid-and-enable-a-service) +* [⇢ ⇢ ⇢ Include to Android startup:](#include-to-android-startup) ## Step by step guide diff --git a/gemfeed/2016-04-09-jails-and-zfs-on-freebsd-with-puppet.md b/gemfeed/2016-04-09-jails-and-zfs-on-freebsd-with-puppet.md index 3879df57..60df5a1b 100644 --- a/gemfeed/2016-04-09-jails-and-zfs-on-freebsd-with-puppet.md +++ b/gemfeed/2016-04-09-jails-and-zfs-on-freebsd-with-puppet.md @@ -2,6 +2,8 @@ > Published at 2016-04-09T18:29:47+01:00 +Over the last couple of years I wrote quite a few Puppet modules in order to manage my personal server infrastructure. One of them manages FreeBSD Jails and another one ZFS file systems. I thought I would give a brief overview in how it looks and feels. + ``` __ __ (( \---/ )) @@ -25,16 +27,11 @@ ## Table of Contents * [⇢ Jails and ZFS with Puppet on FreeBSD](#jails-and-zfs-with-puppet-on-freebsd) -* [⇢ ⇢ Introduction](#introduction) * [⇢ ⇢ ZFS](#zfs) * [⇢ ⇢ Jails](#jails) * [⇢ ⇢ Inside-Jail Puppet](#inside-jail-puppet) * [⇢ ⇢ Managing multiple Jails](#managing-multiple-jails) -## Introduction - -Over the last couple of years I wrote quite a few Puppet modules in order to manage my personal server infrastructure. One of them manages FreeBSD Jails and another one ZFS file systems. I thought I would give a brief overview in how it looks and feels. - ## ZFS The ZFS module is a pretty basic one. It does not manage ZFS pools yet as I am not creating them often enough which would justify implementing an automation. But let's see how we can create a ZFS file system (on an already given ZFS pool named ztank): diff --git a/gemfeed/2016-05-22-spinning-up-my-own-authoritative-dns-servers.md b/gemfeed/2016-05-22-spinning-up-my-own-authoritative-dns-servers.md index b320bbab..23a30ce2 100644 --- a/gemfeed/2016-05-22-spinning-up-my-own-authoritative-dns-servers.md +++ b/gemfeed/2016-05-22-spinning-up-my-own-authoritative-dns-servers.md @@ -2,12 +2,20 @@ > Published at 2016-05-22T18:59:01+01:00 -## Background - Finally, I had time to deploy my authoritative DNS servers (master and slave) for my domains "buetow.org" and "buetow.zone". My domain name provider is Schlund Technologies. They allow their customers to edit the DNS records (BIND files) manually. And they also allow you to set your authoritative DNS servers for your domains. From now, I am making use of that option. [Schlund Technologies](http://www.schlundtech.de) +## Table of Contents + +* [⇢ Spinning up my own authoritative DNS servers](#spinning-up-my-own-authoritative-dns-servers) +* [⇢ ⇢ All FreeBSD Jails](#all-freebsd-jails) +* [⇢ ⇢ PF firewall](#pf-firewall) +* [⇢ ⇢ Puppet managed BIND zone files](#puppet-managed-bind-zone-files) +* [⇢ ⇢ The result](#the-result) +* [⇢ ⇢ Monitoring](#monitoring) +* [⇢ ⇢ DNS update workflow](#dns-update-workflow) + ## All FreeBSD Jails To set up my authoritative DNS servers, I installed a FreeBSD Jail dedicated for DNS with Puppet on my root machine as follows: diff --git a/gemfeed/2018-06-01-realistic-load-testing-with-ioriot-for-linux.md b/gemfeed/2018-06-01-realistic-load-testing-with-ioriot-for-linux.md index 3c876f60..04846fdb 100644 --- a/gemfeed/2018-06-01-realistic-load-testing-with-ioriot-for-linux.md +++ b/gemfeed/2018-06-01-realistic-load-testing-with-ioriot-for-linux.md @@ -2,6 +2,16 @@ > Published at 2018-06-01T14:50:29+01:00; Updated at 2021-05-08 +This text first was published in the german IT-Administrator computer Magazine. 3 years have passed since and I decided to publish it on my blog too. + +[https://www.admin-magazin.de/Das-Heft/2018/06/Realistische-Lasttests-mit-I-O-Riot](https://www.admin-magazin.de/Das-Heft/2018/06/Realistische-Lasttests-mit-I-O-Riot) + +I havn't worked on I/O Riot for some time now, but all what is written here is still valid. I am still using I/O Riot to debug I/O issues and pattern once in a while, so by all means the tool is not obsolete yet. The tool even helped to resolve a major production incident at work caused by disk I/O. + +I am eagerly looking forward to revamp I/O Riot so that it uses the new BPF Linux capabilities instead of plain old Systemtap (or alternatively: Newer versions of Systemtap can also use BPF as the backend I have learned). Also, when I wrote I/O Riot initially, I didn't have any experience with the Go programming language yet and therefore I wrote it in C. Once it gets revamped I might consider using Go instead of C as it would spare me from many segmentation faults and headaches during development ;-). I might also just stick to C for plain performance reasons and just refactor the code dealing with concurrency. + +Pleace notice that some of the screenshots show the command "ioreplay" instead of "ioriot". That's because the name has changed after taking those. + ``` .---. / \ @@ -13,17 +23,21 @@ jgs\__/'---'\__/ ``` -## Foreword - -This text first was published in the german IT-Administrator computer Magazine. 3 years have passed since and I decided to publish it on my blog too. - -[https://www.admin-magazin.de/Das-Heft/2018/06/Realistische-Lasttests-mit-I-O-Riot](https://www.admin-magazin.de/Das-Heft/2018/06/Realistische-Lasttests-mit-I-O-Riot) - -I havn't worked on I/O Riot for some time now, but all what is written here is still valid. I am still using I/O Riot to debug I/O issues and pattern once in a while, so by all means the tool is not obsolete yet. The tool even helped to resolve a major production incident at work caused by disk I/O. - -I am eagerly looking forward to revamp I/O Riot so that it uses the new BPF Linux capabilities instead of plain old Systemtap (or alternatively: Newer versions of Systemtap can also use BPF as the backend I have learned). Also, when I wrote I/O Riot initially, I didn't have any experience with the Go programming language yet and therefore I wrote it in C. Once it gets revamped I might consider using Go instead of C as it would spare me from many segmentation faults and headaches during development ;-). I might also just stick to C for plain performance reasons and just refactor the code dealing with concurrency. - -Pleace notice that some of the screenshots show the command "ioreplay" instead of "ioriot". That's because the name has changed after taking those. +## Table of Contents + +* [⇢ Realistic load testing with I/O Riot for Linux](#realistic-load-testing-with-io-riot-for-linux) +* [⇢ The article](#the-article) +* [⇢ ⇢ Background: Existing Techniques](#background-existing-techniques) +* [⇢ ⇢ Benchmarking the Email Cloud at Mimecast](#benchmarking-the-email-cloud-at-mimecast) +* [⇢ ⇢ Using I/O Riot](#using-io-riot) +* [⇢ ⇢ ⇢ Installation](#installation) +* [⇢ ⇢ ⇢ Recording of I/O events](#recording-of-io-events) +* [⇢ ⇢ ⇢ Test preparation](#test-preparation) +* [⇢ ⇢ ⇢ Test Initialization](#test-initialization) +* [⇢ ⇢ ⇢ Replay](#replay) +* [⇢ ⇢ I/O Riot is Open Source](#io-riot-is-open-source) +* [⇢ ⇢ Systemtap](#systemtap) +* [⇢ ⇢ More refereces](#more-refereces) # The article diff --git a/gemfeed/2021-04-22-dtail-the-distributed-log-tail-program.md b/gemfeed/2021-04-22-dtail-the-distributed-log-tail-program.md index b0a2bf0f..0caa64b0 100644 --- a/gemfeed/2021-04-22-dtail-the-distributed-log-tail-program.md +++ b/gemfeed/2021-04-22-dtail-the-distributed-log-tail-program.md @@ -2,12 +2,23 @@ > Published at 2021-04-22T19:28:41+01:00; Updated at 2021-04-26 +This article first appeared at the Mimecast Engineering Blog but I made it available here in my personal internet site too. + +[Original Mimecast Engineering Blog post at Medium](https://medium.com/mimecast-engineering/dtail-the-distributed-log-tail-program-79b8087904bb) + +Running a large cloud-based service requires monitoring the state of huge numbers of machines, a task for which many standard UNIX tools were not really designed. In this post, I will describe a simple program, DTail, that Mimecast has built and released as Open-Source, which enables us to monitor log files of many servers at once without the costly overhead of a full-blown log management system. + +At Mimecast, we run over 10 thousand server boxes. Most of them host multiple microservices and each of them produces log files. Even with the use of time series databases and monitoring systems, raw application logs are still an important source of information when it comes to analysing, debugging, and troubleshooting services. + +Every engineer familiar with UNIX or a UNIX-like platform (e.g., Linux) is well aware of tail, a command-line program for displaying a text file content on the terminal which is also especially useful for following application or system log files with tail -f logfile. + +Think of DTail as a distributed version of the tail program which is very useful when you have a distributed application running on many servers. DTail is an Open-Source, cross-platform, fairly easy to use, support and maintain log file analysis & statistics gathering tool designed for Engineers and Systems Administrators. It is programmed in Google Go. + [![DTail logo image](./dtail-the-distributed-log-tail-program/title.png "DTail logo image")](./dtail-the-distributed-log-tail-program/title.png) ## Table of Contents * [⇢ DTail - The distributed log tail program](#dtail---the-distributed-log-tail-program) -* [⇢ ⇢ Introduction](#introduction) * [⇢ ⇢ A Mimecast Pet Project](#a-mimecast-pet-project) * [⇢ ⇢ Differentiating from log management systems](#differentiating-from-log-management-systems) * [⇢ ⇢ Combining simplicity, security and efficiency](#combining-simplicity-security-and-efficiency) @@ -18,20 +29,6 @@ * [⇢ ⇢ For the future](#for-the-future) * [⇢ ⇢ Open Source](#open-source) -## Introduction - -This article first appeared at the Mimecast Engineering Blog but I made it available here in my personal internet site too. - -[Original Mimecast Engineering Blog post at Medium](https://medium.com/mimecast-engineering/dtail-the-distributed-log-tail-program-79b8087904bb) - -Running a large cloud-based service requires monitoring the state of huge numbers of machines, a task for which many standard UNIX tools were not really designed. In this post, I will describe a simple program, DTail, that Mimecast has built and released as Open-Source, which enables us to monitor log files of many servers at once without the costly overhead of a full-blown log management system. - -At Mimecast, we run over 10 thousand server boxes. Most of them host multiple microservices and each of them produces log files. Even with the use of time series databases and monitoring systems, raw application logs are still an important source of information when it comes to analysing, debugging, and troubleshooting services. - -Every engineer familiar with UNIX or a UNIX-like platform (e.g., Linux) is well aware of tail, a command-line program for displaying a text file content on the terminal which is also especially useful for following application or system log files with tail -f logfile. - -Think of DTail as a distributed version of the tail program which is very useful when you have a distributed application running on many servers. DTail is an Open-Source, cross-platform, fairly easy to use, support and maintain log file analysis & statistics gathering tool designed for Engineers and Systems Administrators. It is programmed in Google Go. - ## A Mimecast Pet Project DTail got its inspiration from public domain tools available already in this area but it is a blue sky from-scratch development which was first presented at Mimecast’s annual internal Pet Project competition (awarded with a Bronze prize). It has gained popularity since and is one of the most widely deployed DevOps tools at Mimecast (reaching nearly 10k server installations) and many engineers use it on a regular basis. The Open-Source version of DTail is available at: diff --git a/gemfeed/2021-05-16-personal-bash-coding-style-guide.md b/gemfeed/2021-05-16-personal-bash-coding-style-guide.md index 87f8ccb0..d2c0f050 100644 --- a/gemfeed/2021-05-16-personal-bash-coding-style-guide.md +++ b/gemfeed/2021-05-16-personal-bash-coding-style-guide.md @@ -2,6 +2,10 @@ > Published at 2021-05-16T14:51:57+01:00 +Lately, I have been polishing and writing a lot of Bash code. Not that I never wrote a lot of Bash, but now as I also looked through the Google Shell Style Guide, I thought it is time also to write my thoughts on that. I agree with that guide in most, but not in all points. + +[Google Shell Style Guide](https://google.github.io/styleguide/shellguide.html) + ``` .---------------------------. /,--..---..---..---..---..--. `. @@ -18,7 +22,6 @@ ## Table of Contents * [⇢ Personal Bash coding style guide](#personal-bash-coding-style-guide) -* [⇢ ⇢ Introduction](#introduction) * [⇢ ⇢ My modifications](#my-modifications) * [⇢ ⇢ ⇢ Shebang](#shebang) * [⇢ ⇢ ⇢ Two space soft-tabs indentation](#two-space-soft-tabs-indentation) @@ -37,12 +40,6 @@ * [⇢ ⇢ Use common sense and BE CONSISTENT.](#use-common-sense-and-be-consistent) * [⇢ ⇢ Advanced Bash learning pro tip](#advanced-bash-learning-pro-tip) -## Introduction - -Lately, I have been polishing and writing a lot of Bash code. Not that I never wrote a lot of Bash, but now as I also looked through the Google Shell Style Guide, I thought it is time also to write my thoughts on that. I agree with that guide in most, but not in all points. - -[Google Shell Style Guide](https://google.github.io/styleguide/shellguide.html) - ## My modifications These are my modifications to the Google Guide. diff --git a/gemfeed/2021-06-05-gemtexter-one-bash-script-to-rule-it-all.md b/gemfeed/2021-06-05-gemtexter-one-bash-script-to-rule-it-all.md index 580aceab..f71fb3d0 100644 --- a/gemfeed/2021-06-05-gemtexter-one-bash-script-to-rule-it-all.md +++ b/gemfeed/2021-06-05-gemtexter-one-bash-script-to-rule-it-all.md @@ -2,6 +2,10 @@ > Published at 2021-06-05T19:03:32+01:00 +You might have read my previous blog posts about entering the Geminispace, where I pointed out the benefits of having and maintaining an internet presence there. This whole site (the blog and all other pages) is composed in the Gemtext markup language. + +This comes with the benefit that I can write content in my favourite text editor (Vim). + ``` o .,<>., o |\/\/\/\/| @@ -46,8 +50,7 @@ ## Table of Contents * [⇢ Gemtexter - One Bash script to rule it all](#gemtexter---one-bash-script-to-rule-it-all) -* [⇢ ⇢ Introduction](#introduction) -* [⇢ ⇢ ⇢ Motivation](#motivation) +* [⇢ ⇢ Motivation](#motivation) * [⇢ ⇢ Output formats](#output-formats) * [⇢ ⇢ Taking it as far as I should, but no farther](#taking-it-as-far-as-i-should-but-no-farther) * [⇢ ⇢ ⇢ Modularization ](#modularization-) @@ -60,13 +63,7 @@ * [⇢ ⇢ Future features](#future-features) * [⇢ ⇢ Conclusion](#conclusion) -## Introduction - -You might have read my previous blog posts about entering the Geminispace, where I pointed out the benefits of having and maintaining an internet presence there. This whole site (the blog and all other pages) is composed in the Gemtext markup language. - -This comes with the benefit that I can write content in my favourite text editor (Vim). - -### Motivation +## Motivation Another benefit of using Gemini is that the Gemtext markup language is easy to parse. As my site is dual-hosted (Gemini+HTTP), I could, in theory, just write a shell script to deal with the conversion from Gemtext to HTML; there is no need for a full-featured programming language here. I have done a lot of Bash in the past, but I am also often revisiting old tools and techniques for refreshing and keeping the knowledge up to date here. diff --git a/gemfeed/2021-07-04-the-well-grounded-rubyist.md b/gemfeed/2021-07-04-the-well-grounded-rubyist.md index 0e2b2def..07d40f0a 100644 --- a/gemfeed/2021-07-04-the-well-grounded-rubyist.md +++ b/gemfeed/2021-07-04-the-well-grounded-rubyist.md @@ -14,6 +14,20 @@ Superficially, Perl seems to have many similarities to Ruby (but, of course, it Yukihiro Matsumoto, the inventor of Ruby, said: "I wanted a scripting language that was more powerful than Perl and more object-oriented than Python" - So I can see where some of the similarities come from. I personally don't believe that Ruby is more powerful than Perl, though, especially when you take CPAN and/or Perl 6 (now known as Raku) into the equation. Well, it all depends on what you mean with "more powerful". But I want to stay pragmatic and use what's already used at my workplace. +## Table of Contents + +* [⇢ The Well-Grounded Rubyist](#the-well-grounded-rubyist) +* [⇢ ⇢ My Ruby problem domain](#my-ruby-problem-domain) +* [⇢ ⇢ Being stuck in Ruby-mediocrity](#being-stuck-in-ruby-mediocrity) +* [⇢ ⇢ O'Reilly Safari Books Online](#o-reilly-safari-books-online) +* [⇢ ⇢ Key takeaways](#key-takeaways) +* [⇢ ⇢ ⇢ "Everything" is an object](#everything-is-an-object) +* [⇢ ⇢ ⇢ "Normal" objects and singleton objects](#normal-objects-and-singleton-objects) +* [⇢ ⇢ ⇢ Domain specific languages](#domain-specific-languages) +* [⇢ ⇢ ⇢ Ruby is "self-ish"](#ruby-is-self-ish) +* [⇢ ⇢ ⇢ Functional programming](#functional-programming) +* [⇢ ⇢ Perl](#perl) + ## My Ruby problem domain I wrote a lot of Ruby code over the last couple of years. There were many small to medium-sized tools and other projects such as Nagios monitoring checks, even an internal monitoring & reporting site based on Sinatra. All Ruby scripts I wrote do their work well; I didn't encounter any significant problems using Ruby for any of these tasks. Of course, there's nothing that couldn't be written in Perl (or Python), though, after all, these languages are all Turing-complete and all these languages also come with a huge set of 3rd party libraries :-). diff --git a/gemfeed/2021-08-01-on-being-pedantic-about-open-source.md b/gemfeed/2021-08-01-on-being-pedantic-about-open-source.md index a57e01aa..7fea060c 100644 --- a/gemfeed/2021-08-01-on-being-pedantic-about-open-source.md +++ b/gemfeed/2021-08-01-on-being-pedantic-about-open-source.md @@ -2,6 +2,8 @@ > Published at 2021-08-01T10:37:58+03:00; Updated at 2023-01-23 +I believe that it is essential to always have free and open-source alternatives to any kind of closed-source proprietary software available to choose from. But there are a couple of points you need to take into consideration. + ``` __ _____....--' .' @@ -14,7 +16,23 @@ '^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^' LGB - Art by lgbearrd ``` -I believe that it is essential to always have free and open-source alternatives to any kind of closed-source proprietary software available to choose from. But there are a couple of points you need to take into consideration. +## Table of Contents + +* [⇢ On being Pedantic about Open-Source](#on-being-pedantic-about-open-source) +* [⇢ ⇢ The costs of open-source](#the-costs-of-open-source) +* [⇢ ⇢ Commercial providers](#commercial-providers) +* [⇢ ⇢ Earning on open-source](#earning-on-open-source) +* [⇢ ⇢ Open-source organizations and individual contributors](#open-source-organizations-and-individual-contributors) +* [⇢ ⇢ Lesser known projects and the charm of clunkiness](#lesser-known-projects-and-the-charm-of-clunkiness) +* [⇢ ⇢ The security aspect](#the-security-aspect) +* [⇢ ⇢ Always watch out for open-source alternatives](#always-watch-out-for-open-source-alternatives) +* [⇢ ⇢ What about mobile?](#what-about-mobile) +* [⇢ ⇢ Know the alternatives](#know-the-alternatives) +* [⇢ ⇢ You can't control it all](#you-can-t-control-it-all) +* [⇢ ⇢ The middle way](#the-middle-way) +* [⇢ ⇢ The downside of being a nobody](#the-downside-of-being-a-nobody) +* [⇢ ⇢ Mobile open-source OSes are still evolving](#mobile-open-source-oses-are-still-evolving) +* [⇢ ⇢ Conclusion](#conclusion) ## The costs of open-source diff --git a/gemfeed/2021-09-12-keep-it-simple-and-stupid.md b/gemfeed/2021-09-12-keep-it-simple-and-stupid.md index 35215a19..a8617c16 100644 --- a/gemfeed/2021-09-12-keep-it-simple-and-stupid.md +++ b/gemfeed/2021-09-12-keep-it-simple-and-stupid.md @@ -2,6 +2,8 @@ > Published at 2021-09-12T09:39:20+03:00; Updated at 2023-03-23 +A robust computer system must be kept simple and stupid (KISS). The fancier the system is, the more can break. Unfortunately, most systems tend to become complex and challenging to maintain in today's world. In the early days, so I was told, engineers understood every part of the system, but nowadays, we see more of the "lasagna" stack. One layer or framework is built on top of another layer, and in the end, nobody has got a clue what's going on. + ``` _______________ |*\_/*|_______ | ___________ | .-. .-. ||_/-\_|______ | @@ -20,7 +22,6 @@ ## Table of Contents * [⇢ Keep it simple and stupid](#keep-it-simple-and-stupid) -* [⇢ ⇢ Introduction](#introduction) * [⇢ ⇢ Need faster hardware](#need-faster-hardware) * [⇢ ⇢ Too complex to be replaced](#too-complex-to-be-replaced) * [⇢ ⇢ ⇢ On COBOL](#on-cobol) @@ -35,10 +36,6 @@ * [⇢ ⇢ When KISS is not KISS anymore](#when-kiss-is-not-kiss-anymore) * [⇢ ⇢ Other relevant readings](#other-relevant-readings) -## Introduction - -A robust computer system must be kept simple and stupid (KISS). The fancier the system is, the more can break. Unfortunately, most systems tend to become complex and challenging to maintain in today's world. In the early days, so I was told, engineers understood every part of the system, but nowadays, we see more of the "lasagna" stack. One layer or framework is built on top of another layer, and in the end, nobody has got a clue what's going on. - ## Need faster hardware This not just makes the system much more complex, difficult to maintain and challenging to troubleshoot, but also slow. So more experts are needed to support it. Also, newer and faster hardware is required to make it run smoothly. Often, it's so much easier to buy speedier hardware than rewrite a whole system from scratch from the bottom-up. The latter would require much more resources in the short run, but in the long run, it should pay off. Unfortunately, many project owners scare away from it as they only want to get their project done and then move on. diff --git a/gemfeed/2021-10-22-defensive-devops.md b/gemfeed/2021-10-22-defensive-devops.md index d46311ff..2fa5849a 100644 --- a/gemfeed/2021-10-22-defensive-devops.md +++ b/gemfeed/2021-10-22-defensive-devops.md @@ -2,6 +2,16 @@ > Published at 2021-10-22T10:02:46+03:00 +I have seen many different setups and infrastructures during my carreer. My roles always included front-line ad-hoc fire fighting production issues. This often involves identifying and fixing these under time pressure, without the comfort of 2-week-long SCRUM sprints and without an exhaustive QA process. I also wrote a lot of code (Bash, Ruby, Perl, Go, and a little Java), and I followed the typical software development process, but that did not always apply to critical production issues. + +Unfortunately, no system is 100% reliable, and you can never be prepared for a subset of the possible problem-space. IT infrastructures can be complex. Not even mentioning Kubernetes yet, a Microservice-based infrastructure can complicate things even further. You can take care of 99% of all potential problems by following all DevOps best practices. Those best practices are not the subject of this blog post; this post is about the sub 1% of the issues arising from nowhere you can't be prepared for. + +Is there a software bug in a production, even though the software passed QA (after all, it is challenging to reproduce production behaviour in an artificial testing environment) and the software didn't show any issues running in production until a special case came up just now after it got deployed to production a week ago? Are there multiple hardware failure happening which causes loss of service redundancy or data inaccessibility? Is the automation of external customers connected to our infrastructure putting unexpectedly extra pressure on your grid, driving higher latencies and putting the SLAs at risk? You bet the solution is: Sysadmins, SREs and DevOps Engineers to the rescue. + +You agree that fixing production issues this way is not proactive but rather reactive. I prefer to call it defensive, though, as you "defend" your system against a production issue. But, at the same time, you have to take a cautious (defensive) approach to fix it, as you don't want to make things worse. + +Over time, I have compiled a list of fire-fighting automation strategies, which I would like to share here. + ``` c=====e H @@ -12,15 +22,17 @@ ASCII Art by Clyde Watson ``` -I have seen many different setups and infrastructures during my carreer. My roles always included front-line ad-hoc fire fighting production issues. This often involves identifying and fixing these under time pressure, without the comfort of 2-week-long SCRUM sprints and without an exhaustive QA process. I also wrote a lot of code (Bash, Ruby, Perl, Go, and a little Java), and I followed the typical software development process, but that did not always apply to critical production issues. - -Unfortunately, no system is 100% reliable, and you can never be prepared for a subset of the possible problem-space. IT infrastructures can be complex. Not even mentioning Kubernetes yet, a Microservice-based infrastructure can complicate things even further. You can take care of 99% of all potential problems by following all DevOps best practices. Those best practices are not the subject of this blog post; this post is about the sub 1% of the issues arising from nowhere you can't be prepared for. - -Is there a software bug in a production, even though the software passed QA (after all, it is challenging to reproduce production behaviour in an artificial testing environment) and the software didn't show any issues running in production until a special case came up just now after it got deployed to production a week ago? Are there multiple hardware failure happening which causes loss of service redundancy or data inaccessibility? Is the automation of external customers connected to our infrastructure putting unexpectedly extra pressure on your grid, driving higher latencies and putting the SLAs at risk? You bet the solution is: Sysadmins, SREs and DevOps Engineers to the rescue. - -You agree that fixing production issues this way is not proactive but rather reactive. I prefer to call it defensive, though, as you "defend" your system against a production issue. But, at the same time, you have to take a cautious (defensive) approach to fix it, as you don't want to make things worse. - -Over time, I have compiled a list of fire-fighting automation strategies, which I would like to share here. +## Table of Contents + +* [⇢ Defensive DevOps](#defensive-devops) +* [⇢ ⇢ Meet Defensive DevOps](#meet-defensive-devops) +* [⇢ ⇢ Don't fully automate from the beginning](#don-t-fully-automate-from-the-beginning) +* [⇢ ⇢ Develop code directly on production systems](#develop-code-directly-on-production-systems) +* [⇢ ⇢ ⇢ Don't make it worse](#don-t-make-it-worse) +* [⇢ ⇢ Test your code](#test-your-code) +* [⇢ ⇢ Automation](#automation) +* [⇢ ⇢ Out of office hours](#out-of-office-hours) +* [⇢ ⇢ Retrospective](#retrospective) ## Meet Defensive DevOps diff --git a/gemfeed/2021-11-29-bash-golf-part-1.md b/gemfeed/2021-11-29-bash-golf-part-1.md index d0e4fb26..a9f0c793 100644 --- a/gemfeed/2021-11-29-bash-golf-part-1.md +++ b/gemfeed/2021-11-29-bash-golf-part-1.md @@ -2,6 +2,12 @@ > Published at 2021-11-29T14:06:14+00:00; Updated at 2022-01-05 +This is the first blog post about my Bash Golf series. This series is about random Bash tips, tricks and weirdnesses I came across. It's a collection of smaller articles I wrote in an older (in German language) blog, which I translated and refreshed with some new content. + +[2021-11-29 Bash Golf Part 1 (You are currently reading this)](./2021-11-29-bash-golf-part-1.md) +[2022-01-01 Bash Golf Part 2](./2022-01-01-bash-golf-part-2.md) +[2023-12-10 Bash Golf Part 3](./2023-12-10-bash-golf-part-3.md) + ``` '\ . . |>18>> @@ -17,7 +23,6 @@ jgs^^^^^^^`^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^ ## Table of Contents * [⇢ Bash Golf Part 1](#bash-golf-part-1) -* [⇢ ⇢ Introduction](#introduction) * [⇢ ⇢ TCP/IP networking](#tcpip-networking) * [⇢ ⇢ Process substitution](#process-substitution) * [⇢ ⇢ Grouping](#grouping) @@ -27,14 +32,6 @@ jgs^^^^^^^`^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^ * [⇢ ⇢ : aka the null command](#-aka-the-null-command) * [⇢ ⇢ (No) floating point support](#no-floating-point-support) -## Introduction - -This is the first blog post about my Bash Golf series. This series is about random Bash tips, tricks and weirdnesses I came across. It's a collection of smaller articles I wrote in an older (in German language) blog, which I translated and refreshed with some new content. - -[2021-11-29 Bash Golf Part 1 (You are currently reading this)](./2021-11-29-bash-golf-part-1.md) -[2022-01-01 Bash Golf Part 2](./2022-01-01-bash-golf-part-2.md) -[2023-12-10 Bash Golf Part 3](./2023-12-10-bash-golf-part-3.md) - ## TCP/IP networking You probably know the Netcat tool, which is a swiss army knife for TCP/IP networking on the command line. But did you know that the Bash natively supports TCP/IP networking? diff --git a/gemfeed/2021-12-26-how-to-stay-sane-as-a-devops-person.md b/gemfeed/2021-12-26-how-to-stay-sane-as-a-devops-person.md index 03367c30..72b3486d 100644 --- a/gemfeed/2021-12-26-how-to-stay-sane-as-a-devops-person.md +++ b/gemfeed/2021-12-26-how-to-stay-sane-as-a-devops-person.md @@ -2,6 +2,12 @@ > Published at 2021-12-26T12:02:02+00:00; Updated at 2022-01-12 +Log4shell (CVE-2021-44228) made it clear, once again, that working in information technology is not an easy job (especially when you are a DevOps person). I thought it would be interesting to summarize a few techniques to help you to relax. + +(PS: When I mean DevOps, I also mean Site Reliability Engineers and Sysadmins. I believe SRE, DevOps Engineer and Sysadmin are just synonym titles for the same job). + +[https://en.wikipedia.org/wiki/Log4Shell](https://en.wikipedia.org/wiki/Log4Shell) + ``` ) ) (( ( @@ -22,13 +28,25 @@ ||| \ __/_|| __||__ -----||-/------`-._/||-o--o---o--- ~~~~~' -``` - -Log4shell (CVE-2021-44228) made it clear, once again, that working in information technology is not an easy job (especially when you are a DevOps person). I thought it would be interesting to summarize a few techniques to help you to relax. - -(PS: When I mean DevOps, I also mean Site Reliability Engineers and Sysadmins. I believe SRE, DevOps Engineer and Sysadmin are just synonym titles for the same job). - -[https://en.wikipedia.org/wiki/Log4Shell](https://en.wikipedia.org/wiki/Log4Shell) +``` + +## Table of Contents + +* [⇢ How to stay sane as a DevOps person ](#how-to-stay-sane-as-a-devops-person-) +* [⇢ ⇢ Set clear expectations](#set-clear-expectations) +* [⇢ ⇢ Always respond to requests but set expectations and boundaries](#always-respond-to-requests-but-set-expectations-and-boundaries) +* [⇢ ⇢ ⇢ Dealing with requests](#dealing-with-requests) +* [⇢ ⇢ ⇢ Escalation is only a tool](#escalation-is-only-a-tool) +* [⇢ ⇢ Think positively](#think-positively) +* [⇢ ⇢ Go slower even if you could go faster](#go-slower-even-if-you-could-go-faster) +* [⇢ ⇢ ⇢ You work in a team](#you-work-in-a-team) +* [⇢ ⇢ ⇢ Don't rush](#don-t-rush) +* [⇢ ⇢ You are not a superhero](#you-are-not-a-superhero) +* [⇢ ⇢ ⇢ Give away some of your superpowers](#give-away-some-of-your-superpowers) +* [⇢ ⇢ Don't jump on all problems immediately](#don-t-jump-on-all-problems-immediately) +* [⇢ ⇢ Force breaks; and shutdown now](#force-breaks-and-shutdown-now) +* [⇢ ⇢ Block time every day for personal advance](#block-time-every-day-for-personal-advance) +* [⇢ ⇢ More](#more) ## Set clear expectations diff --git a/gemfeed/2022-01-01-bash-golf-part-2.md b/gemfeed/2022-01-01-bash-golf-part-2.md index 5f6df763..d1330128 100644 --- a/gemfeed/2022-01-01-bash-golf-part-2.md +++ b/gemfeed/2022-01-01-bash-golf-part-2.md @@ -2,6 +2,12 @@ > Published at 2022-01-01T23:36:15+00:00; Updated at 2022-01-05 +This is the second blog post about my Bash Golf series. This series is random Bash tips, tricks and weirdnesses I came across. It's a collection of smaller articles I wrote in an older (in German language) blog, which I translated and refreshed with some new content. + +[2021-11-29 Bash Golf Part 1](./2021-11-29-bash-golf-part-1.md) +[2022-01-01 Bash Golf Part 2 (You are currently reading this)](./2022-01-01-bash-golf-part-2.md) +[2023-12-10 Bash Golf Part 3](./2023-12-10-bash-golf-part-3.md) + ``` '\ '\ . . |>18>> @@ -17,7 +23,6 @@ jgs^^^^^^^`^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^ ## Table of Contents * [⇢ Bash Golf Part 2](#bash-golf-part-2) -* [⇢ ⇢ Introduction](#introduction) * [⇢ ⇢ Redirection](#redirection) * [⇢ ⇢ HERE](#here) * [⇢ ⇢ RANDOM](#random) @@ -26,14 +31,6 @@ jgs^^^^^^^`^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^ * [⇢ ⇢ ⇢ -e](#-e) * [⇢ ⇢ ⇢ pipefail](#pipefail) -## Introduction - -This is the second blog post about my Bash Golf series. This series is random Bash tips, tricks and weirdnesses I came across. It's a collection of smaller articles I wrote in an older (in German language) blog, which I translated and refreshed with some new content. - -[2021-11-29 Bash Golf Part 1](./2021-11-29-bash-golf-part-1.md) -[2022-01-01 Bash Golf Part 2 (You are currently reading this)](./2022-01-01-bash-golf-part-2.md) -[2023-12-10 Bash Golf Part 3](./2023-12-10-bash-golf-part-3.md) - ## Redirection Let's have a closer look at Bash redirection. As you might already know that there are 3 standard file descriptors: diff --git a/gemfeed/2022-02-04-computer-operating-systems-i-use.md b/gemfeed/2022-02-04-computer-operating-systems-i-use.md index d19adeb9..ea88b859 100644 --- a/gemfeed/2022-02-04-computer-operating-systems-i-use.md +++ b/gemfeed/2022-02-04-computer-operating-systems-i-use.md @@ -2,6 +2,8 @@ > Published at 2022-02-04T09:58:22+00:00; Updated at 2022-02-18 +This is a list of Operating Systems I currently use. This list is in no particular order and also will be updated over time. The very first operating system I used was MS-DOS (mainly for games) and the very first Unix like operating system I used was SuSE Linux 5.3. My first smartphone OS was Symbian on a clunky Sony Ericsson device. + ``` /( )` \ \___ / | @@ -26,7 +28,6 @@ ## Table of Contents * [⇢ Computer operating systems I use(d)](#computer-operating-systems-i-used) -* [⇢ ⇢ Introduction](#introduction) * [⇢ ⇢ Fedora Linux](#fedora-linux) * [⇢ ⇢ EndeavourOS](#endeavouros) * [⇢ ⇢ FreeBSD](#freebsd) @@ -48,10 +49,6 @@ * [⇢ ⇢ ⇢ Other OSes I only had a glance at...](#other-oses-i-only-had-a-glance-at) * [⇢ ⇢ ⇢ Other OSes which seem interesting...](#other-oses-which-seem-interesting) -## Introduction - -This is a list of Operating Systems I currently use. This list is in no particular order and also will be updated over time. The very first operating system I used was MS-DOS (mainly for games) and the very first Unix like operating system I used was SuSE Linux 5.3. My first smartphone OS was Symbian on a clunky Sony Ericsson device. - ## Fedora Linux Fedora Linux is the operating system I use on my primary (personal) laptop. It's a ThinkPad X1 Carbon Gen. 9. Lenovo which comes along with official Lenovo Linux support. I already noticed hardware firmware updates being installed directly through Fedora from Lenovo. Fedora is a real powerhouse, cutting-edge and reasonably stable at the same time. It's baked by Red Hat. diff --git a/gemfeed/2022-03-06-the-release-of-dtail-4.0.0.md b/gemfeed/2022-03-06-the-release-of-dtail-4.0.0.md index 42527f51..98b238d0 100644 --- a/gemfeed/2022-03-06-the-release-of-dtail-4.0.0.md +++ b/gemfeed/2022-03-06-the-release-of-dtail-4.0.0.md @@ -2,6 +2,10 @@ > Published at 2022-03-06T18:11:39+00:00 +I have recently released DTail 4.0.0 and this blog post goes through all the new goodies. If you want to jump directly to DTail, do it here (there are nice animated gifs which demonstrates the usage pretty well): + +[https://dtail.dev](https://dtail.dev) + ``` ,_---~~~~~----._ _,,_,*^____ _____``*g*\"*, @@ -19,7 +23,6 @@ ## Table of Contents * [⇢ The release of DTail 4.0.0](#the-release-of-dtail-400) -* [⇢ ⇢ Introduction](#introduction) * [⇢ ⇢ So, what's new in 4.0.0?](#so-what-s-new-in-400) * [⇢ ⇢ ⇢ Rewritten logging](#rewritten-logging) * [⇢ ⇢ ⇢ Configurable terminal color codes](#configurable-terminal-color-codes) @@ -34,12 +37,6 @@ * [⇢ ⇢ ⇢ Use of memory pools](#use-of-memory-pools) * [⇢ ⇢ What's next](#what-s-next) -## Introduction - -I have recently released DTail 4.0.0 and this blog post goes through all the new goodies. If you want to jump directly to DTail, do it here (there are nice animated gifs which demonstrates the usage pretty well): - -[https://dtail.dev](https://dtail.dev) - ## So, what's new in 4.0.0? ### Rewritten logging diff --git a/gemfeed/2022-04-10-creative-universe.md b/gemfeed/2022-04-10-creative-universe.md index f884dc1b..4f49e989 100644 --- a/gemfeed/2022-04-10-creative-universe.md +++ b/gemfeed/2022-04-10-creative-universe.md @@ -2,6 +2,22 @@ > Published at 2022-04-10T10:09:11+01:00; Updated at 2022-04-18 +I have been participating in an annual work-internal project contest (we call it Pet Project contest) since I moved to London and switched jobs to my current employer. I am very happy to say that I won a "silver" prize last week here 🎆. Over the last couple of years I have been a finalist in this contest six times and won some kind of prize five times. Some of my projects were also released as open source software. One had a magazine article published, and for another one I wrote an article on my employer's engineering blog. If you have followed all my posts on this blog (the one you are currently reading), then you have probably figured out what these projects were: + +[DTail - The distributed log tail program](./2021-04-22-dtail-the-distributed-log-tail-program.md) +[Realistic load testing with I/O Riot for linux](./2018-06-01-realistic-load-testing-with-ioriot-for-linux.md) + +Note that my latest silver prize project isn't open source software and because of that there is no public material I can refer to. Maybe the next one again? + +I want to point out that I never won the "gold" prize and it's the first time I won "silver", though. I believe, looking at the company's contest history, I am the employee with the most consecutive successful project submissions (my streak broke as I didn't participate last year) and am also the one with the highest successful project count in total. Sorry if this all sounds a bit self-promotional, but I think it is something to be proud of. Consistency beats a one-off success. + +I often put endless hours and sometimes sleepless nights into such projects and all of that in my own time. I, an engineer whose native tongue is not English, also have to present such a project in front of the CEO, CTO and CPO, the Chief Scientist, the founders of the company, and, if it is not enough, to all other staff of the company too. I usually also demonstrate a working prototype live on a production grid during the presentation. 😓 + +So why would I sign up myself for such side projects? Isn't it a lot of stress and extra work? Besides the prize in form of money (you can not count on that, you may win or you may not win something) and recognition, there are also other motivational points: + +* I want to learn new technologies or to deepen my knowledge of a given technology. I want to have a personal benefit from the project, even when I don't win any prize. So when the company is offering a contest, why not use it as a motivational trampoline? It's good to have a hard deadline for a project. And the project will also benefit the company in some way. So it's a win-win. +* I love the idea of combining several old things into a new thing. You can call this creativity. At work, we call this sometimes Lego: Building new things from given blocks. But I also love to add something new and unique to the mix, something that didn't exist as a Lego block before and could not be built by using only the already existing blocks. + ``` . + . . . . . . . . . * @@ -23,23 +39,18 @@ - the universe ``` -## Prelude - -I have been participating in an annual work-internal project contest (we call it Pet Project contest) since I moved to London and switched jobs to my current employer. I am very happy to say that I won a "silver" prize last week here 🎆. Over the last couple of years I have been a finalist in this contest six times and won some kind of prize five times. Some of my projects were also released as open source software. One had a magazine article published, and for another one I wrote an article on my employer's engineering blog. If you have followed all my posts on this blog (the one you are currently reading), then you have probably figured out what these projects were: - -[DTail - The distributed log tail program](./2021-04-22-dtail-the-distributed-log-tail-program.md) -[Realistic load testing with I/O Riot for linux](./2018-06-01-realistic-load-testing-with-ioriot-for-linux.md) - -Note that my latest silver prize project isn't open source software and because of that there is no public material I can refer to. Maybe the next one again? - -I want to point out that I never won the "gold" prize and it's the first time I won "silver", though. I believe, looking at the company's contest history, I am the employee with the most consecutive successful project submissions (my streak broke as I didn't participate last year) and am also the one with the highest successful project count in total. Sorry if this all sounds a bit self-promotional, but I think it is something to be proud of. Consistency beats a one-off success. - -I often put endless hours and sometimes sleepless nights into such projects and all of that in my own time. I, an engineer whose native tongue is not English, also have to present such a project in front of the CEO, CTO and CPO, the Chief Scientist, the founders of the company, and, if it is not enough, to all other staff of the company too. I usually also demonstrate a working prototype live on a production grid during the presentation. 😓 - -So why would I sign up myself for such side projects? Isn't it a lot of stress and extra work? Besides the prize in form of money (you can not count on that, you may win or you may not win something) and recognition, there are also other motivational points: - -* I want to learn new technologies or to deepen my knowledge of a given technology. I want to have a personal benefit from the project, even when I don't win any prize. So when the company is offering a contest, why not use it as a motivational trampoline? It's good to have a hard deadline for a project. And the project will also benefit the company in some way. So it's a win-win. -* I love the idea of combining several old things into a new thing. You can call this creativity. At work, we call this sometimes Lego: Building new things from given blocks. But I also love to add something new and unique to the mix, something that didn't exist as a Lego block before and could not be built by using only the already existing blocks. +## Table of Contents + +* [⇢ Creative universe](#creative-universe) +* [⇢ ⇢ How to be creative](#how-to-be-creative) +* [⇢ ⇢ ⇢ Know which problem you want to solve](#know-which-problem-you-want-to-solve) +* [⇢ ⇢ ⇢ Immerse / deep dive](#immerse--deep-dive) +* [⇢ ⇢ ⇢ Always have a notebook with you](#always-have-a-notebook-with-you) +* [⇢ ⇢ ⇢ When you didn't sleep enough](#when-you-didn-t-sleep-enough) +* [⇢ ⇢ ⇢ Have regular breaks and relax](#have-regular-breaks-and-relax) +* [⇢ ⇢ ⇢ Upside-down approach](#upside-down-approach) +* [⇢ ⇢ ⇢ Don't be busy all the time](#don-t-be-busy-all-the-time) +* [⇢ ⇢ Conclusion](#conclusion) ## How to be creative diff --git a/gemfeed/2022-05-27-perl-is-still-a-great-choice.md b/gemfeed/2022-05-27-perl-is-still-a-great-choice.md index 2849a07f..b7ba1644 100644 --- a/gemfeed/2022-05-27-perl-is-still-a-great-choice.md +++ b/gemfeed/2022-05-27-perl-is-still-a-great-choice.md @@ -2,20 +2,6 @@ > Published at 2022-05-27T07:50:12+01:00; Updated at 2023-01-28 -[![Comic source: XKCD](./perl-is-still-a-great-choice/regular_expressions.png "Comic source: XKCD")](./perl-is-still-a-great-choice/regular_expressions.png) - -## Table of Contents - -* [⇢ Perl is still a great choice](#perl-is-still-a-great-choice) -* [⇢ ⇢ Introduction](#introduction) -* [⇢ ⇢ Write-only language](#write-only-language) -* [⇢ ⇢ Is Perl abandoned?](#is-perl-abandoned) -* [⇢ ⇢ Why use Perl as there are better alternatives?](#why-use-perl-as-there-are-better-alternatives) -* [⇢ ⇢ Why all the sigils? It looks like an exploding ASCII factory!!](#why-all-the-sigils-it-looks-like-an-exploding-ascii-factory) -* [⇢ ⇢ Where do I personally still use perl?](#where-do-i-personally-still-use-perl) - -## Introduction - Perl (the Practical Extraction and Report Language) is a battle-tested, mature, multi-paradigm dynamic programming language. Note that it's not called PERL, neither P.E.R.L. nor Pearl. "Perl" is the name of the language and `perl` the name of the interpreter or the interpreter command. Unfortunately (it makes me sad), Perl's popularity has been declining over the last years as Google trends shows: @@ -29,6 +15,17 @@ So why is that? Once the de-facto standard super-glue language for the web nowad * Why use Perl as there are better alternatives? * Why all the sigils? It looks like an exploding ASCII factory!! +[![Comic source: XKCD](./perl-is-still-a-great-choice/regular_expressions.png "Comic source: XKCD")](./perl-is-still-a-great-choice/regular_expressions.png) + +## Table of Contents + +* [⇢ Perl is still a great choice](#perl-is-still-a-great-choice) +* [⇢ ⇢ Write-only language](#write-only-language) +* [⇢ ⇢ Is Perl abandoned?](#is-perl-abandoned) +* [⇢ ⇢ Why use Perl as there are better alternatives?](#why-use-perl-as-there-are-better-alternatives) +* [⇢ ⇢ Why all the sigils? It looks like an exploding ASCII factory!!](#why-all-the-sigils-it-looks-like-an-exploding-ascii-factory) +* [⇢ ⇢ Where do I personally still use perl?](#where-do-i-personally-still-use-perl) + ## Write-only language Is Perl really a write-only language? You have to understand that Perl 5 was released in 1994 (28 years ago as of this writing) and when we refer to Perl we usually mean Perl 5. That's many years, and there are many old scripts not following the modern Perl best practices (as they didn't exist yet). So yes, legacy scripts may be difficult to read. Japanese may be difficult to read too if you don't know Japanese, though. diff --git a/gemfeed/2022-06-15-sweating-the-small-stuff.md b/gemfeed/2022-06-15-sweating-the-small-stuff.md index cbc0311f..43807184 100644 --- a/gemfeed/2022-06-15-sweating-the-small-stuff.md +++ b/gemfeed/2022-06-15-sweating-the-small-stuff.md @@ -2,14 +2,6 @@ > Published at 2022-06-15T08:47:44+01:00; Updated at 2022-06-18 -``` - _ - /_/_ .'''. - =O(_)))) ...' `. - jgs \_\ `. .''' - `..' -``` - This blog post is a bit different from the others. It consists of multiple but smaller projects worth mentioning. I got inspired by Julia Evan's "Tiny programs" blog post and the side projects of The Sephist, so I thought I would also write a blog posts listing a couple of small projects of mine: [Tiny programs](https://jvns.ca/blog/2022/03/08/tiny-programs/) @@ -19,6 +11,39 @@ Working on tiny projects is a lot of fun as you don't need to worry about any st But before going through the tiny projects let's take a paragraph for the `1y` anniversary retrospective. +``` + _ + /_/_ .'''. + =O(_)))) ...' `. + jgs \_\ `. .''' + `..' +``` + +## Table of Contents + +* [⇢ Sweating the small stuff - Tiny projects of mine](#sweating-the-small-stuff---tiny-projects-of-mine) +* [⇢ ⇢ `1y` anniversary](#1y-anniversary) +* [⇢ ⇢ Static photo album generator](#static-photo-album-generator) +* [⇢ ⇢ ⇢ The Irregular Ninja](#the-irregular-ninja) +* [⇢ ⇢ Random journal page extractor](#random-journal-page-extractor) +* [⇢ ⇢ Global uptime records statistic generator](#global-uptime-records-statistic-generator) +* [⇢ ⇢ Server configuration management](#server-configuration-management) +* [⇢ ⇢ Fancy SSH execution loop](#fancy-ssh-execution-loop) +* [⇢ ⇢ A KISS dynamic DNS solution](#a-kiss-dynamic-dns-solution) +* [⇢ ⇢ CPU information gatherer for Linux](#cpu-information-gatherer-for-linux) +* [⇢ ⇢ Show differences of two files over the network](#show-differences-of-two-files-over-the-network) +* [⇢ ⇢ Delay sending out E-Mails with Mutt](#delay-sending-out-e-mails-with-mutt) +* [⇢ ⇢ Graphical UI for sending text messages](#graphical-ui-for-sending-text-messages) +* [⇢ ⇢ IPv6 and IPv4 connectivity testing site](#ipv6-and-ipv4-connectivity-testing-site) +* [⇢ ⇢ List open Jira tickets in the terminal](#list-open-jira-tickets-in-the-terminal) +* [⇢ ⇢ Debian running on "your" Android phone](#debian-running-on-your-android-phone) +* [⇢ ⇢ Perl service framework](#perl-service-framework) +* [⇢ ⇢ More](#more) +* [⇢ ⇢ ⇢ Work time tracker](#work-time-tracker) +* [⇢ ⇢ ⇢ Password and document store](#password-and-document-store) +* [⇢ ⇢ ⇢ Backup procedure](#backup-procedure) +* [⇢ ⇢ konpeito.media](#konpeitomedia) + ## `1y` anniversary It has been one year since I started posting regularly (at least once monthly) on this blog again. It has been a lot of fun (and work) doing so for various reasons: diff --git a/gemfeed/2022-07-30-lets-encrypt-with-openbsd-and-rex.md b/gemfeed/2022-07-30-lets-encrypt-with-openbsd-and-rex.md index 746dab78..35870c2c 100644 --- a/gemfeed/2022-07-30-lets-encrypt-with-openbsd-and-rex.md +++ b/gemfeed/2022-07-30-lets-encrypt-with-openbsd-and-rex.md @@ -2,6 +2,8 @@ > Published at 2022-07-30T12:14:31+01:00 +I was amazed at how easy it is to automatically generate and update Let's Encrypt certificates with OpenBSD. + ``` / _ \ The Hebern Machine \ ." ". / @@ -32,7 +34,6 @@ ## Table of Contents * [⇢ Let's Encrypt with OpenBSD and Rex](#let-s-encrypt-with-openbsd-and-rex) -* [⇢ ⇢ Introduction](#introduction) * [⇢ ⇢ ⇢ What's Let's Encrypt?](#what-s-let-s-encrypt) * [⇢ ⇢ Meet `acme-client`](#meet-acme-client) * [⇢ ⇢ Configuration](#configuration) @@ -46,10 +47,6 @@ * [⇢ ⇢ All pieces together](#all-pieces-together) * [⇢ ⇢ Conclusion](#conclusion) -## Introduction - -I was amazed at how easy it is to automatically generate and update Let's Encrypt certificates with OpenBSD. - ### What's Let's Encrypt? > Let's Encrypt is a non-profit certificate authority run by Internet Security Research Group that provides X.509 certificates for Transport Layer Security (TLS) encryption at no charge. It is the world's largest certificate authority, used by more than 265 million websites, with the goal of all websites being secure and using HTTPS. diff --git a/gemfeed/2022-08-27-gemtexter-1.1.0-lets-gemtext-again.md b/gemfeed/2022-08-27-gemtexter-1.1.0-lets-gemtext-again.md index 8e7a2464..24161520 100644 --- a/gemfeed/2022-08-27-gemtexter-1.1.0-lets-gemtext-again.md +++ b/gemfeed/2022-08-27-gemtexter-1.1.0-lets-gemtext-again.md @@ -2,6 +2,12 @@ > Published at 2022-08-27T18:25:57+01:00 +I proudly announce that I've released Gemtexter version `1.1.0`. What is Gemtexter? It's my minimalist static site generator for Gemini Gemtext, HTML and Markdown written in GNU Bash. + +[https://codeberg.org/snonux/gemtexter](https://codeberg.org/snonux/gemtexter) + +It has been around a year since I released the first version `1.0.0`. Although, there aren't any groundbreaking changes, there have been a couple of smaller commits and adjustments. I was quite surprised that I received a bunch of feedback and requests about Gemtexter so it means that I am not the only person in the universe actually using it. + ``` -=[ typewriter ]=- 1/98 @@ -17,7 +23,6 @@ ## Table of Contents * [⇢ Gemtexter 1.1.0 - Let's Gemtext again](#gemtexter-110---let-s-gemtext-again) -* [⇢ ⇢ Introduction](#introduction) * [⇢ ⇢ What's new?](#what-s-new) * [⇢ ⇢ ⇢ Automatic check for GNU version requirements](#automatic-check-for-gnu-version-requirements) * [⇢ ⇢ ⇢ Backticks now produce `inline code blocks` in the HTML output](#backticks-now-produce-inline-code-blocks-in-the-html-output) @@ -28,14 +33,6 @@ * [⇢ ⇢ ⇢ Sub-section support](#sub-section-support) * [⇢ ⇢ ⇢ More](#more) -## Introduction - -I proudly announce that I've released Gemtexter version `1.1.0`. What is Gemtexter? It's my minimalist static site generator for Gemini Gemtext, HTML and Markdown written in GNU Bash. - -[https://codeberg.org/snonux/gemtexter](https://codeberg.org/snonux/gemtexter) - -It has been around a year since I released the first version `1.0.0`. Although, there aren't any groundbreaking changes, there have been a couple of smaller commits and adjustments. I was quite surprised that I received a bunch of feedback and requests about Gemtexter so it means that I am not the only person in the universe actually using it. - ## What's new? ### Automatic check for GNU version requirements diff --git a/gemfeed/2022-09-30-after-a-bad-nights-sleep.md b/gemfeed/2022-09-30-after-a-bad-nights-sleep.md index 91c6f553..100c55b8 100644 --- a/gemfeed/2022-09-30-after-a-bad-nights-sleep.md +++ b/gemfeed/2022-09-30-after-a-bad-nights-sleep.md @@ -2,6 +2,8 @@ > Published at 2022-09-30T09:53:23+03:00; Updated at 2022-10-12 +Everyone has it once in a while: A bad night's sleep. Here I attempt to list valuable tips on how to deal with it. + ``` z z @@ -16,7 +18,24 @@ jgs (________\ \ '-' ``` -Everyone has it once in a while: A bad night's sleep. Here I attempt to list valuable tips on how to deal with it. +## Table of Contents + +* [⇢ After a bad night's sleep](#after-a-bad-night-s-sleep) +* [⇢ ⇢ Don't take the day off.](#don-t-take-the-day-off) +* [⇢ ⇢ Start work early](#start-work-early) +* [⇢ ⇢ Sweat the small stuff](#sweat-the-small-stuff) +* [⇢ ⇢ Enter the flow state](#enter-the-flow-state) +* [⇢ ⇢ Reschedule meetings](#reschedule-meetings) +* [⇢ ⇢ Invent](#invent) +* [⇢ ⇢ Fast](#fast) +* [⇢ ⇢ Stretch](#stretch) +* [⇢ ⇢ Walk](#walk) +* [⇢ ⇢ Red Bull](#red-bull) +* [⇢ ⇢ Power nap](#power-nap) +* [⇢ ⇢ Don't take anything personally.](#don-t-take-anything-personally) +* [⇢ ⇢ Meditate](#meditate) +* [⇢ ⇢ Write things down](#write-things-down) +* [⇢ ⇢ Social media](#social-media) ## Don't take the day off. diff --git a/gemfeed/2022-10-30-installing-dtail-on-openbsd.md b/gemfeed/2022-10-30-installing-dtail-on-openbsd.md index bf3d9a96..232e7bb4 100644 --- a/gemfeed/2022-10-30-installing-dtail-on-openbsd.md +++ b/gemfeed/2022-10-30-installing-dtail-on-openbsd.md @@ -2,6 +2,18 @@ > Published at 2022-10-30T11:03:19+02:00 +This will be a quick blog post, as I am busy with my personal life now. I have relocated to a different country and am still busy arranging things. So bear with me :-) + + In this post, I want to give a quick overview (or how-to) about installing DTail on OpenBSD, as the official documentation only covers Red Hat and Fedora Linux! And this blog post will also be used as my reference! + +[https://dtail.dev](https://dtail.dev) + +I am using Rexify for my OpenBSD automation. Check out the following article covering my Rex setup in a little bit more detail: + +[Let's Encrypt with OpenBSD and Rex](./2022-07-30-lets-encrypt-with-openbsd-and-rex.md) + +I will also mention some relevant `Rexfile` snippets in this post! + ``` ,_---~~~~~----._ _,,_,*^____ _____``*g*\"*, @@ -42,7 +54,6 @@ ## Table of Contents * [⇢ Installing DTail on OpenBSD](#installing-dtail-on-openbsd) -* [⇢ ⇢ Introduction](#introduction) * [⇢ ⇢ Compile it](#compile-it) * [⇢ ⇢ Install it](#install-it) * [⇢ ⇢ ⇢ Rexification](#rexification) @@ -54,20 +65,6 @@ * [⇢ ⇢ Use it](#use-it) * [⇢ ⇢ Conclusions](#conclusions) -## Introduction - -This will be a quick blog post, as I am busy with my personal life now. I have relocated to a different country and am still busy arranging things. So bear with me :-) - - In this post, I want to give a quick overview (or how-to) about installing DTail on OpenBSD, as the official documentation only covers Red Hat and Fedora Linux! And this blog post will also be used as my reference! - -[https://dtail.dev](https://dtail.dev) - -I am using Rexify for my OpenBSD automation. Check out the following article covering my Rex setup in a little bit more detail: - -[Let's Encrypt with OpenBSD and Rex](./2022-07-30-lets-encrypt-with-openbsd-and-rex.md) - -I will also mention some relevant `Rexfile` snippets in this post! - ## Compile it First of all, DTail needs to be downloaded and compiled. For that, `git`, `go`, and `gmake` are required: diff --git a/gemfeed/2022-11-24-i-tried-emacs-but-i-switched-back-to-neovim.md b/gemfeed/2022-11-24-i-tried-emacs-but-i-switched-back-to-neovim.md index adefac5d..1f92fd71 100644 --- a/gemfeed/2022-11-24-i-tried-emacs-but-i-switched-back-to-neovim.md +++ b/gemfeed/2022-11-24-i-tried-emacs-but-i-switched-back-to-neovim.md @@ -2,6 +2,18 @@ > Published at 2022-11-24T11:17:15+02:00; Updated at 2022-11-26 +As a long-lasting user of Vim (and NeoVim), I always wondered what GNU Emacs is really about, so I decided to try it. I didn't try vanilla GNU Emacs, but Doom Emacs. I chose Doom Emacs as it is a neat distribution of Emacs with Evil mode enabled by default. Evil mode allows Vi(m) key bindings (so to speak, it's emulating Vim within Emacs), and I am pretty sure I won't be ready to give up all the muscle memory I have built over more than a decade. + +[GNU Emacs](https://www.gnu.org/software/emacs/) +[Doom Emacs](https://github.com/doomemacs/) + +I used Doom Emacs for around two months. Still, ultimately I decided to switch back to NeoVim as my primary editor and IDE and Vim (usually pre-installed on Linux-based systems) and Nvi (usually pre-installed on *BSD systems) as my "always available editor" for quick edits. (It is worth mentioning that I don't have a high opinion on whether Vim or NeoVim is the better editor, I prefer NeoVim as it comes with better defaults out of the box, but there is no real blocker to use Vim instead). + +[Vim](https://www.vim.org) +[NeoVim](https://neovim.io) + +So why did I switch back to the Vi-family? + ``` _/ \ _(\(o / \ / _ ^^^o @@ -15,17 +27,16 @@ Art by \ \_! / __! ^^----^^ "^--v' ``` -As a long-lasting user of Vim (and NeoVim), I always wondered what GNU Emacs is really about, so I decided to try it. I didn't try vanilla GNU Emacs, but Doom Emacs. I chose Doom Emacs as it is a neat distribution of Emacs with Evil mode enabled by default. Evil mode allows Vi(m) key bindings (so to speak, it's emulating Vim within Emacs), and I am pretty sure I won't be ready to give up all the muscle memory I have built over more than a decade. - -[GNU Emacs](https://www.gnu.org/software/emacs/) -[Doom Emacs](https://github.com/doomemacs/) +## Table of Contents -I used Doom Emacs for around two months. Still, ultimately I decided to switch back to NeoVim as my primary editor and IDE and Vim (usually pre-installed on Linux-based systems) and Nvi (usually pre-installed on *BSD systems) as my "always available editor" for quick edits. (It is worth mentioning that I don't have a high opinion on whether Vim or NeoVim is the better editor, I prefer NeoVim as it comes with better defaults out of the box, but there is no real blocker to use Vim instead). - -[Vim](https://www.vim.org) -[NeoVim](https://neovim.io) - -So why did I switch back to the Vi-family? +* [⇢ I tried (Doom) Emacs, but I switched back to (Neo)Vim](#i-tried-doom-emacs-but-i-switched-back-to-neovim) +* [⇢ ⇢ Emacs is a giant dragon](#emacs-is-a-giant-dragon) +* [⇢ ⇢ Magit love](#magit-love) +* [⇢ ⇢ Graphical UI](#graphical-ui) +* [⇢ ⇢ Scripting it](#scripting-it) +* [⇢ ⇢ The famous Emacs Org mode](#the-famous-emacs-org-mode) +* [⇢ ⇢ Seeking simplicity](#seeking-simplicity) +* [⇢ ⇢ Conclusion](#conclusion) ## Emacs is a giant dragon diff --git a/gemfeed/2022-12-24-ultrarelearning-java-my-takeaways.md b/gemfeed/2022-12-24-ultrarelearning-java-my-takeaways.md index 90f57d05..4dedc97d 100644 --- a/gemfeed/2022-12-24-ultrarelearning-java-my-takeaways.md +++ b/gemfeed/2022-12-24-ultrarelearning-java-my-takeaways.md @@ -2,8 +2,6 @@ > Published at 2022-12-24T23:18:40+02:00 -[![./ultrarelearning-java-my-takeaways/learnjava.jpg](./ultrarelearning-java-my-takeaways/learnjava.jpg)](./ultrarelearning-java-my-takeaways/learnjava.jpg) - As a regular participant in the annual Pet Project competition at work, I always try to find a project where I can learn something new. In this post, I would like to share my takeaways after revisiting Java. You can read about my motivations in my "Creative universe" post: [Creative universe](./2022-04-10-creative-universe.md) @@ -16,6 +14,23 @@ However, after that, I became a Linux Sysadmin and mainly continued programming At my workplace, as an SRE, I don't do Java a lot. I have been reading Java code to understand the software better so I can apply and suggest workarounds or fixes to existing issues and bugs. However, most of our stack is in Java, and our Software Engineers use Java as their primary programming language. +[![./ultrarelearning-java-my-takeaways/learnjava.jpg](./ultrarelearning-java-my-takeaways/learnjava.jpg)](./ultrarelearning-java-my-takeaways/learnjava.jpg) + +## Table of Contents + +* [⇢ (Re)learning Java - My takeaways](#relearning-java---my-takeaways) +* [⇢ ⇢ Stuck at Java 1.4](#stuck-at-java-14) +* [⇢ ⇢ (Re)learning & upskilling to Java 18](#relearning--upskilling-to-java-18) +* [⇢ ⇢ ⇢ Effective Java](#effective-java) +* [⇢ ⇢ ⇢ Java Pub House](#java-pub-house) +* [⇢ ⇢ ⇢ Java Concurrency course](#java-concurrency-course) +* [⇢ ⇢ ⇢ Read a lot of Java code](#read-a-lot-of-java-code) +* [⇢ ⇢ ⇢ Observed Java code reviews](#observed-java-code-reviews) +* [⇢ ⇢ ⇢ Took ownership of a roadmap-Java project](#took-ownership-of-a-roadmap-java-project) +* [⇢ ⇢ The good](#the-good) +* [⇢ ⇢ The bad and the ugly](#the-bad-and-the-ugly) +* [⇢ ⇢ Conclusion](#conclusion) + ## Stuck at Java 1.4 Over time, I had been missing out on many new features that were added to the language since Java 1.4, so I decided to implement my next Pet Project in Java and learn every further aspect of the language as my main goal. Of course, I still liked the idea of winning a Pet Project Prize, but my main objective was to level up my Java skills. diff --git a/gemfeed/2023-01-23-why-grapheneos-rox.md b/gemfeed/2023-01-23-why-grapheneos-rox.md index 765c0825..2cd45d62 100644 --- a/gemfeed/2023-01-23-why-grapheneos-rox.md +++ b/gemfeed/2023-01-23-why-grapheneos-rox.md @@ -2,6 +2,19 @@ > Published at 2023-01-23T15:31:52+02:00 +In 2021 I wrote "On Being Pedantic about Open-Source", and there was a section "What about mobile?" where I expressed the dilemma about the necessity of using proprietary mobile operating systems. With GrapheneOS, I found my perfect solution for personal mobile phone use. + +[On Being Pedantic about Open-Source](./2021-08-01-on-being-pedantic-about-open-source.md) + +What is GrapheneOS? + +> GrapheneOS is a privacy and security-focused mobile OS with Android app compatibility developed as a non-profit open-source project. It's focused on the research and development of privacy and security technologies, including substantial improvements to sandboxing, exploits mitigations and the permission model. + +GrapheneOS is an independent Android distribution based on the Android Open Source Project (AOSP) but hardened in multiple ways. Other independent Android distributions, like LineageOS, are also based on AOSP, but GrapheneOS takes it further so that it can be my daily driver on my phone. + +[https://GrapheneOS.org](https://GrapheneOS.org) +[https://LineageOS.org](https://LineageOS.org) + ``` Art by Joan Stark _.===========================._ @@ -25,18 +38,17 @@ Art by Joan Stark '-'-'-'--' ``` -In 2021 I wrote "On Being Pedantic about Open-Source", and there was a section "What about mobile?" where I expressed the dilemma about the necessity of using proprietary mobile operating systems. With GrapheneOS, I found my perfect solution for personal mobile phone use. - -[On Being Pedantic about Open-Source](./2021-08-01-on-being-pedantic-about-open-source.md) - -What is GrapheneOS? - -> GrapheneOS is a privacy and security-focused mobile OS with Android app compatibility developed as a non-profit open-source project. It's focused on the research and development of privacy and security technologies, including substantial improvements to sandboxing, exploits mitigations and the permission model. - -GrapheneOS is an independent Android distribution based on the Android Open Source Project (AOSP) but hardened in multiple ways. Other independent Android distributions, like LineageOS, are also based on AOSP, but GrapheneOS takes it further so that it can be my daily driver on my phone. - -[https://GrapheneOS.org](https://GrapheneOS.org) -[https://LineageOS.org](https://LineageOS.org) +## Table of Contents + +* [⇢ Why GrapheneOS rox](#why-grapheneos-rox) +* [⇢ ⇢ User Profiles](#user-profiles) +* [⇢ ⇢ Proxying some of the Google offerings ](#proxying-some-of-the-google-offerings-) +* [⇢ ⇢ Google Play Sandboxing ](#google-play-sandboxing-) +* [⇢ ⇢ The camera and the cloud ](#the-camera-and-the-cloud-) +* [⇢ ⇢ Fine granular permissions](#fine-granular-permissions) +* [⇢ ⇢ Termux](#termux) +* [⇢ ⇢ So, why not use a pure Linux phone?](#so-why-not-use-a-pure-linux-phone) +* [⇢ ⇢ Small GrapheneOS downsides ](#small-grapheneos-downsides-) ## User Profiles diff --git a/gemfeed/2023-02-26-how-to-shut-down-after-work.md b/gemfeed/2023-02-26-how-to-shut-down-after-work.md index 8212c60c..90a71d7b 100644 --- a/gemfeed/2023-02-26-how-to-shut-down-after-work.md +++ b/gemfeed/2023-02-26-how-to-shut-down-after-work.md @@ -2,6 +2,8 @@ > Published at 2023-02-26T23:48:01+02:00 +Do you need help fully discharging from work in the evenings or for the weekend? Shutting down from work won't just improve your work-life balance; it will also significantly improve the quality of your personal life and work. After a restful weekend, you will be much more energized and productive the next working day. So it should not just be in your own, but also your employers' interest that you fully relax and shut down after work. + ``` |\ "Music should be heard not only with the ears, but also the soul." |---|--\-----------------------|-----------------------------------------| @@ -17,7 +19,16 @@ -@- [kom...@uwec.edu] ``` -Do you need help fully discharging from work in the evenings or for the weekend? Shutting down from work won't just improve your work-life balance; it will also significantly improve the quality of your personal life and work. After a restful weekend, you will be much more energized and productive the next working day. So it should not just be in your own, but also your employers' interest that you fully relax and shut down after work. +## Table of Contents + +* [⇢ How to shut down after work](#how-to-shut-down-after-work) +* [⇢ ⇢ Have a shutdown routine](#have-a-shutdown-routine) +* [⇢ ⇢ Don't work when you officially don't work](#don-t-work-when-you-officially-don-t-work) +* [⇢ ⇢ Distract your mind](#distract-your-mind) +* [⇢ ⇢ Get a pet](#get-a-pet) +* [⇢ ⇢ Journal your day](#journal-your-day) +* [⇢ ⇢ Don't stress about what your employer expects from you](#don-t-stress-about-what-your-employer-expects-from-you) +* [⇢ ⇢ Call it a day](#call-it-a-day) ## Have a shutdown routine diff --git a/gemfeed/2023-03-25-gemtexter-2.0.0-lets-gemtext-again-2.md b/gemfeed/2023-03-25-gemtexter-2.0.0-lets-gemtext-again-2.md index f8b31a17..a025fd8f 100644 --- a/gemfeed/2023-03-25-gemtexter-2.0.0-lets-gemtext-again-2.md +++ b/gemfeed/2023-03-25-gemtexter-2.0.0-lets-gemtext-again-2.md @@ -2,6 +2,14 @@ > Published at 2023-03-25T17:50:32+02:00 +I proudly announce that I've released Gemtexter version `2.0.0`. What is Gemtexter? It's my minimalist static site generator for Gemini Gemtext, HTML and Markdown written in GNU Bash. + +[https://codeberg.org/snonux/gemtexter](https://codeberg.org/snonux/gemtexter) + +This is a new major release, so it contains a breaking change (see "Meta cache made obsolete"). + +Let's list what's new! + ``` -=[ typewriters ]=- 1/98 @@ -18,7 +26,6 @@ ## Table of Contents * [⇢ Gemtexter 2.0.0 - Let's Gemtext again²](#gemtexter-200---let-s-gemtext-again) -* [⇢ ⇢ Introduction](#introduction) * [⇢ ⇢ Minimal template engine](#minimal-template-engine) * [⇢ ⇢ Added hooks](#added-hooks) * [⇢ ⇢ Use of safer Bash options](#use-of-safer-bash-options) @@ -26,16 +33,6 @@ * [⇢ ⇢ XMLLint support](#xmllint-support) * [⇢ ⇢ More](#more) -## Introduction - -I proudly announce that I've released Gemtexter version `2.0.0`. What is Gemtexter? It's my minimalist static site generator for Gemini Gemtext, HTML and Markdown written in GNU Bash. - -[https://codeberg.org/snonux/gemtexter](https://codeberg.org/snonux/gemtexter) - -This is a new major release, so it contains a breaking change (see "Meta cache made obsolete"). - -Let's list what's new! - ## Minimal template engine Gemtexter now supports templating, enabling dynamically generated content to `.gmi` files before converting anything to any output format like HTML and Markdown. diff --git a/gemfeed/2023-04-01-never-split-the-difference-book-notes.md b/gemfeed/2023-04-01-never-split-the-difference-book-notes.md index 171d357b..0dcc7a8e 100644 --- a/gemfeed/2023-04-01-never-split-the-difference-book-notes.md +++ b/gemfeed/2023-04-01-never-split-the-difference-book-notes.md @@ -16,6 +16,21 @@ These are my personal takeaways after reading "Never split the difference" by Ch ''' ``` +## Table of Contents + +* [⇢ "Never split the difference" book notes](#never-split-the-difference-book-notes) +* [⇢ ⇢ Tactical listening, spreading empathy](#tactical-listening-spreading-empathy) +* [⇢ ⇢ Mindset of discovery](#mindset-of-discovery) +* [⇢ ⇢ ⇢ More tips ](#more-tips-) +* [⇢ ⇢ "No" starts the conversation](#no-starts-the-conversation) +* [⇢ ⇢ Win-win](#win-win) +* [⇢ ⇢ On Deadlines](#on-deadlines) +* [⇢ ⇢ Analyse the opponent](#analyse-the-opponent) +* [⇢ ⇢ Use different ways of saying "no."](#use-different-ways-of-saying-no) +* [⇢ ⇢ Calibrated question](#calibrated-question) +* [⇢ ⇢ The black swan ](#the-black-swan-) +* [⇢ ⇢ More](#more) + ## Tactical listening, spreading empathy Be a mirror, copy each other to be comfy with each other to build up trust. Mirroring is mainly body language. A mirror is to repeat the words the other just said. Simple but effective. diff --git a/gemfeed/2023-04-09-algorithms-and-data-structures-in-golang-part-1.md b/gemfeed/2023-04-09-algorithms-and-data-structures-in-golang-part-1.md index dd8fc38a..265fe76b 100644 --- a/gemfeed/2023-04-09-algorithms-and-data-structures-in-golang-part-1.md +++ b/gemfeed/2023-04-09-algorithms-and-data-structures-in-golang-part-1.md @@ -2,6 +2,12 @@ > Published at 2023-04-09T22:31:42+03:00 +This is the first blog post about my Algorithms and Data Structures in Go series. I am not a Software Developer in my day job. In my current role, programming and scripting skills are desirable but not mandatory. I have been learning about Data Structures and Algorithms many years ago at University. I thought it would be fun to revisit/refresh my knowledge here and implement many of the algorithms in Go. + +[2023-04-09 Algorithms and Data Structures in Go - Part 1 (You are currently reading this)](./2023-04-09-algorithms-and-data-structures-in-golang-part-1.md) + +This post is about setting up some basic data structures and methods for this blog series. I promise, everything will be easy to follow in this post. It will become more interesting later in this series. + ``` ,_---~~~~~----._ _,,_,*^____ _____``*g*\"*, @@ -19,21 +25,12 @@ ## Table of Contents * [⇢ Algorithms and Data Structures in Go - Part 1](#algorithms-and-data-structures-in-go---part-1) -* [⇢ ⇢ Introduction](#introduction) * [⇢ ⇢ Type constraints](#type-constraints) * [⇢ ⇢ ArrayList](#arraylist) * [⇢ ⇢ Helper methods](#helper-methods) * [⇢ ⇢ Sleep sort](#sleep-sort) * [⇢ ⇢ ⇢ Testing](#testing) -## Introduction - -This is the first blog post about my Algorithms and Data Structures in Go series. I am not a Software Developer in my day job. In my current role, programming and scripting skills are desirable but not mandatory. I have been learning about Data Structures and Algorithms many years ago at University. I thought it would be fun to revisit/refresh my knowledge here and implement many of the algorithms in Go. - -[2023-04-09 Algorithms and Data Structures in Go - Part 1 (You are currently reading this)](./2023-04-09-algorithms-and-data-structures-in-golang-part-1.md) - -This post is about setting up some basic data structures and methods for this blog series. I promise, everything will be easy to follow in this post. It will become more interesting later in this series. - ## Type constraints First, the package `ds` (data structures) defines the `types.go`. All examples will either operate on the `Integer` or `Number` type: diff --git a/gemfeed/2023-05-01-unveiling-guprecords b/gemfeed/2023-05-01-unveiling-guprecords index e69de29b..8b137891 100644 --- a/gemfeed/2023-05-01-unveiling-guprecords +++ b/gemfeed/2023-05-01-unveiling-guprecords @@ -0,0 +1 @@ + diff --git a/gemfeed/2023-05-06-the-obstacle-is-the-way-book-notes.md b/gemfeed/2023-05-06-the-obstacle-is-the-way-book-notes.md index 8a2e31a9..e546bcc8 100644 --- a/gemfeed/2023-05-06-the-obstacle-is-the-way-book-notes.md +++ b/gemfeed/2023-05-06-the-obstacle-is-the-way-book-notes.md @@ -2,10 +2,23 @@ > Published at 2023-05-06T17:23:16+03:00 +These are my personal takeaways after reading "The Obstacle Is the Way" by Ryan Holiday. This is mainly for my own use, but you might find it helpful too. + +``` + ,.......... .........., + ,..,' '.' ',.., + ,' ,' : ', ', + ,' ,' : ', ', + ,' ,' : ', ', + ,' ,'............., : ,.............', ', +,' '............ '.' ............' ', + '''''''''''''''''';''';'''''''''''''''''' + ''' +``` + ## Table of Contents * [⇢ "The Obstacle is the Way" book notes](#the-obstacle-is-the-way-book-notes) -* [⇢ ⇢ Introduction](#introduction) * [⇢ ⇢ Reframe your perspective](#reframe-your-perspective) * [⇢ ⇢ Embrace rationality](#embrace-rationality) * [⇢ ⇢ Control your response](#control-your-response) @@ -19,23 +32,6 @@ * [⇢ ⇢ Love everything that happens](#love-everything-that-happens) * [⇢ ⇢ Conclusion](#conclusion) -## Introduction - -These are my personal takeaways after reading "The Obstacle Is the Way" by Ryan Holiday. This is mainly for my own use, but you might find it helpful too. - - -``` - ,.......... .........., - ,..,' '.' ',.., - ,' ,' : ', ', - ,' ,' : ', ', - ,' ,' : ', ', - ,' ,'............., : ,.............', ', -,' '............ '.' ............' ', - '''''''''''''''''';''';'''''''''''''''''' - ''' -``` - "The obstacle is the way" is a powerful statement that encapsulates the wisdom of turning challenges into opportunities for growth and success. We will explore using obstacles as fuel, transforming weaknesses into strengths, and adopting a mindset that allows us to be creative and persistent in the face of adversity. ## Reframe your perspective diff --git a/gemfeed/2023-06-01-kiss-server-monitoring-with-gogios.md b/gemfeed/2023-06-01-kiss-server-monitoring-with-gogios.md index d9a34b54..9da6dceb 100644 --- a/gemfeed/2023-06-01-kiss-server-monitoring-with-gogios.md +++ b/gemfeed/2023-06-01-kiss-server-monitoring-with-gogios.md @@ -2,12 +2,17 @@ > Published at 2023-06-01T21:10:17+03:00 +Gogios is a minimalistic and easy-to-use monitoring tool I programmed in Google Go designed specifically for small-scale self-hosted servers and virtual machines. The primary purpose of Gogios is to monitor my personal server infrastructure for `foo.zone`, my MTAs, my authoritative DNS servers, my NextCloud, Wallabag and Anki sync server installations, etc. + +With compatibility with the Nagios Check API, Gogios offers a simple yet effective solution to monitor a limited number of resources. In theory, Gogios scales to a couple of thousand checks, though. You can clone it from Codeberg here: + +[https://codeberg.org/snonux/gogios](https://codeberg.org/snonux/gogios) + [![Gogios logo](./kiss-server-monitoring-with-gogios/gogios-small.png "Gogios logo")](./kiss-server-monitoring-with-gogios/gogios-small.png) ## Table of Contents * [⇢ KISS server monitoring with Gogios](#kiss-server-monitoring-with-gogios) -* [⇢ ⇢ Introduction](#introduction) * [⇢ ⇢ Motivation](#motivation) * [⇢ ⇢ Features](#features) * [⇢ ⇢ Example alert](#example-alert) @@ -22,14 +27,6 @@ * [⇢ ⇢ ⇢ High-availability](#high-availability) * [⇢ ⇢ Conclusion:](#conclusion) -## Introduction - -Gogios is a minimalistic and easy-to-use monitoring tool I programmed in Google Go designed specifically for small-scale self-hosted servers and virtual machines. The primary purpose of Gogios is to monitor my personal server infrastructure for `foo.zone`, my MTAs, my authoritative DNS servers, my NextCloud, Wallabag and Anki sync server installations, etc. - -With compatibility with the Nagios Check API, Gogios offers a simple yet effective solution to monitor a limited number of resources. In theory, Gogios scales to a couple of thousand checks, though. You can clone it from Codeberg here: - -[https://codeberg.org/snonux/gogios](https://codeberg.org/snonux/gogios) - ``` _____________________________ ____________________________ / \ / \ diff --git a/gemfeed/2023-07-17-career-guide-and-soft-skills-book-notes.md b/gemfeed/2023-07-17-career-guide-and-soft-skills-book-notes.md index 67439538..3a28aa17 100644 --- a/gemfeed/2023-07-17-career-guide-and-soft-skills-book-notes.md +++ b/gemfeed/2023-07-17-career-guide-and-soft-skills-book-notes.md @@ -2,16 +2,29 @@ > Published at 2023-07-17T04:56:20+03:00 +These notes are of two books by "John Sommez" I found helpful. I also added some of my own keypoints to it. These notes are mainly for my own use, but you might find them helpful, too. + +``` + ,.......... .........., + ,..,' '.' ',.., + ,' ,' : ', ', + ,' ,' : ', ', + ,' ,' : ', ', + ,' ,'............., : ,.............', ', +,' '............ '.' ............' ', + '''''''''''''''''';''';'''''''''''''''''' + ''' +``` + ## Table of Contents * [⇢ "Software Developmers Career Guide and Soft Skills" book notes](#software-developmers-career-guide-and-soft-skills-book-notes) -* [⇢ Introduction](#introduction) -* [⇢ Improve](#improve) -* [⇢ ⇢ Always learn new things](#always-learn-new-things) -* [⇢ ⇢ Set goals](#set-goals) -* [⇢ ⇢ Ratings](#ratings) -* [⇢ ⇢ Promotions](#promotions) -* [⇢ ⇢ Finish things](#finish-things) +* [⇢ ⇢ Improve](#improve) +* [⇢ ⇢ ⇢ Always learn new things](#always-learn-new-things) +* [⇢ ⇢ ⇢ Set goals](#set-goals) +* [⇢ ⇢ ⇢ Ratings](#ratings) +* [⇢ ⇢ ⇢ Promotions](#promotions) +* [⇢ ⇢ ⇢ Finish things](#finish-things) * [⇢ ⇢ Expand the empire](#expand-the-empire) * [⇢ ⇢ Be pragmatic and also manage your time](#be-pragmatic-and-also-manage-your-time) * [⇢ ⇢ ⇢ The quota system](#the-quota-system) @@ -35,25 +48,9 @@ * [⇢ ⇢ Testing](#testing) * [⇢ ⇢ Books to read](#books-to-read) -# Introduction - -These notes are of two books by "John Sommez" I found helpful. I also added some of my own keypoints to it. These notes are mainly for my own use, but you might find them helpful, too. - -``` - ,.......... .........., - ,..,' '.' ',.., - ,' ,' : ', ', - ,' ,' : ', ', - ,' ,' : ', ', - ,' ,'............., : ,.............', ', -,' '............ '.' ............' ', - '''''''''''''''''';''';'''''''''''''''''' - ''' -``` - -# Improve +## Improve -## Always learn new things +### Always learn new things When you learn something new, e.g. a programming language, first gather an overview, learn from multiple sources, play around and learn by doing and not consuming and form your own questions. Don't read too much upfront. A large amount of time is spent in learning technical skills which were never use. You want to have a practical set of skills you are actually using. You need to know 20 percent to get out 80 percent of the results. @@ -70,18 +67,18 @@ Fake it until you make it. But be honest about your abilities or lack of. There Boot camps: The advantage of a boot camp is to pragmatically learn things fast. We almost always overestimate what we can do in a day. Especially during boot camps. Connect to others during the boot camps -## Set goals +### Set goals Your own goals are important but the manager also looks at how the team performs and how someone can help the team perform better. Check whether you are on track with your goals every 2 weeks in order to avoid surprises for the annual review. Make concrete goals for next review. Track and document your progress. Invest in your education. Make your goals known. If you want something, then ask for it. Nobody but you knows what you want. -## Ratings +### Ratings That's a trap: If you have to rate yourself, that's a trap. That never works in an unbiased way. Rate yourself always the best way but rate your weakest part as high as possible minus one point. Rate yourself as good as you can otherwise. Nobody is putting for fun a gun on his own head. * Don't do peer rating, it can fire back on you. What if the colleague becomes your new boss? * Cooperate rankings are unfortunately HR guidelines and politics and only mirror a little your actual performance. -## Promotions +### Promotions The most valuable employees are the ones who make themselves obsolete and automate all away. Keep a safety net of 3 to 6 months of finances. Safe at least 10 percent of your earnings. Also, if you make money it does not mean that you have to spent more money. Is a new car better than a used car which both can bring you from A to B? Liability vs assets. @@ -93,7 +90,7 @@ The most valuable employees are the ones who make themselves obsolete and automa * If you want a raise be specific how much and know to back your demands. Don't make a thread and no ultimatums. * Best way for a promotion is to switch jobs. You can even switch back with a better salary. -## Finish things +### Finish things Hard work is necessary for accomplish results. However, work smarter not harder. Furthermore, working smart is not a substitute for working hard. Work both, hard and smart. diff --git a/gemfeed/2023-07-21-gemtexter-2.1.0-lets-gemtext-again-3.md b/gemfeed/2023-07-21-gemtexter-2.1.0-lets-gemtext-again-3.md index 92531bbb..f98ce69d 100644 --- a/gemfeed/2023-07-21-gemtexter-2.1.0-lets-gemtext-again-3.md +++ b/gemfeed/2023-07-21-gemtexter-2.1.0-lets-gemtext-again-3.md @@ -2,6 +2,10 @@ > Published at 2023-07-21T10:19:31+03:00 +I proudly announce that I've released Gemtexter version `2.1.0`. What is Gemtexter? It's my minimalist static site generator for Gemini Gemtext, HTML and Markdown, written in GNU Bash. + +[https://codeberg.org/snonux/gemtexter](https://codeberg.org/snonux/gemtexter) + ``` -=[ typewriters ]=- 1/98 .-------. @@ -18,7 +22,6 @@ ## Table of Contents * [⇢ Gemtexter 2.1.0 - Let's Gemtext again³](#gemtexter-210---let-s-gemtext-again) -* [⇢ ⇢ Introduction](#introduction) * [⇢ ⇢ Why Bash?](#why-bash) * [⇢ ⇢ Switch to GPL3 license](#switch-to-gpl3-license) * [⇢ ⇢ Source code highlighting support](#source-code-highlighting-support) @@ -27,12 +30,6 @@ * [⇢ ⇢ HTML Mastodon verification support](#html-mastodon-verification-support) * [⇢ ⇢ More](#more) -## Introduction - -I proudly announce that I've released Gemtexter version `2.1.0`. What is Gemtexter? It's my minimalist static site generator for Gemini Gemtext, HTML and Markdown, written in GNU Bash. - -[https://codeberg.org/snonux/gemtexter](https://codeberg.org/snonux/gemtexter) - ## Why Bash? This project is too complex for a Bash script. Writing it in Bash was to try out how maintainable a "larger" Bash script could be. It's still pretty maintainable and helps me try new Bash tricks here and then! diff --git a/gemfeed/2023-09-25-dtail-usage-examples.md b/gemfeed/2023-09-25-dtail-usage-examples.md index 6eeb4521..595afb36 100644 --- a/gemfeed/2023-09-25-dtail-usage-examples.md +++ b/gemfeed/2023-09-25-dtail-usage-examples.md @@ -2,22 +2,6 @@ > Published at 2023-09-25T14:57:42+03:00 -## Table of Contents - -* [⇢ DTail usage examples](#dtail-usage-examples) -* [⇢ ⇢ Introduction](#introduction) -* [⇢ ⇢ Following logs](#following-logs) -* [⇢ ⇢ Aggregating logs](#aggregating-logs) -* [⇢ ⇢ How to use `dcat`](#how-to-use-dcat) -* [⇢ ⇢ How to use `dgrep`](#how-to-use-dgrep) -* [⇢ ⇢ How to use `dmap`](#how-to-use-dmap) -* [⇢ ⇢ How to use the DTail serverless mode](#how-to-use-the-dtail-serverless-mode) -* [⇢ ⇢ ⇢ Serverless map-reduce query](#serverless-map-reduce-query) -* [⇢ ⇢ ⇢ Aggregating CSV files](#aggregating-csv-files) -* [⇢ ⇢ ⇢ Other serverless commands](#other-serverless-commands) - -## Introduction - Hey there. As I am pretty busy this month personally (I am now on Paternity Leave) and as I still want to post once monthly, the blog post of this month will only be some DTail usage examples. They're from the DTail documentation, but not all readers of my blog may be aware of those! DTail is a distributed DevOps tool for tailing, grepping, catting logs and other text files on many remote machines at once which I programmed in Go. @@ -38,6 +22,22 @@ DTail is a distributed DevOps tool for tailing, grepping, catting logs and other | | ``` +## Table of Contents + +* [⇢ DTail usage examples](#dtail-usage-examples) +* [⇢ ⇢ Commands](#commands) +* [⇢ ⇢ Following logs](#following-logs) +* [⇢ ⇢ Aggregating logs](#aggregating-logs) +* [⇢ ⇢ How to use `dcat`](#how-to-use-dcat) +* [⇢ ⇢ How to use `dgrep`](#how-to-use-dgrep) +* [⇢ ⇢ How to use `dmap`](#how-to-use-dmap) +* [⇢ ⇢ How to use the DTail serverless mode](#how-to-use-the-dtail-serverless-mode) +* [⇢ ⇢ ⇢ Serverless map-reduce query](#serverless-map-reduce-query) +* [⇢ ⇢ ⇢ Aggregating CSV files](#aggregating-csv-files) +* [⇢ ⇢ ⇢ Other serverless commands](#other-serverless-commands) + +## Commands + DTail consists out of a server and several client binaries. In this post, I am showcasing their use! * Use `dtail` to follow logs diff --git a/gemfeed/2023-10-29-kiss-static-web-photo-albums-with-photoalbum.sh.md b/gemfeed/2023-10-29-kiss-static-web-photo-albums-with-photoalbum.sh.md index e9321c24..dd8c0167 100644 --- a/gemfeed/2023-10-29-kiss-static-web-photo-albums-with-photoalbum.sh.md +++ b/gemfeed/2023-10-29-kiss-static-web-photo-albums-with-photoalbum.sh.md @@ -2,6 +2,12 @@ > Published at 2023-10-29T22:25:04+02:00 +Once in a while, I share photos on the inter-web with either family and friends or on my The Irregular Ninja photo site. One hobby of mine is photography (even though I don't have enough time for it - so I am primarily a point-and-shoot photographer). + +I'm not particularly eager to use any photo social sharing platforms such as Flickr, 500px (I used them regularly in the past), etc., anymore. I value self-hosting, DIY and privacy (nobody should data mine my photos), and no third party should have any rights to my pictures. + +I value KISS (keep it simple and stupid) and simplicity. All that's required for a web photo album is some simple HTML and spice it up with CSS. No need for JavaScript, no need for a complex dynamic website. + ``` ___ .---------.._ ______!fsc!_....-' .g8888888p. '-------....._ @@ -22,7 +28,6 @@ ## Table of Contents * [⇢ KISS static web photo albums with `photoalbum.sh`](#kiss-static-web-photo-albums-with-photoalbumsh) -* [⇢ ⇢ Motivation](#motivation) * [⇢ ⇢ Introducing `photoalbum.sh`](#introducing-photoalbumsh) * [⇢ ⇢ Installation](#installation) * [⇢ ⇢ Setting it up](#setting-it-up) @@ -31,14 +36,6 @@ * [⇢ ⇢ HTML templates](#html-templates) * [⇢ ⇢ Conclusion](#conclusion) -## Motivation - -Once in a while, I share photos on the inter-web with either family and friends or on my The Irregular Ninja photo site. One hobby of mine is photography (even though I don't have enough time for it - so I am primarily a point-and-shoot photographer). - -I'm not particularly eager to use any photo social sharing platforms such as Flickr, 500px (I used them regularly in the past), etc., anymore. I value self-hosting, DIY and privacy (nobody should data mine my photos), and no third party should have any rights to my pictures. - -I value KISS (keep it simple and stupid) and simplicity. All that's required for a web photo album is some simple HTML and spice it up with CSS. No need for JavaScript, no need for a complex dynamic website. - ## Introducing `photoalbum.sh` `photoalbum.sh` is a minimal Bash (Bourne Again Shell) script for Unix-like operating systems (such as Linux) to generate static web photo albums. The resulting static photo album is pure HTML+CSS (without any JavaScript!). It is specially designed to be as simple as possible. diff --git a/gemfeed/2023-11-11-mind-management-book-notes.md b/gemfeed/2023-11-11-mind-management-book-notes.md index 9efc6f85..863f33e5 100644 --- a/gemfeed/2023-11-11-mind-management-book-notes.md +++ b/gemfeed/2023-11-11-mind-management-book-notes.md @@ -2,21 +2,6 @@ > Published at 2023-11-11T22:21:47+02:00 -## Table of Contents - -* [⇢ "Mind Management" book notes](#mind-management-book-notes) -* [⇢ ⇢ Introduction](#introduction) -* [⇢ ⇢ Empty slots in the calendar](#empty-slots-in-the-calendar) -* [⇢ ⇢ When you safe time...](#when-you-safe-time) -* [⇢ ⇢ Follow your mood](#follow-your-mood) -* [⇢ ⇢ Boosting creativity](#boosting-creativity) -* [⇢ ⇢ The right mood for the task at hand](#the-right-mood-for-the-task-at-hand) -* [⇢ ⇢ Creativity hacks](#creativity-hacks) -* [⇢ ⇢ Planning and strategizing](#planning-and-strategizing) -* [⇢ ⇢ Fake it until you make it. ](#fake-it-until-you-make-it-) - -## Introduction - These are my personal takeaways after reading "Mind Management" by David Kadavy. Note that the book contains much more knowledge wisdom and that these notes only contain points I personally found worth writing down. This is mainly for my own use, but you might find it helpful too. ``` @@ -31,6 +16,21 @@ These are my personal takeaways after reading "Mind Management" by David Kadavy. ''' ``` +## Table of Contents + +* [⇢ "Mind Management" book notes](#mind-management-book-notes) +* [⇢ ⇢ It's not about time management](#it-s-not-about-time-management) +* [⇢ ⇢ Empty slots in the calendar](#empty-slots-in-the-calendar) +* [⇢ ⇢ When you safe time...](#when-you-safe-time) +* [⇢ ⇢ Follow your mood](#follow-your-mood) +* [⇢ ⇢ Boosting creativity](#boosting-creativity) +* [⇢ ⇢ The right mood for the task at hand](#the-right-mood-for-the-task-at-hand) +* [⇢ ⇢ Creativity hacks](#creativity-hacks) +* [⇢ ⇢ Planning and strategizing](#planning-and-strategizing) +* [⇢ ⇢ Fake it until you make it. ](#fake-it-until-you-make-it-) + +## It's not about time management + Productivity isn't about time management - it's about mind management. When you put a lot of effort into something, there are: * The point of diminishing returns diff --git a/gemfeed/2023-12-10-bash-golf-part-3.md b/gemfeed/2023-12-10-bash-golf-part-3.md index 6e58a05e..f315e387 100644 --- a/gemfeed/2023-12-10-bash-golf-part-3.md +++ b/gemfeed/2023-12-10-bash-golf-part-3.md @@ -2,6 +2,12 @@ > Published at 2023-12-10T11:35:54+02:00 +This is the third blog post about my Bash Golf series. This series is random Bash tips, tricks, and weirdnesses I have encountered over time. + +[2021-11-29 Bash Golf Part 1](./2021-11-29-bash-golf-part-1.md) +[2022-01-01 Bash Golf Part 2](./2022-01-01-bash-golf-part-2.md) +[2023-12-10 Bash Golf Part 3 (You are currently reading this)](./2023-12-10-bash-golf-part-3.md) + ``` '\ '\ '\ . . |>18>> @@ -17,7 +23,6 @@ jgs^^^^^^^`^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^ ## Table of Contents * [⇢ Bash Golf Part 3](#bash-golf-part-3) -* [⇢ ⇢ Introduction](#introduction) * [⇢ ⇢ `FUNCNAME`](#funcname) * [⇢ ⇢ `:(){ :|:& };:`](#--) * [⇢ ⇢ Inner functions](#inner-functions) @@ -27,14 +32,6 @@ jgs^^^^^^^`^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^ * [⇢ ⇢ Multi-line comments](#multi-line-comments) * [⇢ ⇢ Don't change it while it's executed](#don-t-change-it-while-it-s-executed) -## Introduction - -This is the third blog post about my Bash Golf series. This series is random Bash tips, tricks, and weirdnesses I have encountered over time. - -[2021-11-29 Bash Golf Part 1](./2021-11-29-bash-golf-part-1.md) -[2022-01-01 Bash Golf Part 2](./2022-01-01-bash-golf-part-2.md) -[2023-12-10 Bash Golf Part 3 (You are currently reading this)](./2023-12-10-bash-golf-part-3.md) - ## `FUNCNAME` `FUNCNAME` is an array you are looking for a way to dynamically determine the name of the current function (which could be considered the callee in the context of its own execution), you can use the special variable `FUNCNAME`. This is an array variable that contains the names of all shell functions currently in the execution call stack. The element `FUNCNAME[0]` holds the name of the currently executing function, `FUNCNAME[1]` the name of the function that called that, and so on. diff --git a/gemfeed/2024-02-04-from-babylon5.buetow.org-to-.cloud.md b/gemfeed/2024-02-04-from-babylon5.buetow.org-to-.cloud.md index dacb1fe5..f78a7d51 100644 --- a/gemfeed/2024-02-04-from-babylon5.buetow.org-to-.cloud.md +++ b/gemfeed/2024-02-04-from-babylon5.buetow.org-to-.cloud.md @@ -8,6 +8,23 @@ So, I migrated all of my Docker-based self-hosted services to AWS. Usually, I am [![Old man yells at cloud](./from-.org-to-.cloud/old-man-yells-at-cloud.jpg "Old man yells at cloud")](./from-.org-to-.cloud/old-man-yells-at-cloud.jpg) +## Table of Contents + +* [⇢ From `babylon5.buetow.org` to `*.buetow.cloud`](#from-babylon5buetoworg-to-buetowcloud) +* [⇢ ⇢ The old `*.buetow.org` way](#the-old-buetoworg-way) +* [⇢ ⇢ I kept my `buetow.org` OpenBSD boxes alive](#i-kept-my-buetoworg-openbsd-boxes-alive) +* [⇢ ⇢ The new `*.buetow.cloud` way](#the-new-buetowcloud-way) +* [⇢ ⇢ The container apps](#the-container-apps) +* [⇢ ⇢ ⇢ `flux.buetow.cloud`](#fluxbuetowcloud) +* [⇢ ⇢ ⇢ `audiobookshelf.buetow.cloud`](#audiobookshelfbuetowcloud) +* [⇢ ⇢ ⇢ `syncthing.buetow.cloud`](#syncthingbuetowcloud) +* [⇢ ⇢ ⇢ `radicale.buetow.cloud`](#radicalebuetowcloud) +* [⇢ ⇢ ⇢ `bag.buetow.cloud`](#bagbuetowcloud) +* [⇢ ⇢ ⇢ `anki.buetow.cloud`](#ankibuetowcloud) +* [⇢ ⇢ ⇢ `vault.buetow.cloud`](#vaultbuetowcloud) +* [⇢ ⇢ ⇢ `bastion.buetow.cloud`](#bastionbuetowcloud) +* [⇢ ⇢ Conclusion](#conclusion) + ## The old `*.buetow.org` way Before the migration, all those services were reachable through `buetow.org`-subdomains (Buetow is my last name) and ran on Docker containers on a single Rocky Linux 9 VM at Hetzner. And there was a Nginx reverse proxy with TLS offloading (with Let's Encrypt certificates). The Rocky Linux 9's hostname was `babylon5.buetow.org` (based on the Science Fiction series). diff --git a/gemfeed/2024-03-03-a-fine-fyne-android-app-for-quickly-logging-ideas-programmed-in-golang.md b/gemfeed/2024-03-03-a-fine-fyne-android-app-for-quickly-logging-ideas-programmed-in-golang.md index 6c0421df..2d7a0873 100644 --- a/gemfeed/2024-03-03-a-fine-fyne-android-app-for-quickly-logging-ideas-programmed-in-golang.md +++ b/gemfeed/2024-03-03-a-fine-fyne-android-app-for-quickly-logging-ideas-programmed-in-golang.md @@ -2,20 +2,20 @@ > Published at 2024-03-03T00:07:21+02:00 -## Table of Contents - -* [⇢ A fine Fyne Android app for quickly logging ideas programmed in Go](#a-fine-fyne-android-app-for-quickly-logging-ideas-programmed-in-go) -* [⇢ ⇢ Introduction](#introduction) -* [⇢ ⇢ All easy-peasy?](#all-easy-peasy) - -## Introduction - I am an ideas person. I find myself frequently somewhere on the streets with an idea in my head but no paper journal noting it down. I have tried many note apps for my Android (I use GrapheneOS) phone. Most of them either don't do what I want, are proprietary software, require Google Play services (I have the main profile on my phone de-googled) or are too bloated. I was never into mobile app development, as I'm not too fond of the complexity of the developer toolchains. I don't want to use Android Studio (as a NeoVim user), and I don't want to use Java or Kotlin. I want to use a language I know (and like) for mobile app development. Go would be one of those languages. [![Quick logger Logo](a-fine-fyne-android-app-for-quickly-logging-ideas-programmed-in-golang/logo-small.png "Quick logger Logo")](a-fine-fyne-android-app-for-quickly-logging-ideas-programmed-in-golang/logo-small.png) +## Table of Contents + +* [⇢ A fine Fyne Android app for quickly logging ideas programmed in Go](#a-fine-fyne-android-app-for-quickly-logging-ideas-programmed-in-go) +* [⇢ ⇢ Enter Quick logger](#enter-quick-logger) +* [⇢ ⇢ All easy-peasy?](#all-easy-peasy) + +## Enter Quick logger + Enter Quick logger – a compact GUI Android (well, cross-platform due to Fyne) app I've crafted using Go and the nifty Fyne framework. With Fyne, the app can be compiled easily into an Android APK. As of this writing, this app's whole Go source code is only 75 lines short!! This little tool is designed for spontaneous moments, allowing me to quickly log my thoughts as plain text files on my Android phone. There are no fancy file formats. Just plain text! [https://codeberg.org/snonux/quicklogger](https://codeberg.org/snonux/quicklogger) diff --git a/gemfeed/2024-04-01-KISS-high-availability-with-OpenBSD.md b/gemfeed/2024-04-01-KISS-high-availability-with-OpenBSD.md index f45b5c14..84875f62 100644 --- a/gemfeed/2024-04-01-KISS-high-availability-with-OpenBSD.md +++ b/gemfeed/2024-04-01-KISS-high-availability-with-OpenBSD.md @@ -2,6 +2,14 @@ > Published at 2024-03-30T22:12:56+02:00 +I have always wanted a highly available setup for my personal websites. I could have used off-the-shelf hosting solutions or hosted my sites in an AWS S3 bucket. I have used technologies like (in unsorted and slightly unrelated order) BGP, LVS/IPVS, ldirectord, Pacemaker, STONITH, scripted VIP failover via ARP, heartbeat, heartbeat2, Corosync, keepalived, DRBD, and commercial F5 Load Balancers for high availability at work. + +But still, my personal sites were never highly available. All those technologies are great for professional use, but I was looking for something much more straightforward for my personal space - something as KISS (keep it simple and stupid) as possible. + +It would be fine if my personal website wasn't highly available, but the geek in me wants it anyway. + +> PS: ASCII-art below reflects an OpenBSD under-water world with all the tools available in the base system. + ``` Art by Michael J. Penick (mod. by Paul B.) ACME-sky @@ -30,7 +38,6 @@ _____|_:_:_| (o)-(o) |_:_:_|--'`-. ,--. ksh under-water (((\'/ ## Table of Contents * [⇢ KISS high-availability with OpenBSD](#kiss-high-availability-with-openbsd) -* [⇢ ⇢ Introduction](#introduction) * [⇢ ⇢ My auto-failover requirements](#my-auto-failover-requirements) * [⇢ ⇢ My HA solution](#my-ha-solution) * [⇢ ⇢ ⇢ Only OpenBSD base installation required](#only-openbsd-base-installation-required) @@ -42,16 +49,6 @@ _____|_:_:_| (o)-(o) |_:_:_|--'`-. ,--. ksh under-water (((\'/ * [⇢ ⇢ ⇢ Rex automation](#rex-automation) * [⇢ ⇢ More HA](#more-ha) -## Introduction - -I have always wanted a highly available setup for my personal websites. I could have used off-the-shelf hosting solutions or hosted my sites in an AWS S3 bucket. I have used technologies like (in unsorted and slightly unrelated order) BGP, LVS/IPVS, ldirectord, Pacemaker, STONITH, scripted VIP failover via ARP, heartbeat, heartbeat2, Corosync, keepalived, DRBD, and commercial F5 Load Balancers for high availability at work. - -But still, my personal sites were never highly available. All those technologies are great for professional use, but I was looking for something much more straightforward for my personal space - something as KISS (keep it simple and stupid) as possible. - -It would be fine if my personal website wasn't highly available, but the geek in me wants it anyway. - -> PS: ASCII-art reflects an OpenBSD under-water world with all the tools available in the base system. - ## My auto-failover requirements * Be OpenBSD-based (I prefer OpenBSD because of the cleanliness and good documentation) and rely on as few external packages as possible. diff --git a/gemfeed/2024-05-01-slow-productivity-book-notes.md b/gemfeed/2024-05-01-slow-productivity-book-notes.md index 138cec50..b53ac2ee 100644 --- a/gemfeed/2024-05-01-slow-productivity-book-notes.md +++ b/gemfeed/2024-05-01-slow-productivity-book-notes.md @@ -2,18 +2,6 @@ > Published at 2024-04-27T14:18:51+03:00 -## Table of Contents - -* [⇢ "Slow Productivity" book notes](#slow-productivity-book-notes) -* [⇢ ⇢ Introduction](#introduction) -* [⇢ ⇢ Pseudo-productivity and Shallow work](#pseudo-productivity-and-shallow-work) -* [⇢ ⇢ Accomplishments without burnout](#accomplishments-without-burnout) -* [⇢ ⇢ Do fewer things](#do-fewer-things) -* [⇢ ⇢ Work at a natural pace](#work-at-a-natural-pace) -* [⇢ ⇢ Obsess over quality ](#obsess-over-quality-) - -## Introduction - These are my personal takeaways after reading "Slow Productivity - The lost Art of Accomplishment Without Burnout" by Cal Newport. The case studies in this book were a bit long, but they appeared to be well-researched. I will only highlight the interesting, actionable items in the book notes. @@ -32,6 +20,18 @@ These notes are mainly for my own use, but you may find them helpful. ''' ``` +## Table of Contents + +* [⇢ "Slow Productivity" book notes](#slow-productivity-book-notes) +* [⇢ ⇢ It's not "slow productivity"](#it-s-not-slow-productivity) +* [⇢ ⇢ Pseudo-productivity and Shallow work](#pseudo-productivity-and-shallow-work) +* [⇢ ⇢ Accomplishments without burnout](#accomplishments-without-burnout) +* [⇢ ⇢ Do fewer things](#do-fewer-things) +* [⇢ ⇢ Work at a natural pace](#work-at-a-natural-pace) +* [⇢ ⇢ Obsess over quality ](#obsess-over-quality-) + +## It's not "slow productivity" + "Slow productivity" does not mean being less productive. Cal Newport wants to point out that you can be much more productive with "slow productivity" than you would be without it. It is a different way of working than most of us are used to in the modern workplace, which is hyper-connected and always online. ## Pseudo-productivity and Shallow work diff --git a/gemfeed/2024-05-03-projects-i-currently-dont-have-time-for.md b/gemfeed/2024-05-03-projects-i-currently-dont-have-time-for.md index 8230e707..8badb762 100644 --- a/gemfeed/2024-05-03-projects-i-currently-dont-have-time-for.md +++ b/gemfeed/2024-05-03-projects-i-currently-dont-have-time-for.md @@ -2,6 +2,8 @@ > Published at 2024-05-03T16:23:03+03:00 +Over the years, I have collected many ideas for my personal projects and noted them down. I am currently in the process of cleaning up all my notes and reviewing those ideas. I don’t have time for the ones listed here and won’t have any soon due to other commitments and personal projects. So, in order to "get rid of them" from my notes folder, I decided to simply put them in this blog post so that those ideas don't get lost. Maybe I will pick up one or another idea someday in the future, but for now, they are all put on ice in favor of other personal projects or family time. + ``` Art by Laura Brown @@ -18,7 +20,6 @@ Art by Laura Brown ## Table of Contents * [⇢ Projects I currently don't have time for](#projects-i-currently-don-t-have-time-for) -* [⇢ ⇢ Introduction](#introduction) * [⇢ ⇢ Hardware projects I don't have time for](#hardware-projects-i-don-t-have-time-for) * [⇢ ⇢ ⇢ I use Arch, btw!](#i-use-arch-btw) * [⇢ ⇢ ⇢ OpenBSD home router](#openbsd-home-router) @@ -53,10 +54,6 @@ Art by Laura Brown * [⇢ ⇢ ⇢ Project secure](#project-secure) * [⇢ ⇢ ⇢ CPU utilisation is all wrong](#cpu-utilisation-is-all-wrong) -## Introduction - -Over the years, I have collected many ideas for my personal projects and noted them down. I am currently in the process of cleaning up all my notes and reviewing those ideas. I don’t have time for the ones listed here and won’t have any soon due to other commitments and personal projects. So, in order to "get rid of them" from my notes folder, I decided to simply put them in this blog post so that those ideas don't get lost. Maybe I will pick up one or another idea someday in the future, but for now, they are all put on ice in favor of other personal projects or family time. - ## Hardware projects I don't have time for ### I use Arch, btw! diff --git a/gemfeed/2024-06-23-terminal-multiplexing-with-tmux.md b/gemfeed/2024-06-23-terminal-multiplexing-with-tmux.md index 142d059a..c20d523a 100644 --- a/gemfeed/2024-06-23-terminal-multiplexing-with-tmux.md +++ b/gemfeed/2024-06-23-terminal-multiplexing-with-tmux.md @@ -2,6 +2,15 @@ > Published at 2024-06-23T22:41:59+03:00 +Tmux (Terminal Multiplexer) is a powerful, terminal-based tool that manages multiple terminal sessions within a single window. Here are some of its primary features and functionalities: + +* Session management +* Window and Pane management +* Persistent Workspace +* Customization + +[https://github.com/tmux/tmux/wiki](https://github.com/tmux/tmux/wiki) + ``` _______ |.-----.| @@ -17,7 +26,7 @@ jgs `-=========-`() ## Table of Contents * [⇢ Terminal multiplexing with `tmux`](#terminal-multiplexing-with-tmux) -* [⇢ ⇢ Introduction](#introduction) +* [⇢ ⇢ Before continuing...](#before-continuing) * [⇢ ⇢ Shell aliases](#shell-aliases) * [⇢ ⇢ The `tn` alias - Creating a new session](#the-tn-alias---creating-a-new-session) * [⇢ ⇢ ⇢ Cleaning up default sessions automatically](#cleaning-up-default-sessions-automatically) @@ -34,16 +43,7 @@ jgs `-=========-`() * [⇢ ⇢ Copy and paste workflow](#copy-and-paste-workflow) * [⇢ ⇢ Tmux configurations](#tmux-configurations) -## Introduction - -Tmux (Terminal Multiplexer) is a powerful, terminal-based tool that manages multiple terminal sessions within a single window. Here are some of its primary features and functionalities: - -* Session management -* Window and Pane management -* Persistent Workspace -* Customization - -[https://github.com/tmux/tmux/wiki](https://github.com/tmux/tmux/wiki) +## Before continuing... Before continuing to read this post, I encourage you to get familiar with Tmux first (unless you already know the basics). You can go through the official getting started guide: diff --git a/gemfeed/2024-07-05-random-weird-things.md b/gemfeed/2024-07-05-random-weird-things.md index cbe595ae..f8866ba7 100644 --- a/gemfeed/2024-07-05-random-weird-things.md +++ b/gemfeed/2024-07-05-random-weird-things.md @@ -2,10 +2,20 @@ > Published at 2024-07-05T10:59:59+03:00 +Every so often, I come across random, weird, and unexpected things on the internet. I thought it would be neat to share them here from time to time. As a start, here are ten of them. + +``` + /\_/\ +WHOA!! ( o.o ) + > ^ < + / - \ + / \ + /______\ \ +``` + ## Table of Contents * [⇢ Random Weird Things](#random-weird-things) -* [⇢ ⇢ Introduction](#introduction) * [⇢ ⇢ 1. `bad.horse` traceroute](#1-badhorse-traceroute) * [⇢ ⇢ 2. ASCII cinema](#2-ascii-cinema) * [⇢ ⇢ 3. Netflix's Hello World application](#3-netflix-s-hello-world-application) @@ -18,19 +28,6 @@ * [⇢ ⇢ 9. `jq` is a functional programming language](#9-jq-is-a-functional-programming-language) * [⇢ ⇢ 10. Regular expression to verify email addresses](#10-regular-expression-to-verify-email-addresses) -## Introduction - -Every so often, I come across random, weird, and unexpected things on the internet. I thought it would be neat to share them here from time to time. As a start, here are ten of them. - -``` - /\_/\ -WHOA!! ( o.o ) - > ^ < - / - \ - / \ - /______\ \ -``` - ## 1. `bad.horse` traceroute Run traceroute to get the poem (or song). diff --git a/gemfeed/2024-07-07-the-stoic-challenge-book-notes.md b/gemfeed/2024-07-07-the-stoic-challenge-book-notes.md index ba326c66..55edb442 100644 --- a/gemfeed/2024-07-07-the-stoic-challenge-book-notes.md +++ b/gemfeed/2024-07-07-the-stoic-challenge-book-notes.md @@ -2,15 +2,6 @@ > Published at 2024-07-07T12:46:55+03:00 -## Table of Contents - -* [⇢ "The Stoic Challenge" book notes](#the-stoic-challenge-book-notes) -* [⇢ ⇢ Introduction](#introduction) -* [⇢ ⇢ Negative visualization](#negative-visualization) -* [⇢ ⇢ Oh, nice trick, you stoic "god"! ;-)](#oh-nice-trick-you-stoic-god--) - -## Introduction - These are my personal takeaways after reading "The Stoic Challenge: A Philosopher's Guide to Becoming Tougher, Calmer, and More Resilient" by William B. Irvine. ``` @@ -25,6 +16,15 @@ These are my personal takeaways after reading "The Stoic Challenge: A Philosoph ''' ``` +## Table of Contents + +* [⇢ "The Stoic Challenge" book notes](#the-stoic-challenge-book-notes) +* [⇢ ⇢ Got sets you up for a challenge](#got-sets-you-up-for-a-challenge) +* [⇢ ⇢ Negative visualization](#negative-visualization) +* [⇢ ⇢ Oh, nice trick, you stoic "god"! ;-)](#oh-nice-trick-you-stoic-god--) + +## Got sets you up for a challenge + Gods set you up for a challenge to see how resilient you are. Is getting angry worth the price? If you stay calm then you can find the optimal workaround for the obstacle. Stay calm even with big setbacks. Practice minimalism of negative emotions. Put a positive spin on everything. What should you do if someone wrong you? Don't get angry, there is no point in that, it just makes you suffer. Do the best what you got now and keep calm and carry on. A resilient person will refuse to play the role of a victim. You can develop the setback response skills. Turn a setback. e.g. a handycap, into a personal triumph. diff --git a/gemfeed/2024-08-05-typing-127.1-words-per-minute.md b/gemfeed/2024-08-05-typing-127.1-words-per-minute.md index 94900c69..25a484c4 100644 --- a/gemfeed/2024-08-05-typing-127.1-words-per-minute.md +++ b/gemfeed/2024-08-05-typing-127.1-words-per-minute.md @@ -2,6 +2,14 @@ > Published at 2024-08-05T17:39:30+03:00 +After work one day, I noticed some discomfort in my right wrist. Upon research, it appeared to be a mild case of Repetitive Strain Injury (RSI). Initially, I thought that this would go away after a while, but after a week it became even worse. This led me to consider potential causes such as poor posture or keyboard use habits. As an enthusiast of keyboards, I experimented with ergonomic concave ortholinear split keyboards. Wait, what?... + +* Concave: Some fingers are longer than others. A concave keyboard makes it so that the keycaps meant to be pressed by the longer fingers are further down (e.g., left middle finger for `e` on a Qwerty layout), and keycaps meant to be pressed by shorter fingers are further up (e.g., right pinky finger for the letter `p`). +* Ortholinear: The keys are arranged in a straight vertical line, unlike most conventional keyboards. The conventional keyboards still resemble the old typewriters, where the placement of the keys was optimized so that the typewriter would not jam. There is no such requirement anymore. +* Split: The keyboard is split into two halves (left and right), allowing one to place either hand where it is most ergonomic. + +After discovering ThePrimagen (I found him long ago, but I never bothered buying the same keyboard he is on) on YouTube and reading/watching a couple of reviews, I thought that as a computer professional, the equipment could be expensive anyway (laptop, adjustable desk, comfortable chair), so why not invest a bit more into the keyboard? I purchased myself the Kinesis Advantage360 Professional keyboard. + ``` ,---,---,---,---,---,---,---,---,---,---,---,---,---,-------, |1/2| 1 | 2 | 3 | 4 | 5 | 6 | 7 | 8 | 9 | 0 | + | ' | <- | @@ -20,7 +28,6 @@ ## Table of Contents * [⇢ Typing `127.1` words per minute (`>100wpm average`)](#typing-1271-words-per-minute-100wpm-average) -* [⇢ ⇢ Introduction](#introduction) * [⇢ ⇢ Kinesis review](#kinesis-review) * [⇢ ⇢ ⇢ Top build quality](#top-build-quality) * [⇢ ⇢ ⇢ Bluetooth connectivity](#bluetooth-connectivity) @@ -46,16 +53,6 @@ * [⇢ ⇢ Upcoming custom Kinesis build](#upcoming-custom-kinesis-build) * [⇢ ⇢ Conclusion](#conclusion) -## Introduction - -After work one day, I noticed some discomfort in my right wrist. Upon research, it appeared to be a mild case of Repetitive Strain Injury (RSI). Initially, I thought that this would go away after a while, but after a week it became even worse. This led me to consider potential causes such as poor posture or keyboard use habits. As an enthusiast of keyboards, I experimented with ergonomic concave ortholinear split keyboards. Wait, what?... - -* Concave: Some fingers are longer than others. A concave keyboard makes it so that the keycaps meant to be pressed by the longer fingers are further down (e.g., left middle finger for `e` on a Qwerty layout), and keycaps meant to be pressed by shorter fingers are further up (e.g., right pinky finger for the letter `p`). -* Ortholinear: The keys are arranged in a straight vertical line, unlike most conventional keyboards. The conventional keyboards still resemble the old typewriters, where the placement of the keys was optimized so that the typewriter would not jam. There is no such requirement anymore. -* Split: The keyboard is split into two halves (left and right), allowing one to place either hand where it is most ergonomic. - -After discovering ThePrimagen (I found him long ago, but I never bothered buying the same keyboard he is on) on YouTube and reading/watching a couple of reviews, I thought that as a computer professional, the equipment could be expensive anyway (laptop, adjustable desk, comfortable chair), so why not invest a bit more into the keyboard? I purchased myself the Kinesis Advantage360 Professional keyboard. - ## Kinesis review For an in-depth review, have a look at this great article: -- cgit v1.2.3 From 1ee12764606136aa9ee3234fc78e5f1d192cce3a Mon Sep 17 00:00:00 2001 From: Paul Buetow Date: Sat, 7 Sep 2024 16:05:13 +0300 Subject: Update content for md --- gemfeed/2024-09-07-projects-i-support.md | 90 ++++++++++++++++++++++++++++++++ gemfeed/index.md | 1 + 2 files changed, 91 insertions(+) create mode 100644 gemfeed/2024-09-07-projects-i-support.md (limited to 'gemfeed') diff --git a/gemfeed/2024-09-07-projects-i-support.md b/gemfeed/2024-09-07-projects-i-support.md new file mode 100644 index 00000000..d8b1eeef --- /dev/null +++ b/gemfeed/2024-09-07-projects-i-support.md @@ -0,0 +1,90 @@ +# Projects I support + +> Published at 2024-09-07T16:04:19+03:00 + +This is the list of projects and initiatives I support/sponsor. + +``` +||====================================================================|| +||//$\\/\/\/\/\/\/\/\/\/\/\/\/\/\/\/\/\/\/\/\/\/\/\/\/\/\/\/\/\/\//$\\|| +||(100)==================| FEDERAL SPONSOR NOTE |================(100)|| +||\\$// ~ '------========--------' \\$//|| +||<< / /$\ // ____ \\ \ >>|| +||>>| 12 //L\\ // ///..) \\ L38036133B 12 |<<|| +||<<| \\ // || <|| >\ || |>>|| +||>>| \$/ || $$ --/ || One Hundred |<<|| +||<<| L38036133B *\\ |\_/ //* series |>>|| +||>>| 12 *\\/___\_//* 1989 |<<|| +||<<\ Open Soure ______/Franklin\________ Supporting />>|| +||//$\ ~| SPONSORING AND FUNDING |~ /$\\|| +||(100)=================== AWESOME OPEN SOURCE =================(100)|| +||\\$//\/\/\/\/\/\/\/\/\/\/\/\/\/\/\/\/\/\/\/\/\/\/\/\/\/\/\/\/\/\\$//|| +||====================================================================|| + +``` + +## Table of Contents + +* [⇢ Projects I support](#projects-i-support) +* [⇢ ⇢ Motivation](#motivation) +* [⇢ ⇢ Cup o' Go Podcast](#cup-o--go-podcast) +* [⇢ ⇢ Codeberg](#codeberg) +* [⇢ ⇢ GrapheneOS](#grapheneos) +* [⇢ ⇢ AnkiDroid](#ankidroid) +* [⇢ ⇢ OpenBSD through OpenBSD.Amsterdam](#openbsd-through-openbsdamsterdam) +* [⇢ ⇢ ProtonMail](#protonmail) + +## Motivation + +Sponsoring free and open-source projects, even for personal use, is important to ensure the sustainability, security, and continuous improvement of the software. It supports developers who often maintain these projects without compensation, helping them provide updates, new features, and security patches. By contributing, you recognize their efforts, foster a culture of innovation, and benefit from perks like early access or support, all while ensuring the long-term viability of the tools you rely on. + +Albeit I am not putting a lot of money into my sponsoring efforts, it still helps the open-source maintainers because the more little sponsors there are, the higher the total sum. + +## Cup o' Go Podcast + +I am a Patreon of the Cup o' Go Podcast. The podcast helps me stay updated with the Go community for around 15 minutes per week. I am not a full-time software developer, but my long-term ambition is to become better in Go every week by working on personal projects and tools for work. + +[https://cupogo.dev](https://cupogo.dev) + +## Codeberg + +Codeberg e.V. is a nonprofit organization that provides online resources for software development and collaboration. I am a user and a supporting member, paying an annual membership of €24. I didn't have to pay that membership fee, as Codeberg offers all the services I use for free. + +[https://codeberg.org](https://codeberg.org) +[https://codeberg.org/snonux - My Codeberg page](https://codeberg.org/snonux) + +## GrapheneOS + +GrapheneOS is an open-source project that improves Android's privacy and security with sandboxing, exploit mitigations, and a permission model. It does not include Google apps or services but offers a sandboxed Google Play compatibility layer and its own apps and services. + +I've made a one-off €100 donation because I really like this, and I run GrapheneOS on my personal Phone as my main daily driver. + +[https://grapheneos.org/](https://grapheneos.org/) +[Why GrapheneOS Rox](https://foo.zone/gemfeed/2023-01-23-why-grapheneos-rox.html) + +## AnkiDroid + +AnkiDroid is an app that lets you learn flashcards efficiently with spaced repetition. It is compatible with Anki software and supports various flashcard content, syncing, statistics, and more. + +I've been learning vocabulary with this free app, and it is, in my opinion, the best flashcard app I know. I've made a 20$ one-off donation to this project. + +[https://opencollective.com/ankidroid](https://opencollective.com/ankidroid) + +## OpenBSD through OpenBSD.Amsterdam + + The OpenBSD project produces a FREE, multi-platform 4.4BSD-based UNIX-like operating system. Our efforts emphasize portability, standardization, correctness, proactive security and integrated cryptography. As an example of the effect OpenBSD has, the popular OpenSSH software comes from OpenBSD. OpenBSD is freely available from their download sites. + +I implicitly support the OpenBSD project through a VM I have rented at OpenBSD Amsterdam. They donate €10 per VM and €15 per VM for every renewal to the OpenBSD Foundation, with dedicated servers running vmm(4)/vmd(8) to host opinionated VMs. + +[https://www.OpenBSD.org](https://www.OpenBSD.org) +[https://OpenBSD.Amsterdam](https://OpenBSD.Amsterdam) + +## ProtonMail + +I am not directly funding this project, but I am a very happy paying customer, and I am listing it here as an alternative to big tech if you don't want to run your own mail infrastructure. I am listing ProtonMail here as it is a non-profit organization, and I want to emphasize the importance of considering alternatives to big tech. + +[https://proton.me/](https://proton.me/) + +E-mail your comments to `paul@nospam.buetow.org` :-) + +[Back to the main site](../) diff --git a/gemfeed/index.md b/gemfeed/index.md index 58464a0a..0b888b34 100644 --- a/gemfeed/index.md +++ b/gemfeed/index.md @@ -2,6 +2,7 @@ ## To be in the .zone! +[2024-09-07 - Projects I support](./2024-09-07-projects-i-support.md) [2024-08-05 - Typing `127.1` words per minute (`>100wpm average`)](./2024-08-05-typing-127.1-words-per-minute.md) [2024-07-07 - 'The Stoic Challenge' book notes](./2024-07-07-the-stoic-challenge-book-notes.md) [2024-07-05 - Random Weird Things](./2024-07-05-random-weird-things.md) -- cgit v1.2.3 From bbf4aa0ed380f1b7892bd9ec6eb38ad2a236c5a5 Mon Sep 17 00:00:00 2001 From: Paul Buetow Date: Sat, 7 Sep 2024 16:11:53 +0300 Subject: Update content for md --- gemfeed/2024-09-07-projects-i-support.md | 9 +++++++++ 1 file changed, 9 insertions(+) (limited to 'gemfeed') diff --git a/gemfeed/2024-09-07-projects-i-support.md b/gemfeed/2024-09-07-projects-i-support.md index d8b1eeef..bb4e5c05 100644 --- a/gemfeed/2024-09-07-projects-i-support.md +++ b/gemfeed/2024-09-07-projects-i-support.md @@ -33,6 +33,7 @@ This is the list of projects and initiatives I support/sponsor. * [⇢ ⇢ AnkiDroid](#ankidroid) * [⇢ ⇢ OpenBSD through OpenBSD.Amsterdam](#openbsd-through-openbsdamsterdam) * [⇢ ⇢ ProtonMail](#protonmail) +* [⇢ ⇢ `Libro.fm`](#librofm) ## Motivation @@ -85,6 +86,14 @@ I am not directly funding this project, but I am a very happy paying customer, a [https://proton.me/](https://proton.me/) +## `Libro.fm` + +This is the alternative to Audible if you are into audiobooks (like I am). For every book or every month of membership, I am also supporting a local bookstore I selected. Their catalog is not as large as Audible's, but it's still pretty decent. + +Libro.fm began as a conversation among friends at Third Place Books, a local bookstore in Seattle, Washington, about the growing popularity of audiobooks and the lack of a way for readers to purchase them from independent bookstores. Flash forward, and Libro.fm was founded in 2014. + +[https://libfo.fm](https://libfo.fm) + E-mail your comments to `paul@nospam.buetow.org` :-) [Back to the main site](../) -- cgit v1.2.3 From ae825dce02aea0bfbe7aeeceba470e5b16d4eafb Mon Sep 17 00:00:00 2001 From: Paul Buetow Date: Sat, 7 Sep 2024 16:33:42 +0300 Subject: Update content for md --- ...23-08-18-site-reliability-engineering-part-1.md | 7 ++- ...23-11-19-site-reliability-engineering-part-2.md | 11 ++-- ...24-01-09-site-reliability-engineering-part-3.md | 9 +-- ...24-09-07-site-reliability-engineering-part-4.md | 69 ++++++++++++++++++++++ gemfeed/index.md | 5 +- 5 files changed, 87 insertions(+), 14 deletions(-) create mode 100644 gemfeed/2024-09-07-site-reliability-engineering-part-4.md (limited to 'gemfeed') diff --git a/gemfeed/2023-08-18-site-reliability-engineering-part-1.md b/gemfeed/2023-08-18-site-reliability-engineering-part-1.md index 37976a18..5c61f9ac 100644 --- a/gemfeed/2023-08-18-site-reliability-engineering-part-1.md +++ b/gemfeed/2023-08-18-site-reliability-engineering-part-1.md @@ -5,8 +5,9 @@ Being a Site Reliability Engineer (SRE) is like stepping into a lively, ever-evolving universe. The world of SRE mixes together different tech, a unique culture, and a whole lot of determination. It’s one of the toughest but most exciting jobs out there. There's zero chance of getting bored because there's always a fresh challenge to tackle and new technology to play around with. It's not just about the tech side of things either; it's heavily rooted in communication, collaboration, and teamwork. As someone currently working as an SRE, I’m here to break it all down for you in this blog series. Let's dive into what SRE is really all about! [2023-08-18 Site Reliability Engineering - Part 1: SRE and Organizational Culture (You are currently reading this)](./2023-08-18-site-reliability-engineering-part-1.md) -[2023-11-19 Site Reliability Engineering - Part 2: Operational Balance in SRE](./2023-11-19-site-reliability-engineering-part-2.md) -[2024-01-09 Site Reliability Engineering - Part 3: On-Call Culture and the Human Side](./2024-01-09-site-reliability-engineering-part-3.md) +[2023-11-19 Site Reliability Engineering - Part 2: Operational Balance](./2023-11-19-site-reliability-engineering-part-2.md) +[2024-01-09 Site Reliability Engineering - Part 3: On-Call Culture](./2024-01-09-site-reliability-engineering-part-3.md) +[2024-09-07 Site Reliability Engineering - Part 4: Onboarding for On-Call Engineers](./2024-09-07-site-reliability-engineering-part-4.md) ``` ▓▓▓▓░░ @@ -52,7 +53,7 @@ Organizations that have SLIs, SLOs, and error budgets in place are already prett Continue with the second part of this series: -[2023-11-19 Site Reliability Engineering - Part 2: Operational Balance in SRE](./2023-11-19-site-reliability-engineering-part-2.md) +[2023-11-19 Site Reliability Engineering - Part 2: Operational Balance](./2023-11-19-site-reliability-engineering-part-2.md) E-Mail your comments to `paul@nospam.buetow.org` :-) diff --git a/gemfeed/2023-11-19-site-reliability-engineering-part-2.md b/gemfeed/2023-11-19-site-reliability-engineering-part-2.md index 9bddfbcc..29749257 100644 --- a/gemfeed/2023-11-19-site-reliability-engineering-part-2.md +++ b/gemfeed/2023-11-19-site-reliability-engineering-part-2.md @@ -1,12 +1,13 @@ -# Site Reliability Engineering - Part 2: Operational Balance in SRE +# Site Reliability Engineering - Part 2: Operational Balance > Published at 2023-11-19T00:18:18+03:00 This is the second part of my Site Reliability Engineering (SRE) series. I am currently employed as a Site Reliability Engineer and will try to share what SRE is about in this blog series. [2023-08-18 Site Reliability Engineering - Part 1: SRE and Organizational Culture](./2023-08-18-site-reliability-engineering-part-1.md) -[2023-11-19 Site Reliability Engineering - Part 2: Operational Balance in SRE (You are currently reading this)](./2023-11-19-site-reliability-engineering-part-2.md) -[2024-01-09 Site Reliability Engineering - Part 3: On-Call Culture and the Human Side](./2024-01-09-site-reliability-engineering-part-3.md) +[2023-11-19 Site Reliability Engineering - Part 2: Operational Balance (You are currently reading this)](./2023-11-19-site-reliability-engineering-part-2.md) +[2024-01-09 Site Reliability Engineering - Part 3: On-Call Culture](./2024-01-09-site-reliability-engineering-part-3.md) +[2024-09-07 Site Reliability Engineering - Part 4: Onboarding for On-Call Engineers](./2024-09-07-site-reliability-engineering-part-4.md) ``` ⠀⠀⠀⠀⠀⠀⠀⠀⠀⠀⠀⠀⢀⣠⣾⣷⣄⡀⠀⠀⠀⠀⠀⠀⠀⠀⠀⠀⠀⠀ @@ -23,7 +24,7 @@ This is the second part of my Site Reliability Engineering (SRE) series. I am cu ⠀⠀⠀⠀⠀⠀⠴⠶⠿⠿⠿⠿⠿⠿⠿⠿⠿⠿⠿⠿⠿⠿⠶⠦⠀⠀ ``` -## Operational Balance in SRE: Striking the Right Balance Between Reliability and Speed +## Striking the Right Balance Between Reliability and Speed Site Reliability Engineering is more than just a bunch of best practices or methods. It's a guiding light for engineering teams, helping them navigate the tricky waters of modern software development and system management. In the world of software production, there are two big forces that often clash: the push for fast feature releases (velocity) and the need for reliable systems. Traditionally, moving faster meant more risk. SRE helps balance these opposing goals with things like error budgets and SLIs/SLOs. These tools give teams a clear way to measure how much they can push changes without hurting system health. So, the error budget becomes a balancing act, helping teams trade off between innovation and reliability. @@ -42,7 +43,7 @@ That all sounds pretty idealistic. The reality is that getting the perfect balan Continue with the third part of this series: -[2024-01-09 Site Reliability Engineering - Part 3: On-Call Culture and the Human Side](./2024-01-09-site-reliability-engineering-part-3.md) +[2024-01-09 Site Reliability Engineering - Part 3: On-Call Culture](./2024-01-09-site-reliability-engineering-part-3.md) E-Mail your comments to `paul@nospam.buetow.org` :-) diff --git a/gemfeed/2024-01-09-site-reliability-engineering-part-3.md b/gemfeed/2024-01-09-site-reliability-engineering-part-3.md index 314f50e0..af82c899 100644 --- a/gemfeed/2024-01-09-site-reliability-engineering-part-3.md +++ b/gemfeed/2024-01-09-site-reliability-engineering-part-3.md @@ -1,12 +1,13 @@ -# Site Reliability Engineering - Part 3: On-Call Culture and the Human Side +# Site Reliability Engineering - Part 3: On-Call Culture > Published at 2024-01-09T18:35:48+02:00 Welcome to Part 3 of my Site Reliability Engineering (SRE) series. I'm currently working as a Site Reliability Engineer, and I’m here to share what SRE is all about in this blog series. [2023-08-18 Site Reliability Engineering - Part 1: SRE and Organizational Culture](./2023-08-18-site-reliability-engineering-part-1.md) -[2023-11-19 Site Reliability Engineering - Part 2: Operational Balance in SRE](./2023-11-19-site-reliability-engineering-part-2.md) -[2024-01-09 Site Reliability Engineering - Part 3: On-Call Culture and the Human Side (You are currently reading this)](./2024-01-09-site-reliability-engineering-part-3.md) +[2023-11-19 Site Reliability Engineering - Part 2: Operational Balance](./2023-11-19-site-reliability-engineering-part-2.md) +[2024-01-09 Site Reliability Engineering - Part 3: On-Call Culture (You are currently reading this)](./2024-01-09-site-reliability-engineering-part-3.md) +[2024-09-07 Site Reliability Engineering - Part 4: Onboarding for On-Call Engineers](./2024-09-07-site-reliability-engineering-part-4.md) ``` ..--""""----.. @@ -34,7 +35,7 @@ Welcome to Part 3 of my Site Reliability Engineering (SRE) series. I'm currently ``` -## On-Call Culture and the Human Side: Putting Well-being First in the World of Reliability +## Putting Well-being First Site Reliability Engineering is all about keeping systems reliable, but we often forget how important the human side is. A healthy on-call culture is just as crucial as any technical fix. The well-being of the engineers really matters. diff --git a/gemfeed/2024-09-07-site-reliability-engineering-part-4.md b/gemfeed/2024-09-07-site-reliability-engineering-part-4.md new file mode 100644 index 00000000..3425956a --- /dev/null +++ b/gemfeed/2024-09-07-site-reliability-engineering-part-4.md @@ -0,0 +1,69 @@ +# Site Reliability Engineering - Part 4: Onboarding for On-Call Engineers + +> Published at 2024-09-07T16:27:58+03:00 + +Welcome to Part 4 of my Site Reliability Engineering (SRE) series. I'm currently working as a Site Reliability Engineer, and I’m here to share what SRE is all about in this blog series. + +[2023-08-18 Site Reliability Engineering - Part 1: SRE and Organizational Culture](./2023-08-18-site-reliability-engineering-part-1.md) +[2023-11-19 Site Reliability Engineering - Part 2: Operational Balance](./2023-11-19-site-reliability-engineering-part-2.md) +[2024-01-09 Site Reliability Engineering - Part 3: On-Call Culture](./2024-01-09-site-reliability-engineering-part-3.md) +[2024-09-07 Site Reliability Engineering - Part 4: Onboarding for On-Call Engineers (You are currently reading this)](./2024-09-07-site-reliability-engineering-part-4.md) + +``` + __..._ _...__ + _..-" `Y` "-._ + \ Once upon | / + \\ a time..| // + \\\ | /// + \\\ _..---.|.---.._ /// +jgs \\`_..---.Y.---.._`// +``` + +This time, I want to share some tips on how to onboard software engineers, QA engineers, and Site Reliability Engineers (SREs) to the primary on-call rotation. Traditionally, onboarding might take half a year (depending on the complexity of the infrastructure), but with a bit of strategy and structured sessions, we've managed to reduce it to just six weeks per person. Let's dive in! + +## Setting the Scene: Tier-1 On-Call Rotation + +First things first, let's talk about Tier-1. This is where the magic begins. Tier-1 covers over 80% of the common on-call cases and is the perfect breeding ground for new on-call engineers to get their feet wet. It's designed to be manageable training ground. + +### Why Tier-1? + +* Easy to Understand: Every on-call engineer should be familiar with Tier-1 tasks. +* Training Ground: This is where engineers start their on-call career. It's purposefully kept simple so that it's not overwhelming right off the bat. +* Runbook/recipe driven: Every alert is attached to a comprehensive runbook, making it easy for every engineer to follow. + +## Onboarding Process: From 6 Months to 6 Weeks + +So how did we cut down the onboarding time so drastically? Here’s the breakdown of our process: + +Knowledge Transfer (KT) Sessions: We kicked things off with more than 10 KT sessions, complete with video recordings. These sessions are comprehensive and cover everything from the basics to some more advanced topics. The recorded sessions mean that new engineers can revisit them anytime they need a refresher. + +Shadowing Sessions: Each new engineer undergoes two on-call week shadowing sessions. This hands-on experience is invaluable. They get to see real-time incident handling and resolution, gaining practical knowledge that's hard to get from just reading docs. + +Comprehensive Runbooks: We created 64 runbooks (by the time writing this probably more than 100) that are composable like Lego bricks. Each runbook covers a specific scenario and guides the engineer step-by-step to resolution. Pairing these with monitoring alerts linked directly to Confluence docs, and from there to the respective runbooks, ensures every alert can be navigated with ease (well, there are always exceptions to the rule...). + +Self-Sufficiency & Confidence Building: With all these resources at their fingertips, our on-call engineers become self-sufficient for most of the common issues they'll face (new starters can now handle around 80% of the most common issue after 6 weeks they had joined the company). This boosts their confidence and ensures they can handle Tier-1 incidents independently. + +Documentation and Feedback Loop: Continuous improvement is key. We regularly update our documentation based on feedback from the engineers. This makes our process even more robust and user-friendly. + +## It's All About the Tiers + +Let’s briefly touch on the Tier levels: + +* Tier 1: Easy and foundational tasks. Perfect for getting new engineers started. This covers around 80% of all on-call cases we face. This is what we trained on. +* Tier 2: Slightly more complex, requiring more background knowledge. We trained on some of the topics but not all. +* Tier 3: Requires a good understanding of the platform/architecture. Likely needs KT sessions with domain experts. +* Tier DE (Domain Expert): The heavy hitters. Domain experts are required for these tasks. + +### Growing into Higher Tiers + +From Tier-1, engineers naturally grow into Tier-2 and beyond. The structured training and gradual increase in complexity help ensure a smooth transition as they gain experience and confidence. The key here is that engineers stay curous and engaged in the on-call, so that they always keep learning. + +## Keeping Runbooks Up to Date + +It is important that runbooks are not a "project to be finished"; runbooks have to be maintained and updated over time. Sections may change, new runbooks need to be added, and old ones can be deleted. So the acceptance criteria of an on-call shift would not just be reacting to alerts and incidents, but also reviewing and updating the current runbooks. + +## Conclusion + +By structuring the onboarding process with KT sessions, shadowing, comprehensive runbooks, and a feedback loop, we've been able to fast-track the process from six months to just six weeks. This not only prepares our engineers for the on-call rotation quicker but also ensures they're confident and capable when handling incidents. + +If you're looking to optimize your on-call onboarding process, these strategies could be your ticket to a more efficient and effective transition. Happy on-calling! diff --git a/gemfeed/index.md b/gemfeed/index.md index 0b888b34..1ec71ea7 100644 --- a/gemfeed/index.md +++ b/gemfeed/index.md @@ -2,6 +2,7 @@ ## To be in the .zone! +[2024-09-07 - Site Reliability Engineering - Part 4: Onboarding for On-Call Engineers](./2024-09-07-site-reliability-engineering-part-4.md) [2024-09-07 - Projects I support](./2024-09-07-projects-i-support.md) [2024-08-05 - Typing `127.1` words per minute (`>100wpm average`)](./2024-08-05-typing-127.1-words-per-minute.md) [2024-07-07 - 'The Stoic Challenge' book notes](./2024-07-07-the-stoic-challenge-book-notes.md) @@ -13,9 +14,9 @@ [2024-03-03 - A fine Fyne Android app for quickly logging ideas programmed in Go](./2024-03-03-a-fine-fyne-android-app-for-quickly-logging-ideas-programmed-in-golang.md) [2024-02-04 - From `babylon5.buetow.org` to `*.buetow.cloud`](./2024-02-04-from-babylon5.buetow.org-to-.cloud.md) [2024-01-13 - One reason why I love OpenBSD](./2024-01-13-one-reason-why-i-love-openbsd.md) -[2024-01-09 - Site Reliability Engineering - Part 3: On-Call Culture and the Human Side](./2024-01-09-site-reliability-engineering-part-3.md) +[2024-01-09 - Site Reliability Engineering - Part 3: On-Call Culture](./2024-01-09-site-reliability-engineering-part-3.md) [2023-12-10 - Bash Golf Part 3](./2023-12-10-bash-golf-part-3.md) -[2023-11-19 - Site Reliability Engineering - Part 2: Operational Balance in SRE](./2023-11-19-site-reliability-engineering-part-2.md) +[2023-11-19 - Site Reliability Engineering - Part 2: Operational Balance](./2023-11-19-site-reliability-engineering-part-2.md) [2023-11-11 - 'Mind Management' book notes](./2023-11-11-mind-management-book-notes.md) [2023-10-29 - KISS static web photo albums with `photoalbum.sh`](./2023-10-29-kiss-static-web-photo-albums-with-photoalbum.sh.md) [2023-09-25 - DTail usage examples](./2023-09-25-dtail-usage-examples.md) -- cgit v1.2.3 From 83c63d655720e9cd18bbf852d033cbebda90ddfc Mon Sep 17 00:00:00 2001 From: Paul Buetow Date: Sat, 7 Sep 2024 16:38:15 +0300 Subject: Update content for md --- gemfeed/2024-09-07-projects-i-support.md | 4 ++-- gemfeed/index.md | 2 +- 2 files changed, 3 insertions(+), 3 deletions(-) (limited to 'gemfeed') diff --git a/gemfeed/2024-09-07-projects-i-support.md b/gemfeed/2024-09-07-projects-i-support.md index bb4e5c05..6dee3c91 100644 --- a/gemfeed/2024-09-07-projects-i-support.md +++ b/gemfeed/2024-09-07-projects-i-support.md @@ -1,4 +1,4 @@ -# Projects I support +# Projects I financially support > Published at 2024-09-07T16:04:19+03:00 @@ -25,7 +25,7 @@ This is the list of projects and initiatives I support/sponsor. ## Table of Contents -* [⇢ Projects I support](#projects-i-support) +* [⇢ Projects I financially support](#projects-i-financially-support) * [⇢ ⇢ Motivation](#motivation) * [⇢ ⇢ Cup o' Go Podcast](#cup-o--go-podcast) * [⇢ ⇢ Codeberg](#codeberg) diff --git a/gemfeed/index.md b/gemfeed/index.md index 1ec71ea7..952eb8b0 100644 --- a/gemfeed/index.md +++ b/gemfeed/index.md @@ -3,7 +3,7 @@ ## To be in the .zone! [2024-09-07 - Site Reliability Engineering - Part 4: Onboarding for On-Call Engineers](./2024-09-07-site-reliability-engineering-part-4.md) -[2024-09-07 - Projects I support](./2024-09-07-projects-i-support.md) +[2024-09-07 - Projects I financially support](./2024-09-07-projects-i-support.md) [2024-08-05 - Typing `127.1` words per minute (`>100wpm average`)](./2024-08-05-typing-127.1-words-per-minute.md) [2024-07-07 - 'The Stoic Challenge' book notes](./2024-07-07-the-stoic-challenge-book-notes.md) [2024-07-05 - Random Weird Things](./2024-07-05-random-weird-things.md) -- cgit v1.2.3 From a2297d659620c860ca44eaa324a9a601f23977e6 Mon Sep 17 00:00:00 2001 From: Paul Buetow Date: Sat, 7 Sep 2024 16:41:30 +0300 Subject: Update content for md --- gemfeed/2024-01-09-site-reliability-engineering-part-3.md | 4 ++++ 1 file changed, 4 insertions(+) (limited to 'gemfeed') diff --git a/gemfeed/2024-01-09-site-reliability-engineering-part-3.md b/gemfeed/2024-01-09-site-reliability-engineering-part-3.md index af82c899..15b9a170 100644 --- a/gemfeed/2024-01-09-site-reliability-engineering-part-3.md +++ b/gemfeed/2024-01-09-site-reliability-engineering-part-3.md @@ -55,6 +55,10 @@ A blameless on-call culture is essential for creating a safe and collaborative e Mistakes are gonna happen, which is why having a blameless on-call culture is so important. +Continue with the fourth part of this series: + +[2024-09-07 Site Reliability Engineering - Part 4: Onboarding for On-Call Engineers](./2024-09-07-site-reliability-engineering-part-4.md) + E-Mail your comments to `paul@nospam.buetow.org` :-) [Back to the main site](../) -- cgit v1.2.3 From 46c8b42b07141d59994997e1370d90d4065769dd Mon Sep 17 00:00:00 2001 From: Paul Buetow Date: Sat, 7 Sep 2024 16:45:25 +0300 Subject: Update content for md --- gemfeed/2024-09-07-site-reliability-engineering-part-4.md | 2 ++ 1 file changed, 2 insertions(+) (limited to 'gemfeed') diff --git a/gemfeed/2024-09-07-site-reliability-engineering-part-4.md b/gemfeed/2024-09-07-site-reliability-engineering-part-4.md index 3425956a..4af52caf 100644 --- a/gemfeed/2024-09-07-site-reliability-engineering-part-4.md +++ b/gemfeed/2024-09-07-site-reliability-engineering-part-4.md @@ -67,3 +67,5 @@ It is important that runbooks are not a "project to be finished"; runbooks have By structuring the onboarding process with KT sessions, shadowing, comprehensive runbooks, and a feedback loop, we've been able to fast-track the process from six months to just six weeks. This not only prepares our engineers for the on-call rotation quicker but also ensures they're confident and capable when handling incidents. If you're looking to optimize your on-call onboarding process, these strategies could be your ticket to a more efficient and effective transition. Happy on-calling! + +[Back to the main site](../) -- cgit v1.2.3 From 8872da4fa0c3886bef6a08265999394976d4988c Mon Sep 17 00:00:00 2001 From: Paul Buetow Date: Sat, 7 Sep 2024 16:51:44 +0300 Subject: Update content for md --- gemfeed/2024-09-07-projects-i-support.md | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) (limited to 'gemfeed') diff --git a/gemfeed/2024-09-07-projects-i-support.md b/gemfeed/2024-09-07-projects-i-support.md index 6dee3c91..cd7b446a 100644 --- a/gemfeed/2024-09-07-projects-i-support.md +++ b/gemfeed/2024-09-07-projects-i-support.md @@ -92,7 +92,7 @@ This is the alternative to Audible if you are into audiobooks (like I am). For e Libro.fm began as a conversation among friends at Third Place Books, a local bookstore in Seattle, Washington, about the growing popularity of audiobooks and the lack of a way for readers to purchase them from independent bookstores. Flash forward, and Libro.fm was founded in 2014. -[https://libfo.fm](https://libfo.fm) +[https://libro.fm](https://libro.fm) E-mail your comments to `paul@nospam.buetow.org` :-) -- cgit v1.2.3 From 5387b4360c6bf0c64b3cb1568443e9348aed50f9 Mon Sep 17 00:00:00 2001 From: Paul Buetow Date: Mon, 9 Sep 2024 22:27:26 +0300 Subject: Update content for md --- gemfeed/2024-08-05-typing-127.1-words-per-minute.md | 18 ++++++++++-------- 1 file changed, 10 insertions(+), 8 deletions(-) (limited to 'gemfeed') diff --git a/gemfeed/2024-08-05-typing-127.1-words-per-minute.md b/gemfeed/2024-08-05-typing-127.1-words-per-minute.md index 25a484c4..e892aa08 100644 --- a/gemfeed/2024-08-05-typing-127.1-words-per-minute.md +++ b/gemfeed/2024-08-05-typing-127.1-words-per-minute.md @@ -2,14 +2,6 @@ > Published at 2024-08-05T17:39:30+03:00 -After work one day, I noticed some discomfort in my right wrist. Upon research, it appeared to be a mild case of Repetitive Strain Injury (RSI). Initially, I thought that this would go away after a while, but after a week it became even worse. This led me to consider potential causes such as poor posture or keyboard use habits. As an enthusiast of keyboards, I experimented with ergonomic concave ortholinear split keyboards. Wait, what?... - -* Concave: Some fingers are longer than others. A concave keyboard makes it so that the keycaps meant to be pressed by the longer fingers are further down (e.g., left middle finger for `e` on a Qwerty layout), and keycaps meant to be pressed by shorter fingers are further up (e.g., right pinky finger for the letter `p`). -* Ortholinear: The keys are arranged in a straight vertical line, unlike most conventional keyboards. The conventional keyboards still resemble the old typewriters, where the placement of the keys was optimized so that the typewriter would not jam. There is no such requirement anymore. -* Split: The keyboard is split into two halves (left and right), allowing one to place either hand where it is most ergonomic. - -After discovering ThePrimagen (I found him long ago, but I never bothered buying the same keyboard he is on) on YouTube and reading/watching a couple of reviews, I thought that as a computer professional, the equipment could be expensive anyway (laptop, adjustable desk, comfortable chair), so why not invest a bit more into the keyboard? I purchased myself the Kinesis Advantage360 Professional keyboard. - ``` ,---,---,---,---,---,---,---,---,---,---,---,---,---,-------, |1/2| 1 | 2 | 3 | 4 | 5 | 6 | 7 | 8 | 9 | 0 | + | ' | <- | @@ -28,6 +20,7 @@ After discovering ThePrimagen (I found him long ago, but I never bothered buying ## Table of Contents * [⇢ Typing `127.1` words per minute (`>100wpm average`)](#typing-1271-words-per-minute-100wpm-average) +* [⇢ ⇢ Introduction](#introduction) * [⇢ ⇢ Kinesis review](#kinesis-review) * [⇢ ⇢ ⇢ Top build quality](#top-build-quality) * [⇢ ⇢ ⇢ Bluetooth connectivity](#bluetooth-connectivity) @@ -53,6 +46,15 @@ After discovering ThePrimagen (I found him long ago, but I never bothered buying * [⇢ ⇢ Upcoming custom Kinesis build](#upcoming-custom-kinesis-build) * [⇢ ⇢ Conclusion](#conclusion) +## Introduction + +After work one day, I noticed some discomfort in my right wrist. Upon research, it appeared to be a mild case of Repetitive Strain Injury (RSI). Initially, I thought that this would go away after a while, but after a week it became even worse. This led me to consider potential causes such as poor posture or keyboard use habits. As an enthusiast of keyboards, I experimented with ergonomic concave ortholinear split keyboards. Wait, what?... + +* Concave: Some fingers are longer than others. A concave keyboard makes it so that the keycaps meant to be pressed by the longer fingers are further down (e.g., left middle finger for `e` on a Qwerty layout), and keycaps meant to be pressed by shorter fingers are further up (e.g., right pinky finger for the letter `p`). +* Ortholinear: The keys are arranged in a straight vertical line, unlike most conventional keyboards. The conventional keyboards still resemble the old typewriters, where the placement of the keys was optimized so that the typewriter would not jam. There is no such requirement anymore. +* Split: The keyboard is split into two halves (left and right), allowing one to place either hand where it is most ergonomic. + +After discovering ThePrimagen (I found him long ago, but I never bothered buying the same keyboard he is on) on YouTube and reading/watching a couple of reviews, I thought that as a computer professional, the equipment could be expensive anyway (laptop, adjustable desk, comfortable chair), so why not invest a bit more into the keyboard? I purchased myself the Kinesis Advantage360 Professional keyboard. ## Kinesis review For an in-depth review, have a look at this great article: -- cgit v1.2.3 From 145f3a854b71b814caccd3cc884e23184751c9a6 Mon Sep 17 00:00:00 2001 From: Paul Buetow Date: Tue, 17 Sep 2024 05:44:02 +0300 Subject: Update content for md --- gemfeed/2024-08-05-typing-127.1-words-per-minute.md | 1 + gemfeed/2024-09-07-projects-i-support.md | 2 +- 2 files changed, 2 insertions(+), 1 deletion(-) (limited to 'gemfeed') diff --git a/gemfeed/2024-08-05-typing-127.1-words-per-minute.md b/gemfeed/2024-08-05-typing-127.1-words-per-minute.md index e892aa08..94900c69 100644 --- a/gemfeed/2024-08-05-typing-127.1-words-per-minute.md +++ b/gemfeed/2024-08-05-typing-127.1-words-per-minute.md @@ -55,6 +55,7 @@ After work one day, I noticed some discomfort in my right wrist. Upon research, * Split: The keyboard is split into two halves (left and right), allowing one to place either hand where it is most ergonomic. After discovering ThePrimagen (I found him long ago, but I never bothered buying the same keyboard he is on) on YouTube and reading/watching a couple of reviews, I thought that as a computer professional, the equipment could be expensive anyway (laptop, adjustable desk, comfortable chair), so why not invest a bit more into the keyboard? I purchased myself the Kinesis Advantage360 Professional keyboard. + ## Kinesis review For an in-depth review, have a look at this great article: diff --git a/gemfeed/2024-09-07-projects-i-support.md b/gemfeed/2024-09-07-projects-i-support.md index cd7b446a..76282035 100644 --- a/gemfeed/2024-09-07-projects-i-support.md +++ b/gemfeed/2024-09-07-projects-i-support.md @@ -15,7 +15,7 @@ This is the list of projects and initiatives I support/sponsor. ||>>| \$/ || $$ --/ || One Hundred |<<|| ||<<| L38036133B *\\ |\_/ //* series |>>|| ||>>| 12 *\\/___\_//* 1989 |<<|| -||<<\ Open Soure ______/Franklin\________ Supporting />>|| +||<<\ Open Source ______/Franklin\________ Supporting />>|| ||//$\ ~| SPONSORING AND FUNDING |~ /$\\|| ||(100)=================== AWESOME OPEN SOURCE =================(100)|| ||\\$//\/\/\/\/\/\/\/\/\/\/\/\/\/\/\/\/\/\/\/\/\/\/\/\/\/\/\/\/\/\\$//|| -- cgit v1.2.3 From 0a5b0d8bfbee8656ae0e943ee59b095471bac697 Mon Sep 17 00:00:00 2001 From: Paul Buetow Date: Wed, 18 Sep 2024 21:57:07 +0300 Subject: Update content for md --- gemfeed/2021-04-24-welcome-to-the-geminispace.md | 17 +++++++++-------- 1 file changed, 9 insertions(+), 8 deletions(-) (limited to 'gemfeed') diff --git a/gemfeed/2021-04-24-welcome-to-the-geminispace.md b/gemfeed/2021-04-24-welcome-to-the-geminispace.md index 27f82c24..f6bb09e1 100644 --- a/gemfeed/2021-04-24-welcome-to-the-geminispace.md +++ b/gemfeed/2021-04-24-welcome-to-the-geminispace.md @@ -2,14 +2,6 @@ > Published at 2021-04-24T19:28:41+01:00; Updated at 2021-06-18 -ASCII Art by Andy Hood! - -Have you reached this article already via Gemini? It requires a Gemini client; web browsers such as Firefox, Chrome, Safari, etc., don't support the Gemini protocol. The Gemini address of this site (or the address of this capsule as people say in Geminispace) is: - -[gemini://foo.zone](gemini://foo.zone) - -However, if you still use HTTP, you are just surfing the fallback HTML version of this capsule. In that case, I suggest reading on what this is all about :-). - ``` /\ @@ -33,6 +25,7 @@ However, if you still use HTTP, you are just surfing the fallback HTML version o ## Table of Contents * [⇢ Welcome to the Geminispace](#welcome-to-the-geminispace) +* [⇢ ⇢ Introduction](#introduction) * [⇢ ⇢ Motivation](#motivation) * [⇢ ⇢ ⇢ My urge to revamp my personal website](#my-urge-to-revamp-my-personal-website) * [⇢ ⇢ ⇢ My still great Laptop running hot](#my-still-great-laptop-running-hot) @@ -41,6 +34,14 @@ However, if you still use HTTP, you are just surfing the fallback HTML version o * [⇢ ⇢ Gemini advantages summarised](#gemini-advantages-summarised) * [⇢ ⇢ Dive into deep Gemini space](#dive-into-deep-gemini-space) +## Introduction + +Have you reached this article already via Gemini? It requires a Gemini client; web browsers such as Firefox, Chrome, Safari, etc., don't support the Gemini protocol. The Gemini address of this site (or the address of this capsule as people say in Geminispace) is: + +[gemini://foo.zone](gemini://foo.zone) + +However, if you still use HTTP, you are just surfing the fallback HTML version of this capsule. In that case, I suggest reading on what this is all about :-). + ## Motivation ### My urge to revamp my personal website -- cgit v1.2.3 From 89af082f138fdb4c3f3dd39b7ef06a61b83c35ca Mon Sep 17 00:00:00 2001 From: Paul Buetow Date: Fri, 27 Sep 2024 23:28:32 +0300 Subject: Update content for md --- ...orithms-and-data-structures-in-golang-part-1.md | 240 --------------------- ...r-quickly-logging-ideas-programmed-in-golang.md | 1 - gemfeed/index.md | 1 - 3 files changed, 242 deletions(-) delete mode 100644 gemfeed/2023-04-09-algorithms-and-data-structures-in-golang-part-1.md (limited to 'gemfeed') diff --git a/gemfeed/2023-04-09-algorithms-and-data-structures-in-golang-part-1.md b/gemfeed/2023-04-09-algorithms-and-data-structures-in-golang-part-1.md deleted file mode 100644 index 265fe76b..00000000 --- a/gemfeed/2023-04-09-algorithms-and-data-structures-in-golang-part-1.md +++ /dev/null @@ -1,240 +0,0 @@ -# Algorithms and Data Structures in Go - Part 1 - -> Published at 2023-04-09T22:31:42+03:00 - -This is the first blog post about my Algorithms and Data Structures in Go series. I am not a Software Developer in my day job. In my current role, programming and scripting skills are desirable but not mandatory. I have been learning about Data Structures and Algorithms many years ago at University. I thought it would be fun to revisit/refresh my knowledge here and implement many of the algorithms in Go. - -[2023-04-09 Algorithms and Data Structures in Go - Part 1 (You are currently reading this)](./2023-04-09-algorithms-and-data-structures-in-golang-part-1.md) - -This post is about setting up some basic data structures and methods for this blog series. I promise, everything will be easy to follow in this post. It will become more interesting later in this series. - -``` - ,_---~~~~~----._ - _,,_,*^____ _____``*g*\"*, - / __/ /' ^. / \ ^@q f -[ @f | @)) | | @)) l 0 _/ - \`/ \~____ / __ \_____/ \ - | _l__l_ I - } [______] I - ] | | | | - ] ~ ~ | - | | - | | -``` - -## Table of Contents - -* [⇢ Algorithms and Data Structures in Go - Part 1](#algorithms-and-data-structures-in-go---part-1) -* [⇢ ⇢ Type constraints](#type-constraints) -* [⇢ ⇢ ArrayList](#arraylist) -* [⇢ ⇢ Helper methods](#helper-methods) -* [⇢ ⇢ Sleep sort](#sleep-sort) -* [⇢ ⇢ ⇢ Testing](#testing) - -## Type constraints - -First, the package `ds` (data structures) defines the `types.go`. All examples will either operate on the `Integer` or `Number` type: - -```go -package ds - -import ( - "golang.org/x/exp/constraints" -) - -type Integer interface { - constraints.Integer -} - -type Number interface { - constraints.Integer | constraints.Float -} - -``` - -## ArrayList - -Next comes the `arraylist.go`, which defines the underlying data structure all the algorithms of this series will use. `ArrayList` is just a type alias of a Go array (or slice) with custom methods on it: - -```go -package ds - -import ( - "fmt" - "math/rand" - "strings" -) - -type ArrayList[V Number] []V - -func NewArrayList[V Number](l int) ArrayList[V] { - return make(ArrayList[V], l) -} -``` - -As you can see, the code uses Go generics, which I refactored recently. Besides the default constructor (which only returns an empty `ArrayList` with a given capacity), there are also a bunch of special constructors. `NewRandomArrayList` is returning an `ArrayList` with random numbers, `NewAscendingArrayList` and `NewDescendingArrayList` are returning `ArrayList`s in either ascending or descending order. They all will be used later on for testing and benchmarking the algorithms. - -```go -func NewRandomArrayList[V Number](l, max int) ArrayList[V] { - a := make(ArrayList[V], l) - for i := 0; i < l; i++ { - if max > 0 { - a[i] = V(rand.Intn(max)) - continue - } - a[i] = V(rand.Int()) - } - return a -} - -func NewAscendingArrayList[V Number](l int) ArrayList[V] { - a := make(ArrayList[V], l) - for i := 0; i < l; i++ { - a[i] = V(i) - } - return a -} - -func NewDescendingArrayList[V Number](l int) ArrayList[V] { - a := make(ArrayList[V], l) - j := l - 1 - for i := 0; i < l; i++ { - a[i] = V(j) - j-- - } - return a -} -``` - -## Helper methods - -The `FirstN` method only returns the first N elements of the `ArrayList`. This is useful for printing out only parts of the data structure: - -```go -func (a ArrayList[V]) FirstN(n int) string { - var sb strings.Builder - j := n - - l := len(a) - if j > l { - j = l - } - - for i := 0; i < j; i++ { - fmt.Fprintf(&sb, "%v ", a[i]) - } - - if j < l { - fmt.Fprintf(&sb, "... ") - } - - return sb.String() -} -``` - -The `Sorted` method checks whether the `ArrayList` is sorted. This will be used by the unit tests later on: - -```go -func (a ArrayList[V]) Sorted() bool { - for i := len(a) - 1; i > 0; i-- { - if a[i] < a[i-1] { - return false - } - } - return true -} -``` - -And the last utility method used is `Swap`, which allows swapping the values of two indices in the `ArrayList`: - -```go -func (a ArrayList[V]) Swap(i, j int) { - aux := a[i] - a[i] = a[j] - a[j] = aux -} - -``` - -## Sleep sort - -Let's implement our first algorithm, sleep sort. Sleep sort is a non-traditional and unconventional sorting algorithm based on the idea of waiting a certain amount of time corresponding to the value of each element in the input `ArrayList`. It's more of a fun, creative concept rather than an efficient or practical sorting technique. This is not a sorting algorithm you would use in any production code. As you can imagine, it is quite an inefficient sorting algorithm (it's only listed here as a warm-up exercise). This sorting method may also return false results depending on how the Goroutines are scheduled by the Go runtime. - - -```go -package sort - -import ( - "codeberg.org/snonux/algorithms/ds" - "sync" - "time" -) - -func Sleep[V ds.Integer](a ds.ArrayList[V]) ds.ArrayList[V] { - sorted := ds.NewArrayList[V](len(a)) - - numCh := make(chan V) - var wg sync.WaitGroup - wg.Add(len(a)) - - go func() { - wg.Wait() - close(numCh) - }() - - for _, num := range a { - go func(num V) { - defer wg.Done() - time.Sleep(time.Duration(num) * time.Second) - numCh <- num - }(num) - } - - for num := range numCh { - sorted = append(sorted, num) - } - - return sorted -} -``` - -This Go code implements the sleep sort algorithm using generics and goroutines. The main function `Sleep[V ds.Integer](a ds.ArrayList[V]) ds.ArrayList[V]` takes a generic `ArrayList` as input and returns a sorted `ArrayList`. The code creates a separate goroutine for each element in the input array, sleeps for a duration proportional to the element's value, and then sends the element to a channel. Another goroutine waits for all the sleeping goroutines to finish and then closes the channel. The sorted result `ArrayList` is constructed by appending the elements received from the channel in the order they arrive. The `sync.WaitGroup` is used to synchronize goroutines and ensure that all of them have completed before closing the channel. - -### Testing - -For testing, we only allow values up to 10, as otherwise, it would take too long to finish: - -```go -package sort - -import ( - "fmt" - "testing" - - "codeberg.org/snonux/algorithms/ds" -) - -func TestSleepSort(t *testing.T) { - a := ds.NewRandomArrayList[int](10, 10) - a = Sleep(a) - if !a.Sorted() { - t.Errorf("Array not sorted: %v", a) - } -} -``` - -As you can see, it takes `9s` here for the algorithm to finish (which is the highest value in the `ArrayList`): - -```sh -❯ go test ./sort -v -run SleepSort -=== RUN TestSleepSort ---- PASS: TestSleepSort (9.00s) -PASS -ok codeberg.org/snonux/algorithms/sort 9.002s -``` - -I won't write any benchmark for sleep sort; that will be done for the algorithms to come in this series :-). - -E-Mail your comments to `paul@nospam.buetow.org` :-) - -[Back to the main site](../) diff --git a/gemfeed/2024-03-03-a-fine-fyne-android-app-for-quickly-logging-ideas-programmed-in-golang.md b/gemfeed/2024-03-03-a-fine-fyne-android-app-for-quickly-logging-ideas-programmed-in-golang.md index 2d7a0873..1f660405 100644 --- a/gemfeed/2024-03-03-a-fine-fyne-android-app-for-quickly-logging-ideas-programmed-in-golang.md +++ b/gemfeed/2024-03-03-a-fine-fyne-android-app-for-quickly-logging-ideas-programmed-in-golang.md @@ -54,7 +54,6 @@ E-Mail your comments to `paul@nospam.buetow.org` :-) Other Go related posts are: -[2023-04-09 Algorithms and Data Structures in Go - Part 1](./2023-04-09-algorithms-and-data-structures-in-golang-part-1.md) [2024-03-03 A fine Fyne Android app for quickly logging ideas programmed in Go (You are currently reading this)](./2024-03-03-a-fine-fyne-android-app-for-quickly-logging-ideas-programmed-in-golang.md) [Back to the main site](../) diff --git a/gemfeed/index.md b/gemfeed/index.md index 952eb8b0..2749618c 100644 --- a/gemfeed/index.md +++ b/gemfeed/index.md @@ -26,7 +26,6 @@ [2023-06-01 - KISS server monitoring with Gogios](./2023-06-01-kiss-server-monitoring-with-gogios.md) [2023-05-06 - 'The Obstacle is the Way' book notes](./2023-05-06-the-obstacle-is-the-way-book-notes.md) [2023-05-01 - Unveiling `guprecords.raku`: Global Uptime Records with Raku](./2023-05-01-unveiling-guprecords:-uptime-records-with-raku.md) -[2023-04-09 - Algorithms and Data Structures in Go - Part 1](./2023-04-09-algorithms-and-data-structures-in-golang-part-1.md) [2023-04-01 - 'Never split the difference' book notes](./2023-04-01-never-split-the-difference-book-notes.md) [2023-03-25 - Gemtexter 2.0.0 - Let's Gemtext again²](./2023-03-25-gemtexter-2.0.0-lets-gemtext-again-2.md) [2023-03-16 - 'The Pragmatic Programmer' book notes](./2023-03-16-the-pragmatic-programmer-book-notes.md) -- cgit v1.2.3 From 3ca470a8c0eaacb0e03e85a5673baedc0fbe6517 Mon Sep 17 00:00:00 2001 From: Paul Buetow Date: Tue, 1 Oct 2024 21:47:25 +0300 Subject: Update content for md --- gemfeed/2021-04-24-welcome-to-the-geminispace.md | 1 + ...-05-gemtexter-one-bash-script-to-rule-it-all.md | 1 + ...022-08-27-gemtexter-1.1.0-lets-gemtext-again.md | 1 + ...3-03-25-gemtexter-2.0.0-lets-gemtext-again-2.md | 1 + ...3-07-21-gemtexter-2.1.0-lets-gemtext-again-3.md | 1 + ...4-10-02-gemtexter-3.0.0-lets-gemtext-again-4.md | 86 ++++++++++++++++++++++ gemfeed/index.md | 1 + 7 files changed, 92 insertions(+) create mode 100644 gemfeed/2024-10-02-gemtexter-3.0.0-lets-gemtext-again-4.md (limited to 'gemfeed') diff --git a/gemfeed/2021-04-24-welcome-to-the-geminispace.md b/gemfeed/2021-04-24-welcome-to-the-geminispace.md index f6bb09e1..17d3291f 100644 --- a/gemfeed/2021-04-24-welcome-to-the-geminispace.md +++ b/gemfeed/2021-04-24-welcome-to-the-geminispace.md @@ -99,5 +99,6 @@ Other related posts are: [2022-08-27 Gemtexter 1.1.0 - Let's Gemtext again](./2022-08-27-gemtexter-1.1.0-lets-gemtext-again.md) [2023-03-25 Gemtexter 2.0.0 - Let's Gemtext again²](./2023-03-25-gemtexter-2.0.0-lets-gemtext-again-2.md) [2023-07-21 Gemtexter 2.1.0 - Let's Gemtext again³](./2023-07-21-gemtexter-2.1.0-lets-gemtext-again-3.md) +[2024-10-02 Gemtexter 3.0.0 - Let's Gemtext again⁴](./2024-10-02-gemtexter-3.0.0-lets-gemtext-again-4.md) [Back to the main site](../) diff --git a/gemfeed/2021-06-05-gemtexter-one-bash-script-to-rule-it-all.md b/gemfeed/2021-06-05-gemtexter-one-bash-script-to-rule-it-all.md index f71fb3d0..1766c067 100644 --- a/gemfeed/2021-06-05-gemtexter-one-bash-script-to-rule-it-all.md +++ b/gemfeed/2021-06-05-gemtexter-one-bash-script-to-rule-it-all.md @@ -192,5 +192,6 @@ Other related posts are: [2023-03-25 Gemtexter 2.0.0 - Let's Gemtext again²](./2023-03-25-gemtexter-2.0.0-lets-gemtext-again-2.md) [2023-07-21 Gemtexter 2.1.0 - Let's Gemtext again³](./2023-07-21-gemtexter-2.1.0-lets-gemtext-again-3.md) [2023-12-10 Bash Golf Part 3](./2023-12-10-bash-golf-part-3.md) +[2024-10-02 Gemtexter 3.0.0 - Let's Gemtext again⁴](./2024-10-02-gemtexter-3.0.0-lets-gemtext-again-4.md) [Back to the main site](../) diff --git a/gemfeed/2022-08-27-gemtexter-1.1.0-lets-gemtext-again.md b/gemfeed/2022-08-27-gemtexter-1.1.0-lets-gemtext-again.md index 24161520..fa08c841 100644 --- a/gemfeed/2022-08-27-gemtexter-1.1.0-lets-gemtext-again.md +++ b/gemfeed/2022-08-27-gemtexter-1.1.0-lets-gemtext-again.md @@ -107,5 +107,6 @@ Other related posts are: [2022-08-27 Gemtexter 1.1.0 - Let's Gemtext again (You are currently reading this)](./2022-08-27-gemtexter-1.1.0-lets-gemtext-again.md) [2023-03-25 Gemtexter 2.0.0 - Let's Gemtext again²](./2023-03-25-gemtexter-2.0.0-lets-gemtext-again-2.md) [2023-07-21 Gemtexter 2.1.0 - Let's Gemtext again³](./2023-07-21-gemtexter-2.1.0-lets-gemtext-again-3.md) +[2024-10-02 Gemtexter 3.0.0 - Let's Gemtext again⁴](./2024-10-02-gemtexter-3.0.0-lets-gemtext-again-4.md) [Back to the main site](../) diff --git a/gemfeed/2023-03-25-gemtexter-2.0.0-lets-gemtext-again-2.md b/gemfeed/2023-03-25-gemtexter-2.0.0-lets-gemtext-again-2.md index a025fd8f..568d1262 100644 --- a/gemfeed/2023-03-25-gemtexter-2.0.0-lets-gemtext-again-2.md +++ b/gemfeed/2023-03-25-gemtexter-2.0.0-lets-gemtext-again-2.md @@ -155,5 +155,6 @@ Other related posts are: [2022-08-27 Gemtexter 1.1.0 - Let's Gemtext again](./2022-08-27-gemtexter-1.1.0-lets-gemtext-again.md) [2023-03-25 Gemtexter 2.0.0 - Let's Gemtext again² (You are currently reading this)](./2023-03-25-gemtexter-2.0.0-lets-gemtext-again-2.md) [2023-07-21 Gemtexter 2.1.0 - Let's Gemtext again³](./2023-07-21-gemtexter-2.1.0-lets-gemtext-again-3.md) +[2024-10-02 Gemtexter 3.0.0 - Let's Gemtext again⁴](./2024-10-02-gemtexter-3.0.0-lets-gemtext-again-4.md) [Back to the main site](../) diff --git a/gemfeed/2023-07-21-gemtexter-2.1.0-lets-gemtext-again-3.md b/gemfeed/2023-07-21-gemtexter-2.1.0-lets-gemtext-again-3.md index f98ce69d..fcb68332 100644 --- a/gemfeed/2023-07-21-gemtexter-2.1.0-lets-gemtext-again-3.md +++ b/gemfeed/2023-07-21-gemtexter-2.1.0-lets-gemtext-again-3.md @@ -111,5 +111,6 @@ Other related posts are: [2022-08-27 Gemtexter 1.1.0 - Let's Gemtext again](./2022-08-27-gemtexter-1.1.0-lets-gemtext-again.md) [2023-03-25 Gemtexter 2.0.0 - Let's Gemtext again²](./2023-03-25-gemtexter-2.0.0-lets-gemtext-again-2.md) [2023-07-21 Gemtexter 2.1.0 - Let's Gemtext again³ (You are currently reading this)](./2023-07-21-gemtexter-2.1.0-lets-gemtext-again-3.md) +[2024-10-02 Gemtexter 3.0.0 - Let's Gemtext again⁴](./2024-10-02-gemtexter-3.0.0-lets-gemtext-again-4.md) [Back to the main site](../) diff --git a/gemfeed/2024-10-02-gemtexter-3.0.0-lets-gemtext-again-4.md b/gemfeed/2024-10-02-gemtexter-3.0.0-lets-gemtext-again-4.md new file mode 100644 index 00000000..a4a8554e --- /dev/null +++ b/gemfeed/2024-10-02-gemtexter-3.0.0-lets-gemtext-again-4.md @@ -0,0 +1,86 @@ +# Gemtexter 3.0.0 - Let's Gemtext again⁴ + +> Published at 2024-10-01T21:46:26+03:00 + +I proudly announce that I've released Gemtexter version `3.0.0`. What is Gemtexter? It's my minimalist static site generator for Gemini Gemtext, HTML and Markdown, written in GNU Bash. + +[https://codeberg.org/snonux/gemtexter](https://codeberg.org/snonux/gemtexter) + +``` +-=[ typewriters ]=- 1/98 + .-------. + .-------. _|~~ ~~ |_ + _|~~ ~~ |_ .-------. =(_|_______|_) + =(_|_______|_)= _|~~ ~~ |_ |:::::::::| .-------. + |:::::::::| =(_|_______|_) |:::::::[]| _|~~ ~~ |_ + |:::::::[]| |:::::::::| |o=======.| =(_|_______|_) + |o=======.| |:::::::[]| `"""""""""` |:::::::::| + jgs `"""""""""` |o=======.| |:::::::[]| + mod. by Paul Buetow `"""""""""` |o=======.| + `"""""""""` +``` + +## Table of Contents + +* [⇢ Gemtexter 3.0.0 - Let's Gemtext again⁴](#gemtexter-300---let-s-gemtext-again) +* [⇢ ⇢ Why Bash?](#why-bash) +* [⇢ ⇢ HTML exact variant is the only variant](#html-exact-variant-is-the-only-variant) +* [⇢ ⇢ Table of Contents auto-generation](#table-of-contents-auto-generation) +* [⇢ ⇢ Configurable themes](#configurable-themes) +* [⇢ ⇢ No use of webfonts by default](#no-use-of-webfonts-by-default) +* [⇢ ⇢ More](#more) + +## Why Bash? + +This project is too complex for a Bash script. Writing it in Bash was to try out how maintainable a "larger" Bash script could be. It's still pretty maintainable and helps me try new Bash tricks here and then! + +Let's list what's new! + +## HTML exact variant is the only variant + +The last version of Gemtexter introduced the HTML exact variant, which wasn't enabled by default. This version of Gemtexter removes the previous (inexact) variant and makes the exact variant the default. This is a breaking change, which is why there is a major version bump of Gemtexter. Here is a reminder of what the exact variant was: + +> Gemtexter is there to convert your Gemini Capsule into other formats, such as HTML and Markdown. An HTML exact variant can now be enabled in the `gemtexter.conf` by adding the line `declare -rx HTML_VARIANT=exact`. The HTML/CSS output changed to reflect a more exact Gemtext appearance and to respect the same spacing as you would see in the Geminispace. + +## Table of Contents auto-generation + +Just add... + +``` + << template::inline::toc +``` + +...into a Gemtexter template file and Gemtexter will automatically generate a table of contents for the page based on the headings (see this page's ToC for example). The ToC will also have links to the relevant sections in HTML and Markdown output. The Gemtext format does not support links, so the ToC will simply be displayed as a bullet list. + +## Configurable themes + +It was always possible to customize the style of a Gemtexter's resulting HTML page, but all the config options were scattered across multiple files. Now, the CSS style, web fonts, etc., are all configurable via themes. + +Simply configure `HTML_THEME_DIR` in the `gemtexter.conf` file to the corresponding directory. For example: + +```bash +declare -xr HTML_THEME_DIR=./extras/html/themes/simple +``` + +To customize the theme or create your own, simply copy the theme directory and modify it as needed. This makes it also much easier to switch between layouts. + +## No use of webfonts by default + +The default theme is now "back to the basics" and does not utilize any web fonts. The previous themes are still part of the release and can be easily configured. These are currently the `future` and `business` themes. You can check them out from the themes directory. + +## More + +Additionally, there were a couple of bug fixes, refactorings and overall improvements in the documentation made. + +E-Mail your comments to `paul@nospam.buetow.org` :-) + +Other related posts are: + +[2021-04-24 Welcome to the Geminispace](./2021-04-24-welcome-to-the-geminispace.md) +[2021-06-05 Gemtexter - One Bash script to rule it all](./2021-06-05-gemtexter-one-bash-script-to-rule-it-all.md) +[2022-08-27 Gemtexter 1.1.0 - Let's Gemtext again](./2022-08-27-gemtexter-1.1.0-lets-gemtext-again.md) +[2023-03-25 Gemtexter 2.0.0 - Let's Gemtext again²](./2023-03-25-gemtexter-2.0.0-lets-gemtext-again-2.md) +[2023-07-21 Gemtexter 2.1.0 - Let's Gemtext again³](./2023-07-21-gemtexter-2.1.0-lets-gemtext-again-3.md) +[2024-10-02 Gemtexter 3.0.0 - Let's Gemtext again⁴ (You are currently reading this)](./2024-10-02-gemtexter-3.0.0-lets-gemtext-again-4.md) + +[Back to the main site](../) diff --git a/gemfeed/index.md b/gemfeed/index.md index 2749618c..d1b2f6a4 100644 --- a/gemfeed/index.md +++ b/gemfeed/index.md @@ -2,6 +2,7 @@ ## To be in the .zone! +[2024-10-02 - Gemtexter 3.0.0 - Let's Gemtext again⁴](./2024-10-02-gemtexter-3.0.0-lets-gemtext-again-4.md) [2024-09-07 - Site Reliability Engineering - Part 4: Onboarding for On-Call Engineers](./2024-09-07-site-reliability-engineering-part-4.md) [2024-09-07 - Projects I financially support](./2024-09-07-projects-i-support.md) [2024-08-05 - Typing `127.1` words per minute (`>100wpm average`)](./2024-08-05-typing-127.1-words-per-minute.md) -- cgit v1.2.3 From 9d170b46ac4cdae74e01eab8c1db7d662f63f26c Mon Sep 17 00:00:00 2001 From: Paul Buetow Date: Thu, 24 Oct 2024 21:05:39 +0300 Subject: Update content for md --- gemfeed/2022-04-10-creative-universe.md | 2 +- ...23-03-16-the-pragmatic-programmer-book-notes.md | 2 +- ...-04-01-never-split-the-difference-book-notes.md | 1 + ...023-05-06-the-obstacle-is-the-way-book-notes.md | 2 +- ...7-17-career-guide-and-soft-skills-book-notes.md | 2 +- gemfeed/2023-11-11-mind-management-book-notes.md | 2 +- gemfeed/2024-05-01-slow-productivity-book-notes.md | 2 +- .../2024-07-07-the-stoic-challenge-book-notes.md | 2 +- gemfeed/2024-10-24-staff-engineer-book-notes.md | 71 ++++++++++++++++++++++ gemfeed/index.md | 1 + 10 files changed, 80 insertions(+), 7 deletions(-) create mode 100644 gemfeed/2024-10-24-staff-engineer-book-notes.md (limited to 'gemfeed') diff --git a/gemfeed/2022-04-10-creative-universe.md b/gemfeed/2022-04-10-creative-universe.md index 4f49e989..ff464c96 100644 --- a/gemfeed/2022-04-10-creative-universe.md +++ b/gemfeed/2022-04-10-creative-universe.md @@ -90,7 +90,7 @@ I am not saying that you should skip sleep. By all means, if you can sleep, then Have regular breaks. Don't skip your lunch break. Best, have a walk during lunchtime. And after work, do some kind of workout or visit a sports class. Do something completely unrelated to work before going to sleep (e.g. visit a parallel universe and read a Science Fiction novel). In short: Totally hit the off-switch after your work for the day is finished. You will be much more energised and motivated the next time you open your work laptop. -[I personally love to read Science Fiction novels](../other-resources.md) +[I personally love to read Science Fiction novels](../about/novels.md) I skip breakfast and lunch during the week. This means that on average, I intermittent fast on average 18-20 hours daily. It may sound odd to most people (who don't intermittent fast), but in a fasted state, I can be even more focused, thus helping me immerse myself in something even more. Not having breakfast and lunch also gives me back some time for other things (e.g. a nice walk, where I listen to podcasts or audiobooks or practise using my camera (street photography)). I relax my routine during the week ends, where I may enjoy a meal at any given time of the day. diff --git a/gemfeed/2023-03-16-the-pragmatic-programmer-book-notes.md b/gemfeed/2023-03-16-the-pragmatic-programmer-book-notes.md index 045eb4ee..f43d1055 100644 --- a/gemfeed/2023-03-16-the-pragmatic-programmer-book-notes.md +++ b/gemfeed/2023-03-16-the-pragmatic-programmer-book-notes.md @@ -87,6 +87,6 @@ Other book notes of mine are: [2023-11-11 "Mind Management" book notes](./2023-11-11-mind-management-book-notes.md) [2024-05-01 "Slow Productivity" book notes](./2024-05-01-slow-productivity-book-notes.md) [2024-07-07 "The Stoic Challenge" book notes](./2024-07-07-the-stoic-challenge-book-notes.md) +[2024-10-24 "Staff Engineer" book notes](./2024-10-24-staff-engineer-book-notes.md) -[More books and other resources I found useful.](../resources.md) [Back to the main site](../) diff --git a/gemfeed/2023-04-01-never-split-the-difference-book-notes.md b/gemfeed/2023-04-01-never-split-the-difference-book-notes.md index 0dcc7a8e..9500ae38 100644 --- a/gemfeed/2023-04-01-never-split-the-difference-book-notes.md +++ b/gemfeed/2023-04-01-never-split-the-difference-book-notes.md @@ -146,5 +146,6 @@ Other book notes of mine are: [2023-11-11 "Mind Management" book notes](./2023-11-11-mind-management-book-notes.md) [2024-05-01 "Slow Productivity" book notes](./2024-05-01-slow-productivity-book-notes.md) [2024-07-07 "The Stoic Challenge" book notes](./2024-07-07-the-stoic-challenge-book-notes.md) +[2024-10-24 "Staff Engineer" book notes](./2024-10-24-staff-engineer-book-notes.md) [Back to the main site](../) diff --git a/gemfeed/2023-05-06-the-obstacle-is-the-way-book-notes.md b/gemfeed/2023-05-06-the-obstacle-is-the-way-book-notes.md index e546bcc8..1256673d 100644 --- a/gemfeed/2023-05-06-the-obstacle-is-the-way-book-notes.md +++ b/gemfeed/2023-05-06-the-obstacle-is-the-way-book-notes.md @@ -107,6 +107,6 @@ Other book notes of mine are: [2023-11-11 "Mind Management" book notes](./2023-11-11-mind-management-book-notes.md) [2024-05-01 "Slow Productivity" book notes](./2024-05-01-slow-productivity-book-notes.md) [2024-07-07 "The Stoic Challenge" book notes](./2024-07-07-the-stoic-challenge-book-notes.md) +[2024-10-24 "Staff Engineer" book notes](./2024-10-24-staff-engineer-book-notes.md) -[More books and other resources I found useful.](../resources.md) [Back to the main site](../) diff --git a/gemfeed/2023-07-17-career-guide-and-soft-skills-book-notes.md b/gemfeed/2023-07-17-career-guide-and-soft-skills-book-notes.md index 3a28aa17..8c5e6500 100644 --- a/gemfeed/2023-07-17-career-guide-and-soft-skills-book-notes.md +++ b/gemfeed/2023-07-17-career-guide-and-soft-skills-book-notes.md @@ -315,6 +315,6 @@ Other book notes of mine are: [2023-11-11 "Mind Management" book notes](./2023-11-11-mind-management-book-notes.md) [2024-05-01 "Slow Productivity" book notes](./2024-05-01-slow-productivity-book-notes.md) [2024-07-07 "The Stoic Challenge" book notes](./2024-07-07-the-stoic-challenge-book-notes.md) +[2024-10-24 "Staff Engineer" book notes](./2024-10-24-staff-engineer-book-notes.md) -[More books and other resources I found useful.](../resources.md) [Back to the main site](../) diff --git a/gemfeed/2023-11-11-mind-management-book-notes.md b/gemfeed/2023-11-11-mind-management-book-notes.md index 863f33e5..96a2c6e5 100644 --- a/gemfeed/2023-11-11-mind-management-book-notes.md +++ b/gemfeed/2023-11-11-mind-management-book-notes.md @@ -117,6 +117,6 @@ Other book notes of mine are: [2023-11-11 "Mind Management" book notes (You are currently reading this)](./2023-11-11-mind-management-book-notes.md) [2024-05-01 "Slow Productivity" book notes](./2024-05-01-slow-productivity-book-notes.md) [2024-07-07 "The Stoic Challenge" book notes](./2024-07-07-the-stoic-challenge-book-notes.md) +[2024-10-24 "Staff Engineer" book notes](./2024-10-24-staff-engineer-book-notes.md) -[More books and other resources I found useful.](../resources.md) [Back to the main site](../) diff --git a/gemfeed/2024-05-01-slow-productivity-book-notes.md b/gemfeed/2024-05-01-slow-productivity-book-notes.md index b53ac2ee..6fde73fa 100644 --- a/gemfeed/2024-05-01-slow-productivity-book-notes.md +++ b/gemfeed/2024-05-01-slow-productivity-book-notes.md @@ -145,6 +145,6 @@ Other book notes of mine are: [2023-11-11 "Mind Management" book notes](./2023-11-11-mind-management-book-notes.md) [2024-05-01 "Slow Productivity" book notes (You are currently reading this)](./2024-05-01-slow-productivity-book-notes.md) [2024-07-07 "The Stoic Challenge" book notes](./2024-07-07-the-stoic-challenge-book-notes.md) +[2024-10-24 "Staff Engineer" book notes](./2024-10-24-staff-engineer-book-notes.md) -[More books and other resources I found useful.](../resources.md) [Back to the main site](../) diff --git a/gemfeed/2024-07-07-the-stoic-challenge-book-notes.md b/gemfeed/2024-07-07-the-stoic-challenge-book-notes.md index 55edb442..cb9b3294 100644 --- a/gemfeed/2024-07-07-the-stoic-challenge-book-notes.md +++ b/gemfeed/2024-07-07-the-stoic-challenge-book-notes.md @@ -64,6 +64,6 @@ Other book notes of mine are: [2023-11-11 "Mind Management" book notes](./2023-11-11-mind-management-book-notes.md) [2024-05-01 "Slow Productivity" book notes](./2024-05-01-slow-productivity-book-notes.md) [2024-07-07 "The Stoic Challenge" book notes (You are currently reading this)](./2024-07-07-the-stoic-challenge-book-notes.md) +[2024-10-24 "Staff Engineer" book notes](./2024-10-24-staff-engineer-book-notes.md) -[More books and other resources I found useful.](../resources.md) [Back to the main site](../) diff --git a/gemfeed/2024-10-24-staff-engineer-book-notes.md b/gemfeed/2024-10-24-staff-engineer-book-notes.md new file mode 100644 index 00000000..4608c965 --- /dev/null +++ b/gemfeed/2024-10-24-staff-engineer-book-notes.md @@ -0,0 +1,71 @@ +# "Staff Engineer" book notes + +> Published at 2024-10-24T20:57:44+03:00 + +These are my personal takeaways after reading "Staff Engineer" by Will Larson. Note that the book contains much more knowledge wisdom and that these notes only contain points I personally found worth writing down. This is mainly for my own use, but you might find it helpful too. + +``` + ,.......... .........., + ,..,' '.' ',.., + ,' ,' : ', ', + ,' ,' : ', ', + ,' ,' : ', ', + ,' ,'............., : ,.............', ', +,' '............ '.' ............' ', + '''''''''''''''''';''';'''''''''''''''''' + ''' +``` + +## Table of Contents + +* [⇢ "Staff Engineer" book notes](#staff-engineer-book-notes) +* [⇢ ⇢ Not a faster Senior Engineer](#not-a-faster-senior-engineer) +* [⇢ ⇢ The Balance](#the-balance) +* [⇢ ⇢ More things](#more-things) + +## Not a faster Senior Engineer + +* A Staff engineer is more than just a faster Senior. +* A staff engineer is not a senior engineer but a bit better. (But I want to be a senior engineer but a bit better). + +It's important to know what work or which role most energizes you. A Staff engineer is not a more senior engineer. A Staff engineer also fits into another archetype. + +As a staff engineer, you are always expected to go beyond your comfort zone and learn new things. + +Your job sometimes will feel like an SEM and sometimes strangely similar to your senior roles. + +A Staff engineer is, like a Manager, a leader. However, being a Manager is a specific job. Leaders can apply to any job, especially to Staff engineers. + +## The Balance + +The more senior you become, the more responsibility you will have to cope with them in less time. Balance your speed of progress with your personal life, don't work late hours and don't skip these personal care events. + +Do fewer things but do them better. Everything done will accelerate the organization. Everything else will drag it down—quality over quantity. + +Don't work at ten things and progress slowly; focus on one thing and finish it. + +Only spend some of the time firefighting. Have time for deep thinking. Only deep think some of the time. Otherwise, you lose touch with reality. + +Sebactical: Take at least six months. Otherwise, it won't be as restored. + +## More things + +* Provide simple but widely used tools. Complex and powerful tools will have power users but only a very few. All others will not use the tool. +* In meetings, when someone is inactive, try to pull him in. Pull in max one person at a time. Don't open the discussion to multiple people. +* Get used to writing things down and repeating yourself. You will scale yourself much more. +* Title inflation: skills correspond to work, but the titles don't. + +E-Mail your comments to `paul@nospam.buetow.org` :-) + +Other book notes of mine are: + +[2023-03-16 "The Pragmatic Programmer" book notes](./2023-03-16-the-pragmatic-programmer-book-notes.md) +[2023-04-01 "Never split the difference" book notes](./2023-04-01-never-split-the-difference-book-notes.md) +[2023-05-06 "The Obstacle is the Way" book notes](./2023-05-06-the-obstacle-is-the-way-book-notes.md) +[2023-07-17 "Software Developmers Career Guide and Soft Skills" book notes](./2023-07-17-career-guide-and-soft-skills-book-notes.md) +[2023-11-11 "Mind Management" book notes](./2023-11-11-mind-management-book-notes.md) +[2024-05-01 "Slow Productivity" book notes](./2024-05-01-slow-productivity-book-notes.md) +[2024-07-07 "The Stoic Challenge" book notes](./2024-07-07-the-stoic-challenge-book-notes.md) +[2024-10-24 "Staff Engineer" book notes (You are currently reading this)](./2024-10-24-staff-engineer-book-notes.md) + +[Back to the main site](../) diff --git a/gemfeed/index.md b/gemfeed/index.md index d1b2f6a4..a88036bf 100644 --- a/gemfeed/index.md +++ b/gemfeed/index.md @@ -2,6 +2,7 @@ ## To be in the .zone! +[2024-10-24 - 'Staff Engineer' book notes](./2024-10-24-staff-engineer-book-notes.md) [2024-10-02 - Gemtexter 3.0.0 - Let's Gemtext again⁴](./2024-10-02-gemtexter-3.0.0-lets-gemtext-again-4.md) [2024-09-07 - Site Reliability Engineering - Part 4: Onboarding for On-Call Engineers](./2024-09-07-site-reliability-engineering-part-4.md) [2024-09-07 - Projects I financially support](./2024-09-07-projects-i-support.md) -- cgit v1.2.3 From 39c9814f5b9382239401ed80c8b1d9a8b5895e54 Mon Sep 17 00:00:00 2001 From: Paul Buetow Date: Thu, 24 Oct 2024 21:12:39 +0300 Subject: Update content for md --- gemfeed/2024-10-24-staff-engineer-book-notes.md | 62 +++++++++++++++++++++++++ 1 file changed, 62 insertions(+) (limited to 'gemfeed') diff --git a/gemfeed/2024-10-24-staff-engineer-book-notes.md b/gemfeed/2024-10-24-staff-engineer-book-notes.md index 4608c965..86f9abbe 100644 --- a/gemfeed/2024-10-24-staff-engineer-book-notes.md +++ b/gemfeed/2024-10-24-staff-engineer-book-notes.md @@ -19,10 +19,72 @@ These are my personal takeaways after reading "Staff Engineer" by Will Larson. N ## Table of Contents * [⇢ "Staff Engineer" book notes](#staff-engineer-book-notes) +* [⇢ ⇢ The Four Archetypes of a Staff Engineer](#the-four-archetypes-of-a-staff-engineer) +* [⇢ ⇢ Influence and Impact over Authority](#influence-and-impact-over-authority) +* [⇢ ⇢ Breadth and Depth of Knowledge](#breadth-and-depth-of-knowledge) +* [⇢ ⇢ Mentorship and Sponsorship](#mentorship-and-sponsorship) +* [⇢ ⇢ Managing Up and Across](#managing-up-and-across) +* [⇢ ⇢ Strategic Thinking](#strategic-thinking) +* [⇢ ⇢ Emotional Intelligence](#emotional-intelligence) +* [⇢ ⇢ Navigating Ambiguity](#navigating-ambiguity) +* [⇢ ⇢ Visible and Invisible Work](#visible-and-invisible-work) +* [⇢ ⇢ Scaling Yourself](#scaling-yourself) +* [⇢ ⇢ Career Progression and Title Inflation](#career-progression-and-title-inflation) * [⇢ ⇢ Not a faster Senior Engineer](#not-a-faster-senior-engineer) * [⇢ ⇢ The Balance](#the-balance) * [⇢ ⇢ More things](#more-things) +## The Four Archetypes of a Staff Engineer + +Larson breaks down the role of a Staff Engineer into four main archetypes, which can help frame how you approach the role: + +* Tech Lead: Focuses on the technical direction of a team, ensuring high-quality execution, architecture, and aligning the team around shared goals. +* Solver: Gets pulled into complex, high-impact problems that often involve many teams or systems, operating as a fixer or troubleshooter. +* Architect: Works on the long-term technical vision for an organization, setting standards and designing systems that will scale and last over time. +* Right Hand: Functions as a trusted technical advisor to leadership, providing input on strategy, long-term decisions, and navigating organizational politics. + +## Influence and Impact over Authority + +As a Staff Engineer, influence is often more important than formal authority. You’ll rarely have direct control over teams or projects but will need to drive outcomes by influencing peers, other teams, and leadership. It’s about understanding how to persuade, align, and mentor others to achieve technical outcomes. + +## Breadth and Depth of Knowledge + +Staff Engineers often need to maintain a breadth of knowledge across various areas while maintaining depth in a few. This can mean keeping a high-level understanding of several domains (e.g., infrastructure, security, product development) but being able to dive deep when needed in certain core areas. + +## Mentorship and Sponsorship + +An important part of a Staff Engineer’s role is mentoring others, not just in technical matters but in career development as well. Sponsorship goes a step beyond mentorship, where you actively advocate for others, create opportunities for them, and push them toward growth. + +## Managing Up and Across + +Success as a Staff Engineer often depends on managing up (influencing leadership and setting expectations) and managing across (working effectively with peers and other teams). This is often tied to communication skills, the ability to advocate for technical needs, and fostering alignment across departments or organizations. + +## Strategic Thinking + +While Senior Engineers may focus on execution, Staff Engineers are expected to think strategically, making decisions that will affect the company or product months or years down the line. This means balancing short-term execution needs with long-term architectural decisions, which may require challenging short-term pressures. + +## Emotional Intelligence + +The higher you go in engineering roles, the more soft skills, particularly emotional intelligence (EQ), come into play. Building relationships, resolving conflicts, and understanding the broader emotional dynamics of the team and organization become key parts of your role. + +## Navigating Ambiguity + +Staff Engineers are often placed in situations with high ambiguity—whether in defining the problem space, coming up with a solution, or aligning stakeholders. The ability to operate effectively in these unclear areas is critical to success. + +## Visible and Invisible Work + +Much of the work done by Staff Engineers is invisible. Solving complex problems, creating alignment, or influencing decisions doesn’t always result in tangible code, but it can have a massive impact. Larson emphasizes that part of the role is being comfortable with this type of invisible contribution. + +## Scaling Yourself + +At the Staff Engineer level, you must scale your impact beyond direct contribution. This can involve improving documentation, developing repeatable processes, mentoring others, or automating parts of the workflow. The idea is to enable teams and individuals to be more effective, even when you’re not directly involved. + +## Career Progression and Title Inflation + +Larson touches on how different companies have varying definitions of "Staff Engineer," and titles don’t always correlate directly with responsibility or skill. He emphasizes the importance of focusing more on the work you're doing and the impact you're having, rather than the title itself. + +These additional points reflect more of the strategic, interpersonal, and leadership aspects that go beyond the technical expertise expected at this level. The role of a Staff Engineer is often about balancing high-level strategy with technical execution, while influencing teams and projects in a sustainable, long-term way. + ## Not a faster Senior Engineer * A Staff engineer is more than just a faster Senior. -- cgit v1.2.3 From 970e9f5bd93f6b004e44628ec67e96e9a6aea6fd Mon Sep 17 00:00:00 2001 From: Paul Buetow Date: Fri, 1 Nov 2024 09:33:42 +0200 Subject: Update content for md --- gemfeed/2024-10-24-staff-engineer-book-notes.md | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) (limited to 'gemfeed') diff --git a/gemfeed/2024-10-24-staff-engineer-book-notes.md b/gemfeed/2024-10-24-staff-engineer-book-notes.md index 86f9abbe..4bc901b9 100644 --- a/gemfeed/2024-10-24-staff-engineer-book-notes.md +++ b/gemfeed/2024-10-24-staff-engineer-book-notes.md @@ -88,7 +88,7 @@ These additional points reflect more of the strategic, interpersonal, and leader ## Not a faster Senior Engineer * A Staff engineer is more than just a faster Senior. -* A staff engineer is not a senior engineer but a bit better. (But I want to be a senior engineer but a bit better). +* A staff engineer is not a senior engineer but a bit better. It's important to know what work or which role most energizes you. A Staff engineer is not a more senior engineer. A Staff engineer also fits into another archetype. -- cgit v1.2.3 From cf7c04c301c62c7c34ed618525c3169cc8946c96 Mon Sep 17 00:00:00 2001 From: Paul Buetow Date: Fri, 1 Nov 2024 11:56:12 +0200 Subject: Update content for md --- gemfeed/2024-09-07-projects-i-support.md | 6 ++++++ 1 file changed, 6 insertions(+) (limited to 'gemfeed') diff --git a/gemfeed/2024-09-07-projects-i-support.md b/gemfeed/2024-09-07-projects-i-support.md index 76282035..f43c25b4 100644 --- a/gemfeed/2024-09-07-projects-i-support.md +++ b/gemfeed/2024-09-07-projects-i-support.md @@ -27,6 +27,7 @@ This is the list of projects and initiatives I support/sponsor. * [⇢ Projects I financially support](#projects-i-financially-support) * [⇢ ⇢ Motivation](#motivation) +* [⇢ ⇢ OSNews](#osnews) * [⇢ ⇢ Cup o' Go Podcast](#cup-o--go-podcast) * [⇢ ⇢ Codeberg](#codeberg) * [⇢ ⇢ GrapheneOS](#grapheneos) @@ -41,6 +42,11 @@ Sponsoring free and open-source projects, even for personal use, is important to Albeit I am not putting a lot of money into my sponsoring efforts, it still helps the open-source maintainers because the more little sponsors there are, the higher the total sum. +## OSNews + +I am a silver Patreon member of OSNews. I have been following this site since my student years. It's always been a great source of independent IT news. +[https://osnews.com](https://osnews.com) + ## Cup o' Go Podcast I am a Patreon of the Cup o' Go Podcast. The podcast helps me stay updated with the Go community for around 15 minutes per week. I am not a full-time software developer, but my long-term ambition is to become better in Go every week by working on personal projects and tools for work. -- cgit v1.2.3 From 0645f5a419564704a352069494efa98b5f0511c4 Mon Sep 17 00:00:00 2001 From: Paul Buetow Date: Fri, 1 Nov 2024 12:00:35 +0200 Subject: Update content for md --- gemfeed/2024-09-07-projects-i-support.md | 3 ++- 1 file changed, 2 insertions(+), 1 deletion(-) (limited to 'gemfeed') diff --git a/gemfeed/2024-09-07-projects-i-support.md b/gemfeed/2024-09-07-projects-i-support.md index f43c25b4..1e339e7c 100644 --- a/gemfeed/2024-09-07-projects-i-support.md +++ b/gemfeed/2024-09-07-projects-i-support.md @@ -44,7 +44,8 @@ Albeit I am not putting a lot of money into my sponsoring efforts, it still help ## OSNews -I am a silver Patreon member of OSNews. I have been following this site since my student years. It's always been a great source of independent IT news. +I am a silver Patreon member of OSNews. I have been following this site since my student years. It's always been a great source of independent and slightly alternative IT news. + [https://osnews.com](https://osnews.com) ## Cup o' Go Podcast -- cgit v1.2.3 From 3a18c16bd3ff5715ed382b8e1c6187b34c646bc1 Mon Sep 17 00:00:00 2001 From: Paul Buetow Date: Thu, 7 Nov 2024 09:28:54 +0200 Subject: Update content for md --- gemfeed/2024-09-07-projects-i-support.md | 6 +++--- 1 file changed, 3 insertions(+), 3 deletions(-) (limited to 'gemfeed') diff --git a/gemfeed/2024-09-07-projects-i-support.md b/gemfeed/2024-09-07-projects-i-support.md index 1e339e7c..1ed5c2e4 100644 --- a/gemfeed/2024-09-07-projects-i-support.md +++ b/gemfeed/2024-09-07-projects-i-support.md @@ -27,7 +27,7 @@ This is the list of projects and initiatives I support/sponsor. * [⇢ Projects I financially support](#projects-i-financially-support) * [⇢ ⇢ Motivation](#motivation) -* [⇢ ⇢ OSNews](#osnews) +* [⇢ ⇢ OSnews](#osnews) * [⇢ ⇢ Cup o' Go Podcast](#cup-o--go-podcast) * [⇢ ⇢ Codeberg](#codeberg) * [⇢ ⇢ GrapheneOS](#grapheneos) @@ -42,9 +42,9 @@ Sponsoring free and open-source projects, even for personal use, is important to Albeit I am not putting a lot of money into my sponsoring efforts, it still helps the open-source maintainers because the more little sponsors there are, the higher the total sum. -## OSNews +## OSnews -I am a silver Patreon member of OSNews. I have been following this site since my student years. It's always been a great source of independent and slightly alternative IT news. +I am a silver Patreon member of OSnews. I have been following this site since my student years. It's always been a great source of independent and slightly alternative IT news. [https://osnews.com](https://osnews.com) -- cgit v1.2.3 From 7e0dbb7fa5168c5abd86dc3fc7d4d55bdfad2635 Mon Sep 17 00:00:00 2001 From: Paul Buetow Date: Sat, 16 Nov 2024 23:09:05 +0200 Subject: Update content for md --- ...6-04-09-jails-and-zfs-on-freebsd-with-puppet.md | 1 + ...2022-07-30-lets-encrypt-with-openbsd-and-rex.md | 1 + .../2024-01-13-one-reason-why-i-love-openbsd.md | 1 + ...24-04-01-KISS-high-availability-with-OpenBSD.md | 1 + ...024-11-17-f3s-kubernetes-with-freebsd-part-1.md | 157 +++++++++++++++++++++ .../f3s-kubernetes-with-freebsd-part-1/diagram.png | Bin 0 -> 479024 bytes .../f3s-kubernetes-with-freebsd-part-1/f3slogo.png | Bin 0 -> 317766 bytes gemfeed/index.md | 1 + 8 files changed, 162 insertions(+) create mode 100644 gemfeed/2024-11-17-f3s-kubernetes-with-freebsd-part-1.md create mode 100644 gemfeed/f3s-kubernetes-with-freebsd-part-1/diagram.png create mode 100644 gemfeed/f3s-kubernetes-with-freebsd-part-1/f3slogo.png (limited to 'gemfeed') diff --git a/gemfeed/2016-04-09-jails-and-zfs-on-freebsd-with-puppet.md b/gemfeed/2016-04-09-jails-and-zfs-on-freebsd-with-puppet.md index 60df5a1b..10fc37cc 100644 --- a/gemfeed/2016-04-09-jails-and-zfs-on-freebsd-with-puppet.md +++ b/gemfeed/2016-04-09-jails-and-zfs-on-freebsd-with-puppet.md @@ -402,5 +402,6 @@ Other *BSD related posts are: [2022-10-30 Installing DTail on OpenBSD](./2022-10-30-installing-dtail-on-openbsd.md) [2024-01-13 One reason why I love OpenBSD](./2024-01-13-one-reason-why-i-love-openbsd.md) [2024-04-01 KISS high-availability with OpenBSD](./2024-04-01-KISS-high-availability-with-OpenBSD.md) +[2024-11-17 f3s: Kubernetes with FreeBSD - Setting the stage - Part 1](./2024-11-17-f3s-kubernetes-with-freebsd-part-1.md) [Back to the main site](../) diff --git a/gemfeed/2022-07-30-lets-encrypt-with-openbsd-and-rex.md b/gemfeed/2022-07-30-lets-encrypt-with-openbsd-and-rex.md index 35870c2c..c870ccab 100644 --- a/gemfeed/2022-07-30-lets-encrypt-with-openbsd-and-rex.md +++ b/gemfeed/2022-07-30-lets-encrypt-with-openbsd-and-rex.md @@ -681,5 +681,6 @@ Other *BSD related posts are: [2022-10-30 Installing DTail on OpenBSD](./2022-10-30-installing-dtail-on-openbsd.md) [2024-01-13 One reason why I love OpenBSD](./2024-01-13-one-reason-why-i-love-openbsd.md) [2024-04-01 KISS high-availability with OpenBSD](./2024-04-01-KISS-high-availability-with-OpenBSD.md) +[2024-11-17 f3s: Kubernetes with FreeBSD - Setting the stage - Part 1](./2024-11-17-f3s-kubernetes-with-freebsd-part-1.md) [Back to the main site](../) diff --git a/gemfeed/2024-01-13-one-reason-why-i-love-openbsd.md b/gemfeed/2024-01-13-one-reason-why-i-love-openbsd.md index f598189b..91f3b2cd 100644 --- a/gemfeed/2024-01-13-one-reason-why-i-love-openbsd.md +++ b/gemfeed/2024-01-13-one-reason-why-i-love-openbsd.md @@ -56,5 +56,6 @@ Other *BSD related posts are: [2022-10-30 Installing DTail on OpenBSD](./2022-10-30-installing-dtail-on-openbsd.md) [2024-01-13 One reason why I love OpenBSD (You are currently reading this)](./2024-01-13-one-reason-why-i-love-openbsd.md) [2024-04-01 KISS high-availability with OpenBSD](./2024-04-01-KISS-high-availability-with-OpenBSD.md) +[2024-11-17 f3s: Kubernetes with FreeBSD - Setting the stage - Part 1](./2024-11-17-f3s-kubernetes-with-freebsd-part-1.md) [Back to the main site](../) diff --git a/gemfeed/2024-04-01-KISS-high-availability-with-OpenBSD.md b/gemfeed/2024-04-01-KISS-high-availability-with-OpenBSD.md index 84875f62..881d66d1 100644 --- a/gemfeed/2024-04-01-KISS-high-availability-with-OpenBSD.md +++ b/gemfeed/2024-04-01-KISS-high-availability-with-OpenBSD.md @@ -307,5 +307,6 @@ Other *BSD and KISS related posts are: [2023-10-29 KISS static web photo albums with `photoalbum.sh`](./2023-10-29-kiss-static-web-photo-albums-with-photoalbum.sh.md) [2024-01-13 One reason why I love OpenBSD](./2024-01-13-one-reason-why-i-love-openbsd.md) [2024-04-01 KISS high-availability with OpenBSD (You are currently reading this)](./2024-04-01-KISS-high-availability-with-OpenBSD.md) +[2024-11-17 f3s: Kubernetes with FreeBSD - Setting the stage - Part 1](./2024-11-17-f3s-kubernetes-with-freebsd-part-1.md) [Back to the main site](../) diff --git a/gemfeed/2024-11-17-f3s-kubernetes-with-freebsd-part-1.md b/gemfeed/2024-11-17-f3s-kubernetes-with-freebsd-part-1.md new file mode 100644 index 00000000..6aae0ab2 --- /dev/null +++ b/gemfeed/2024-11-17-f3s-kubernetes-with-freebsd-part-1.md @@ -0,0 +1,157 @@ +# f3s: Kubernetes with FreeBSD - Setting the stage - Part 1 + +> Published at 2024-11-16T23:08:10+02:00 + +This is the first blog post about my f3s series for my self-hosting demands in my home lab. f3s? The "f" stands for FreeBSD, and the "3s" stands for k3s, the Kubernetes distribution I will use on FreeBSD-based physical machines. + +I will post a new entry every month or so (there are too many other side projects for more frequent updates—I bet you can understand). + +[2024-11-17 f3s: Kubernetes with FreeBSD - Setting the stage - Part 1 (You are currently reading this)](./2024-11-17-f3s-kubernetes-with-freebsd-part-1.md) + +[![f3s logo](./f3s-kubernetes-with-freebsd-part-1/f3slogo.png "f3s logo")](./f3s-kubernetes-with-freebsd-part-1/f3slogo.png) + +Let's begin... + +## Table of Contents + +* [⇢ f3s: Kubernetes with FreeBSD - Setting the stage - Part 1](#f3s-kubernetes-with-freebsd---setting-the-stage---part-1) +* [⇢ ⇢ Why this setup?](#why-this-setup) +* [⇢ ⇢ The infrastructure](#the-infrastructure) +* [⇢ ⇢ ⇢ Physical FreeBSD nodes and Linux VMs](#physical-freebsd-nodes-and-linux-vms) +* [⇢ ⇢ ⇢ Kubernetes with k3s ](#kubernetes-with-k3s-) +* [⇢ ⇢ ⇢ HA volumes for k3s with HAST/ZFS and NFS](#ha-volumes-for-k3s-with-hastzfs-and-nfs) +* [⇢ ⇢ ⇢ OpenBSD/`relayd` to the rescue for external connectivity](#openbsdrelayd-to-the-rescue-for-external-connectivity) +* [⇢ ⇢ Data integrity](#data-integrity) +* [⇢ ⇢ ⇢ Periodic backups](#periodic-backups) +* [⇢ ⇢ ⇢ Power protection](#power-protection) +* [⇢ ⇢ Monitoring: Keeping an Eye on Everything](#monitoring-keeping-an-eye-on-everything) +* [⇢ ⇢ ⇢ Prometheus and Grafana](#prometheus-and-grafana) +* [⇢ ⇢ ⇢ Gogios: My Custom Alerting System](#gogios-my-custom-alerting-system) +* [⇢ ⇢ What's after this all?](#what-s-after-this-all) + +## Why this setup? + +Look at my previous setup, which was great to learn Terraform and AWS, but the setup is too expensive. Costs are under control there, but only because I am shutting down all containers after use (so they are offline ninety per cent of the time and still cost around 20 bucks monthly). With the new setup, I could run all containers 24/7 at home, which would still be cheaper for electricity consumption. + +[From `babylon5.buetow.org` to `.cloud`](https://foo.zone/gemfeed/2024-02-04-from-babylon5.buetow.org-to-.cloud.html) + +Migrating off all my containers from AWS ECS means I need a reliable and scalable environment to host my workloads. I wanted something: + +* To self-host all my open-source apps (Docker containers). +* Fully under my control (goodbye cloud vendor lock-in). +* Secure and redundant. +* Cost-efficient (after the initial hardware investment). +* Something I can poke around with and also pick up new skills. + +## The infrastructure + +This is still in progress, and I need to own the hardware. But in this first part of the blog series, I will outline what I intend to do. + +[![Diagram](./f3s-kubernetes-with-freebsd-part-1/diagram.png "Diagram")](./f3s-kubernetes-with-freebsd-part-1/diagram.png) + +### Physical FreeBSD nodes and Linux VMs + +The setup starts with three physical FreeBSD nodes. On these, I'm running Rocky Linux virtual machines with bhyve. Why Linux VMs in FreeBSD and not Linux directly? I want to leverage the great ZFS integration in FreeBSD (among other features), and I have been using FreeBSD for a while in my home lab. And with bhyve, there is a very performant hypervisor available which makes the Linux VMs de-facto run at native speed (another use case of mine would be maybe running a Windows bhyve VM on one of the nodes - but out of scope for this blog series). + +[https://www.freebsd.org/](https://www.freebsd.org/) +[https://wiki.freebsd.org/bhyve](https://wiki.freebsd.org/bhyve) + +I selected Rocky Linux because it comes with long-term support (I don't want to upgrade the VMs every 6 months). Rocky Linux 9 will reach its end of life in 2032, which is plenty of time! Of course, there will be minor upgrades, but nothing will significantly break my setup. + +[https://rockylinux.org/](https://rockylinux.org/) +[https://wiki.rockylinux.org/rocky/version/](https://wiki.rockylinux.org/rocky/version/) + +Furthermore, I am already using "RHEL-family" related distros at work and Fedora on my main personal laptop. Rocky Linux belongs to the same type of Linux distribution family, so I already feel at home here. I also used Rocky 9 before I switched to AWS ECS. Now, I am switching back in one sense or another ;-) + +### Kubernetes with k3s + +These Linux VMs form a three-node k3s Kubernetes cluster, where my containers will reside moving forward. The 3-node k3s cluster will be highly available (in `etcd` mode), and all apps will probably be deployed with Helm. Prometheus will also be running in k3s, collecting time-series metrics and handling monitoring. Additionally, a private Docker registry will be deployed into the k3s cluster, where I will store some of my self-created Docker images. k3s is the perfect distribution of Kubernetes for homelabbers due to its simplicity and the inclusion of the most useful features out of the box! + +[https://k3s.io/](https://k3s.io/) + +### HA volumes for k3s with HAST/ZFS and NFS + +Persistent storage for the k3s cluster will be handled by highly available (HA) NFS shares backed by ZFS on the FreeBSD hosts. + +On two of the three physical FreeBSD nodes, I will add a second SSD drive to each and dedicate it to a `pool` ZFS pool. With HAST (FreeBSD's solution for highly available storage), this `pool` will be replicated at the byte level to a standby node. + +A virtual IP (VIP) will point to the master node. When the master node goes down, the VIP will failover to the standby node, where the ZFS pool will be mounted. An NFS server will listen to both nodes. k3s will use the VIP to access the NFS shares. + +[https://wiki.freebsd.org/HighlyAvailableStorage](https://wiki.freebsd.org/HighlyAvailableStorage) + +### OpenBSD/`relayd` to the rescue for external connectivity + +All apps should be reachable through the internet (e.g., from my phone or computer when travelling). For external connectivity and TLS management, I've got two OpenBSD VMs (one hosted by OpenBSD Amsterdam and another hosted by Hetzner) handling public-facing services like DNS, relaying traffic, and automating Let's Encrypt certificates. + +All of this (every Linux VM to every OpenBSD box) will be connected via WireGuard tunnels, keeping everything private and secure. There will be 6 WireGuard tunnels (3 k3s nodes times two OpenBSD VMs). + +[https://en.wikipedia.org/wiki/WireGuard](https://en.wikipedia.org/wiki/WireGuard) + +So, when I want to access a service running in k3s, I will hit an external DNS endpoint (with the authoritative DNS servers being the OpenBSD boxes). The DNS will resolve to the master OpenBSD VM (see my KISS highly-available with OpenBSD blog post), and from there, the `relayd` process (with a Let's Encrypt certificate—see my Let's Encrypt with OpenBSD and Rex blog post) will accept the TCP connection and forward it through the WireGuard tunnel to a reachable node port of one of the k3s nodes, thus serving the traffic. + +[KISS high-availability with OpenBSD](https://foo.zone/gemfeed/2024-04-01-KISS-high-availability-with-OpenBSD.html) +[Le's Encrypt with OpenBSD and Rex](https://foo.zone/gemfeed/2022-07-30-lets-encrypt-with-openbsd-and-rex.html) + +The OpenBSD setup described here already exists and is ready to use. The only thing that does not yet exist is the configuration of `relayd` to forward requests to k3s through the WireGuard tunnel(s). + +## Data integrity + +### Periodic backups + +Let's face it, backups are non-negotiable. + +On the HAST master node, incremental and encrypted ZFS snapshots are created daily and automatically backed up to AWS S3 Glacier Deep Archive via CRON. I have a bunch of scripts already available, which I currently use for a similar purpose on my FreeBSD Home NAS server (an old ThinkPad T440 with an external USB drive enclosure, which I will eventually retire when the HAST setup is ready). I will copy them and slightly modify them to fit the purpose. + +[https://www.freshports.org/sysutils/zfstools](https://www.freshports.org/sysutils/zfstools) + +The backup scripts also perform some zpool scrubbing now and then. A scrub once in a while keeps the trouble away. + +### Power protection + +Power outages are regularly in my area, so a UPS keeps the infrastructure running during short outages and protects the hardware. I'm still trying to decide which hardware to get, and I still need one, as my previous NAS is simply an older laptop that already has a battery for power outages. However, there are plenty of options to choose from. My main criterion is that the UPS should be silent, as the whole setup will be installed in an upper shelf unit in my daughter's room. ;-) + +## Monitoring: Keeping an Eye on Everything + +Robust monitoring is vital to any infrastructure, especially one as distributed as mine. I've thought about a setup that ensures I'll always be aware of what's happening in my environment. + +### Prometheus and Grafana + +Inside the k3s cluster, Prometheus will be deployed to handle metrics collection. It will be configured to scrape data from my Kubernetes workloads, nodes, and any services I monitor. Prometheus also integrates with Alertmanager to generate alerts based on predefined thresholds or conditions. + +[https://prometheus.io](https://prometheus.io) + +For visualization, Grafana will be deployed alongside Prometheus. Grafana lets me build dynamic, customizable dashboards that provide a real-time view of everything from resource utilization to application performance. Whether it's keeping track of CPU load, memory usage, or the health of Kubernetes pods, Grafana has it covered. This will also make troubleshooting easier, as I can quickly pinpoint where issues are arising. + +[https://grafana.com](https://grafana.com) + +### Gogios: My Custom Alerting System + +Alerts generated by Prometheus are forwarded to Alertmanager, which I will configure to work with Gogios, a lightweight monitoring and alerting system I wrote myself. Gogios runs on one of my OpenBSD VMs. At regular intervals, Gogios scrapes the alerts generated in the k3s cluster and notifies me via Email. + +[KISS server monitoring with Gogios](https://foo.zone/gemfeed/2023-06-01-kiss-server-monitoring-with-gogios.html) + +Ironically, I implemented Gogios to avoid using more complex alerting systems like Prometheus, but here we go—it integrates well now. + +## What's after this all? + +This setup is just the beginning. Some ideas I'm thinking about for the future: + +* Adding more FreeBSD nodes (in different physical locations, maybe at my wider family's places?) for better redundancy. (HA storage then might be trickier) +* Deploying more Docker apps (data-intensive ones, like a picture gallery, my entire audiobook catalogue, or even a music server) to k3s. + +For now, though, I'm focused on completing the migration from AWS ECS and getting all my Docker containers running smoothly in k3s. + +What's your take on self-hosting? Are you planning to move away from managed cloud services? Stay tuned for the second part of this series, where I will likely write about the hardware and the OS setups. + +Other *BSD-related posts: + +[2016-04-09 Jails and ZFS with Puppet on FreeBSD](./2016-04-09-jails-and-zfs-on-freebsd-with-puppet.md) +[2022-07-30 Let's Encrypt with OpenBSD and Rex](./2022-07-30-lets-encrypt-with-openbsd-and-rex.md) +[2022-10-30 Installing DTail on OpenBSD](./2022-10-30-installing-dtail-on-openbsd.md) +[2024-01-13 One reason why I love OpenBSD](./2024-01-13-one-reason-why-i-love-openbsd.md) +[2024-04-01 KISS high-availability with OpenBSD](./2024-04-01-KISS-high-availability-with-OpenBSD.md) +[2024-11-17 f3s: Kubernetes with FreeBSD - Setting the stage - Part 1 (You are currently reading this)](./2024-11-17-f3s-kubernetes-with-freebsd-part-1.md) + +E-Mail your comments to `paul@nospam.buetow.org` :-) + +[Back to the main site](../) diff --git a/gemfeed/f3s-kubernetes-with-freebsd-part-1/diagram.png b/gemfeed/f3s-kubernetes-with-freebsd-part-1/diagram.png new file mode 100644 index 00000000..fa6b655a Binary files /dev/null and b/gemfeed/f3s-kubernetes-with-freebsd-part-1/diagram.png differ diff --git a/gemfeed/f3s-kubernetes-with-freebsd-part-1/f3slogo.png b/gemfeed/f3s-kubernetes-with-freebsd-part-1/f3slogo.png new file mode 100644 index 00000000..c9eb8945 Binary files /dev/null and b/gemfeed/f3s-kubernetes-with-freebsd-part-1/f3slogo.png differ diff --git a/gemfeed/index.md b/gemfeed/index.md index a88036bf..1ce39023 100644 --- a/gemfeed/index.md +++ b/gemfeed/index.md @@ -2,6 +2,7 @@ ## To be in the .zone! +[2024-11-17 - f3s: Kubernetes with FreeBSD - Setting the stage - Part 1](./2024-11-17-f3s-kubernetes-with-freebsd-part-1.md) [2024-10-24 - 'Staff Engineer' book notes](./2024-10-24-staff-engineer-book-notes.md) [2024-10-02 - Gemtexter 3.0.0 - Let's Gemtext again⁴](./2024-10-02-gemtexter-3.0.0-lets-gemtext-again-4.md) [2024-09-07 - Site Reliability Engineering - Part 4: Onboarding for On-Call Engineers](./2024-09-07-site-reliability-engineering-part-4.md) -- cgit v1.2.3 From 865c4640d7d134e26f0bf35ecb3d55d712542ecf Mon Sep 17 00:00:00 2001 From: Paul Buetow Date: Sat, 16 Nov 2024 23:21:10 +0200 Subject: Update content for md --- gemfeed/2024-11-17-f3s-kubernetes-with-freebsd-part-1.md | 4 +++- 1 file changed, 3 insertions(+), 1 deletion(-) (limited to 'gemfeed') diff --git a/gemfeed/2024-11-17-f3s-kubernetes-with-freebsd-part-1.md b/gemfeed/2024-11-17-f3s-kubernetes-with-freebsd-part-1.md index 6aae0ab2..7dd002a9 100644 --- a/gemfeed/2024-11-17-f3s-kubernetes-with-freebsd-part-1.md +++ b/gemfeed/2024-11-17-f3s-kubernetes-with-freebsd-part-1.md @@ -1,6 +1,6 @@ # f3s: Kubernetes with FreeBSD - Setting the stage - Part 1 -> Published at 2024-11-16T23:08:10+02:00 +> Published at 2024-11-16T23:20:14+02:00 This is the first blog post about my f3s series for my self-hosting demands in my home lab. f3s? The "f" stands for FreeBSD, and the "3s" stands for k3s, the Kubernetes distribution I will use on FreeBSD-based physical machines. @@ -79,6 +79,8 @@ A virtual IP (VIP) will point to the master node. When the master node goes down [https://wiki.freebsd.org/HighlyAvailableStorage](https://wiki.freebsd.org/HighlyAvailableStorage) +You can think of DRBD being the Linux equivalent to FreeBSD's HAST. + ### OpenBSD/`relayd` to the rescue for external connectivity All apps should be reachable through the internet (e.g., from my phone or computer when travelling). For external connectivity and TLS management, I've got two OpenBSD VMs (one hosted by OpenBSD Amsterdam and another hosted by Hetzner) handling public-facing services like DNS, relaying traffic, and automating Let's Encrypt certificates. -- cgit v1.2.3 From 810ded7d4932ef33cc87ebcce1c3a3e54fa76a43 Mon Sep 17 00:00:00 2001 From: Paul Buetow Date: Sat, 16 Nov 2024 23:25:53 +0200 Subject: Update content for md --- gemfeed/2024-11-17-f3s-kubernetes-with-freebsd-part-1.md | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) (limited to 'gemfeed') diff --git a/gemfeed/2024-11-17-f3s-kubernetes-with-freebsd-part-1.md b/gemfeed/2024-11-17-f3s-kubernetes-with-freebsd-part-1.md index 7dd002a9..022e61ac 100644 --- a/gemfeed/2024-11-17-f3s-kubernetes-with-freebsd-part-1.md +++ b/gemfeed/2024-11-17-f3s-kubernetes-with-freebsd-part-1.md @@ -73,7 +73,7 @@ These Linux VMs form a three-node k3s Kubernetes cluster, where my containers wi Persistent storage for the k3s cluster will be handled by highly available (HA) NFS shares backed by ZFS on the FreeBSD hosts. -On two of the three physical FreeBSD nodes, I will add a second SSD drive to each and dedicate it to a `pool` ZFS pool. With HAST (FreeBSD's solution for highly available storage), this `pool` will be replicated at the byte level to a standby node. +On two of the three physical FreeBSD nodes, I will add a second SSD drive to each and dedicate it to a `zhast` ZFS pool. With HAST (FreeBSD's solution for highly available storage), this `pool` will be replicated at the byte level to a standby node. A virtual IP (VIP) will point to the master node. When the master node goes down, the VIP will failover to the standby node, where the ZFS pool will be mounted. An NFS server will listen to both nodes. k3s will use the VIP to access the NFS shares. -- cgit v1.2.3 From fea3ab554253637802a73efd27cc4c782bf4bf36 Mon Sep 17 00:00:00 2001 From: Paul Buetow Date: Sat, 16 Nov 2024 23:31:00 +0200 Subject: Update content for md --- gemfeed/2024-11-17-f3s-kubernetes-with-freebsd-part-1.md | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) (limited to 'gemfeed') diff --git a/gemfeed/2024-11-17-f3s-kubernetes-with-freebsd-part-1.md b/gemfeed/2024-11-17-f3s-kubernetes-with-freebsd-part-1.md index 022e61ac..1020685c 100644 --- a/gemfeed/2024-11-17-f3s-kubernetes-with-freebsd-part-1.md +++ b/gemfeed/2024-11-17-f3s-kubernetes-with-freebsd-part-1.md @@ -31,7 +31,7 @@ Let's begin... ## Why this setup? -Look at my previous setup, which was great to learn Terraform and AWS, but the setup is too expensive. Costs are under control there, but only because I am shutting down all containers after use (so they are offline ninety per cent of the time and still cost around 20 bucks monthly). With the new setup, I could run all containers 24/7 at home, which would still be cheaper for electricity consumption. +My previous setup was great for learning Terraform and AWS, but it is too expensive. Costs are under control there, but only because I am shutting down all containers after use (so they are offline ninety percent of the time and still cost around $20 monthly). With the new setup, I could run all containers 24/7 at home, which would still be cheaper in terms of electricity consumption. I have a 50 MBit/s uplink (I could have more if I wanted, but it is plenty for my use case already). [From `babylon5.buetow.org` to `.cloud`](https://foo.zone/gemfeed/2024-02-04-from-babylon5.buetow.org-to-.cloud.html) -- cgit v1.2.3 From 59a7d0c5b74968976d633e737097556b6c38decb Mon Sep 17 00:00:00 2001 From: Paul Buetow Date: Sat, 16 Nov 2024 23:35:11 +0200 Subject: Update content for md --- gemfeed/2024-11-17-f3s-kubernetes-with-freebsd-part-1.md | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) (limited to 'gemfeed') diff --git a/gemfeed/2024-11-17-f3s-kubernetes-with-freebsd-part-1.md b/gemfeed/2024-11-17-f3s-kubernetes-with-freebsd-part-1.md index 1020685c..524b7c70 100644 --- a/gemfeed/2024-11-17-f3s-kubernetes-with-freebsd-part-1.md +++ b/gemfeed/2024-11-17-f3s-kubernetes-with-freebsd-part-1.md @@ -92,7 +92,7 @@ All of this (every Linux VM to every OpenBSD box) will be connected via WireGuar So, when I want to access a service running in k3s, I will hit an external DNS endpoint (with the authoritative DNS servers being the OpenBSD boxes). The DNS will resolve to the master OpenBSD VM (see my KISS highly-available with OpenBSD blog post), and from there, the `relayd` process (with a Let's Encrypt certificate—see my Let's Encrypt with OpenBSD and Rex blog post) will accept the TCP connection and forward it through the WireGuard tunnel to a reachable node port of one of the k3s nodes, thus serving the traffic. [KISS high-availability with OpenBSD](https://foo.zone/gemfeed/2024-04-01-KISS-high-availability-with-OpenBSD.html) -[Le's Encrypt with OpenBSD and Rex](https://foo.zone/gemfeed/2022-07-30-lets-encrypt-with-openbsd-and-rex.html) +[Let's Encrypt with OpenBSD and Rex](https://foo.zone/gemfeed/2022-07-30-lets-encrypt-with-openbsd-and-rex.html) The OpenBSD setup described here already exists and is ready to use. The only thing that does not yet exist is the configuration of `relayd` to forward requests to k3s through the WireGuard tunnel(s). -- cgit v1.2.3 From 1b8de26005feb21678ca5eb4cd9a6648fbd70575 Mon Sep 17 00:00:00 2001 From: Paul Buetow Date: Sat, 16 Nov 2024 23:46:35 +0200 Subject: Update content for md --- ...024-11-17-f3s-kubernetes-with-freebsd-part-1.md | 10 +++--- ...T-f3s-kubernetes-with-freebsd-hardware-setup.md | 39 ++++++++++++++++++++++ 2 files changed, 44 insertions(+), 5 deletions(-) create mode 100644 gemfeed/DRAFT-f3s-kubernetes-with-freebsd-hardware-setup.md (limited to 'gemfeed') diff --git a/gemfeed/2024-11-17-f3s-kubernetes-with-freebsd-part-1.md b/gemfeed/2024-11-17-f3s-kubernetes-with-freebsd-part-1.md index 524b7c70..0f59d815 100644 --- a/gemfeed/2024-11-17-f3s-kubernetes-with-freebsd-part-1.md +++ b/gemfeed/2024-11-17-f3s-kubernetes-with-freebsd-part-1.md @@ -24,9 +24,9 @@ Let's begin... * [⇢ ⇢ Data integrity](#data-integrity) * [⇢ ⇢ ⇢ Periodic backups](#periodic-backups) * [⇢ ⇢ ⇢ Power protection](#power-protection) -* [⇢ ⇢ Monitoring: Keeping an Eye on Everything](#monitoring-keeping-an-eye-on-everything) +* [⇢ ⇢ Monitoring: Keeping an eye on everything](#monitoring-keeping-an-eye-on-everything) * [⇢ ⇢ ⇢ Prometheus and Grafana](#prometheus-and-grafana) -* [⇢ ⇢ ⇢ Gogios: My Custom Alerting System](#gogios-my-custom-alerting-system) +* [⇢ ⇢ ⇢ Gogios: My custom alerting system](#gogios-my-custom-alerting-system) * [⇢ ⇢ What's after this all?](#what-s-after-this-all) ## Why this setup? @@ -112,7 +112,7 @@ The backup scripts also perform some zpool scrubbing now and then. A scrub once Power outages are regularly in my area, so a UPS keeps the infrastructure running during short outages and protects the hardware. I'm still trying to decide which hardware to get, and I still need one, as my previous NAS is simply an older laptop that already has a battery for power outages. However, there are plenty of options to choose from. My main criterion is that the UPS should be silent, as the whole setup will be installed in an upper shelf unit in my daughter's room. ;-) -## Monitoring: Keeping an Eye on Everything +## Monitoring: Keeping an eye on everything Robust monitoring is vital to any infrastructure, especially one as distributed as mine. I've thought about a setup that ensures I'll always be aware of what's happening in my environment. @@ -126,7 +126,7 @@ For visualization, Grafana will be deployed alongside Prometheus. Grafana lets m [https://grafana.com](https://grafana.com) -### Gogios: My Custom Alerting System +### Gogios: My custom alerting system Alerts generated by Prometheus are forwarded to Alertmanager, which I will configure to work with Gogios, a lightweight monitoring and alerting system I wrote myself. Gogios runs on one of my OpenBSD VMs. At regular intervals, Gogios scrapes the alerts generated in the k3s cluster and notifies me via Email. @@ -136,7 +136,7 @@ Ironically, I implemented Gogios to avoid using more complex alerting systems li ## What's after this all? -This setup is just the beginning. Some ideas I'm thinking about for the future: +This setup may be just the beginning. Some ideas I'm thinking about for the future: * Adding more FreeBSD nodes (in different physical locations, maybe at my wider family's places?) for better redundancy. (HA storage then might be trickier) * Deploying more Docker apps (data-intensive ones, like a picture gallery, my entire audiobook catalogue, or even a music server) to k3s. diff --git a/gemfeed/DRAFT-f3s-kubernetes-with-freebsd-hardware-setup.md b/gemfeed/DRAFT-f3s-kubernetes-with-freebsd-hardware-setup.md new file mode 100644 index 00000000..c0db723b --- /dev/null +++ b/gemfeed/DRAFT-f3s-kubernetes-with-freebsd-hardware-setup.md @@ -0,0 +1,39 @@ +# f3s: Kubernetes with FreeBSD - Setting the stage - Part 1 + +> Published at 2024-11-16T23:20:14+02:00 + +This is the second blog post about my f3s series for my self-hosting demands in my home lab. f3s? The "f" stands for FreeBSD, and the "3s" stands for k3s, the Kubernetes distribution I will use on FreeBSD-based physical machines. + +I will post a new entry every month or so (there are too many other side projects for more frequent updates—I bet you can understand). + +[2024-11-17 f3s: Kubernetes with FreeBSD - Setting the stage - Part 1](./2024-11-17-f3s-kubernetes-with-freebsd-part-1.md) + +[![f3s logo](./f3s-kubernetes-with-freebsd-part-1/f3slogo.png "f3s logo")](./f3s-kubernetes-with-freebsd-part-1/f3slogo.png) + +Let's begin... + +## Table of Contents + +* [⇢ f3s: Kubernetes with FreeBSD - Setting the stage - Part 1](#f3s-kubernetes-with-freebsd---setting-the-stage---part-1) + +## + +Hardware + photos + basic unpacking +Base os insallation (FreeBSD) +* static IPs +* utimed +* bhyve setup +* minimal rocky linux installs, with staic IPs + +Other *BSD-related posts: + +[2016-04-09 Jails and ZFS with Puppet on FreeBSD](./2016-04-09-jails-and-zfs-on-freebsd-with-puppet.md) +[2022-07-30 Let's Encrypt with OpenBSD and Rex](./2022-07-30-lets-encrypt-with-openbsd-and-rex.md) +[2022-10-30 Installing DTail on OpenBSD](./2022-10-30-installing-dtail-on-openbsd.md) +[2024-01-13 One reason why I love OpenBSD](./2024-01-13-one-reason-why-i-love-openbsd.md) +[2024-04-01 KISS high-availability with OpenBSD](./2024-04-01-KISS-high-availability-with-OpenBSD.md) +[2024-11-17 f3s: Kubernetes with FreeBSD - Setting the stage - Part 1](./2024-11-17-f3s-kubernetes-with-freebsd-part-1.md) + +E-Mail your comments to `paul@nospam.buetow.org` :-) + +[Back to the main site](../) -- cgit v1.2.3 From aa74f001a967400ee02d58b29fc9fdb134d6c935 Mon Sep 17 00:00:00 2001 From: Paul Buetow Date: Sat, 16 Nov 2024 23:53:15 +0200 Subject: Update content for md --- gemfeed/2024-11-17-f3s-kubernetes-with-freebsd-part-1.md | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) (limited to 'gemfeed') diff --git a/gemfeed/2024-11-17-f3s-kubernetes-with-freebsd-part-1.md b/gemfeed/2024-11-17-f3s-kubernetes-with-freebsd-part-1.md index 0f59d815..8ae3a9b7 100644 --- a/gemfeed/2024-11-17-f3s-kubernetes-with-freebsd-part-1.md +++ b/gemfeed/2024-11-17-f3s-kubernetes-with-freebsd-part-1.md @@ -51,7 +51,7 @@ This is still in progress, and I need to own the hardware. But in this first par ### Physical FreeBSD nodes and Linux VMs -The setup starts with three physical FreeBSD nodes. On these, I'm running Rocky Linux virtual machines with bhyve. Why Linux VMs in FreeBSD and not Linux directly? I want to leverage the great ZFS integration in FreeBSD (among other features), and I have been using FreeBSD for a while in my home lab. And with bhyve, there is a very performant hypervisor available which makes the Linux VMs de-facto run at native speed (another use case of mine would be maybe running a Windows bhyve VM on one of the nodes - but out of scope for this blog series). +The setup starts with three physical FreeBSD nodes deployed into my home LAN. On these, I'm going to run Rocky Linux virtual machines with bhyve. Why Linux VMs in FreeBSD and not Linux directly? I want to leverage the great ZFS integration in FreeBSD (among other features), and I have been using FreeBSD for a while in my home lab. And with bhyve, there is a very performant hypervisor available which makes the Linux VMs de-facto run at native speed (another use case of mine would be maybe running a Windows bhyve VM on one of the nodes - but out of scope for this blog series). [https://www.freebsd.org/](https://www.freebsd.org/) [https://wiki.freebsd.org/bhyve](https://wiki.freebsd.org/bhyve) -- cgit v1.2.3 From 69b62c38864ea0e5a205af1b641d60db8db765ae Mon Sep 17 00:00:00 2001 From: Paul Buetow Date: Sun, 17 Nov 2024 09:32:38 +0200 Subject: Update content for md --- ...024-11-17-f3s-kubernetes-with-freebsd-part-1.md | 2 +- .../f3s-kubernetes-with-freebsd-part-1/f3slogo.png | Bin 317766 -> 185496 bytes 2 files changed, 1 insertion(+), 1 deletion(-) (limited to 'gemfeed') diff --git a/gemfeed/2024-11-17-f3s-kubernetes-with-freebsd-part-1.md b/gemfeed/2024-11-17-f3s-kubernetes-with-freebsd-part-1.md index 8ae3a9b7..6a850b52 100644 --- a/gemfeed/2024-11-17-f3s-kubernetes-with-freebsd-part-1.md +++ b/gemfeed/2024-11-17-f3s-kubernetes-with-freebsd-part-1.md @@ -138,7 +138,7 @@ Ironically, I implemented Gogios to avoid using more complex alerting systems li This setup may be just the beginning. Some ideas I'm thinking about for the future: -* Adding more FreeBSD nodes (in different physical locations, maybe at my wider family's places?) for better redundancy. (HA storage then might be trickier) +* Adding more FreeBSD nodes (in different physical locations, maybe at my wider family's places? WireGuard would make it possible!) for better redundancy. (HA storage then might be trickier) * Deploying more Docker apps (data-intensive ones, like a picture gallery, my entire audiobook catalogue, or even a music server) to k3s. For now, though, I'm focused on completing the migration from AWS ECS and getting all my Docker containers running smoothly in k3s. diff --git a/gemfeed/f3s-kubernetes-with-freebsd-part-1/f3slogo.png b/gemfeed/f3s-kubernetes-with-freebsd-part-1/f3slogo.png index c9eb8945..cc45b40e 100644 Binary files a/gemfeed/f3s-kubernetes-with-freebsd-part-1/f3slogo.png and b/gemfeed/f3s-kubernetes-with-freebsd-part-1/f3slogo.png differ -- cgit v1.2.3 From 2ce3cbf2db018108f75faadef4967692c5a3b965 Mon Sep 17 00:00:00 2001 From: Paul Buetow Date: Sun, 17 Nov 2024 09:35:23 +0200 Subject: Update content for md --- gemfeed/2024-11-17-f3s-kubernetes-with-freebsd-part-1.md | 2 ++ 1 file changed, 2 insertions(+) (limited to 'gemfeed') diff --git a/gemfeed/2024-11-17-f3s-kubernetes-with-freebsd-part-1.md b/gemfeed/2024-11-17-f3s-kubernetes-with-freebsd-part-1.md index 6a850b52..00257786 100644 --- a/gemfeed/2024-11-17-f3s-kubernetes-with-freebsd-part-1.md +++ b/gemfeed/2024-11-17-f3s-kubernetes-with-freebsd-part-1.md @@ -10,6 +10,8 @@ I will post a new entry every month or so (there are too many other side project [![f3s logo](./f3s-kubernetes-with-freebsd-part-1/f3slogo.png "f3s logo")](./f3s-kubernetes-with-freebsd-part-1/f3slogo.png) +> Logo was generated by ChatGPT. + Let's begin... ## Table of Contents -- cgit v1.2.3 From df122c0a5baa1ee96859aea05035e56ef06d8641 Mon Sep 17 00:00:00 2001 From: Paul Buetow Date: Sun, 17 Nov 2024 10:14:54 +0200 Subject: Update content for md --- gemfeed/2024-11-17-f3s-kubernetes-with-freebsd-part-1.md | 2 ++ 1 file changed, 2 insertions(+) (limited to 'gemfeed') diff --git a/gemfeed/2024-11-17-f3s-kubernetes-with-freebsd-part-1.md b/gemfeed/2024-11-17-f3s-kubernetes-with-freebsd-part-1.md index 00257786..581e730c 100644 --- a/gemfeed/2024-11-17-f3s-kubernetes-with-freebsd-part-1.md +++ b/gemfeed/2024-11-17-f3s-kubernetes-with-freebsd-part-1.md @@ -106,6 +106,8 @@ Let's face it, backups are non-negotiable. On the HAST master node, incremental and encrypted ZFS snapshots are created daily and automatically backed up to AWS S3 Glacier Deep Archive via CRON. I have a bunch of scripts already available, which I currently use for a similar purpose on my FreeBSD Home NAS server (an old ThinkPad T440 with an external USB drive enclosure, which I will eventually retire when the HAST setup is ready). I will copy them and slightly modify them to fit the purpose. +There's also `zfstools` in the ports, which helps set up an automatic snapshot regime: + [https://www.freshports.org/sysutils/zfstools](https://www.freshports.org/sysutils/zfstools) The backup scripts also perform some zpool scrubbing now and then. A scrub once in a while keeps the trouble away. -- cgit v1.2.3 From 27605ecdb85b7c1920d373900ed9ee4900c02d76 Mon Sep 17 00:00:00 2001 From: Paul Buetow Date: Sun, 17 Nov 2024 18:03:28 +0200 Subject: Update content for md --- gemfeed/2024-11-17-f3s-kubernetes-with-freebsd-part-1.md | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) (limited to 'gemfeed') diff --git a/gemfeed/2024-11-17-f3s-kubernetes-with-freebsd-part-1.md b/gemfeed/2024-11-17-f3s-kubernetes-with-freebsd-part-1.md index 581e730c..5c7df09b 100644 --- a/gemfeed/2024-11-17-f3s-kubernetes-with-freebsd-part-1.md +++ b/gemfeed/2024-11-17-f3s-kubernetes-with-freebsd-part-1.md @@ -79,7 +79,7 @@ On two of the three physical FreeBSD nodes, I will add a second SSD drive to eac A virtual IP (VIP) will point to the master node. When the master node goes down, the VIP will failover to the standby node, where the ZFS pool will be mounted. An NFS server will listen to both nodes. k3s will use the VIP to access the NFS shares. -[https://wiki.freebsd.org/HighlyAvailableStorage](https://wiki.freebsd.org/HighlyAvailableStorage) +[FreeBSD Wiki: Highly Available Storage](https://wiki.freebsd.org/HighlyAvailableStorage) You can think of DRBD being the Linux equivalent to FreeBSD's HAST. -- cgit v1.2.3 From 620a192ae35e939bfc8fbc7cf27dfab0e082ff41 Mon Sep 17 00:00:00 2001 From: Paul Buetow Date: Sun, 1 Dec 2024 12:50:44 +0200 Subject: Update content for md --- gemfeed/2024-11-17-f3s-kubernetes-with-freebsd-part-1.md | 4 ++-- gemfeed/index.md | 2 +- 2 files changed, 3 insertions(+), 3 deletions(-) (limited to 'gemfeed') diff --git a/gemfeed/2024-11-17-f3s-kubernetes-with-freebsd-part-1.md b/gemfeed/2024-11-17-f3s-kubernetes-with-freebsd-part-1.md index 5c7df09b..af254e43 100644 --- a/gemfeed/2024-11-17-f3s-kubernetes-with-freebsd-part-1.md +++ b/gemfeed/2024-11-17-f3s-kubernetes-with-freebsd-part-1.md @@ -1,4 +1,4 @@ -# f3s: Kubernetes with FreeBSD - Setting the stage - Part 1 +# f3s: Kubernetes with FreeBSD - Part 1: Setting the stage > Published at 2024-11-16T23:20:14+02:00 @@ -16,7 +16,7 @@ Let's begin... ## Table of Contents -* [⇢ f3s: Kubernetes with FreeBSD - Setting the stage - Part 1](#f3s-kubernetes-with-freebsd---setting-the-stage---part-1) +* [⇢ f3s: Kubernetes with FreeBSD - Part 1: Setting the stage](#f3s-kubernetes-with-freebsd---part-1-setting-the-stage) * [⇢ ⇢ Why this setup?](#why-this-setup) * [⇢ ⇢ The infrastructure](#the-infrastructure) * [⇢ ⇢ ⇢ Physical FreeBSD nodes and Linux VMs](#physical-freebsd-nodes-and-linux-vms) diff --git a/gemfeed/index.md b/gemfeed/index.md index 1ce39023..37c8aefa 100644 --- a/gemfeed/index.md +++ b/gemfeed/index.md @@ -2,7 +2,7 @@ ## To be in the .zone! -[2024-11-17 - f3s: Kubernetes with FreeBSD - Setting the stage - Part 1](./2024-11-17-f3s-kubernetes-with-freebsd-part-1.md) +[2024-11-17 - f3s: Kubernetes with FreeBSD - Part 1: Setting the stage](./2024-11-17-f3s-kubernetes-with-freebsd-part-1.md) [2024-10-24 - 'Staff Engineer' book notes](./2024-10-24-staff-engineer-book-notes.md) [2024-10-02 - Gemtexter 3.0.0 - Let's Gemtext again⁴](./2024-10-02-gemtexter-3.0.0-lets-gemtext-again-4.md) [2024-09-07 - Site Reliability Engineering - Part 4: Onboarding for On-Call Engineers](./2024-09-07-site-reliability-engineering-part-4.md) -- cgit v1.2.3 From 2b5066694595fa85c382f923372d2c4daeeb36f6 Mon Sep 17 00:00:00 2001 From: Paul Buetow Date: Sun, 1 Dec 2024 12:52:59 +0200 Subject: Update content for md --- gemfeed/2016-04-09-jails-and-zfs-on-freebsd-with-puppet.md | 2 +- gemfeed/2022-07-30-lets-encrypt-with-openbsd-and-rex.md | 2 +- gemfeed/2024-01-13-one-reason-why-i-love-openbsd.md | 2 +- gemfeed/2024-04-01-KISS-high-availability-with-OpenBSD.md | 2 +- gemfeed/2024-11-17-f3s-kubernetes-with-freebsd-part-1.md | 4 ++-- gemfeed/DRAFT-f3s-kubernetes-with-freebsd-hardware-setup.md | 4 ++-- 6 files changed, 8 insertions(+), 8 deletions(-) (limited to 'gemfeed') diff --git a/gemfeed/2016-04-09-jails-and-zfs-on-freebsd-with-puppet.md b/gemfeed/2016-04-09-jails-and-zfs-on-freebsd-with-puppet.md index 10fc37cc..b2dd4ed7 100644 --- a/gemfeed/2016-04-09-jails-and-zfs-on-freebsd-with-puppet.md +++ b/gemfeed/2016-04-09-jails-and-zfs-on-freebsd-with-puppet.md @@ -402,6 +402,6 @@ Other *BSD related posts are: [2022-10-30 Installing DTail on OpenBSD](./2022-10-30-installing-dtail-on-openbsd.md) [2024-01-13 One reason why I love OpenBSD](./2024-01-13-one-reason-why-i-love-openbsd.md) [2024-04-01 KISS high-availability with OpenBSD](./2024-04-01-KISS-high-availability-with-OpenBSD.md) -[2024-11-17 f3s: Kubernetes with FreeBSD - Setting the stage - Part 1](./2024-11-17-f3s-kubernetes-with-freebsd-part-1.md) +[2024-11-17 f3s: Kubernetes with FreeBSD - Part 1: Setting the stage](./2024-11-17-f3s-kubernetes-with-freebsd-part-1.md) [Back to the main site](../) diff --git a/gemfeed/2022-07-30-lets-encrypt-with-openbsd-and-rex.md b/gemfeed/2022-07-30-lets-encrypt-with-openbsd-and-rex.md index c870ccab..f8ce7cae 100644 --- a/gemfeed/2022-07-30-lets-encrypt-with-openbsd-and-rex.md +++ b/gemfeed/2022-07-30-lets-encrypt-with-openbsd-and-rex.md @@ -681,6 +681,6 @@ Other *BSD related posts are: [2022-10-30 Installing DTail on OpenBSD](./2022-10-30-installing-dtail-on-openbsd.md) [2024-01-13 One reason why I love OpenBSD](./2024-01-13-one-reason-why-i-love-openbsd.md) [2024-04-01 KISS high-availability with OpenBSD](./2024-04-01-KISS-high-availability-with-OpenBSD.md) -[2024-11-17 f3s: Kubernetes with FreeBSD - Setting the stage - Part 1](./2024-11-17-f3s-kubernetes-with-freebsd-part-1.md) +[2024-11-17 f3s: Kubernetes with FreeBSD - Part 1: Setting the stage](./2024-11-17-f3s-kubernetes-with-freebsd-part-1.md) [Back to the main site](../) diff --git a/gemfeed/2024-01-13-one-reason-why-i-love-openbsd.md b/gemfeed/2024-01-13-one-reason-why-i-love-openbsd.md index 91f3b2cd..607c6b83 100644 --- a/gemfeed/2024-01-13-one-reason-why-i-love-openbsd.md +++ b/gemfeed/2024-01-13-one-reason-why-i-love-openbsd.md @@ -56,6 +56,6 @@ Other *BSD related posts are: [2022-10-30 Installing DTail on OpenBSD](./2022-10-30-installing-dtail-on-openbsd.md) [2024-01-13 One reason why I love OpenBSD (You are currently reading this)](./2024-01-13-one-reason-why-i-love-openbsd.md) [2024-04-01 KISS high-availability with OpenBSD](./2024-04-01-KISS-high-availability-with-OpenBSD.md) -[2024-11-17 f3s: Kubernetes with FreeBSD - Setting the stage - Part 1](./2024-11-17-f3s-kubernetes-with-freebsd-part-1.md) +[2024-11-17 f3s: Kubernetes with FreeBSD - Part 1: Setting the stage](./2024-11-17-f3s-kubernetes-with-freebsd-part-1.md) [Back to the main site](../) diff --git a/gemfeed/2024-04-01-KISS-high-availability-with-OpenBSD.md b/gemfeed/2024-04-01-KISS-high-availability-with-OpenBSD.md index 881d66d1..44495d5c 100644 --- a/gemfeed/2024-04-01-KISS-high-availability-with-OpenBSD.md +++ b/gemfeed/2024-04-01-KISS-high-availability-with-OpenBSD.md @@ -307,6 +307,6 @@ Other *BSD and KISS related posts are: [2023-10-29 KISS static web photo albums with `photoalbum.sh`](./2023-10-29-kiss-static-web-photo-albums-with-photoalbum.sh.md) [2024-01-13 One reason why I love OpenBSD](./2024-01-13-one-reason-why-i-love-openbsd.md) [2024-04-01 KISS high-availability with OpenBSD (You are currently reading this)](./2024-04-01-KISS-high-availability-with-OpenBSD.md) -[2024-11-17 f3s: Kubernetes with FreeBSD - Setting the stage - Part 1](./2024-11-17-f3s-kubernetes-with-freebsd-part-1.md) +[2024-11-17 f3s: Kubernetes with FreeBSD - Part 1: Setting the stage](./2024-11-17-f3s-kubernetes-with-freebsd-part-1.md) [Back to the main site](../) diff --git a/gemfeed/2024-11-17-f3s-kubernetes-with-freebsd-part-1.md b/gemfeed/2024-11-17-f3s-kubernetes-with-freebsd-part-1.md index af254e43..5f11fa22 100644 --- a/gemfeed/2024-11-17-f3s-kubernetes-with-freebsd-part-1.md +++ b/gemfeed/2024-11-17-f3s-kubernetes-with-freebsd-part-1.md @@ -6,7 +6,7 @@ This is the first blog post about my f3s series for my self-hosting demands in m I will post a new entry every month or so (there are too many other side projects for more frequent updates—I bet you can understand). -[2024-11-17 f3s: Kubernetes with FreeBSD - Setting the stage - Part 1 (You are currently reading this)](./2024-11-17-f3s-kubernetes-with-freebsd-part-1.md) +[2024-11-17 f3s: Kubernetes with FreeBSD - Part 1: Setting the stage (You are currently reading this)](./2024-11-17-f3s-kubernetes-with-freebsd-part-1.md) [![f3s logo](./f3s-kubernetes-with-freebsd-part-1/f3slogo.png "f3s logo")](./f3s-kubernetes-with-freebsd-part-1/f3slogo.png) @@ -156,7 +156,7 @@ Other *BSD-related posts: [2022-10-30 Installing DTail on OpenBSD](./2022-10-30-installing-dtail-on-openbsd.md) [2024-01-13 One reason why I love OpenBSD](./2024-01-13-one-reason-why-i-love-openbsd.md) [2024-04-01 KISS high-availability with OpenBSD](./2024-04-01-KISS-high-availability-with-OpenBSD.md) -[2024-11-17 f3s: Kubernetes with FreeBSD - Setting the stage - Part 1 (You are currently reading this)](./2024-11-17-f3s-kubernetes-with-freebsd-part-1.md) +[2024-11-17 f3s: Kubernetes with FreeBSD - Part 1: Setting the stage (You are currently reading this)](./2024-11-17-f3s-kubernetes-with-freebsd-part-1.md) E-Mail your comments to `paul@nospam.buetow.org` :-) diff --git a/gemfeed/DRAFT-f3s-kubernetes-with-freebsd-hardware-setup.md b/gemfeed/DRAFT-f3s-kubernetes-with-freebsd-hardware-setup.md index c0db723b..707c3598 100644 --- a/gemfeed/DRAFT-f3s-kubernetes-with-freebsd-hardware-setup.md +++ b/gemfeed/DRAFT-f3s-kubernetes-with-freebsd-hardware-setup.md @@ -6,7 +6,7 @@ This is the second blog post about my f3s series for my self-hosting demands in I will post a new entry every month or so (there are too many other side projects for more frequent updates—I bet you can understand). -[2024-11-17 f3s: Kubernetes with FreeBSD - Setting the stage - Part 1](./2024-11-17-f3s-kubernetes-with-freebsd-part-1.md) +[2024-11-17 f3s: Kubernetes with FreeBSD - Part 1: Setting the stage](./2024-11-17-f3s-kubernetes-with-freebsd-part-1.md) [![f3s logo](./f3s-kubernetes-with-freebsd-part-1/f3slogo.png "f3s logo")](./f3s-kubernetes-with-freebsd-part-1/f3slogo.png) @@ -32,7 +32,7 @@ Other *BSD-related posts: [2022-10-30 Installing DTail on OpenBSD](./2022-10-30-installing-dtail-on-openbsd.md) [2024-01-13 One reason why I love OpenBSD](./2024-01-13-one-reason-why-i-love-openbsd.md) [2024-04-01 KISS high-availability with OpenBSD](./2024-04-01-KISS-high-availability-with-OpenBSD.md) -[2024-11-17 f3s: Kubernetes with FreeBSD - Setting the stage - Part 1](./2024-11-17-f3s-kubernetes-with-freebsd-part-1.md) +[2024-11-17 f3s: Kubernetes with FreeBSD - Part 1: Setting the stage](./2024-11-17-f3s-kubernetes-with-freebsd-part-1.md) E-Mail your comments to `paul@nospam.buetow.org` :-) -- cgit v1.2.3 From ab927163804ebfcb5a86f2ce65d583dc60461148 Mon Sep 17 00:00:00 2001 From: Paul Buetow Date: Mon, 2 Dec 2024 23:46:50 +0200 Subject: Update content for md --- ...6-04-09-jails-and-zfs-on-freebsd-with-puppet.md | 1 + ...2022-07-30-lets-encrypt-with-openbsd-and-rex.md | 1 + .../2024-01-13-one-reason-why-i-love-openbsd.md | 1 + ...24-04-01-KISS-high-availability-with-OpenBSD.md | 1 + ...024-11-17-f3s-kubernetes-with-freebsd-part-1.md | 8 + ...024-12-03-f3s-kubernetes-with-freebsd-part-2.md | 289 +++++++++++++++++++++ ...T-f3s-kubernetes-with-freebsd-hardware-setup.md | 2 + .../3beelinks.jpg | Bin 0 -> 244333 bytes .../f3s-collage1.jpg | Bin 0 -> 76514 bytes .../f3s-collage2.jpg | Bin 0 -> 105206 bytes .../f3s-kubernetes-with-freebsd-part-2/switch.jpg | Bin 0 -> 73109 bytes .../f3s-kubernetes-with-freebsd-part-2/watt.jpg | Bin 0 -> 208816 bytes gemfeed/index.md | 1 + 13 files changed, 304 insertions(+) create mode 100644 gemfeed/2024-12-03-f3s-kubernetes-with-freebsd-part-2.md create mode 100644 gemfeed/f3s-kubernetes-with-freebsd-part-2/3beelinks.jpg create mode 100644 gemfeed/f3s-kubernetes-with-freebsd-part-2/f3s-collage1.jpg create mode 100644 gemfeed/f3s-kubernetes-with-freebsd-part-2/f3s-collage2.jpg create mode 100644 gemfeed/f3s-kubernetes-with-freebsd-part-2/switch.jpg create mode 100644 gemfeed/f3s-kubernetes-with-freebsd-part-2/watt.jpg (limited to 'gemfeed') diff --git a/gemfeed/2016-04-09-jails-and-zfs-on-freebsd-with-puppet.md b/gemfeed/2016-04-09-jails-and-zfs-on-freebsd-with-puppet.md index b2dd4ed7..80ee2f80 100644 --- a/gemfeed/2016-04-09-jails-and-zfs-on-freebsd-with-puppet.md +++ b/gemfeed/2016-04-09-jails-and-zfs-on-freebsd-with-puppet.md @@ -403,5 +403,6 @@ Other *BSD related posts are: [2024-01-13 One reason why I love OpenBSD](./2024-01-13-one-reason-why-i-love-openbsd.md) [2024-04-01 KISS high-availability with OpenBSD](./2024-04-01-KISS-high-availability-with-OpenBSD.md) [2024-11-17 f3s: Kubernetes with FreeBSD - Part 1: Setting the stage](./2024-11-17-f3s-kubernetes-with-freebsd-part-1.md) +[2024-12-03 f3s: Kubernetes with FreeBSD - Part 2: Hardware and base installation](./2024-12-03-f3s-kubernetes-with-freebsd-part-2.md) [Back to the main site](../) diff --git a/gemfeed/2022-07-30-lets-encrypt-with-openbsd-and-rex.md b/gemfeed/2022-07-30-lets-encrypt-with-openbsd-and-rex.md index f8ce7cae..6cd856e3 100644 --- a/gemfeed/2022-07-30-lets-encrypt-with-openbsd-and-rex.md +++ b/gemfeed/2022-07-30-lets-encrypt-with-openbsd-and-rex.md @@ -682,5 +682,6 @@ Other *BSD related posts are: [2024-01-13 One reason why I love OpenBSD](./2024-01-13-one-reason-why-i-love-openbsd.md) [2024-04-01 KISS high-availability with OpenBSD](./2024-04-01-KISS-high-availability-with-OpenBSD.md) [2024-11-17 f3s: Kubernetes with FreeBSD - Part 1: Setting the stage](./2024-11-17-f3s-kubernetes-with-freebsd-part-1.md) +[2024-12-03 f3s: Kubernetes with FreeBSD - Part 2: Hardware and base installation](./2024-12-03-f3s-kubernetes-with-freebsd-part-2.md) [Back to the main site](../) diff --git a/gemfeed/2024-01-13-one-reason-why-i-love-openbsd.md b/gemfeed/2024-01-13-one-reason-why-i-love-openbsd.md index 607c6b83..56dc6c7f 100644 --- a/gemfeed/2024-01-13-one-reason-why-i-love-openbsd.md +++ b/gemfeed/2024-01-13-one-reason-why-i-love-openbsd.md @@ -57,5 +57,6 @@ Other *BSD related posts are: [2024-01-13 One reason why I love OpenBSD (You are currently reading this)](./2024-01-13-one-reason-why-i-love-openbsd.md) [2024-04-01 KISS high-availability with OpenBSD](./2024-04-01-KISS-high-availability-with-OpenBSD.md) [2024-11-17 f3s: Kubernetes with FreeBSD - Part 1: Setting the stage](./2024-11-17-f3s-kubernetes-with-freebsd-part-1.md) +[2024-12-03 f3s: Kubernetes with FreeBSD - Part 2: Hardware and base installation](./2024-12-03-f3s-kubernetes-with-freebsd-part-2.md) [Back to the main site](../) diff --git a/gemfeed/2024-04-01-KISS-high-availability-with-OpenBSD.md b/gemfeed/2024-04-01-KISS-high-availability-with-OpenBSD.md index 44495d5c..50de8943 100644 --- a/gemfeed/2024-04-01-KISS-high-availability-with-OpenBSD.md +++ b/gemfeed/2024-04-01-KISS-high-availability-with-OpenBSD.md @@ -308,5 +308,6 @@ Other *BSD and KISS related posts are: [2024-01-13 One reason why I love OpenBSD](./2024-01-13-one-reason-why-i-love-openbsd.md) [2024-04-01 KISS high-availability with OpenBSD (You are currently reading this)](./2024-04-01-KISS-high-availability-with-OpenBSD.md) [2024-11-17 f3s: Kubernetes with FreeBSD - Part 1: Setting the stage](./2024-11-17-f3s-kubernetes-with-freebsd-part-1.md) +[2024-12-03 f3s: Kubernetes with FreeBSD - Part 2: Hardware and base installation](./2024-12-03-f3s-kubernetes-with-freebsd-part-2.md) [Back to the main site](../) diff --git a/gemfeed/2024-11-17-f3s-kubernetes-with-freebsd-part-1.md b/gemfeed/2024-11-17-f3s-kubernetes-with-freebsd-part-1.md index 5f11fa22..568813dd 100644 --- a/gemfeed/2024-11-17-f3s-kubernetes-with-freebsd-part-1.md +++ b/gemfeed/2024-11-17-f3s-kubernetes-with-freebsd-part-1.md @@ -6,7 +6,10 @@ This is the first blog post about my f3s series for my self-hosting demands in m I will post a new entry every month or so (there are too many other side projects for more frequent updates—I bet you can understand). +These are all the posts so far: + [2024-11-17 f3s: Kubernetes with FreeBSD - Part 1: Setting the stage (You are currently reading this)](./2024-11-17-f3s-kubernetes-with-freebsd-part-1.md) +[2024-12-03 f3s: Kubernetes with FreeBSD - Part 2: Hardware and base installation](./2024-12-03-f3s-kubernetes-with-freebsd-part-2.md) [![f3s logo](./f3s-kubernetes-with-freebsd-part-1/f3slogo.png "f3s logo")](./f3s-kubernetes-with-freebsd-part-1/f3slogo.png) @@ -149,6 +152,10 @@ For now, though, I'm focused on completing the migration from AWS ECS and gettin What's your take on self-hosting? Are you planning to move away from managed cloud services? Stay tuned for the second part of this series, where I will likely write about the hardware and the OS setups. +Read the next post of this series: + +[f3s: Kubernetes with FreeBSD - Part 2: Hardware and base installation](./2024-12-03-f3s-kubernetes-with-freebsd-part-2.md) + Other *BSD-related posts: [2016-04-09 Jails and ZFS with Puppet on FreeBSD](./2016-04-09-jails-and-zfs-on-freebsd-with-puppet.md) @@ -157,6 +164,7 @@ Other *BSD-related posts: [2024-01-13 One reason why I love OpenBSD](./2024-01-13-one-reason-why-i-love-openbsd.md) [2024-04-01 KISS high-availability with OpenBSD](./2024-04-01-KISS-high-availability-with-OpenBSD.md) [2024-11-17 f3s: Kubernetes with FreeBSD - Part 1: Setting the stage (You are currently reading this)](./2024-11-17-f3s-kubernetes-with-freebsd-part-1.md) +[2024-12-03 f3s: Kubernetes with FreeBSD - Part 2: Hardware and base installation](./2024-12-03-f3s-kubernetes-with-freebsd-part-2.md) E-Mail your comments to `paul@nospam.buetow.org` :-) diff --git a/gemfeed/2024-12-03-f3s-kubernetes-with-freebsd-part-2.md b/gemfeed/2024-12-03-f3s-kubernetes-with-freebsd-part-2.md new file mode 100644 index 00000000..9066d035 --- /dev/null +++ b/gemfeed/2024-12-03-f3s-kubernetes-with-freebsd-part-2.md @@ -0,0 +1,289 @@ +# f3s: Kubernetes with FreeBSD - Part 2: Hardware and base installation + +> Published at 2024-12-02T23:46:16+02:00 + +This is the second blog post about my f3s series for my self-hosting demands in my home lab. f3s? The "f" stands for FreeBSD, and the "3s" stands for k3s, the Kubernetes distribution I will use on FreeBSD-based physical machines. + +We set the stage last time; this time, we will set up the hardware for this project. + +These are all the posts so far: + +[2024-11-17 f3s: Kubernetes with FreeBSD - Part 1: Setting the stage](./2024-11-17-f3s-kubernetes-with-freebsd-part-1.md) +[2024-12-03 f3s: Kubernetes with FreeBSD - Part 2: Hardware and base installation (You are currently reading this)](./2024-12-03-f3s-kubernetes-with-freebsd-part-2.md) + +[![f3s logo](./f3s-kubernetes-with-freebsd-part-1/f3slogo.png "f3s logo")](./f3s-kubernetes-with-freebsd-part-1/f3slogo.png) + +> Logo was generated by ChatGPT. + +Let's continue... + +## Table of Contents + +* [⇢ f3s: Kubernetes with FreeBSD - Part 2: Hardware and base installation](#f3s-kubernetes-with-freebsd---part-2-hardware-and-base-installation) +* [⇢ ⇢ Deciding on the hardware](#deciding-on-the-hardware) +* [⇢ ⇢ ⇢ Not ARM but Intel N100 ](#not-arm-but-intel-n100-) +* [⇢ ⇢ ⇢ Beelink unboxing](#beelink-unboxing) +* [⇢ ⇢ ⇢ Network switch](#network-switch) +* [⇢ ⇢ Installing FreeBSD](#installing-freebsd) +* [⇢ ⇢ ⇢ Base install](#base-install) +* [⇢ ⇢ ⇢ Latest patch level and customizing `/etc/hosts`](#latest-patch-level-and-customizing-etchosts) +* [⇢ ⇢ ⇢ Additional packages after install](#additional-packages-after-install) +* [⇢ ⇢ Hardware check](#hardware-check) +* [⇢ ⇢ ⇢ Ethernet](#ethernet) +* [⇢ ⇢ ⇢ RAM](#ram) +* [⇢ ⇢ ⇢ CPUs](#cpus) +* [⇢ ⇢ ⇢ CPU throttling](#cpu-throttling) +* [⇢ ⇢ Conclusion](#conclusion) + +## Deciding on the hardware + +Note that the OpenBSD VMs included in the F3S setup (which will be used later in this blog series for internet ingress) are already there. These are virtual machines that I rent at OpenBSD Amsterdam and Hetzner. + +[https://openbsd.amsterdam](https://openbsd.amsterdam) +[https://hetzner.cloud](https://hetzner.cloud) + +This means that the FreeBSD boxes need to be covered, which will later be running k3s in Linux VMs via bhyve hypervisor. + +I've been considering whether to use Raspberry Pis or look for alternatives. It turns out that complete N100-based mini-computers aren't much more expensive than Raspberry Pi 5s, and they don't require assembly. Furthermore, I like that they are AMD64 and not ARM-based, which increases compatibility with some applications (e.g., I might want to virtualize Windows (via bhyve) on one of those, though that's out of scope for this blog series). + +### Not ARM but Intel N100 + +I needed something compact, efficient, and capable enough to handle the demands of a small-scale Kubernetes cluster and preferably something I don't have to assemble a lot. After researching, I decided on the Beelink S12 Pro with Intel N100 CPUs. + +[Beelink Min S12 Pro N100 official page](https://www.bee-link.com/products/beelink-mini-s12-pro-n100) + +The Intel N100 CPUs are built on the "Alder Lake-N" architecture. These chips are designed to balance performance and energy efficiency well. With four cores, they're more than capable of running multiple containers, even with moderate workloads. Plus, they consume only 6W of power, keeping the electricity bill low and the setup quiet - perfect for 24/7 operation. + +[![Beelink preparation](./f3s-kubernetes-with-freebsd-part-2/f3s-collage1.jpg "Beelink preparation")](./f3s-kubernetes-with-freebsd-part-2/f3s-collage1.jpg) + +The Beelink comes with the following specs: + +* 12th Gen Intel N100 processor, with four cores and four threads, and a maximum frequency of up to 3.4 GHz. +* 16 GB of DDR4 RAM, with a maximum (official) size of 16 GB (but people could install 32 GB on it). +* 500 GB M.2 SSD, with the option to install a 2nd 2.5 SSD drive (which I want to use later in this blog series). +* GBit ethernet +* Four USB 3.2 Gen2 ports (maybe I want to mount something externally at some point) +* Dimensions and weight: 115*102*39mm, 280g +* Silent cooling system. +* HDMI output (needed only for the initial installation) +* Auto power on via WoL (may make use of it) +* Wi-Fi (not going to use it) + +I bought three (3) of them for the cluster I intend to build. + +### Beelink unboxing + +Unboxing was uneventful. Every Beelink PC came with: + +* An AC power adapter +* An HDMI cable +* A VESA mount with screws (not using it as of now) +* Some manuals +* The pre-assembled Beelink PC itself. +* A "Hello" post card (??) + +Overall, I love the small form factor. + +### Network switch + +I went with the TP-Link mini 5-port switch, as I had a spare one available. That switch will be plugged into my wall Ethernet port, which connects directly to my fiber internet router with 100 Mbit/s down and 50 Mbit/s upload speed. + +[![Switch](./f3s-kubernetes-with-freebsd-part-2/switch.jpg "Switch")](./f3s-kubernetes-with-freebsd-part-2/switch.jpg) + +## Installing FreeBSD + +### Base install + +First, I downloaded the boot-only ISO of the latest FreeBSD release and dumped it on a USB stick on my Fedora laptop: + +```sh +[paul@earth]~/Downloads% sudo dd \ + if=FreeBSD-14.1-RELEASE-amd64-bootonly.iso \ + of=/dev/sda conv=sync +``` + +Next, I plugged the Beelinks (one after another) into my monitor via HDMI (the resolution of the FreeBSD text console seems strangely stretched, as I am using the LG Dual Up monitor), connected Ethernet, an external USB keyboard, and the FreeBSD USB stick, and booted the devices up. With F7, I entered the boot menu and selected the USB stick for the FreeBSD installation. + +The installation was uneventful. I selected: + +* Guided ZFS on root (pool `zroot`) +* Unencrypted ZFS (I will encrypt separate datasets later; I want it to be able to boot without human interaction) +* Static IP configuration (to ensure that the boxes always have the same IPs, even after switching the router/DHCP server) +* I decided to enable the SSH daemon, NTP server, and NTP time synchronization at boot, and I also enabled powerd for automatic CPU frequency scaling. +* In addition to `root,` I added a personal user, `paul,` whom I placed in the `wheel` group. + +After doing all that three times (once for each Beelink PC), I had three ready-to-use FreeBSD boxes! Their hostnames are `f0`, `f1` and `f2`! + +[![Beelink installation](./f3s-kubernetes-with-freebsd-part-2/f3s-collage2.jpg "Beelink installation")](./f3s-kubernetes-with-freebsd-part-2/f3s-collage2.jpg) + +### Latest patch level and customizing `/etc/hosts` + +After the first boot, I upgraded to the latest FreeBSD patch level as follows: + +```sh +root@f0:~ # freebsd-update fetch +root@f0:~ # freebsd-update install +root@f0:~ # freebsd-update reboot +``` + +I also added the following entries for the three FreeBSD boxes to the `/etc/hosts` file: +```sh +root@f0:~ # cat <>/etc/hosts +192.168.1.130 f0 f0.lan f0.lan.buetow.org +192.168.1.131 f1 f1.lan f1.lan.buetow.org +192.168.1.132 f2 f2.lan f2.lan.buetow.org +END +``` + +### Additional packages after install + +After that, I installed the following additional packages: + +```sh +root@f0:~ # pkg install helix doas zfs-periodic uptimed +``` + +Helix? It's my favourite text editor. I have nothing against `vi` but like `hx` (Helix) more! + +`doas`? It's a pretty neat (and KISS) replacement for `sudo`. It has far fewer features than `sudo`, which is supposed to make it more secure. Its origin is the OpenBSD project. For `doas`, I accepted the default configuration (where users in the `wheel` group are allowed to run commands as `root`): + +```sh +root@f0:~ # cp /usr/local/etc/doas.conf.sample /usr/local/etc/doas.conf +``` + +`zfs-periodic` is a nifty tool for automatically creating ZFS snapshots. I decided to go with the following configuration here: + +```sh +root@f0:~ # sysrc daily_zfs_snapshot_enable=YES +daily_zfs_snapshot_enable: -> YES +root@f0:~ # sysrc daily_zfs_snapshot_pools=zroot +daily_zfs_snapshot_pools: -> zroot +root@f0:~ # sysrc daily_zfs_snapshot_keep=7 +daily_zfs_snapshot_keep: -> 7 +root@f0:~ # sysrc weekly_zfs_snapshot_enable=YES +weekly_zfs_snapshot_enable: -> YES +root@f0:~ # sysrc weekly_zfs_snapshot_pools=zroot +weekly_zfs_snapshot_pools: -> zroot +root@f0:~ # sysrc weekly_zfs_snapshot_keep=5 +weekly_zfs_snapshot_keep: -> 5 +root@f0:~ # sysrc monthly_zfs_snapshot_enable=YES +monthly_zfs_snapshot_enable: -> YES +root@f0:~ # sysrc monthly_zfs_snapshot_pools=zroot +monthly_zfs_snapshot_pools: -> zroot +root@f0:~ # sysrc weekly_zfs_snapshot_keep=2 +weekly_zfs_snapshot_keep: 5 -> 2 +``` + +`uptimed`? I like to track my uptimes. This is how I configured the daemon: + +```sh +root@f0:~ # cp /usr/local/mimecast/etc/uptimed.conf-dist \ + /usr/local/mimecast/etc/uptimed.conf +root@f0:~ # hx /usr/local/mimecast/etc/uptimed.conf +``` + +In the Helix editor session, I changed `LOG_MAXIMUM_ENTRIES` to `0` to keep all uptime entries forever and not cut off at 50 (the default config). After that, I enabled and started `uptimed`: + +```sh +root@f0:~ # service uptimed enable +root@f0:~ # service uptimed start +``` + +To check the current uptime stats, I can now run `uprecords`: + +```sh + root@f0:~ # uprecords + # Uptime | System Boot up +----------------------------+--------------------------------------------------- +-> 1 0 days, 00:07:34 | FreeBSD 14.1-RELEASE Mon Dec 2 12:21:44 2024 +----------------------------+--------------------------------------------------- +NewRec 0 days, 00:07:33 | since Mon Dec 2 12:21:44 2024 + up 0 days, 00:07:34 | since Mon Dec 2 12:21:44 2024 + down 0 days, 00:00:00 | since Mon Dec 2 12:21:44 2024 + %up 100.000 | since Mon Dec 2 12:21:44 2024 +``` + +## Hardware check + +### Ethernet + +Works. Nothing eventful, really. It's a cheap Realtek chip, but it will do what it is supposed to do. + +```sh +paul@f0:~ % ifconfig re0 +re0: flags=1008843 metric 0 mtu 1500 + options=8209b + ether e8:ff:1e:d7:1c:ac + inet 192.168.1.130 netmask 0xffffff00 broadcast 192.168.1.255 + inet6 fe80::eaff:1eff:fed7:1cac%re0 prefixlen 64 scopeid 0x1 + inet6 fd22:c702:acb7:0:eaff:1eff:fed7:1cac prefixlen 64 detached autoconf + inet6 2a01:5a8:304:1d5c:eaff:1eff:fed7:1cac prefixlen 64 autoconf pltime 10800 vltime 14400 + media: Ethernet autoselect (1000baseT ) + status: active + nd6 options=23 +``` + +### RAM + +All there: + +```sh +paul@f1:~ % sysctl hw.physmem +hw.physmem: 16902905856 + +``` + +### CPUs + +Work: + +```sh +paul@f0:~ % sysctl dev.cpu | grep freq: +dev.cpu.3.freq: 705 +dev.cpu.2.freq: 705 +dev.cpu.1.freq: 604 +dev.cpu.0.freq: 604 +``` + +### CPU throttling + +With `powerd` running, CPU freq is dowthrottled when the box isn't jam-packed. To stress it a bit, I run `ubench` to see the frequencies being unthrottled again: + +```sh +paul@f0:~ % doas pkg install ubench +paul@f0:~ % rehash # For tcsh to find the newly installed command +paul@f0:~ % ubench & +paul@f0:~ % sysctl dev.cpu | grep freq: +dev.cpu.3.freq: 2922 +dev.cpu.2.freq: 2922 +dev.cpu.1.freq: 2923 +dev.cpu.0.freq: 2922 +``` + +Idle, all three Beelinks plus the switch consumed 26.2W. But with `ubench` stressing all the CPUs, it went up to 38.8W. + +[![Idle consumption.](./f3s-kubernetes-with-freebsd-part-2/watt.jpg "Idle consumption.")](./f3s-kubernetes-with-freebsd-part-2/watt.jpg) + +## Conclusion + +The Beelink S12 Pro with Intel N100 CPUs checks all the boxes for a k3s project: compact, efficient, expandable, and affordable. Its compatibility with both Linux and FreeBSD makes it versatile for other use cases, whether as part of your cluster or as a standalone system. If you’re looking for hardware that punches above its weight for Kubernetes, this little device deserves a spot on your shortlist. + +[![Beelinks stacked](./f3s-kubernetes-with-freebsd-part-2/3beelinks.jpg "Beelinks stacked")](./f3s-kubernetes-with-freebsd-part-2/3beelinks.jpg) + +To ease cable management, I need to get shorter Ethernet cables. I will place the tower on my shelf, where most of the cables will be hidden (together with a UPS, which will also be added to the setup). + +What will be covered in the next post of this series? The bhyve/Rocky Linux and WireGuard setup as described in part 1 of this series. + +Other *BSD-related posts: + +[2016-04-09 Jails and ZFS with Puppet on FreeBSD](./2016-04-09-jails-and-zfs-on-freebsd-with-puppet.md) +[2022-07-30 Let's Encrypt with OpenBSD and Rex](./2022-07-30-lets-encrypt-with-openbsd-and-rex.md) +[2022-10-30 Installing DTail on OpenBSD](./2022-10-30-installing-dtail-on-openbsd.md) +[2024-01-13 One reason why I love OpenBSD](./2024-01-13-one-reason-why-i-love-openbsd.md) +[2024-04-01 KISS high-availability with OpenBSD](./2024-04-01-KISS-high-availability-with-OpenBSD.md) +[2024-11-17 f3s: Kubernetes with FreeBSD - Part 1: Setting the stage](./2024-11-17-f3s-kubernetes-with-freebsd-part-1.md) +[2024-12-03 f3s: Kubernetes with FreeBSD - Part 2: Hardware and base installation (You are currently reading this)](./2024-12-03-f3s-kubernetes-with-freebsd-part-2.md) + +E-Mail your comments to `paul@nospam.buetow.org` :-) + +[Back to the main site](../) diff --git a/gemfeed/DRAFT-f3s-kubernetes-with-freebsd-hardware-setup.md b/gemfeed/DRAFT-f3s-kubernetes-with-freebsd-hardware-setup.md index 707c3598..4a1b3422 100644 --- a/gemfeed/DRAFT-f3s-kubernetes-with-freebsd-hardware-setup.md +++ b/gemfeed/DRAFT-f3s-kubernetes-with-freebsd-hardware-setup.md @@ -7,6 +7,7 @@ This is the second blog post about my f3s series for my self-hosting demands in I will post a new entry every month or so (there are too many other side projects for more frequent updates—I bet you can understand). [2024-11-17 f3s: Kubernetes with FreeBSD - Part 1: Setting the stage](./2024-11-17-f3s-kubernetes-with-freebsd-part-1.md) +[2024-12-03 f3s: Kubernetes with FreeBSD - Part 2: Hardware and base installation](./2024-12-03-f3s-kubernetes-with-freebsd-part-2.md) [![f3s logo](./f3s-kubernetes-with-freebsd-part-1/f3slogo.png "f3s logo")](./f3s-kubernetes-with-freebsd-part-1/f3slogo.png) @@ -33,6 +34,7 @@ Other *BSD-related posts: [2024-01-13 One reason why I love OpenBSD](./2024-01-13-one-reason-why-i-love-openbsd.md) [2024-04-01 KISS high-availability with OpenBSD](./2024-04-01-KISS-high-availability-with-OpenBSD.md) [2024-11-17 f3s: Kubernetes with FreeBSD - Part 1: Setting the stage](./2024-11-17-f3s-kubernetes-with-freebsd-part-1.md) +[2024-12-03 f3s: Kubernetes with FreeBSD - Part 2: Hardware and base installation](./2024-12-03-f3s-kubernetes-with-freebsd-part-2.md) E-Mail your comments to `paul@nospam.buetow.org` :-) diff --git a/gemfeed/f3s-kubernetes-with-freebsd-part-2/3beelinks.jpg b/gemfeed/f3s-kubernetes-with-freebsd-part-2/3beelinks.jpg new file mode 100644 index 00000000..7da37da7 Binary files /dev/null and b/gemfeed/f3s-kubernetes-with-freebsd-part-2/3beelinks.jpg differ diff --git a/gemfeed/f3s-kubernetes-with-freebsd-part-2/f3s-collage1.jpg b/gemfeed/f3s-kubernetes-with-freebsd-part-2/f3s-collage1.jpg new file mode 100644 index 00000000..294eb37d Binary files /dev/null and b/gemfeed/f3s-kubernetes-with-freebsd-part-2/f3s-collage1.jpg differ diff --git a/gemfeed/f3s-kubernetes-with-freebsd-part-2/f3s-collage2.jpg b/gemfeed/f3s-kubernetes-with-freebsd-part-2/f3s-collage2.jpg new file mode 100644 index 00000000..77c4c0bc Binary files /dev/null and b/gemfeed/f3s-kubernetes-with-freebsd-part-2/f3s-collage2.jpg differ diff --git a/gemfeed/f3s-kubernetes-with-freebsd-part-2/switch.jpg b/gemfeed/f3s-kubernetes-with-freebsd-part-2/switch.jpg new file mode 100644 index 00000000..8fe0edeb Binary files /dev/null and b/gemfeed/f3s-kubernetes-with-freebsd-part-2/switch.jpg differ diff --git a/gemfeed/f3s-kubernetes-with-freebsd-part-2/watt.jpg b/gemfeed/f3s-kubernetes-with-freebsd-part-2/watt.jpg new file mode 100644 index 00000000..e79fe68c Binary files /dev/null and b/gemfeed/f3s-kubernetes-with-freebsd-part-2/watt.jpg differ diff --git a/gemfeed/index.md b/gemfeed/index.md index 37c8aefa..eaab8e5e 100644 --- a/gemfeed/index.md +++ b/gemfeed/index.md @@ -2,6 +2,7 @@ ## To be in the .zone! +[2024-12-03 - f3s: Kubernetes with FreeBSD - Part 2: Hardware and base installation](./2024-12-03-f3s-kubernetes-with-freebsd-part-2.md) [2024-11-17 - f3s: Kubernetes with FreeBSD - Part 1: Setting the stage](./2024-11-17-f3s-kubernetes-with-freebsd-part-1.md) [2024-10-24 - 'Staff Engineer' book notes](./2024-10-24-staff-engineer-book-notes.md) [2024-10-02 - Gemtexter 3.0.0 - Let's Gemtext again⁴](./2024-10-02-gemtexter-3.0.0-lets-gemtext-again-4.md) -- cgit v1.2.3 From 8a3574d3899b5c6a1157a38336f0c8effba245b8 Mon Sep 17 00:00:00 2001 From: Paul Buetow Date: Mon, 2 Dec 2024 23:48:54 +0200 Subject: Update content for md --- gemfeed/2024-12-03-f3s-kubernetes-with-freebsd-part-2.md | 4 ++-- 1 file changed, 2 insertions(+), 2 deletions(-) (limited to 'gemfeed') diff --git a/gemfeed/2024-12-03-f3s-kubernetes-with-freebsd-part-2.md b/gemfeed/2024-12-03-f3s-kubernetes-with-freebsd-part-2.md index 9066d035..c4a49d9e 100644 --- a/gemfeed/2024-12-03-f3s-kubernetes-with-freebsd-part-2.md +++ b/gemfeed/2024-12-03-f3s-kubernetes-with-freebsd-part-2.md @@ -1,6 +1,6 @@ # f3s: Kubernetes with FreeBSD - Part 2: Hardware and base installation -> Published at 2024-12-02T23:46:16+02:00 +> Published at 2024-12-02T23:48:21+02:00 This is the second blog post about my f3s series for my self-hosting demands in my home lab. f3s? The "f" stands for FreeBSD, and the "3s" stands for k3s, the Kubernetes distribution I will use on FreeBSD-based physical machines. @@ -37,7 +37,7 @@ Let's continue... ## Deciding on the hardware -Note that the OpenBSD VMs included in the F3S setup (which will be used later in this blog series for internet ingress) are already there. These are virtual machines that I rent at OpenBSD Amsterdam and Hetzner. +Note that the OpenBSD VMs included in the f3s setup (which will be used later in this blog series for internet ingress) are already there. These are virtual machines that I rent at OpenBSD Amsterdam and Hetzner. [https://openbsd.amsterdam](https://openbsd.amsterdam) [https://hetzner.cloud](https://hetzner.cloud) -- cgit v1.2.3 From 7b22e71cd786e3d2e80fb0659d72b0934234c028 Mon Sep 17 00:00:00 2001 From: Paul Buetow Date: Mon, 2 Dec 2024 23:52:11 +0200 Subject: Update content for md --- gemfeed/2024-12-03-f3s-kubernetes-with-freebsd-part-2.md | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) (limited to 'gemfeed') diff --git a/gemfeed/2024-12-03-f3s-kubernetes-with-freebsd-part-2.md b/gemfeed/2024-12-03-f3s-kubernetes-with-freebsd-part-2.md index c4a49d9e..af562ba0 100644 --- a/gemfeed/2024-12-03-f3s-kubernetes-with-freebsd-part-2.md +++ b/gemfeed/2024-12-03-f3s-kubernetes-with-freebsd-part-2.md @@ -65,7 +65,7 @@ The Beelink comes with the following specs: * Four USB 3.2 Gen2 ports (maybe I want to mount something externally at some point) * Dimensions and weight: 115*102*39mm, 280g * Silent cooling system. -* HDMI output (needed only for the initial installation) +* HDMI output (needed only for the initial installation and maybe for troubleshooting later) * Auto power on via WoL (may make use of it) * Wi-Fi (not going to use it) -- cgit v1.2.3 From 26a482dbc049154f846d7950dfbd2235cd199aed Mon Sep 17 00:00:00 2001 From: Paul Buetow Date: Mon, 2 Dec 2024 23:57:05 +0200 Subject: Update content for md --- gemfeed/2024-12-03-f3s-kubernetes-with-freebsd-part-2.md | 6 +++++- 1 file changed, 5 insertions(+), 1 deletion(-) (limited to 'gemfeed') diff --git a/gemfeed/2024-12-03-f3s-kubernetes-with-freebsd-part-2.md b/gemfeed/2024-12-03-f3s-kubernetes-with-freebsd-part-2.md index af562ba0..a9862741 100644 --- a/gemfeed/2024-12-03-f3s-kubernetes-with-freebsd-part-2.md +++ b/gemfeed/2024-12-03-f3s-kubernetes-with-freebsd-part-2.md @@ -109,7 +109,7 @@ The installation was uneventful. I selected: * Guided ZFS on root (pool `zroot`) * Unencrypted ZFS (I will encrypt separate datasets later; I want it to be able to boot without human interaction) * Static IP configuration (to ensure that the boxes always have the same IPs, even after switching the router/DHCP server) -* I decided to enable the SSH daemon, NTP server, and NTP time synchronization at boot, and I also enabled powerd for automatic CPU frequency scaling. +* I decided to enable the SSH daemon, NTP server, and NTP time synchronization at boot, and I also enabled `powerd` for automatic CPU frequency scaling. * In addition to `root,` I added a personal user, `paul,` whom I placed in the `wheel` group. After doing all that three times (once for each Beelink PC), I had three ready-to-use FreeBSD boxes! Their hostnames are `f0`, `f1` and `f2`! @@ -203,6 +203,10 @@ NewRec 0 days, 00:07:33 | since Mon Dec 2 12:21:44 2024 %up 100.000 | since Mon Dec 2 12:21:44 2024 ``` +This is how I track the uptimes for all of my host: + +[Unveiling `guprecords.raku`: Global Uptime Records with Raku](./2023-05-01-unveiling-guprecords:-uptime-records-with-raku.md) + ## Hardware check ### Ethernet -- cgit v1.2.3 From fa7c858231af5d7fc6a2cf1e167688ceeacc4a2a Mon Sep 17 00:00:00 2001 From: Paul Buetow Date: Mon, 2 Dec 2024 23:58:14 +0200 Subject: Update content for md --- gemfeed/2024-12-03-f3s-kubernetes-with-freebsd-part-2.md | 4 ++-- 1 file changed, 2 insertions(+), 2 deletions(-) (limited to 'gemfeed') diff --git a/gemfeed/2024-12-03-f3s-kubernetes-with-freebsd-part-2.md b/gemfeed/2024-12-03-f3s-kubernetes-with-freebsd-part-2.md index a9862741..e52b75b8 100644 --- a/gemfeed/2024-12-03-f3s-kubernetes-with-freebsd-part-2.md +++ b/gemfeed/2024-12-03-f3s-kubernetes-with-freebsd-part-2.md @@ -232,14 +232,14 @@ re0: flags=1008843 metric 0 mtu All there: ```sh -paul@f1:~ % sysctl hw.physmem +paul@f0:~ % sysctl hw.physmem hw.physmem: 16902905856 ``` ### CPUs -Work: +They work: ```sh paul@f0:~ % sysctl dev.cpu | grep freq: -- cgit v1.2.3 From 5fe5aa5680c8266f29592cbee1c1d74adb96e506 Mon Sep 17 00:00:00 2001 From: Paul Buetow Date: Tue, 3 Dec 2024 00:01:13 +0200 Subject: Update content for md --- gemfeed/2024-12-03-f3s-kubernetes-with-freebsd-part-2.md | 4 ++-- 1 file changed, 2 insertions(+), 2 deletions(-) (limited to 'gemfeed') diff --git a/gemfeed/2024-12-03-f3s-kubernetes-with-freebsd-part-2.md b/gemfeed/2024-12-03-f3s-kubernetes-with-freebsd-part-2.md index e52b75b8..ea877419 100644 --- a/gemfeed/2024-12-03-f3s-kubernetes-with-freebsd-part-2.md +++ b/gemfeed/2024-12-03-f3s-kubernetes-with-freebsd-part-2.md @@ -52,7 +52,7 @@ I needed something compact, efficient, and capable enough to handle the demands [Beelink Min S12 Pro N100 official page](https://www.bee-link.com/products/beelink-mini-s12-pro-n100) -The Intel N100 CPUs are built on the "Alder Lake-N" architecture. These chips are designed to balance performance and energy efficiency well. With four cores, they're more than capable of running multiple containers, even with moderate workloads. Plus, they consume only 6W of power, keeping the electricity bill low and the setup quiet - perfect for 24/7 operation. +The Intel N100 CPUs are built on the "Alder Lake-N" architecture. These chips are designed to balance performance and energy efficiency well. With four cores, they're more than capable of running multiple containers, even with moderate workloads. Plus, they consume only around 8W of power (ok, that's more than the Pis...), keeping the electricity bill low enough and the setup quiet - perfect for 24/7 operation. [![Beelink preparation](./f3s-kubernetes-with-freebsd-part-2/f3s-collage1.jpg "Beelink preparation")](./f3s-kubernetes-with-freebsd-part-2/f3s-collage1.jpg) @@ -270,7 +270,7 @@ Idle, all three Beelinks plus the switch consumed 26.2W. But with `ubench` stres ## Conclusion -The Beelink S12 Pro with Intel N100 CPUs checks all the boxes for a k3s project: compact, efficient, expandable, and affordable. Its compatibility with both Linux and FreeBSD makes it versatile for other use cases, whether as part of your cluster or as a standalone system. If you’re looking for hardware that punches above its weight for Kubernetes, this little device deserves a spot on your shortlist. +The Beelink S12 Pro with Intel N100 CPUs checks all the boxes for a k3s project: Compact, efficient, expandable, and affordable. Its compatibility with both Linux and FreeBSD makes it versatile for other use cases, whether as part of your cluster or as a standalone system. If you’re looking for hardware that punches above its weight for Kubernetes, this little device deserves a spot on your shortlist. [![Beelinks stacked](./f3s-kubernetes-with-freebsd-part-2/3beelinks.jpg "Beelinks stacked")](./f3s-kubernetes-with-freebsd-part-2/3beelinks.jpg) -- cgit v1.2.3 From 419eee2a075ec31d5554a92410ff814beaab052d Mon Sep 17 00:00:00 2001 From: Paul Buetow Date: Tue, 3 Dec 2024 00:13:53 +0200 Subject: Update content for md --- gemfeed/2024-12-03-f3s-kubernetes-with-freebsd-part-2.md | 4 ++-- 1 file changed, 2 insertions(+), 2 deletions(-) (limited to 'gemfeed') diff --git a/gemfeed/2024-12-03-f3s-kubernetes-with-freebsd-part-2.md b/gemfeed/2024-12-03-f3s-kubernetes-with-freebsd-part-2.md index ea877419..2a8eeddb 100644 --- a/gemfeed/2024-12-03-f3s-kubernetes-with-freebsd-part-2.md +++ b/gemfeed/2024-12-03-f3s-kubernetes-with-freebsd-part-2.md @@ -37,7 +37,7 @@ Let's continue... ## Deciding on the hardware -Note that the OpenBSD VMs included in the f3s setup (which will be used later in this blog series for internet ingress) are already there. These are virtual machines that I rent at OpenBSD Amsterdam and Hetzner. +Note that the OpenBSD VMs included in the f3s setup (which will be used later in this blog series for internet ingress - as you know from the first part of this blog series) are already there. These are virtual machines that I rent at OpenBSD Amsterdam and Hetzner. [https://openbsd.amsterdam](https://openbsd.amsterdam) [https://hetzner.cloud](https://hetzner.cloud) @@ -50,7 +50,7 @@ I've been considering whether to use Raspberry Pis or look for alternatives. It I needed something compact, efficient, and capable enough to handle the demands of a small-scale Kubernetes cluster and preferably something I don't have to assemble a lot. After researching, I decided on the Beelink S12 Pro with Intel N100 CPUs. -[Beelink Min S12 Pro N100 official page](https://www.bee-link.com/products/beelink-mini-s12-pro-n100) +[Beelink Mini S12 Pro N100 official page](https://www.bee-link.com/products/beelink-mini-s12-pro-n100) The Intel N100 CPUs are built on the "Alder Lake-N" architecture. These chips are designed to balance performance and energy efficiency well. With four cores, they're more than capable of running multiple containers, even with moderate workloads. Plus, they consume only around 8W of power (ok, that's more than the Pis...), keeping the electricity bill low enough and the setup quiet - perfect for 24/7 operation. -- cgit v1.2.3 From df46efdd5f3b94d038ae61a46b8403c416602137 Mon Sep 17 00:00:00 2001 From: Paul Buetow Date: Tue, 3 Dec 2024 00:21:25 +0200 Subject: Update content for md --- gemfeed/2024-12-03-f3s-kubernetes-with-freebsd-part-2.md | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) (limited to 'gemfeed') diff --git a/gemfeed/2024-12-03-f3s-kubernetes-with-freebsd-part-2.md b/gemfeed/2024-12-03-f3s-kubernetes-with-freebsd-part-2.md index 2a8eeddb..7ab023a6 100644 --- a/gemfeed/2024-12-03-f3s-kubernetes-with-freebsd-part-2.md +++ b/gemfeed/2024-12-03-f3s-kubernetes-with-freebsd-part-2.md @@ -211,7 +211,7 @@ This is how I track the uptimes for all of my host: ### Ethernet -Works. Nothing eventful, really. It's a cheap Realtek chip, but it will do what it is supposed to do. +Works. Nothing eventful, really. It's a cheap Realtek chip, but it will do what it is supposed to do (I hope). ```sh paul@f0:~ % ifconfig re0 -- cgit v1.2.3 From d9b71afb36081f8dcc14cf1346d318815d6652b0 Mon Sep 17 00:00:00 2001 From: Paul Buetow Date: Tue, 3 Dec 2024 09:09:57 +0200 Subject: Update content for md --- .../2024-12-03-f3s-kubernetes-with-freebsd-part-2.md | 18 +++++++++--------- 1 file changed, 9 insertions(+), 9 deletions(-) (limited to 'gemfeed') diff --git a/gemfeed/2024-12-03-f3s-kubernetes-with-freebsd-part-2.md b/gemfeed/2024-12-03-f3s-kubernetes-with-freebsd-part-2.md index 7ab023a6..b547b7f3 100644 --- a/gemfeed/2024-12-03-f3s-kubernetes-with-freebsd-part-2.md +++ b/gemfeed/2024-12-03-f3s-kubernetes-with-freebsd-part-2.md @@ -60,7 +60,7 @@ The Beelink comes with the following specs: * 12th Gen Intel N100 processor, with four cores and four threads, and a maximum frequency of up to 3.4 GHz. * 16 GB of DDR4 RAM, with a maximum (official) size of 16 GB (but people could install 32 GB on it). -* 500 GB M.2 SSD, with the option to install a 2nd 2.5 SSD drive (which I want to use later in this blog series). +* 500 GB M.2 SSD, with the option to install a 2nd 2.5 SSD drive (which I want to make use of later in this blog series). * GBit ethernet * Four USB 3.2 Gen2 ports (maybe I want to mount something externally at some point) * Dimensions and weight: 115*102*39mm, 280g @@ -86,7 +86,7 @@ Overall, I love the small form factor. ### Network switch -I went with the TP-Link mini 5-port switch, as I had a spare one available. That switch will be plugged into my wall Ethernet port, which connects directly to my fiber internet router with 100 Mbit/s down and 50 Mbit/s upload speed. +I went with the tp-link mini 5-port switch, as I had a spare one available. That switch will be plugged into my wall ethernet port, which connects directly to my fiber internet router with 100 Mbit/s down and 50 Mbit/s upload speed. [![Switch](./f3s-kubernetes-with-freebsd-part-2/switch.jpg "Switch")](./f3s-kubernetes-with-freebsd-part-2/switch.jpg) @@ -94,7 +94,7 @@ I went with the TP-Link mini 5-port switch, as I had a spare one available. That ### Base install -First, I downloaded the boot-only ISO of the latest FreeBSD release and dumped it on a USB stick on my Fedora laptop: +First, I downloaded the boot-only ISO of the latest FreeBSD release and dumped it on a USB stick via my Fedora laptop: ```sh [paul@earth]~/Downloads% sudo dd \ @@ -107,7 +107,7 @@ Next, I plugged the Beelinks (one after another) into my monitor via HDMI (the r The installation was uneventful. I selected: * Guided ZFS on root (pool `zroot`) -* Unencrypted ZFS (I will encrypt separate datasets later; I want it to be able to boot without human interaction) +* Unencrypted ZFS (I will encrypt separate datasets later; I want it to be able to boot without manual interaction) * Static IP configuration (to ensure that the boxes always have the same IPs, even after switching the router/DHCP server) * I decided to enable the SSH daemon, NTP server, and NTP time synchronization at boot, and I also enabled `powerd` for automatic CPU frequency scaling. * In addition to `root,` I added a personal user, `paul,` whom I placed in the `wheel` group. @@ -170,8 +170,8 @@ root@f0:~ # sysrc monthly_zfs_snapshot_enable=YES monthly_zfs_snapshot_enable: -> YES root@f0:~ # sysrc monthly_zfs_snapshot_pools=zroot monthly_zfs_snapshot_pools: -> zroot -root@f0:~ # sysrc weekly_zfs_snapshot_keep=2 -weekly_zfs_snapshot_keep: 5 -> 2 +root@f0:~ # sysrc monthly_zfs_snapshot_keep=2 +monthly_zfs_snapshot_keep: 5 -> 2 ``` `uptimed`? I like to track my uptimes. This is how I configured the daemon: @@ -211,7 +211,7 @@ This is how I track the uptimes for all of my host: ### Ethernet -Works. Nothing eventful, really. It's a cheap Realtek chip, but it will do what it is supposed to do (I hope). +Works. Nothing eventful, really. It's a cheap Realtek chip, but it will do what it is supposed to do. ```sh paul@f0:~ % ifconfig re0 @@ -274,9 +274,9 @@ The Beelink S12 Pro with Intel N100 CPUs checks all the boxes for a k3s project: [![Beelinks stacked](./f3s-kubernetes-with-freebsd-part-2/3beelinks.jpg "Beelinks stacked")](./f3s-kubernetes-with-freebsd-part-2/3beelinks.jpg) -To ease cable management, I need to get shorter Ethernet cables. I will place the tower on my shelf, where most of the cables will be hidden (together with a UPS, which will also be added to the setup). +To ease cable management, I need to get shorter ethernet cables. I will place the tower on my shelf, where most of the cables will be hidden (together with a UPS, which will also be added to the setup). -What will be covered in the next post of this series? The bhyve/Rocky Linux and WireGuard setup as described in part 1 of this series. +What will be covered in the next post of this series? Maybe ttttbhyve/Rocky Linux and WireGuard setup as described in part 1 of this series... Other *BSD-related posts: -- cgit v1.2.3 From d6bde85a500ab39ecf1b5d2be3b49a7ee6299631 Mon Sep 17 00:00:00 2001 From: Paul Buetow Date: Tue, 3 Dec 2024 10:17:04 +0200 Subject: Update content for md --- gemfeed/2024-12-03-f3s-kubernetes-with-freebsd-part-2.md | 4 ++-- 1 file changed, 2 insertions(+), 2 deletions(-) (limited to 'gemfeed') diff --git a/gemfeed/2024-12-03-f3s-kubernetes-with-freebsd-part-2.md b/gemfeed/2024-12-03-f3s-kubernetes-with-freebsd-part-2.md index b547b7f3..27986a5a 100644 --- a/gemfeed/2024-12-03-f3s-kubernetes-with-freebsd-part-2.md +++ b/gemfeed/2024-12-03-f3s-kubernetes-with-freebsd-part-2.md @@ -170,8 +170,8 @@ root@f0:~ # sysrc monthly_zfs_snapshot_enable=YES monthly_zfs_snapshot_enable: -> YES root@f0:~ # sysrc monthly_zfs_snapshot_pools=zroot monthly_zfs_snapshot_pools: -> zroot -root@f0:~ # sysrc monthly_zfs_snapshot_keep=2 -monthly_zfs_snapshot_keep: 5 -> 2 +root@f0:~ # sysrc monthly_zfs_snapshot_keep=6 +monthly_zfs_snapshot_keep: 2 -> 6 ``` `uptimed`? I like to track my uptimes. This is how I configured the daemon: -- cgit v1.2.3 From 845fd437eba6a398a4463c70e61bba0399b74553 Mon Sep 17 00:00:00 2001 From: Paul Buetow Date: Thu, 5 Dec 2024 11:29:04 +0200 Subject: Update content for md --- ...024-12-03-f3s-kubernetes-with-freebsd-part-2.md | 70 +++++++++++++--------- 1 file changed, 41 insertions(+), 29 deletions(-) (limited to 'gemfeed') diff --git a/gemfeed/2024-12-03-f3s-kubernetes-with-freebsd-part-2.md b/gemfeed/2024-12-03-f3s-kubernetes-with-freebsd-part-2.md index 27986a5a..710b6b5b 100644 --- a/gemfeed/2024-12-03-f3s-kubernetes-with-freebsd-part-2.md +++ b/gemfeed/2024-12-03-f3s-kubernetes-with-freebsd-part-2.md @@ -20,22 +20,26 @@ Let's continue... ## Table of Contents * [⇢ f3s: Kubernetes with FreeBSD - Part 2: Hardware and base installation](#f3s-kubernetes-with-freebsd---part-2-hardware-and-base-installation) -* [⇢ ⇢ Deciding on the hardware](#deciding-on-the-hardware) -* [⇢ ⇢ ⇢ Not ARM but Intel N100 ](#not-arm-but-intel-n100-) -* [⇢ ⇢ ⇢ Beelink unboxing](#beelink-unboxing) -* [⇢ ⇢ ⇢ Network switch](#network-switch) -* [⇢ ⇢ Installing FreeBSD](#installing-freebsd) -* [⇢ ⇢ ⇢ Base install](#base-install) -* [⇢ ⇢ ⇢ Latest patch level and customizing `/etc/hosts`](#latest-patch-level-and-customizing-etchosts) -* [⇢ ⇢ ⇢ Additional packages after install](#additional-packages-after-install) -* [⇢ ⇢ Hardware check](#hardware-check) -* [⇢ ⇢ ⇢ Ethernet](#ethernet) -* [⇢ ⇢ ⇢ RAM](#ram) -* [⇢ ⇢ ⇢ CPUs](#cpus) -* [⇢ ⇢ ⇢ CPU throttling](#cpu-throttling) -* [⇢ ⇢ Conclusion](#conclusion) - -## Deciding on the hardware +* [⇢ Deciding on the hardware](#deciding-on-the-hardware) +* [⇢ ⇢ Not ARM but Intel N100 ](#not-arm-but-intel-n100-) +* [⇢ ⇢ Beelink unboxing](#beelink-unboxing) +* [⇢ ⇢ Network switch](#network-switch) +* [⇢ Installing FreeBSD](#installing-freebsd) +* [⇢ ⇢ Base install](#base-install) +* [⇢ ⇢ Latest patch level and customizing `/etc/hosts`](#latest-patch-level-and-customizing-etchosts) +* [⇢ ⇢ Additional packages after install](#additional-packages-after-install) +* [⇢ ⇢ ⇢ Helix editor](#helix-editor) +* [⇢ ⇢ ⇢ `doas`](#doas) +* [⇢ ⇢ ⇢ Periodic ZFS snapshotting](#periodic-zfs-snapshotting) +* [⇢ ⇢ ⇢ Uptime tracking](#uptime-tracking) +* [⇢ Hardware check](#hardware-check) +* [⇢ ⇢ Ethernet](#ethernet) +* [⇢ ⇢ RAM](#ram) +* [⇢ ⇢ CPUs](#cpus) +* [⇢ ⇢ CPU throttling](#cpu-throttling) +* [⇢ Conclusion](#conclusion) + +# Deciding on the hardware Note that the OpenBSD VMs included in the f3s setup (which will be used later in this blog series for internet ingress - as you know from the first part of this blog series) are already there. These are virtual machines that I rent at OpenBSD Amsterdam and Hetzner. @@ -46,7 +50,7 @@ This means that the FreeBSD boxes need to be covered, which will later be runnin I've been considering whether to use Raspberry Pis or look for alternatives. It turns out that complete N100-based mini-computers aren't much more expensive than Raspberry Pi 5s, and they don't require assembly. Furthermore, I like that they are AMD64 and not ARM-based, which increases compatibility with some applications (e.g., I might want to virtualize Windows (via bhyve) on one of those, though that's out of scope for this blog series). -### Not ARM but Intel N100 +## Not ARM but Intel N100 I needed something compact, efficient, and capable enough to handle the demands of a small-scale Kubernetes cluster and preferably something I don't have to assemble a lot. After researching, I decided on the Beelink S12 Pro with Intel N100 CPUs. @@ -71,7 +75,7 @@ The Beelink comes with the following specs: I bought three (3) of them for the cluster I intend to build. -### Beelink unboxing +## Beelink unboxing Unboxing was uneventful. Every Beelink PC came with: @@ -84,15 +88,15 @@ Unboxing was uneventful. Every Beelink PC came with: Overall, I love the small form factor. -### Network switch +## Network switch I went with the tp-link mini 5-port switch, as I had a spare one available. That switch will be plugged into my wall ethernet port, which connects directly to my fiber internet router with 100 Mbit/s down and 50 Mbit/s upload speed. [![Switch](./f3s-kubernetes-with-freebsd-part-2/switch.jpg "Switch")](./f3s-kubernetes-with-freebsd-part-2/switch.jpg) -## Installing FreeBSD +# Installing FreeBSD -### Base install +## Base install First, I downloaded the boot-only ISO of the latest FreeBSD release and dumped it on a USB stick via my Fedora laptop: @@ -116,7 +120,7 @@ After doing all that three times (once for each Beelink PC), I had three ready-t [![Beelink installation](./f3s-kubernetes-with-freebsd-part-2/f3s-collage2.jpg "Beelink installation")](./f3s-kubernetes-with-freebsd-part-2/f3s-collage2.jpg) -### Latest patch level and customizing `/etc/hosts` +## Latest patch level and customizing `/etc/hosts` After the first boot, I upgraded to the latest FreeBSD patch level as follows: @@ -135,7 +139,7 @@ root@f0:~ # cat <>/etc/hosts END ``` -### Additional packages after install +## Additional packages after install After that, I installed the following additional packages: @@ -143,14 +147,20 @@ After that, I installed the following additional packages: root@f0:~ # pkg install helix doas zfs-periodic uptimed ``` +### Helix editor + Helix? It's my favourite text editor. I have nothing against `vi` but like `hx` (Helix) more! +### `doas` + `doas`? It's a pretty neat (and KISS) replacement for `sudo`. It has far fewer features than `sudo`, which is supposed to make it more secure. Its origin is the OpenBSD project. For `doas`, I accepted the default configuration (where users in the `wheel` group are allowed to run commands as `root`): ```sh root@f0:~ # cp /usr/local/etc/doas.conf.sample /usr/local/etc/doas.conf ``` +### Periodic ZFS snapshotting + `zfs-periodic` is a nifty tool for automatically creating ZFS snapshots. I decided to go with the following configuration here: ```sh @@ -174,6 +184,8 @@ root@f0:~ # sysrc monthly_zfs_snapshot_keep=6 monthly_zfs_snapshot_keep: 2 -> 6 ``` +### Uptime tracking + `uptimed`? I like to track my uptimes. This is how I configured the daemon: ```sh @@ -207,9 +219,9 @@ This is how I track the uptimes for all of my host: [Unveiling `guprecords.raku`: Global Uptime Records with Raku](./2023-05-01-unveiling-guprecords:-uptime-records-with-raku.md) -## Hardware check +# Hardware check -### Ethernet +## Ethernet Works. Nothing eventful, really. It's a cheap Realtek chip, but it will do what it is supposed to do. @@ -227,7 +239,7 @@ re0: flags=1008843 metric 0 mtu nd6 options=23 ``` -### RAM +## RAM All there: @@ -237,7 +249,7 @@ hw.physmem: 16902905856 ``` -### CPUs +## CPUs They work: @@ -249,7 +261,7 @@ dev.cpu.1.freq: 604 dev.cpu.0.freq: 604 ``` -### CPU throttling +## CPU throttling With `powerd` running, CPU freq is dowthrottled when the box isn't jam-packed. To stress it a bit, I run `ubench` to see the frequencies being unthrottled again: @@ -268,7 +280,7 @@ Idle, all three Beelinks plus the switch consumed 26.2W. But with `ubench` stres [![Idle consumption.](./f3s-kubernetes-with-freebsd-part-2/watt.jpg "Idle consumption.")](./f3s-kubernetes-with-freebsd-part-2/watt.jpg) -## Conclusion +# Conclusion The Beelink S12 Pro with Intel N100 CPUs checks all the boxes for a k3s project: Compact, efficient, expandable, and affordable. Its compatibility with both Linux and FreeBSD makes it versatile for other use cases, whether as part of your cluster or as a standalone system. If you’re looking for hardware that punches above its weight for Kubernetes, this little device deserves a spot on your shortlist. -- cgit v1.2.3 From facc83ff8cd77c1f38a4644aa5634944ef467d91 Mon Sep 17 00:00:00 2001 From: Paul Buetow Date: Thu, 5 Dec 2024 11:32:22 +0200 Subject: Update content for md --- gemfeed/2024-12-03-f3s-kubernetes-with-freebsd-part-2.md | 13 ++++++++++--- 1 file changed, 10 insertions(+), 3 deletions(-) (limited to 'gemfeed') diff --git a/gemfeed/2024-12-03-f3s-kubernetes-with-freebsd-part-2.md b/gemfeed/2024-12-03-f3s-kubernetes-with-freebsd-part-2.md index 710b6b5b..23dd19fa 100644 --- a/gemfeed/2024-12-03-f3s-kubernetes-with-freebsd-part-2.md +++ b/gemfeed/2024-12-03-f3s-kubernetes-with-freebsd-part-2.md @@ -27,7 +27,7 @@ Let's continue... * [⇢ Installing FreeBSD](#installing-freebsd) * [⇢ ⇢ Base install](#base-install) * [⇢ ⇢ Latest patch level and customizing `/etc/hosts`](#latest-patch-level-and-customizing-etchosts) -* [⇢ ⇢ Additional packages after install](#additional-packages-after-install) +* [⇢ ⇢ After install](#after-install) * [⇢ ⇢ ⇢ Helix editor](#helix-editor) * [⇢ ⇢ ⇢ `doas`](#doas) * [⇢ ⇢ ⇢ Periodic ZFS snapshotting](#periodic-zfs-snapshotting) @@ -139,7 +139,7 @@ root@f0:~ # cat <>/etc/hosts END ``` -## Additional packages after install +## After install After that, I installed the following additional packages: @@ -151,6 +151,8 @@ root@f0:~ # pkg install helix doas zfs-periodic uptimed Helix? It's my favourite text editor. I have nothing against `vi` but like `hx` (Helix) more! +[https://helix-editor.com/](https://helix-editor.com/) + ### `doas` `doas`? It's a pretty neat (and KISS) replacement for `sudo`. It has far fewer features than `sudo`, which is supposed to make it more secure. Its origin is the OpenBSD project. For `doas`, I accepted the default configuration (where users in the `wheel` group are allowed to run commands as `root`): @@ -159,6 +161,8 @@ Helix? It's my favourite text editor. I have nothing against `vi` but like `hx` root@f0:~ # cp /usr/local/etc/doas.conf.sample /usr/local/etc/doas.conf ``` +[https://man.openbsd.org/doas](https://man.openbsd.org/doas) + ### Periodic ZFS snapshotting `zfs-periodic` is a nifty tool for automatically creating ZFS snapshots. I decided to go with the following configuration here: @@ -184,6 +188,8 @@ root@f0:~ # sysrc monthly_zfs_snapshot_keep=6 monthly_zfs_snapshot_keep: 2 -> 6 ``` +[https://github.com/ross/zfs-periodic](https://github.com/ross/zfs-periodic) + ### Uptime tracking `uptimed`? I like to track my uptimes. This is how I configured the daemon: @@ -217,7 +223,8 @@ NewRec 0 days, 00:07:33 | since Mon Dec 2 12:21:44 2024 This is how I track the uptimes for all of my host: -[Unveiling `guprecords.raku`: Global Uptime Records with Raku](./2023-05-01-unveiling-guprecords:-uptime-records-with-raku.md) +[Unveiling `guprecords.raku`: Global Uptime Records with Raku-](./2023-05-01-unveiling-guprecords:-uptime-records-with-raku.md) +[https://github.com/rpodgorny/uptimed](https://github.com/rpodgorny/uptimed) # Hardware check -- cgit v1.2.3 From d38bb8203abaa5618cbcaf051bf2ccf1ceb0939d Mon Sep 17 00:00:00 2001 From: Paul Buetow Date: Sun, 15 Dec 2024 13:55:57 +0200 Subject: Update content for md --- gemfeed/2024-12-15-random-helix-themes.md | 57 +++++++++++++++++++++++++++++++ gemfeed/index.md | 1 + 2 files changed, 58 insertions(+) create mode 100644 gemfeed/2024-12-15-random-helix-themes.md (limited to 'gemfeed') diff --git a/gemfeed/2024-12-15-random-helix-themes.md b/gemfeed/2024-12-15-random-helix-themes.md new file mode 100644 index 00000000..187e8d15 --- /dev/null +++ b/gemfeed/2024-12-15-random-helix-themes.md @@ -0,0 +1,57 @@ +# Random Helix themes + +> Published at 2024-12-15T13:55:05+02:00 + +I thought it would be fun to have a random Helix theme every time I open a new shell. Helix is the text editor I use. + +[https://helix-editor.com/](https://helix-editor.com/) + +So I put this into my `zsh` dotfiles (in some `editor.zsh.source` in my `~` directory): + +```sh +export EDITOR=hx +export VISUAL=$EDITOR +export GIT_EDITOR=$EDITOR +export HELIX_CONFIG_DIR=$HOME/.config/helix + +editor::helix::random_theme () { + # May add more theme search paths based on OS. This one is + # for Fedora Linux, but there is also MacOS, etc. + local -r theme_dir=/usr/share/helix/runtime/themes + if [ ! -d $theme_dir ]; then + echo "Helix theme dir $theme_dir doesnt exist" + fi + + local -r config_file=$HELIX_CONFIG_DIR/config.toml + local -r random_theme="$(basename "$(ls $theme_dir \ + | grep -v random.toml | grep .toml | sort -R \ + | head -n 1)" | cut -d. -f1)" + + sed "/^theme =/ { s/.*/theme = \"$random_theme\"/; }" \ + $config_file > $config_file.tmp && + mv $config_file.tmp $config_file +} + +if [ -f $HELIX_CONFIG_DIR/config.toml ]; then + editor::helix::random_theme +fi +``` + +So every time I open a new terminal or shell, `editor::helix::random_theme` gets called, which randomly selects a theme from all installed ones and updates the helix config accordingly. + +```sh +[paul@earth] ~ % editor::helix::random_theme +[paul@earth] ~ % head -n 1 ~/.config/helix/config.toml +theme = "jellybeans" +[paul@earth] ~ % editor::helix::random_theme +[paul@earth] ~ % head -n 1 ~/.config/helix/config.toml +theme = "rose_pine" +[paul@earth] ~ % editor::helix::random_theme +[paul@earth] ~ % head -n 1 ~/.config/helix/config.toml +theme = "noctis" +[paul@earth] ~ % +``` + +I hope you had some fun. E-Mail your comments to `paul@nospam.buetow.org` :-) + +[Back to the main site](../) diff --git a/gemfeed/index.md b/gemfeed/index.md index eaab8e5e..253e7196 100644 --- a/gemfeed/index.md +++ b/gemfeed/index.md @@ -2,6 +2,7 @@ ## To be in the .zone! +[2024-12-15 - Random Helix themes](./2024-12-15-random-helix-themes.md) [2024-12-03 - f3s: Kubernetes with FreeBSD - Part 2: Hardware and base installation](./2024-12-03-f3s-kubernetes-with-freebsd-part-2.md) [2024-11-17 - f3s: Kubernetes with FreeBSD - Part 1: Setting the stage](./2024-11-17-f3s-kubernetes-with-freebsd-part-1.md) [2024-10-24 - 'Staff Engineer' book notes](./2024-10-24-staff-engineer-book-notes.md) -- cgit v1.2.3 From 9dde791c185390b65b3d33c341969c1bec35c7e1 Mon Sep 17 00:00:00 2001 From: Paul Buetow Date: Sun, 15 Dec 2024 14:00:24 +0200 Subject: Update content for md --- gemfeed/2024-12-15-random-helix-themes.md | 1 + 1 file changed, 1 insertion(+) (limited to 'gemfeed') diff --git a/gemfeed/2024-12-15-random-helix-themes.md b/gemfeed/2024-12-15-random-helix-themes.md index 187e8d15..3014a439 100644 --- a/gemfeed/2024-12-15-random-helix-themes.md +++ b/gemfeed/2024-12-15-random-helix-themes.md @@ -20,6 +20,7 @@ editor::helix::random_theme () { local -r theme_dir=/usr/share/helix/runtime/themes if [ ! -d $theme_dir ]; then echo "Helix theme dir $theme_dir doesnt exist" + return 1 fi local -r config_file=$HELIX_CONFIG_DIR/config.toml -- cgit v1.2.3 From b0a62549544385736deaac09c3a73698867c95f3 Mon Sep 17 00:00:00 2001 From: Paul Buetow Date: Sun, 15 Dec 2024 18:50:33 +0200 Subject: Update content for md --- gemfeed/2024-12-15-random-helix-themes.md | 2 +- gemfeed/index.md | 2 +- 2 files changed, 2 insertions(+), 2 deletions(-) (limited to 'gemfeed') diff --git a/gemfeed/2024-12-15-random-helix-themes.md b/gemfeed/2024-12-15-random-helix-themes.md index 3014a439..c3af9589 100644 --- a/gemfeed/2024-12-15-random-helix-themes.md +++ b/gemfeed/2024-12-15-random-helix-themes.md @@ -1,4 +1,4 @@ -# Random Helix themes +# Random Helix Themes > Published at 2024-12-15T13:55:05+02:00 diff --git a/gemfeed/index.md b/gemfeed/index.md index 253e7196..87fb3f92 100644 --- a/gemfeed/index.md +++ b/gemfeed/index.md @@ -2,7 +2,7 @@ ## To be in the .zone! -[2024-12-15 - Random Helix themes](./2024-12-15-random-helix-themes.md) +[2024-12-15 - Random Helix Themes](./2024-12-15-random-helix-themes.md) [2024-12-03 - f3s: Kubernetes with FreeBSD - Part 2: Hardware and base installation](./2024-12-03-f3s-kubernetes-with-freebsd-part-2.md) [2024-11-17 - f3s: Kubernetes with FreeBSD - Part 1: Setting the stage](./2024-11-17-f3s-kubernetes-with-freebsd-part-1.md) [2024-10-24 - 'Staff Engineer' book notes](./2024-10-24-staff-engineer-book-notes.md) -- cgit v1.2.3 From 686897868bd614986de25a9fb8e08b062a6cc6eb Mon Sep 17 00:00:00 2001 From: Paul Buetow Date: Wed, 18 Dec 2024 23:28:25 +0200 Subject: Update content for md --- gemfeed/2024-12-15-random-helix-themes.md | 36 ++++++++++++++++++++++++++++++- 1 file changed, 35 insertions(+), 1 deletion(-) (limited to 'gemfeed') diff --git a/gemfeed/2024-12-15-random-helix-themes.md b/gemfeed/2024-12-15-random-helix-themes.md index c3af9589..1f5ef449 100644 --- a/gemfeed/2024-12-15-random-helix-themes.md +++ b/gemfeed/2024-12-15-random-helix-themes.md @@ -1,6 +1,6 @@ # Random Helix Themes -> Published at 2024-12-15T13:55:05+02:00 +> Published at 2024-12-15T13:55:05+02:00; Last updated 2024-12-18 I thought it would be fun to have a random Helix theme every time I open a new shell. Helix is the text editor I use. @@ -53,6 +53,40 @@ theme = "noctis" [paul@earth] ~ % ``` +## A better version + +> Update 2024-12-18: This is an improved version, which works cross platform (e.g., also on MacOS) and multiple theme directories: + +```sh +export EDITOR=hx +export VISUAL=$EDITOR +export GIT_EDITOR=$EDITOR +export HELIX_CONFIG_DIR=$HOME/.config/helix + +editor::helix::theme::get_random () { + for dir in $(hx --health \ + | awk '/^Runtime directories/ { print $3 }' | tr ';' ' '); do + if [ -d $dir/themes ]; then + ls $dir/themes + fi + done | grep -F .toml | sort -R | head -n 1 | cut -d. -f1 +} + +editor::helix::theme::set () { + local -r theme="$1"; shift + + local -r config_file=$HELIX_CONFIG_DIR/config.toml + + sed "/^theme =/ { s/.*/theme = \"$theme\"/; }" \ + $config_file > $config_file.tmp && + mv $config_file.tmp $config_file +} + +if [ -f $HELIX_CONFIG_DIR/config.toml ]; then + editor::helix::theme::set $(editor::helix::theme::get_random) +fi +``` + I hope you had some fun. E-Mail your comments to `paul@nospam.buetow.org` :-) [Back to the main site](../) -- cgit v1.2.3 From 9b4fd9646bb3e9c70992a5f782353e8f0aa09832 Mon Sep 17 00:00:00 2001 From: Paul Buetow Date: Mon, 30 Dec 2024 00:06:05 +0200 Subject: Update content for md --- .../2024-07-07-the-stoic-challenge-book-notes.md | 4 +- gemfeed/DRAFT-summary-for-202410-202411-202410.md | 311 +++++++++++++++++++++ 2 files changed, 313 insertions(+), 2 deletions(-) create mode 100644 gemfeed/DRAFT-summary-for-202410-202411-202410.md (limited to 'gemfeed') diff --git a/gemfeed/2024-07-07-the-stoic-challenge-book-notes.md b/gemfeed/2024-07-07-the-stoic-challenge-book-notes.md index cb9b3294..395ad2e8 100644 --- a/gemfeed/2024-07-07-the-stoic-challenge-book-notes.md +++ b/gemfeed/2024-07-07-the-stoic-challenge-book-notes.md @@ -19,11 +19,11 @@ These are my personal takeaways after reading "The Stoic Challenge: A Philosoph ## Table of Contents * [⇢ "The Stoic Challenge" book notes](#the-stoic-challenge-book-notes) -* [⇢ ⇢ Got sets you up for a challenge](#got-sets-you-up-for-a-challenge) +* [⇢ ⇢ God sets you up for a challenge](#god-sets-you-up-for-a-challenge) * [⇢ ⇢ Negative visualization](#negative-visualization) * [⇢ ⇢ Oh, nice trick, you stoic "god"! ;-)](#oh-nice-trick-you-stoic-god--) -## Got sets you up for a challenge +## God sets you up for a challenge Gods set you up for a challenge to see how resilient you are. Is getting angry worth the price? If you stay calm then you can find the optimal workaround for the obstacle. Stay calm even with big setbacks. Practice minimalism of negative emotions. diff --git a/gemfeed/DRAFT-summary-for-202410-202411-202410.md b/gemfeed/DRAFT-summary-for-202410-202411-202410.md new file mode 100644 index 00000000..68bfb94c --- /dev/null +++ b/gemfeed/DRAFT-summary-for-202410-202411-202410.md @@ -0,0 +1,311 @@ +# Summary for 202410 202411 202412 + +## Table of Contents + +* [⇢ Summary for 202410 202411 202412](#summary-for-202410-202411-202412) +* [⇢ ⇢ October 2024](#october-2024) +* [⇢ ⇢ ⇢ First on-call experience in a startup. Doesn't ...](#first-on-call-experience-in-a-startup-doesn-t-) +* [⇢ ⇢ ⇢ Reviewing your own PR or MR before asking ...](#reviewing-your-own-pr-or-mr-before-asking-) +* [⇢ ⇢ ⇢ Fun with defer in ` ⇢golang`, I did't know, that ...](#fun-with-defer-in--golang-i-did-t-know-that-) +* [⇢ ⇢ ⇢ I have been in incidents. Understandably, ...](#i-have-been-in-incidents-understandably-) +* [⇢ ⇢ ⇢ Little tips using strings in ` ⇢golang` and I ...](#little-tips-using-strings-in--golang-and-i-) +* [⇢ ⇢ ⇢ Reading this post about ` ⇢rust` (especially the ...](#reading-this-post-about--rust-especially-the-) +* [⇢ ⇢ ⇢ The opposite of ` ⇢ChaosMonkey` ... ...](#the-opposite-of--chaosmonkey--) +* [⇢ ⇢ November 2024](#november-2024) +* [⇢ ⇢ ⇢ I just became a Silver Patreon for OSnews. What ...](#i-just-became-a-silver-patreon-for-osnews-what-) +* [⇢ ⇢ ⇢ Until now, I wasn't aware, that Go is under a ...](#until-now-i-wasn-t-aware-that-go-is-under-a-) +* [⇢ ⇢ ⇢ These are some book notes from "Staff Engineer" ...](#these-are-some-book-notes-from-staff-engineer-) +* [⇢ ⇢ ⇢ Looking at ` ⇢Kubernetes`, it's pretty much ...](#looking-at--kubernetes-it-s-pretty-much-) +* [⇢ ⇢ ⇢ There has been an outage at the upstream ...](#there-has-been-an-outage-at-the-upstream-) +* [⇢ ⇢ ⇢ One of the more confusing parts in Go, nil ...](#one-of-the-more-confusing-parts-in-go-nil-) +* [⇢ ⇢ ⇢ Agreeably, writing down with Diagrams helps you ...](#agreeably-writing-down-with-diagrams-helps-you-) +* [⇢ ⇢ ⇢ I like the idea of types in Ruby. Raku is ...](#i-like-the-idea-of-types-in-ruby-raku-is-) +* [⇢ ⇢ ⇢ So, ` ⇢Haskell` is better suited for general ...](#so--haskell-is-better-suited-for-general-) +* [⇢ ⇢ ⇢ At first, functional options add a bit of ...](#at-first-functional-options-add-a-bit-of-) +* [⇢ ⇢ ⇢ Revamping my home lab a little bit. ` ⇢freebsd` ...](#revamping-my-home-lab-a-little-bit--freebsd-) +* [⇢ ⇢ ⇢ Revamping my home lab a little bit. ` ⇢freebsd` ...](#revamping-my-home-lab-a-little-bit--freebsd-) +* [⇢ ⇢ ⇢ Wondering to which ` ⇢web` ` ⇢browser` I should ...](#wondering-to-which--web--browser-i-should-) +* [⇢ ⇢ ⇢ eks-node-viewer is a nifty tool, showing the ...](#eks-node-viewer-is-a-nifty-tool-showing-the-) +* [⇢ ⇢ ⇢ Have put more Photos on - On my static photo ...](#have-put-more-photos-on---on-my-static-photo-) +* [⇢ ⇢ ⇢ In Go, passing pointers are not automatically ...](#in-go-passing-pointers-are-not-automatically-) +* [⇢ ⇢ ⇢ Myself being part of an on-call rotations over ...](#myself-being-part-of-an-on-call-rotations-over-) +* [⇢ ⇢ ⇢ Feels good to code in my old love ` ⇢Perl` again ...](#feels-good-to-code-in-my-old-love--perl-again-) +* [⇢ ⇢ ⇢ This is an interactive summary of the Go ...](#this-is-an-interactive-summary-of-the-go-) +* [⇢ ⇢ December 2024](#december-2024) +* [⇢ ⇢ ⇢ Thats unexpected, you cant remove a NaN key ...](#thats-unexpected-you-cant-remove-a-nan-key-) +* [⇢ ⇢ ⇢ My second blog post about revamping my home lab ...](#my-second-blog-post-about-revamping-my-home-lab-) +* [⇢ ⇢ ⇢ Very insightful article about tech hiring in ...](#very-insightful-article-about-tech-hiring-in-) +* [⇢ ⇢ ⇢ for ` ⇢bpf` ` ⇢ebpf` performance debugging, have ...](#for--bpf--ebpf-performance-debugging-have-) +* [⇢ ⇢ ⇢ 89 things he/she knows about Git commits is a ...](#89-things-heshe-knows-about-git-commits-is-a-) +* [⇢ ⇢ ⇢ I found that working on multiple side projects ...](#i-found-that-working-on-multiple-side-projects-) +* [⇢ ⇢ ⇢ Agreed? Agreed. Besides ` ⇢Ruby`, I would also ...](#agreed-agreed-besides--ruby-i-would-also-) +* [⇢ ⇢ ⇢ Plan9 assembly format in Go, but wait, it's not ...](#plan9-assembly-format-in-go-but-wait-it-s-not-) +* [⇢ ⇢ ⇢ This is a neat blog post about the Helix text ...](#this-is-a-neat-blog-post-about-the-helix-text-) +* [⇢ ⇢ ⇢ This blog post is basically a rant against ...](#this-blog-post-is-basically-a-rant-against-) +* [⇢ ⇢ ⇢ Quick trick to get Helix themes selected ...](#quick-trick-to-get-helix-themes-selected-) +* [⇢ ⇢ ⇢ Example where complexity attacks you from ...](#example-where-complexity-attacks-you-from-) +* [⇢ ⇢ ⇢ LLMs for Ops? Summaries of logs, probabilities ...](#llms-for-ops-summaries-of-logs-probabilities-) +* [⇢ ⇢ ⇢ Excellent article about your dream Product ...](#excellent-article-about-your-dream-product-) +* [⇢ ⇢ ⇢ I just finished reading all chapters of CPU ...](#i-just-finished-reading-all-chapters-of-cpu-) +* [⇢ ⇢ ⇢ Indeed, useful to know this stuff! ` ⇢sre` ...](#indeed-useful-to-know-this-stuff--sre-) +* [⇢ ⇢ ⇢ It's the small things, which make Unix like ...](#it-s-the-small-things-which-make-unix-like-) + +## October 2024 + +### First on-call experience in a startup. Doesn't ... + +First on-call experience in a startup. Doesn't sound a lot of fun! But the lessons were learned! `#sre` + +[https://ntietz.com/blog/lessons-from-my-first-on-call/](https://ntietz.com/blog/lessons-from-my-first-on-call/) + +### Reviewing your own PR or MR before asking ... + +Reviewing your own PR or MR before asking others to review it makes a lot of sense. Have seen so many silly mistakes which would have been avoided. Saving time for the real reviewer. + +[https://www.jvt.me/posts/2019/01/12/self-code-review/](https://www.jvt.me/posts/2019/01/12/self-code-review/) + +### Fun with defer in `#golang`, I did't know, that ... + +Fun with defer in `#golang`, I did't know, that a defer object can either be heap or stack allocated. And there are some rules for inlining, too. + +[https://victoriametrics.com/blog/defer-in-go/](https://victoriametrics.com/blog/defer-in-go/) + +### I have been in incidents. Understandably, ... + +I have been in incidents. Understandably, everyone wants the issue to be resolved as quickly and others want to know how long TTR will be. IMHO, providing no estimates at all is no solution either. So maybe give a rough estimate but clearly communicate that the estimate is rough and that X, Y, and Z can interfere, meaning there is a chance it will take longer to resolve the incident. Just my thought. What's yours? + +[https://firehydrant.com/blog/hot-...de-incident-resolution-estimates/](https://firehydrant.com/blog/hot-take-dont-provide-incident-resolution-estimates/) + +### Little tips using strings in `#golang` and I ... + +Little tips using strings in `#golang` and I personally think one must look more into the std lib (not just for strings, also for slices, maps,...), there are tons of useful helper functions. + +[https://www.calhoun.io/6-tips-for-using-strings-in-go/](https://www.calhoun.io/6-tips-for-using-strings-in-go/) + +### Reading this post about `#rust` (especially the ... + +Reading this post about `#rust` (especially the first part), I think I made a good choice in deciding to dive into `#golang` instead. There was a point where I wanted to learn a new programming language, and Rust was on my list of choices. I think the Go project does a much better job of deciding what goes into the language and how. What are your thoughts? + +[https://josephg.com/blog/rewriting-rust/](https://josephg.com/blog/rewriting-rust/) + +### The opposite of `#ChaosMonkey` ... ... + +The opposite of `#ChaosMonkey` ... automatically repairing and healing services helping to reduce manual toil work. Runbooks and scripts are only the first step, followed by a fully blown service written in Go. Could be useful, but IMHO why not rather address the root causes of the manual toil work? `#sre` + +[https://blog.cloudflare.com/nl-nl...latform-resilience-at-cloudflare/](https://blog.cloudflare.com/nl-nl/improving-platform-resilience-at-cloudflare/) + +## November 2024 + +### I just became a Silver Patreon for OSnews. What ... + +I just became a Silver Patreon for OSnews. What is OSnews? It is an independent news site about IT. It is slightly independent and, at times, alternative. I have enjoyed it since my early student days. This one and other projects I financially support are listed here: + +[https://foo.zone/gemfeed/2024-09-07-projects-i-support.html](https://foo.zone/gemfeed/2024-09-07-projects-i-support.html) + +### Until now, I wasn't aware, that Go is under a ... + +Until now, I wasn't aware, that Go is under a BSD-style license (3-clause as it seems). Neat. I don't know why, but I always was under the impression it would be MIT. `#bsd` `#golang` + +[https://go.dev/LICENSE](https://go.dev/LICENSE) + +### These are some book notes from "Staff Engineer" ... + +These are some book notes from "Staff Engineer" – there is some really good insight into what is expected from a Staff Engineer and beyond in the industry. I wish I had read the book earlier. + +[https://foo.zone/gemfeed/2024-10-24-staff-engineer-book-notes.html](https://foo.zone/gemfeed/2024-10-24-staff-engineer-book-notes.html) + +### Looking at `#Kubernetes`, it's pretty much ... + +Looking at `#Kubernetes`, it's pretty much following the Unix way of doing things. It has many tools, but each tool has its own single purpose: DNS, scheduling, container runtime, various controllers, networking, observability, alerting, and more services in the control plane. Everything is managed by different services or plugins, mostly running in their dedicated pods. They don't communicate through pipes, but network sockets, though. `#k8s` + +### There has been an outage at the upstream ... + +There has been an outage at the upstream network provider for OpenBSD.Amsterdam (hoster, I am using). This was the first real-world test for my KISS HA setup, and it worked flawlessly! All my sites and services failed over automatically to my other `#OpenBSD` VM! + +[https://foo.zone/gemfeed/2024-04-...gh-availability-with-OpenBSD.html](https://foo.zone/gemfeed/2024-04-01-KISS-high-availability-with-OpenBSD.html) +[https://openbsd.amsterdam/](https://openbsd.amsterdam/) + +### One of the more confusing parts in Go, nil ... + +One of the more confusing parts in Go, nil values vs nil errors: `#golang` + +[https://unexpected-go.com/nil-errors-that-are-non-nil-errors.html](https://unexpected-go.com/nil-errors-that-are-non-nil-errors.html) + +### Agreeably, writing down with Diagrams helps you ... + +Agreeably, writing down with Diagrams helps you to think things more through. And keeps others on the same page. Only worth for projects from a certain size, IMHO. + +[https://ntietz.com/blog/reasons-to-write-design-docs/](https://ntietz.com/blog/reasons-to-write-design-docs/) + +### I like the idea of types in Ruby. Raku is ... + +I like the idea of types in Ruby. Raku is supports that already, but in Ruby, you must specify the types in a separate .rbs file, which is, in my opinion, cumbersome and is a reason not to use it extensively for now. I believe there are efforts to embed the type information in the standard .rb files, and that the .rbs is just an experiment to see how types could work out without introducing changes into the core Ruby language itself right now? `#Ruby` `#RakuLang` + +[https://github.com/ruby/rbs](https://github.com/ruby/rbs) + +### So, `#Haskell` is better suited for general ... + +So, `#Haskell` is better suited for general purpose than `#Rust`? I thought deploying something in Haskell means publishing an academic paper :-) Interesting rant about Rust, though: + +[https://chrisdone.com/posts/rust/](https://chrisdone.com/posts/rust/) + +### At first, functional options add a bit of ... + +At first, functional options add a bit of boilerplate, but they turn out to be quite neat, especially when you have very long parameter lists that need to be made neat and tidy. `#golang` + +[https://www.calhoun.io/using-func...instead-of-method-chaining-in-go/](https://www.calhoun.io/using-functional-options-instead-of-method-chaining-in-go/) + +### Revamping my home lab a little bit. `#freebsd` ... + +Revamping my home lab a little bit. `#freebsd` `#bhyve` `#rocky` `#linux` `#vm` `#k3s` `#kuberbetes` `#wireguard` `#zfs` `#nfs` `#ha` `#relayd` `#k8s` `#selfhosting` `#self`-hosting `#homelab` `#home`-lab + +[https://foo.zone/gemfeed/2024-11-...bernetes-with-freebsd-part-1.html](https://foo.zone/gemfeed/2024-11-17-f3s-kubernetes-with-freebsd-part-1.html) + +### Revamping my home lab a little bit. `#freebsd` ... + +Revamping my home lab a little bit. `#freebsd` `#bhyve` `#rocky` `#linux` `#vm` `#k3s` `#kubernetes` `#wireguard` `#zfs` `#nfs` `#ha` `#relayd` `#k8s` `#selfhosting` `#homelab` + +[https://foo.zone/gemfeed/2024-11-...bernetes-with-freebsd-part-1.html](https://foo.zone/gemfeed/2024-11-17-f3s-kubernetes-with-freebsd-part-1.html) + +### Wondering to which `#web` `#browser` I should ... + +Wondering to which `#web` `#browser` I should switch now personally ... + +[https://www.osnews.com/story/1411...cy-for-open-web-privacy-and-more/](https://www.osnews.com/story/141100/mozilla-foundation-lays-off-30-of-its-employees-ends-advocacy-for-open-web-privacy-and-more/) + +### eks-node-viewer is a nifty tool, showing the ... + +eks-node-viewer is a nifty tool, showing the compute nodes currently in use in the `#EKS` cluster. especially useful when dynamically allocating nodes with `#karpenter` or auto scaling groups. + +[https://github.com/awslabs/eks-node-viewer](https://github.com/awslabs/eks-node-viewer) + +### Have put more Photos on - On my static photo ... + +Have put more Photos on - On my static photo sites - Generated with a `#bash` script + +[https://irregular.ninja](https://irregular.ninja) + +### In Go, passing pointers are not automatically ... + +In Go, passing pointers are not automatically faster than values. Pointers often force the memory to be allocated on the heap, adding GC overhad. With values, Go can determine whether to put the memory on the stack instead. But with large structs/objects (how you want to call them) or if you want to modify state, then pointers are the semantic to use. `#golang` + +[https://blog.boot.dev/golang/pointers-faster-than-values/](https://blog.boot.dev/golang/pointers-faster-than-values/) + +### Myself being part of an on-call rotations over ... + +Myself being part of an on-call rotations over my whole professional life, just have learned this lesson "Tell people who are new to on-call: Just have fun" :-) This is a neat blog post to read: + +[https://ntietz.com/blog/what-i-tell-people-new-to-oncall/](https://ntietz.com/blog/what-i-tell-people-new-to-oncall/) + +### Feels good to code in my old love `#Perl` again ... + +Feels good to code in my old love `#Perl` again after a while. I am implementing a log parser for generating site stats of my personal homepage! :-) @Perl + +### This is an interactive summary of the Go ... + +This is an interactive summary of the Go release, with a lot of examples utilising iterators in the slices and map packages. Love it! `#golang` + +[https://antonz.org/go-1-23/](https://antonz.org/go-1-23/) + +## December 2024 + +### Thats unexpected, you cant remove a NaN key ... + +Thats unexpected, you cant remove a NaN key from a map without clearing it! `#golang` + +[https://unexpected-go.com/you-can...om-a-map-without-clearing-it.html](https://unexpected-go.com/you-cant-remove-a-nan-key-from-a-map-without-clearing-it.html) + +### My second blog post about revamping my home lab ... + +My second blog post about revamping my home lab a little bit just hit the net. `#FreeBSD` `#ZFS` `#n100` `#k8s` `#k3s` `#kubernetes` + +[https://foo.zone/gemfeed/2024-12-...bernetes-with-freebsd-part-2.html](https://foo.zone/gemfeed/2024-12-03-f3s-kubernetes-with-freebsd-part-2.html) + +### Very insightful article about tech hiring in ... + +Very insightful article about tech hiring in the age of LLMs. As an interviewer, I have experienced some of the scrnarios already first hand... + +[https://newsletter.pragmaticengin...m/p/how-genai-changes-tech-hiring](https://newsletter.pragmaticengineer.com/p/how-genai-changes-tech-hiring) + +### for `#bpf` `#ebpf` performance debugging, have ... + +for `#bpf` `#ebpf` performance debugging, have a look at bpftop from Netflix. A neat tool showing you the estimated CPU time and other performance statistics for all the BPF programs currently loaded into the `#linux` kernel. Highly recommend! + +[https://github.com/Netflix/bpftop](https://github.com/Netflix/bpftop) + +### 89 things he/she knows about Git commits is a ... + +89 things he/she knows about Git commits is a neat list of `#Git` wisdoms + +[https://www.jvt.me/posts/2024/07/12/things-know-commits/](https://www.jvt.me/posts/2024/07/12/things-know-commits/) + +### I found that working on multiple side projects ... + +I found that working on multiple side projects concurrently is better than concentrating on just one. This seems inefficient at first, but whenever you tend to lose motivation, you can temporarily switch to another one with full élan. However, remember to stop starting and start finishing. This doesn't mean you should be working on 10+ (and a growing list of) side projects concurrently! Select your projects and commit to finishing them before starting the next thing. For example, my current limit of concurrent side projects is around five. + +### Agreed? Agreed. Besides `#Ruby`, I would also ... + +Agreed? Agreed. Besides `#Ruby`, I would also add `#RakuLang` and `#Perl` @Perl to the list of languages that are great for shell scripts - "Making Easy Things Easy and Hard Things Possible" + +[https://lucasoshiro.github.io/posts-en/2024-06-17-ruby-shellscript/](https://lucasoshiro.github.io/posts-en/2024-06-17-ruby-shellscript/) + +### Plan9 assembly format in Go, but wait, it's not ... + +Plan9 assembly format in Go, but wait, it's not the Operating System Plan9! `#golang` `#rabbithole` + +[https://www.osnews.com/story/1409...emo-speeding-up-calculations-450/](https://www.osnews.com/story/140941/go-plan9-memo-speeding-up-calculations-450/) + +### This is a neat blog post about the Helix text ... + +This is a neat blog post about the Helix text editor, to which I personally switched around a year ago (from NeoVim). I should blog about my experience as well. To summarize: I am using it together with the terminal multiplexer `#tmux`. It doesn't bother me that Helix is purely terminal-based and therefore everything has to be in the same font. `#HelixEditor` + +[https://jonathan-frere.com/posts/helix/](https://jonathan-frere.com/posts/helix/) + +### This blog post is basically a rant against ... + +This blog post is basically a rant against DataDog... Personally, I don't have much experience with DataDog (actually, I have never used it), but one reason to work with logs at my day job (with over 2,000 physical server machines) and to be cost-effective is by using dtail! `#dtail` `#logs` `#logmanagement` + +[https://crys.site/blog/2024/reinventint-the-weel/](https://crys.site/blog/2024/reinventint-the-weel/) +[https://dtail.dev](https://dtail.dev) + +### Quick trick to get Helix themes selected ... + +Quick trick to get Helix themes selected randomly `#HelixEditor` + +[https://foo.zone/gemfeed/2024-12-15-random-helix-themes.html](https://foo.zone/gemfeed/2024-12-15-random-helix-themes.html) + +### Example where complexity attacks you from ... + +Example where complexity attacks you from behind `#k8s` `#kubernetes` `#OpenAI` + +[https://surfingcomplexity.blog/20...-openai-public-incident-write-up/](https://surfingcomplexity.blog/2024/12/14/quick-takes-on-the-recent-openai-public-incident-write-up/) + +### LLMs for Ops? Summaries of logs, probabilities ... + +LLMs for Ops? Summaries of logs, probabilities about correctness, auto-generating Ansible, some uses cases are there. Wouldn't trust it fully, though. + +[https://youtu.be/WodaffxVq-E?si=noY0egrfl5izCSQI](https://youtu.be/WodaffxVq-E?si=noY0egrfl5izCSQI) + +### Excellent article about your dream Product ... + +Excellent article about your dream Product Manager: Why every software team needs a product manager to thrive via @wallabagapp + +[https://testdouble.com/insights/w...elerate-improve-software-delivery](https://testdouble.com/insights/why-product-managers-accelerate-improve-software-delivery) + +### I just finished reading all chapters of CPU ... + +I just finished reading all chapters of CPU land: ... not claiming to remember every detail, but it is a great refresher how CPUs and operating systems actually work under the hood when you execute a program, which we tend to forget in our higher abstraction world. I liked the "story" and some of the jokes along the way! Size wise, it is pretty digestable (not talking about books, but only 7 web articles/chapters)! `#cpu` `#linux` `#unix` `#kernel` `#macOS` + +[https://cpu.land/](https://cpu.land/) + +### Indeed, useful to know this stuff! `#sre` ... + +Indeed, useful to know this stuff! `#sre` + +[https://biriukov.dev/docs/resolve...vers-and-dual-stack-applications/](https://biriukov.dev/docs/resolver-dual-stack-application/0-sre-should-know-about-gnu-linux-resolvers-and-dual-stack-applications/) + +### It's the small things, which make Unix like ... + +It's the small things, which make Unix like systems, like GNU/Linux, interesting. Didn't know about this `#GNU` `#Tar` behaviour yet: + +[https://xeiaso.net/notes/2024/pop-quiz-tar/15110](https://xeiaso.net/notes/2024/pop-quiz-tar/15110) -- cgit v1.2.3 From 15192136a41374ab8f9284da680d5ff1ad6793e9 Mon Sep 17 00:00:00 2001 From: Paul Buetow Date: Mon, 30 Dec 2024 10:22:24 +0200 Subject: Update content for md --- gemfeed/DRAFT-summary-for-202410-202411-202410.md | 26 +++++++++++------------ 1 file changed, 13 insertions(+), 13 deletions(-) (limited to 'gemfeed') diff --git a/gemfeed/DRAFT-summary-for-202410-202411-202410.md b/gemfeed/DRAFT-summary-for-202410-202411-202410.md index 68bfb94c..0f1aefc4 100644 --- a/gemfeed/DRAFT-summary-for-202410-202411-202410.md +++ b/gemfeed/DRAFT-summary-for-202410-202411-202410.md @@ -6,39 +6,39 @@ * [⇢ ⇢ October 2024](#october-2024) * [⇢ ⇢ ⇢ First on-call experience in a startup. Doesn't ...](#first-on-call-experience-in-a-startup-doesn-t-) * [⇢ ⇢ ⇢ Reviewing your own PR or MR before asking ...](#reviewing-your-own-pr-or-mr-before-asking-) -* [⇢ ⇢ ⇢ Fun with defer in ` ⇢golang`, I did't know, that ...](#fun-with-defer-in--golang-i-did-t-know-that-) +* [⇢ ⇢ ⇢ Fun with defer in `#golang`, I did't know, that ...](#fun-with-defer-in-golang-i-did-t-know-that-) * [⇢ ⇢ ⇢ I have been in incidents. Understandably, ...](#i-have-been-in-incidents-understandably-) -* [⇢ ⇢ ⇢ Little tips using strings in ` ⇢golang` and I ...](#little-tips-using-strings-in--golang-and-i-) -* [⇢ ⇢ ⇢ Reading this post about ` ⇢rust` (especially the ...](#reading-this-post-about--rust-especially-the-) -* [⇢ ⇢ ⇢ The opposite of ` ⇢ChaosMonkey` ... ...](#the-opposite-of--chaosmonkey--) +* [⇢ ⇢ ⇢ Little tips using strings in `#golang` and I ...](#little-tips-using-strings-in-golang-and-i-) +* [⇢ ⇢ ⇢ Reading this post about `#rust` (especially the ...](#reading-this-post-about-rust-especially-the-) +* [⇢ ⇢ ⇢ The opposite of `#ChaosMonkey` ... ...](#the-opposite-of-chaosmonkey--) * [⇢ ⇢ November 2024](#november-2024) * [⇢ ⇢ ⇢ I just became a Silver Patreon for OSnews. What ...](#i-just-became-a-silver-patreon-for-osnews-what-) * [⇢ ⇢ ⇢ Until now, I wasn't aware, that Go is under a ...](#until-now-i-wasn-t-aware-that-go-is-under-a-) * [⇢ ⇢ ⇢ These are some book notes from "Staff Engineer" ...](#these-are-some-book-notes-from-staff-engineer-) -* [⇢ ⇢ ⇢ Looking at ` ⇢Kubernetes`, it's pretty much ...](#looking-at--kubernetes-it-s-pretty-much-) +* [⇢ ⇢ ⇢ Looking at `#Kubernetes`, it's pretty much ...](#looking-at-kubernetes-it-s-pretty-much-) * [⇢ ⇢ ⇢ There has been an outage at the upstream ...](#there-has-been-an-outage-at-the-upstream-) * [⇢ ⇢ ⇢ One of the more confusing parts in Go, nil ...](#one-of-the-more-confusing-parts-in-go-nil-) * [⇢ ⇢ ⇢ Agreeably, writing down with Diagrams helps you ...](#agreeably-writing-down-with-diagrams-helps-you-) * [⇢ ⇢ ⇢ I like the idea of types in Ruby. Raku is ...](#i-like-the-idea-of-types-in-ruby-raku-is-) -* [⇢ ⇢ ⇢ So, ` ⇢Haskell` is better suited for general ...](#so--haskell-is-better-suited-for-general-) +* [⇢ ⇢ ⇢ So, `#Haskell` is better suited for general ...](#so-haskell-is-better-suited-for-general-) * [⇢ ⇢ ⇢ At first, functional options add a bit of ...](#at-first-functional-options-add-a-bit-of-) -* [⇢ ⇢ ⇢ Revamping my home lab a little bit. ` ⇢freebsd` ...](#revamping-my-home-lab-a-little-bit--freebsd-) -* [⇢ ⇢ ⇢ Revamping my home lab a little bit. ` ⇢freebsd` ...](#revamping-my-home-lab-a-little-bit--freebsd-) -* [⇢ ⇢ ⇢ Wondering to which ` ⇢web` ` ⇢browser` I should ...](#wondering-to-which--web--browser-i-should-) +* [⇢ ⇢ ⇢ Revamping my home lab a little bit. `#freebsd` ...](#revamping-my-home-lab-a-little-bit-freebsd-) +* [⇢ ⇢ ⇢ Revamping my home lab a little bit. `#freebsd` ...](#revamping-my-home-lab-a-little-bit-freebsd-) +* [⇢ ⇢ ⇢ Wondering to which `#web` `#browser` I should ...](#wondering-to-which-web-browser-i-should-) * [⇢ ⇢ ⇢ eks-node-viewer is a nifty tool, showing the ...](#eks-node-viewer-is-a-nifty-tool-showing-the-) * [⇢ ⇢ ⇢ Have put more Photos on - On my static photo ...](#have-put-more-photos-on---on-my-static-photo-) * [⇢ ⇢ ⇢ In Go, passing pointers are not automatically ...](#in-go-passing-pointers-are-not-automatically-) * [⇢ ⇢ ⇢ Myself being part of an on-call rotations over ...](#myself-being-part-of-an-on-call-rotations-over-) -* [⇢ ⇢ ⇢ Feels good to code in my old love ` ⇢Perl` again ...](#feels-good-to-code-in-my-old-love--perl-again-) +* [⇢ ⇢ ⇢ Feels good to code in my old love `#Perl` again ...](#feels-good-to-code-in-my-old-love-perl-again-) * [⇢ ⇢ ⇢ This is an interactive summary of the Go ...](#this-is-an-interactive-summary-of-the-go-) * [⇢ ⇢ December 2024](#december-2024) * [⇢ ⇢ ⇢ Thats unexpected, you cant remove a NaN key ...](#thats-unexpected-you-cant-remove-a-nan-key-) * [⇢ ⇢ ⇢ My second blog post about revamping my home lab ...](#my-second-blog-post-about-revamping-my-home-lab-) * [⇢ ⇢ ⇢ Very insightful article about tech hiring in ...](#very-insightful-article-about-tech-hiring-in-) -* [⇢ ⇢ ⇢ for ` ⇢bpf` ` ⇢ebpf` performance debugging, have ...](#for--bpf--ebpf-performance-debugging-have-) +* [⇢ ⇢ ⇢ for `#bpf` `#ebpf` performance debugging, have ...](#for-bpf-ebpf-performance-debugging-have-) * [⇢ ⇢ ⇢ 89 things he/she knows about Git commits is a ...](#89-things-heshe-knows-about-git-commits-is-a-) * [⇢ ⇢ ⇢ I found that working on multiple side projects ...](#i-found-that-working-on-multiple-side-projects-) -* [⇢ ⇢ ⇢ Agreed? Agreed. Besides ` ⇢Ruby`, I would also ...](#agreed-agreed-besides--ruby-i-would-also-) +* [⇢ ⇢ ⇢ Agreed? Agreed. Besides `#Ruby`, I would also ...](#agreed-agreed-besides-ruby-i-would-also-) * [⇢ ⇢ ⇢ Plan9 assembly format in Go, but wait, it's not ...](#plan9-assembly-format-in-go-but-wait-it-s-not-) * [⇢ ⇢ ⇢ This is a neat blog post about the Helix text ...](#this-is-a-neat-blog-post-about-the-helix-text-) * [⇢ ⇢ ⇢ This blog post is basically a rant against ...](#this-blog-post-is-basically-a-rant-against-) @@ -47,7 +47,7 @@ * [⇢ ⇢ ⇢ LLMs for Ops? Summaries of logs, probabilities ...](#llms-for-ops-summaries-of-logs-probabilities-) * [⇢ ⇢ ⇢ Excellent article about your dream Product ...](#excellent-article-about-your-dream-product-) * [⇢ ⇢ ⇢ I just finished reading all chapters of CPU ...](#i-just-finished-reading-all-chapters-of-cpu-) -* [⇢ ⇢ ⇢ Indeed, useful to know this stuff! ` ⇢sre` ...](#indeed-useful-to-know-this-stuff--sre-) +* [⇢ ⇢ ⇢ Indeed, useful to know this stuff! `#sre` ...](#indeed-useful-to-know-this-stuff-sre-) * [⇢ ⇢ ⇢ It's the small things, which make Unix like ...](#it-s-the-small-things-which-make-unix-like-) ## October 2024 -- cgit v1.2.3 From dbf9382618cb462d2880846fa8644ac4cd2192e9 Mon Sep 17 00:00:00 2001 From: Paul Buetow Date: Tue, 31 Dec 2024 18:10:59 +0200 Subject: Update content for md --- ...25-01-01-posts-from-october-to-december-2024.md | 324 ++++++++++++++++++++ ...20250101-posts-from-october-to-december-2024.md | 326 +++++++++++++++++++++ gemfeed/index.md | 1 + 3 files changed, 651 insertions(+) create mode 100644 gemfeed/2025-01-01-posts-from-october-to-december-2024.md create mode 100644 gemfeed/20250101-posts-from-october-to-december-2024.md (limited to 'gemfeed') diff --git a/gemfeed/2025-01-01-posts-from-october-to-december-2024.md b/gemfeed/2025-01-01-posts-from-october-to-december-2024.md new file mode 100644 index 00000000..f35f7cc3 --- /dev/null +++ b/gemfeed/2025-01-01-posts-from-october-to-december-2024.md @@ -0,0 +1,324 @@ +# Posts from October to December 2024 + +> Published at 2024-12-31T18:09:58+02:00 + +Happy new year! + +These are my social media posts from the last three months. I keep them here to reflect on them and also to not lose them. Social media networks come and go and are not under my control, but my domain is here to stay. + +These are from Mastodon and LinkedIn. Have a look at my about page for my social media profiles. This list is generated with Gos, my social media platform sharing tool. + +[My about page](../about/index.md) +[https://codeberg.org/snonux/gos](https://codeberg.org/snonux/gos) + +## Table of Contents + +* [⇢ Posts from October to December 2024](#posts-from-october-to-december-2024) +* [⇢ ⇢ October 2024](#october-2024) +* [⇢ ⇢ ⇢ First on-call experience in a startup. Doesn't ...](#first-on-call-experience-in-a-startup-doesn-t-) +* [⇢ ⇢ ⇢ Reviewing your own PR or MR before asking ...](#reviewing-your-own-pr-or-mr-before-asking-) +* [⇢ ⇢ ⇢ Fun with defer in `#golang`, I did't know, that ...](#fun-with-defer-in-golang-i-did-t-know-that-) +* [⇢ ⇢ ⇢ I have been in incidents. Understandably, ...](#i-have-been-in-incidents-understandably-) +* [⇢ ⇢ ⇢ Little tips using strings in `#golang` and I ...](#little-tips-using-strings-in-golang-and-i-) +* [⇢ ⇢ ⇢ Reading this post about `#rust` (especially the ...](#reading-this-post-about-rust-especially-the-) +* [⇢ ⇢ ⇢ The opposite of `#ChaosMonkey` ... ...](#the-opposite-of-chaosmonkey--) +* [⇢ ⇢ November 2024](#november-2024) +* [⇢ ⇢ ⇢ I just became a Silver Patreon for OSnews. What ...](#i-just-became-a-silver-patreon-for-osnews-what-) +* [⇢ ⇢ ⇢ Until now, I wasn't aware, that Go is under a ...](#until-now-i-wasn-t-aware-that-go-is-under-a-) +* [⇢ ⇢ ⇢ These are some book notes from "Staff Engineer" ...](#these-are-some-book-notes-from-staff-engineer-) +* [⇢ ⇢ ⇢ Looking at `#Kubernetes`, it's pretty much ...](#looking-at-kubernetes-it-s-pretty-much-) +* [⇢ ⇢ ⇢ There has been an outage at the upstream ...](#there-has-been-an-outage-at-the-upstream-) +* [⇢ ⇢ ⇢ One of the more confusing parts in Go, nil ...](#one-of-the-more-confusing-parts-in-go-nil-) +* [⇢ ⇢ ⇢ Agreeably, writing down with Diagrams helps you ...](#agreeably-writing-down-with-diagrams-helps-you-) +* [⇢ ⇢ ⇢ I like the idea of types in Ruby. Raku is ...](#i-like-the-idea-of-types-in-ruby-raku-is-) +* [⇢ ⇢ ⇢ So, `#Haskell` is better suited for general ...](#so-haskell-is-better-suited-for-general-) +* [⇢ ⇢ ⇢ At first, functional options add a bit of ...](#at-first-functional-options-add-a-bit-of-) +* [⇢ ⇢ ⇢ Revamping my home lab a little bit. `#freebsd` ...](#revamping-my-home-lab-a-little-bit-freebsd-) +* [⇢ ⇢ ⇢ Wondering to which `#web` `#browser` I should ...](#wondering-to-which-web-browser-i-should-) +* [⇢ ⇢ ⇢ eks-node-viewer is a nifty tool, showing the ...](#eks-node-viewer-is-a-nifty-tool-showing-the-) +* [⇢ ⇢ ⇢ Have put more Photos on - On my static photo ...](#have-put-more-photos-on---on-my-static-photo-) +* [⇢ ⇢ ⇢ In Go, passing pointers are not automatically ...](#in-go-passing-pointers-are-not-automatically-) +* [⇢ ⇢ ⇢ Myself being part of an on-call rotations over ...](#myself-being-part-of-an-on-call-rotations-over-) +* [⇢ ⇢ ⇢ Feels good to code in my old love `#Perl` again ...](#feels-good-to-code-in-my-old-love-perl-again-) +* [⇢ ⇢ ⇢ This is an interactive summary of the Go ...](#this-is-an-interactive-summary-of-the-go-) +* [⇢ ⇢ December 2024](#december-2024) +* [⇢ ⇢ ⇢ Thats unexpected, you cant remove a NaN key ...](#thats-unexpected-you-cant-remove-a-nan-key-) +* [⇢ ⇢ ⇢ My second blog post about revamping my home lab ...](#my-second-blog-post-about-revamping-my-home-lab-) +* [⇢ ⇢ ⇢ Very insightful article about tech hiring in ...](#very-insightful-article-about-tech-hiring-in-) +* [⇢ ⇢ ⇢ for `#bpf` `#ebpf` performance debugging, have ...](#for-bpf-ebpf-performance-debugging-have-) +* [⇢ ⇢ ⇢ 89 things he/she knows about Git commits is a ...](#89-things-heshe-knows-about-git-commits-is-a-) +* [⇢ ⇢ ⇢ I found that working on multiple side projects ...](#i-found-that-working-on-multiple-side-projects-) +* [⇢ ⇢ ⇢ Agreed? Agreed. Besides `#Ruby`, I would also ...](#agreed-agreed-besides-ruby-i-would-also-) +* [⇢ ⇢ ⇢ Plan9 assembly format in Go, but wait, it's not ...](#plan9-assembly-format-in-go-but-wait-it-s-not-) +* [⇢ ⇢ ⇢ This is a neat blog post about the Helix text ...](#this-is-a-neat-blog-post-about-the-helix-text-) +* [⇢ ⇢ ⇢ This blog post is basically a rant against ...](#this-blog-post-is-basically-a-rant-against-) +* [⇢ ⇢ ⇢ Quick trick to get Helix themes selected ...](#quick-trick-to-get-helix-themes-selected-) +* [⇢ ⇢ ⇢ Example where complexity attacks you from ...](#example-where-complexity-attacks-you-from-) +* [⇢ ⇢ ⇢ LLMs for Ops? Summaries of logs, probabilities ...](#llms-for-ops-summaries-of-logs-probabilities-) +* [⇢ ⇢ ⇢ Excellent article about your dream Product ...](#excellent-article-about-your-dream-product-) +* [⇢ ⇢ ⇢ I just finished reading all chapters of CPU ...](#i-just-finished-reading-all-chapters-of-cpu-) +* [⇢ ⇢ ⇢ Indeed, useful to know this stuff! `#sre` ...](#indeed-useful-to-know-this-stuff-sre-) +* [⇢ ⇢ ⇢ It's the small things, which make Unix like ...](#it-s-the-small-things-which-make-unix-like-) +* [⇢ ⇢ ⇢ My New Year's resolution is not to start any ...](#my-new-year-s-resolution-is-not-to-start-any-) + +## October 2024 + +### First on-call experience in a startup. Doesn't ... + +First on-call experience in a startup. Doesn't sound a lot of fun! But the lessons were learned! `#sre` + +[https://ntietz.com/blog/lessons-from-my-first-on-call/](https://ntietz.com/blog/lessons-from-my-first-on-call/) + +### Reviewing your own PR or MR before asking ... + +Reviewing your own PR or MR before asking others to review it makes a lot of sense. Have seen so many silly mistakes which would have been avoided. Saving time for the real reviewer. + +[https://www.jvt.me/posts/2019/01/12/self-code-review/](https://www.jvt.me/posts/2019/01/12/self-code-review/) + +### Fun with defer in `#golang`, I did't know, that ... + +Fun with defer in `#golang`, I did't know, that a defer object can either be heap or stack allocated. And there are some rules for inlining, too. + +[https://victoriametrics.com/blog/defer-in-go/](https://victoriametrics.com/blog/defer-in-go/) + +### I have been in incidents. Understandably, ... + +I have been in incidents. Understandably, everyone wants the issue to be resolved as quickly and others want to know how long TTR will be. IMHO, providing no estimates at all is no solution either. So maybe give a rough estimate but clearly communicate that the estimate is rough and that X, Y, and Z can interfere, meaning there is a chance it will take longer to resolve the incident. Just my thought. What's yours? + +[https://firehydrant.com/blog/hot-...de-incident-resolution-estimates/](https://firehydrant.com/blog/hot-take-dont-provide-incident-resolution-estimates/) + +### Little tips using strings in `#golang` and I ... + +Little tips using strings in `#golang` and I personally think one must look more into the std lib (not just for strings, also for slices, maps,...), there are tons of useful helper functions. + +[https://www.calhoun.io/6-tips-for-using-strings-in-go/](https://www.calhoun.io/6-tips-for-using-strings-in-go/) + +### Reading this post about `#rust` (especially the ... + +Reading this post about `#rust` (especially the first part), I think I made a good choice in deciding to dive into `#golang` instead. There was a point where I wanted to learn a new programming language, and Rust was on my list of choices. I think the Go project does a much better job of deciding what goes into the language and how. What are your thoughts? + +[https://josephg.com/blog/rewriting-rust/](https://josephg.com/blog/rewriting-rust/) + +### The opposite of `#ChaosMonkey` ... ... + +The opposite of `#ChaosMonkey` ... automatically repairing and healing services helping to reduce manual toil work. Runbooks and scripts are only the first step, followed by a fully blown service written in Go. Could be useful, but IMHO why not rather address the root causes of the manual toil work? `#sre` + +[https://blog.cloudflare.com/nl-nl...latform-resilience-at-cloudflare/](https://blog.cloudflare.com/nl-nl/improving-platform-resilience-at-cloudflare/) + +## November 2024 + +### I just became a Silver Patreon for OSnews. What ... + +I just became a Silver Patreon for OSnews. What is OSnews? It is an independent news site about IT. It is slightly independent and, at times, alternative. I have enjoyed it since my early student days. This one and other projects I financially support are listed here: + +[https://foo.zone/gemfeed/2024-09-07-projects-i-support.html](https://foo.zone/gemfeed/2024-09-07-projects-i-support.html) + +### Until now, I wasn't aware, that Go is under a ... + +Until now, I wasn't aware, that Go is under a BSD-style license (3-clause as it seems). Neat. I don't know why, but I always was under the impression it would be MIT. `#bsd` `#golang` + +[https://go.dev/LICENSE](https://go.dev/LICENSE) + +### These are some book notes from "Staff Engineer" ... + +These are some book notes from "Staff Engineer" – there is some really good insight into what is expected from a Staff Engineer and beyond in the industry. I wish I had read the book earlier. + +[https://foo.zone/gemfeed/2024-10-24-staff-engineer-book-notes.html](https://foo.zone/gemfeed/2024-10-24-staff-engineer-book-notes.html) + +### Looking at `#Kubernetes`, it's pretty much ... + +Looking at `#Kubernetes`, it's pretty much following the Unix way of doing things. It has many tools, but each tool has its own single purpose: DNS, scheduling, container runtime, various controllers, networking, observability, alerting, and more services in the control plane. Everything is managed by different services or plugins, mostly running in their dedicated pods. They don't communicate through pipes, but network sockets, though. `#k8s` + +### There has been an outage at the upstream ... + +There has been an outage at the upstream network provider for OpenBSD.Amsterdam (hoster, I am using). This was the first real-world test for my KISS HA setup, and it worked flawlessly! All my sites and services failed over automatically to my other `#OpenBSD` VM! + +[https://foo.zone/gemfeed/2024-04-...gh-availability-with-OpenBSD.html](https://foo.zone/gemfeed/2024-04-01-KISS-high-availability-with-OpenBSD.html) +[https://openbsd.amsterdam/](https://openbsd.amsterdam/) + +### One of the more confusing parts in Go, nil ... + +One of the more confusing parts in Go, nil values vs nil errors: `#golang` + +[https://unexpected-go.com/nil-errors-that-are-non-nil-errors.html](https://unexpected-go.com/nil-errors-that-are-non-nil-errors.html) + +### Agreeably, writing down with Diagrams helps you ... + +Agreeably, writing down with Diagrams helps you to think things more through. And keeps others on the same page. Only worth for projects from a certain size, IMHO. + +[https://ntietz.com/blog/reasons-to-write-design-docs/](https://ntietz.com/blog/reasons-to-write-design-docs/) + +### I like the idea of types in Ruby. Raku is ... + +I like the idea of types in Ruby. Raku is supports that already, but in Ruby, you must specify the types in a separate .rbs file, which is, in my opinion, cumbersome and is a reason not to use it extensively for now. I believe there are efforts to embed the type information in the standard .rb files, and that the .rbs is just an experiment to see how types could work out without introducing changes into the core Ruby language itself right now? `#Ruby` `#RakuLang` + +[https://github.com/ruby/rbs](https://github.com/ruby/rbs) + +### So, `#Haskell` is better suited for general ... + +So, `#Haskell` is better suited for general purpose than `#Rust`? I thought deploying something in Haskell means publishing an academic paper :-) Interesting rant about Rust, though: + +[https://chrisdone.com/posts/rust/](https://chrisdone.com/posts/rust/) + +### At first, functional options add a bit of ... + +At first, functional options add a bit of boilerplate, but they turn out to be quite neat, especially when you have very long parameter lists that need to be made neat and tidy. `#golang` + +[https://www.calhoun.io/using-func...instead-of-method-chaining-in-go/](https://www.calhoun.io/using-functional-options-instead-of-method-chaining-in-go/) + +### Revamping my home lab a little bit. `#freebsd` ... + +Revamping my home lab a little bit. `#freebsd` `#bhyve` `#rocky` `#linux` `#vm` `#k3s` `#kuberbetes` `#wireguard` `#zfs` `#nfs` `#ha` `#relayd` `#k8s` `#selfhosting` `#self`-hosting `#homelab` `#home`-lab + +[https://foo.zone/gemfeed/2024-11-...bernetes-with-freebsd-part-1.html](https://foo.zone/gemfeed/2024-11-17-f3s-kubernetes-with-freebsd-part-1.html) + +### Wondering to which `#web` `#browser` I should ... + +Wondering to which `#web` `#browser` I should switch now personally ... + +[https://www.osnews.com/story/1411...cy-for-open-web-privacy-and-more/](https://www.osnews.com/story/141100/mozilla-foundation-lays-off-30-of-its-employees-ends-advocacy-for-open-web-privacy-and-more/) + +### eks-node-viewer is a nifty tool, showing the ... + +eks-node-viewer is a nifty tool, showing the compute nodes currently in use in the `#EKS` cluster. especially useful when dynamically allocating nodes with `#karpenter` or auto scaling groups. + +[https://github.com/awslabs/eks-node-viewer](https://github.com/awslabs/eks-node-viewer) + +### Have put more Photos on - On my static photo ... + +Have put more Photos on - On my static photo sites - Generated with a `#bash` script + +[https://irregular.ninja](https://irregular.ninja) + +### In Go, passing pointers are not automatically ... + +In Go, passing pointers are not automatically faster than values. Pointers often force the memory to be allocated on the heap, adding GC overhad. With values, Go can determine whether to put the memory on the stack instead. But with large structs/objects (how you want to call them) or if you want to modify state, then pointers are the semantic to use. `#golang` + +[https://blog.boot.dev/golang/pointers-faster-than-values/](https://blog.boot.dev/golang/pointers-faster-than-values/) + +### Myself being part of an on-call rotations over ... + +Myself being part of an on-call rotations over my whole professional life, just have learned this lesson "Tell people who are new to on-call: Just have fun" :-) This is a neat blog post to read: + +[https://ntietz.com/blog/what-i-tell-people-new-to-oncall/](https://ntietz.com/blog/what-i-tell-people-new-to-oncall/) + +### Feels good to code in my old love `#Perl` again ... + +Feels good to code in my old love `#Perl` again after a while. I am implementing a log parser for generating site stats of my personal homepage! :-) @Perl + +### This is an interactive summary of the Go ... + +This is an interactive summary of the Go release, with a lot of examples utilising iterators in the slices and map packages. Love it! `#golang` + +[https://antonz.org/go-1-23/](https://antonz.org/go-1-23/) + +## December 2024 + +### Thats unexpected, you cant remove a NaN key ... + +Thats unexpected, you cant remove a NaN key from a map without clearing it! `#golang` + +[https://unexpected-go.com/you-can...om-a-map-without-clearing-it.html](https://unexpected-go.com/you-cant-remove-a-nan-key-from-a-map-without-clearing-it.html) + +### My second blog post about revamping my home lab ... + +My second blog post about revamping my home lab a little bit just hit the net. `#FreeBSD` `#ZFS` `#n100` `#k8s` `#k3s` `#kubernetes` + +[https://foo.zone/gemfeed/2024-12-...bernetes-with-freebsd-part-2.html](https://foo.zone/gemfeed/2024-12-03-f3s-kubernetes-with-freebsd-part-2.html) + +### Very insightful article about tech hiring in ... + +Very insightful article about tech hiring in the age of LLMs. As an interviewer, I have experienced some of the scrnarios already first hand... + +[https://newsletter.pragmaticengin...m/p/how-genai-changes-tech-hiring](https://newsletter.pragmaticengineer.com/p/how-genai-changes-tech-hiring) + +### for `#bpf` `#ebpf` performance debugging, have ... + +for `#bpf` `#ebpf` performance debugging, have a look at bpftop from Netflix. A neat tool showing you the estimated CPU time and other performance statistics for all the BPF programs currently loaded into the `#linux` kernel. Highly recommend! + +[https://github.com/Netflix/bpftop](https://github.com/Netflix/bpftop) + +### 89 things he/she knows about Git commits is a ... + +89 things he/she knows about Git commits is a neat list of `#Git` wisdoms + +[https://www.jvt.me/posts/2024/07/12/things-know-commits/](https://www.jvt.me/posts/2024/07/12/things-know-commits/) + +### I found that working on multiple side projects ... + +I found that working on multiple side projects concurrently is better than concentrating on just one. This seems inefficient at first, but whenever you tend to lose motivation, you can temporarily switch to another one with full élan. However, remember to stop starting and start finishing. This doesn't mean you should be working on 10+ (and a growing list of) side projects concurrently! Select your projects and commit to finishing them before starting the next thing. For example, my current limit of concurrent side projects is around five. + +### Agreed? Agreed. Besides `#Ruby`, I would also ... + +Agreed? Agreed. Besides `#Ruby`, I would also add `#RakuLang` and `#Perl` @Perl to the list of languages that are great for shell scripts - "Making Easy Things Easy and Hard Things Possible" + +[https://lucasoshiro.github.io/posts-en/2024-06-17-ruby-shellscript/](https://lucasoshiro.github.io/posts-en/2024-06-17-ruby-shellscript/) + +### Plan9 assembly format in Go, but wait, it's not ... + +Plan9 assembly format in Go, but wait, it's not the Operating System Plan9! `#golang` `#rabbithole` + +[https://www.osnews.com/story/1409...emo-speeding-up-calculations-450/](https://www.osnews.com/story/140941/go-plan9-memo-speeding-up-calculations-450/) + +### This is a neat blog post about the Helix text ... + +This is a neat blog post about the Helix text editor, to which I personally switched around a year ago (from NeoVim). I should blog about my experience as well. To summarize: I am using it together with the terminal multiplexer `#tmux`. It doesn't bother me that Helix is purely terminal-based and therefore everything has to be in the same font. `#HelixEditor` + +[https://jonathan-frere.com/posts/helix/](https://jonathan-frere.com/posts/helix/) + +### This blog post is basically a rant against ... + +This blog post is basically a rant against DataDog... Personally, I don't have much experience with DataDog (actually, I have never used it), but one reason to work with logs at my day job (with over 2,000 physical server machines) and to be cost-effective is by using dtail! `#dtail` `#logs` `#logmanagement` + +[https://crys.site/blog/2024/reinventint-the-weel/](https://crys.site/blog/2024/reinventint-the-weel/) +[https://dtail.dev](https://dtail.dev) + +### Quick trick to get Helix themes selected ... + +Quick trick to get Helix themes selected randomly `#HelixEditor` + +[https://foo.zone/gemfeed/2024-12-15-random-helix-themes.html](https://foo.zone/gemfeed/2024-12-15-random-helix-themes.html) + +### Example where complexity attacks you from ... + +Example where complexity attacks you from behind `#k8s` `#kubernetes` `#OpenAI` + +[https://surfingcomplexity.blog/20...-openai-public-incident-write-up/](https://surfingcomplexity.blog/2024/12/14/quick-takes-on-the-recent-openai-public-incident-write-up/) + +### LLMs for Ops? Summaries of logs, probabilities ... + +LLMs for Ops? Summaries of logs, probabilities about correctness, auto-generating Ansible, some uses cases are there. Wouldn't trust it fully, though. + +[https://youtu.be/WodaffxVq-E?si=noY0egrfl5izCSQI](https://youtu.be/WodaffxVq-E?si=noY0egrfl5izCSQI) + +### Excellent article about your dream Product ... + +Excellent article about your dream Product Manager: Why every software team needs a product manager to thrive via @wallabagapp + +[https://testdouble.com/insights/w...elerate-improve-software-delivery](https://testdouble.com/insights/why-product-managers-accelerate-improve-software-delivery) + +### I just finished reading all chapters of CPU ... + +I just finished reading all chapters of CPU land: ... not claiming to remember every detail, but it is a great refresher how CPUs and operating systems actually work under the hood when you execute a program, which we tend to forget in our higher abstraction world. I liked the "story" and some of the jokes along the way! Size wise, it is pretty digestable (not talking about books, but only 7 web articles/chapters)! `#cpu` `#linux` `#unix` `#kernel` `#macOS` + +[https://cpu.land/](https://cpu.land/) + +### Indeed, useful to know this stuff! `#sre` ... + +Indeed, useful to know this stuff! `#sre` + +[https://biriukov.dev/docs/resolve...vers-and-dual-stack-applications/](https://biriukov.dev/docs/resolver-dual-stack-application/0-sre-should-know-about-gnu-linux-resolvers-and-dual-stack-applications/) + +### It's the small things, which make Unix like ... + +It's the small things, which make Unix like systems, like GNU/Linux, interesting. Didn't know about this `#GNU` `#Tar` behaviour yet: + +[https://xeiaso.net/notes/2024/pop-quiz-tar/](https://xeiaso.net/notes/2024/pop-quiz-tar/) + +### My New Year's resolution is not to start any ... + +My plan for the New Year is not to start any new non-fiction books (or only a few) but to re-read and listen to my favorites, which I read to reflect on and see things from different perspectives. Every time you re-read a book, you gain new insights. + +E-Mail your comments to `paul@nospam.buetow.org` :-) + +[Back to the main site](../) diff --git a/gemfeed/20250101-posts-from-october-to-december-2024.md b/gemfeed/20250101-posts-from-october-to-december-2024.md new file mode 100644 index 00000000..a7d5b5d6 --- /dev/null +++ b/gemfeed/20250101-posts-from-october-to-december-2024.md @@ -0,0 +1,326 @@ +# Posts from October to December 2024 + +These are my social media posts from the last three months. I keep them here to reflect on them and also to not lose them. Social media networks come and go and are not under my control, but my domain is here to stay. + +These are from Mastodon and LinkedIn. Have a look at my about page for my social media profiles. + +[../about/index.md](../about/index.md) + +## Table of Contents + +* [⇢ Posts from October to December 2024](#posts-from-october-to-december-2024) +* [⇢ ⇢ October 2024](#october-2024) +* [⇢ ⇢ ⇢ First on-call experience in a startup. Doesn't ...](#first-on-call-experience-in-a-startup-doesn-t-) +* [⇢ ⇢ ⇢ Reviewing your own PR or MR before asking ...](#reviewing-your-own-pr-or-mr-before-asking-) +* [⇢ ⇢ ⇢ Fun with defer in `#golang`, I did't know, that ...](#fun-with-defer-in-golang-i-did-t-know-that-) +* [⇢ ⇢ ⇢ I have been in incidents. Understandably, ...](#i-have-been-in-incidents-understandably-) +* [⇢ ⇢ ⇢ Little tips using strings in `#golang` and I ...](#little-tips-using-strings-in-golang-and-i-) +* [⇢ ⇢ ⇢ Reading this post about `#rust` (especially the ...](#reading-this-post-about-rust-especially-the-) +* [⇢ ⇢ ⇢ The opposite of `#ChaosMonkey` ... ...](#the-opposite-of-chaosmonkey--) +* [⇢ ⇢ November 2024](#november-2024) +* [⇢ ⇢ ⇢ I just became a Silver Patreon for OSnews. What ...](#i-just-became-a-silver-patreon-for-osnews-what-) +* [⇢ ⇢ ⇢ Until now, I wasn't aware, that Go is under a ...](#until-now-i-wasn-t-aware-that-go-is-under-a-) +* [⇢ ⇢ ⇢ These are some book notes from "Staff Engineer" ...](#these-are-some-book-notes-from-staff-engineer-) +* [⇢ ⇢ ⇢ Looking at `#Kubernetes`, it's pretty much ...](#looking-at-kubernetes-it-s-pretty-much-) +* [⇢ ⇢ ⇢ There has been an outage at the upstream ...](#there-has-been-an-outage-at-the-upstream-) +* [⇢ ⇢ ⇢ One of the more confusing parts in Go, nil ...](#one-of-the-more-confusing-parts-in-go-nil-) +* [⇢ ⇢ ⇢ Agreeably, writing down with Diagrams helps you ...](#agreeably-writing-down-with-diagrams-helps-you-) +* [⇢ ⇢ ⇢ I like the idea of types in Ruby. Raku is ...](#i-like-the-idea-of-types-in-ruby-raku-is-) +* [⇢ ⇢ ⇢ So, `#Haskell` is better suited for general ...](#so-haskell-is-better-suited-for-general-) +* [⇢ ⇢ ⇢ At first, functional options add a bit of ...](#at-first-functional-options-add-a-bit-of-) +* [⇢ ⇢ ⇢ Revamping my home lab a little bit. `#freebsd` ...](#revamping-my-home-lab-a-little-bit-freebsd-) +* [⇢ ⇢ ⇢ Revamping my home lab a little bit. `#freebsd` ...](#revamping-my-home-lab-a-little-bit-freebsd-) +* [⇢ ⇢ ⇢ Wondering to which `#web` `#browser` I should ...](#wondering-to-which-web-browser-i-should-) +* [⇢ ⇢ ⇢ eks-node-viewer is a nifty tool, showing the ...](#eks-node-viewer-is-a-nifty-tool-showing-the-) +* [⇢ ⇢ ⇢ Have put more Photos on - On my static photo ...](#have-put-more-photos-on---on-my-static-photo-) +* [⇢ ⇢ ⇢ In Go, passing pointers are not automatically ...](#in-go-passing-pointers-are-not-automatically-) +* [⇢ ⇢ ⇢ Myself being part of an on-call rotations over ...](#myself-being-part-of-an-on-call-rotations-over-) +* [⇢ ⇢ ⇢ Feels good to code in my old love `#Perl` again ...](#feels-good-to-code-in-my-old-love-perl-again-) +* [⇢ ⇢ ⇢ This is an interactive summary of the Go ...](#this-is-an-interactive-summary-of-the-go-) +* [⇢ ⇢ December 2024](#december-2024) +* [⇢ ⇢ ⇢ Thats unexpected, you cant remove a NaN key ...](#thats-unexpected-you-cant-remove-a-nan-key-) +* [⇢ ⇢ ⇢ My second blog post about revamping my home lab ...](#my-second-blog-post-about-revamping-my-home-lab-) +* [⇢ ⇢ ⇢ Very insightful article about tech hiring in ...](#very-insightful-article-about-tech-hiring-in-) +* [⇢ ⇢ ⇢ for `#bpf` `#ebpf` performance debugging, have ...](#for-bpf-ebpf-performance-debugging-have-) +* [⇢ ⇢ ⇢ 89 things he/she knows about Git commits is a ...](#89-things-heshe-knows-about-git-commits-is-a-) +* [⇢ ⇢ ⇢ I found that working on multiple side projects ...](#i-found-that-working-on-multiple-side-projects-) +* [⇢ ⇢ ⇢ Agreed? Agreed. Besides `#Ruby`, I would also ...](#agreed-agreed-besides-ruby-i-would-also-) +* [⇢ ⇢ ⇢ Plan9 assembly format in Go, but wait, it's not ...](#plan9-assembly-format-in-go-but-wait-it-s-not-) +* [⇢ ⇢ ⇢ This is a neat blog post about the Helix text ...](#this-is-a-neat-blog-post-about-the-helix-text-) +* [⇢ ⇢ ⇢ This blog post is basically a rant against ...](#this-blog-post-is-basically-a-rant-against-) +* [⇢ ⇢ ⇢ Quick trick to get Helix themes selected ...](#quick-trick-to-get-helix-themes-selected-) +* [⇢ ⇢ ⇢ Example where complexity attacks you from ...](#example-where-complexity-attacks-you-from-) +* [⇢ ⇢ ⇢ LLMs for Ops? Summaries of logs, probabilities ...](#llms-for-ops-summaries-of-logs-probabilities-) +* [⇢ ⇢ ⇢ Excellent article about your dream Product ...](#excellent-article-about-your-dream-product-) +* [⇢ ⇢ ⇢ I just finished reading all chapters of CPU ...](#i-just-finished-reading-all-chapters-of-cpu-) +* [⇢ ⇢ ⇢ Indeed, useful to know this stuff! `#sre` ...](#indeed-useful-to-know-this-stuff-sre-) +* [⇢ ⇢ ⇢ It's the small things, which make Unix like ...](#it-s-the-small-things-which-make-unix-like-) +* [⇢ ⇢ ⇢ My New Year's resolution is not to start any ...](#my-new-year-s-resolution-is-not-to-start-any-) + +## October 2024 + +### First on-call experience in a startup. Doesn't ... + +First on-call experience in a startup. Doesn't sound a lot of fun! But the lessons were learned! `#sre` + +[https://ntietz.com/blog/lessons-from-my-first-on-call/](https://ntietz.com/blog/lessons-from-my-first-on-call/) + +### Reviewing your own PR or MR before asking ... + +Reviewing your own PR or MR before asking others to review it makes a lot of sense. Have seen so many silly mistakes which would have been avoided. Saving time for the real reviewer. + +[https://www.jvt.me/posts/2019/01/12/self-code-review/](https://www.jvt.me/posts/2019/01/12/self-code-review/) + +### Fun with defer in `#golang`, I did't know, that ... + +Fun with defer in `#golang`, I did't know, that a defer object can either be heap or stack allocated. And there are some rules for inlining, too. + +[https://victoriametrics.com/blog/defer-in-go/](https://victoriametrics.com/blog/defer-in-go/) + +### I have been in incidents. Understandably, ... + +I have been in incidents. Understandably, everyone wants the issue to be resolved as quickly and others want to know how long TTR will be. IMHO, providing no estimates at all is no solution either. So maybe give a rough estimate but clearly communicate that the estimate is rough and that X, Y, and Z can interfere, meaning there is a chance it will take longer to resolve the incident. Just my thought. What's yours? + +[https://firehydrant.com/blog/hot-...de-incident-resolution-estimates/](https://firehydrant.com/blog/hot-take-dont-provide-incident-resolution-estimates/) + +### Little tips using strings in `#golang` and I ... + +Little tips using strings in `#golang` and I personally think one must look more into the std lib (not just for strings, also for slices, maps,...), there are tons of useful helper functions. + +[https://www.calhoun.io/6-tips-for-using-strings-in-go/](https://www.calhoun.io/6-tips-for-using-strings-in-go/) + +### Reading this post about `#rust` (especially the ... + +Reading this post about `#rust` (especially the first part), I think I made a good choice in deciding to dive into `#golang` instead. There was a point where I wanted to learn a new programming language, and Rust was on my list of choices. I think the Go project does a much better job of deciding what goes into the language and how. What are your thoughts? + +[https://josephg.com/blog/rewriting-rust/](https://josephg.com/blog/rewriting-rust/) + +### The opposite of `#ChaosMonkey` ... ... + +The opposite of `#ChaosMonkey` ... automatically repairing and healing services helping to reduce manual toil work. Runbooks and scripts are only the first step, followed by a fully blown service written in Go. Could be useful, but IMHO why not rather address the root causes of the manual toil work? `#sre` + +[https://blog.cloudflare.com/nl-nl...latform-resilience-at-cloudflare/](https://blog.cloudflare.com/nl-nl/improving-platform-resilience-at-cloudflare/) + +## November 2024 + +### I just became a Silver Patreon for OSnews. What ... + +I just became a Silver Patreon for OSnews. What is OSnews? It is an independent news site about IT. It is slightly independent and, at times, alternative. I have enjoyed it since my early student days. This one and other projects I financially support are listed here: + +[https://foo.zone/gemfeed/2024-09-07-projects-i-support.html](https://foo.zone/gemfeed/2024-09-07-projects-i-support.html) + +### Until now, I wasn't aware, that Go is under a ... + +Until now, I wasn't aware, that Go is under a BSD-style license (3-clause as it seems). Neat. I don't know why, but I always was under the impression it would be MIT. `#bsd` `#golang` + +[https://go.dev/LICENSE](https://go.dev/LICENSE) + +### These are some book notes from "Staff Engineer" ... + +These are some book notes from "Staff Engineer" – there is some really good insight into what is expected from a Staff Engineer and beyond in the industry. I wish I had read the book earlier. + +[https://foo.zone/gemfeed/2024-10-24-staff-engineer-book-notes.html](https://foo.zone/gemfeed/2024-10-24-staff-engineer-book-notes.html) + +### Looking at `#Kubernetes`, it's pretty much ... + +Looking at `#Kubernetes`, it's pretty much following the Unix way of doing things. It has many tools, but each tool has its own single purpose: DNS, scheduling, container runtime, various controllers, networking, observability, alerting, and more services in the control plane. Everything is managed by different services or plugins, mostly running in their dedicated pods. They don't communicate through pipes, but network sockets, though. `#k8s` + +### There has been an outage at the upstream ... + +There has been an outage at the upstream network provider for OpenBSD.Amsterdam (hoster, I am using). This was the first real-world test for my KISS HA setup, and it worked flawlessly! All my sites and services failed over automatically to my other `#OpenBSD` VM! + +[https://foo.zone/gemfeed/2024-04-...gh-availability-with-OpenBSD.html](https://foo.zone/gemfeed/2024-04-01-KISS-high-availability-with-OpenBSD.html) +[https://openbsd.amsterdam/](https://openbsd.amsterdam/) + +### One of the more confusing parts in Go, nil ... + +One of the more confusing parts in Go, nil values vs nil errors: `#golang` + +[https://unexpected-go.com/nil-errors-that-are-non-nil-errors.html](https://unexpected-go.com/nil-errors-that-are-non-nil-errors.html) + +### Agreeably, writing down with Diagrams helps you ... + +Agreeably, writing down with Diagrams helps you to think things more through. And keeps others on the same page. Only worth for projects from a certain size, IMHO. + +[https://ntietz.com/blog/reasons-to-write-design-docs/](https://ntietz.com/blog/reasons-to-write-design-docs/) + +### I like the idea of types in Ruby. Raku is ... + +I like the idea of types in Ruby. Raku is supports that already, but in Ruby, you must specify the types in a separate .rbs file, which is, in my opinion, cumbersome and is a reason not to use it extensively for now. I believe there are efforts to embed the type information in the standard .rb files, and that the .rbs is just an experiment to see how types could work out without introducing changes into the core Ruby language itself right now? `#Ruby` `#RakuLang` + +[https://github.com/ruby/rbs](https://github.com/ruby/rbs) + +### So, `#Haskell` is better suited for general ... + +So, `#Haskell` is better suited for general purpose than `#Rust`? I thought deploying something in Haskell means publishing an academic paper :-) Interesting rant about Rust, though: + +[https://chrisdone.com/posts/rust/](https://chrisdone.com/posts/rust/) + +### At first, functional options add a bit of ... + +At first, functional options add a bit of boilerplate, but they turn out to be quite neat, especially when you have very long parameter lists that need to be made neat and tidy. `#golang` + +[https://www.calhoun.io/using-func...instead-of-method-chaining-in-go/](https://www.calhoun.io/using-functional-options-instead-of-method-chaining-in-go/) + +### Revamping my home lab a little bit. `#freebsd` ... + +Revamping my home lab a little bit. `#freebsd` `#bhyve` `#rocky` `#linux` `#vm` `#k3s` `#kuberbetes` `#wireguard` `#zfs` `#nfs` `#ha` `#relayd` `#k8s` `#selfhosting` `#self`-hosting `#homelab` `#home`-lab + +[https://foo.zone/gemfeed/2024-11-...bernetes-with-freebsd-part-1.html](https://foo.zone/gemfeed/2024-11-17-f3s-kubernetes-with-freebsd-part-1.html) + +### Revamping my home lab a little bit. `#freebsd` ... + +Revamping my home lab a little bit. `#freebsd` `#bhyve` `#rocky` `#linux` `#vm` `#k3s` `#kubernetes` `#wireguard` `#zfs` `#nfs` `#ha` `#relayd` `#k8s` `#selfhosting` `#homelab` + +[https://foo.zone/gemfeed/2024-11-...bernetes-with-freebsd-part-1.html](https://foo.zone/gemfeed/2024-11-17-f3s-kubernetes-with-freebsd-part-1.html) + +### Wondering to which `#web` `#browser` I should ... + +Wondering to which `#web` `#browser` I should switch now personally ... + +[https://www.osnews.com/story/1411...cy-for-open-web-privacy-and-more/](https://www.osnews.com/story/141100/mozilla-foundation-lays-off-30-of-its-employees-ends-advocacy-for-open-web-privacy-and-more/) + +### eks-node-viewer is a nifty tool, showing the ... + +eks-node-viewer is a nifty tool, showing the compute nodes currently in use in the `#EKS` cluster. especially useful when dynamically allocating nodes with `#karpenter` or auto scaling groups. + +[https://github.com/awslabs/eks-node-viewer](https://github.com/awslabs/eks-node-viewer) + +### Have put more Photos on - On my static photo ... + +Have put more Photos on - On my static photo sites - Generated with a `#bash` script + +[https://irregular.ninja](https://irregular.ninja) + +### In Go, passing pointers are not automatically ... + +In Go, passing pointers are not automatically faster than values. Pointers often force the memory to be allocated on the heap, adding GC overhad. With values, Go can determine whether to put the memory on the stack instead. But with large structs/objects (how you want to call them) or if you want to modify state, then pointers are the semantic to use. `#golang` + +[https://blog.boot.dev/golang/pointers-faster-than-values/](https://blog.boot.dev/golang/pointers-faster-than-values/) + +### Myself being part of an on-call rotations over ... + +Myself being part of an on-call rotations over my whole professional life, just have learned this lesson "Tell people who are new to on-call: Just have fun" :-) This is a neat blog post to read: + +[https://ntietz.com/blog/what-i-tell-people-new-to-oncall/](https://ntietz.com/blog/what-i-tell-people-new-to-oncall/) + +### Feels good to code in my old love `#Perl` again ... + +Feels good to code in my old love `#Perl` again after a while. I am implementing a log parser for generating site stats of my personal homepage! :-) @Perl + +### This is an interactive summary of the Go ... + +This is an interactive summary of the Go release, with a lot of examples utilising iterators in the slices and map packages. Love it! `#golang` + +[https://antonz.org/go-1-23/](https://antonz.org/go-1-23/) + +## December 2024 + +### Thats unexpected, you cant remove a NaN key ... + +Thats unexpected, you cant remove a NaN key from a map without clearing it! `#golang` + +[https://unexpected-go.com/you-can...om-a-map-without-clearing-it.html](https://unexpected-go.com/you-cant-remove-a-nan-key-from-a-map-without-clearing-it.html) + +### My second blog post about revamping my home lab ... + +My second blog post about revamping my home lab a little bit just hit the net. `#FreeBSD` `#ZFS` `#n100` `#k8s` `#k3s` `#kubernetes` + +[https://foo.zone/gemfeed/2024-12-...bernetes-with-freebsd-part-2.html](https://foo.zone/gemfeed/2024-12-03-f3s-kubernetes-with-freebsd-part-2.html) + +### Very insightful article about tech hiring in ... + +Very insightful article about tech hiring in the age of LLMs. As an interviewer, I have experienced some of the scrnarios already first hand... + +[https://newsletter.pragmaticengin...m/p/how-genai-changes-tech-hiring](https://newsletter.pragmaticengineer.com/p/how-genai-changes-tech-hiring) + +### for `#bpf` `#ebpf` performance debugging, have ... + +for `#bpf` `#ebpf` performance debugging, have a look at bpftop from Netflix. A neat tool showing you the estimated CPU time and other performance statistics for all the BPF programs currently loaded into the `#linux` kernel. Highly recommend! + +[https://github.com/Netflix/bpftop](https://github.com/Netflix/bpftop) + +### 89 things he/she knows about Git commits is a ... + +89 things he/she knows about Git commits is a neat list of `#Git` wisdoms + +[https://www.jvt.me/posts/2024/07/12/things-know-commits/](https://www.jvt.me/posts/2024/07/12/things-know-commits/) + +### I found that working on multiple side projects ... + +I found that working on multiple side projects concurrently is better than concentrating on just one. This seems inefficient at first, but whenever you tend to lose motivation, you can temporarily switch to another one with full élan. However, remember to stop starting and start finishing. This doesn't mean you should be working on 10+ (and a growing list of) side projects concurrently! Select your projects and commit to finishing them before starting the next thing. For example, my current limit of concurrent side projects is around five. + +### Agreed? Agreed. Besides `#Ruby`, I would also ... + +Agreed? Agreed. Besides `#Ruby`, I would also add `#RakuLang` and `#Perl` @Perl to the list of languages that are great for shell scripts - "Making Easy Things Easy and Hard Things Possible" + +[https://lucasoshiro.github.io/posts-en/2024-06-17-ruby-shellscript/](https://lucasoshiro.github.io/posts-en/2024-06-17-ruby-shellscript/) + +### Plan9 assembly format in Go, but wait, it's not ... + +Plan9 assembly format in Go, but wait, it's not the Operating System Plan9! `#golang` `#rabbithole` + +[https://www.osnews.com/story/1409...emo-speeding-up-calculations-450/](https://www.osnews.com/story/140941/go-plan9-memo-speeding-up-calculations-450/) + +### This is a neat blog post about the Helix text ... + +This is a neat blog post about the Helix text editor, to which I personally switched around a year ago (from NeoVim). I should blog about my experience as well. To summarize: I am using it together with the terminal multiplexer `#tmux`. It doesn't bother me that Helix is purely terminal-based and therefore everything has to be in the same font. `#HelixEditor` + +[https://jonathan-frere.com/posts/helix/](https://jonathan-frere.com/posts/helix/) + +### This blog post is basically a rant against ... + +This blog post is basically a rant against DataDog... Personally, I don't have much experience with DataDog (actually, I have never used it), but one reason to work with logs at my day job (with over 2,000 physical server machines) and to be cost-effective is by using dtail! `#dtail` `#logs` `#logmanagement` + +[https://crys.site/blog/2024/reinventint-the-weel/](https://crys.site/blog/2024/reinventint-the-weel/) +[https://dtail.dev](https://dtail.dev) + +### Quick trick to get Helix themes selected ... + +Quick trick to get Helix themes selected randomly `#HelixEditor` + +[https://foo.zone/gemfeed/2024-12-15-random-helix-themes.html](https://foo.zone/gemfeed/2024-12-15-random-helix-themes.html) + +### Example where complexity attacks you from ... + +Example where complexity attacks you from behind `#k8s` `#kubernetes` `#OpenAI` + +[https://surfingcomplexity.blog/20...-openai-public-incident-write-up/](https://surfingcomplexity.blog/2024/12/14/quick-takes-on-the-recent-openai-public-incident-write-up/) + +### LLMs for Ops? Summaries of logs, probabilities ... + +LLMs for Ops? Summaries of logs, probabilities about correctness, auto-generating Ansible, some uses cases are there. Wouldn't trust it fully, though. + +[https://youtu.be/WodaffxVq-E?si=noY0egrfl5izCSQI](https://youtu.be/WodaffxVq-E?si=noY0egrfl5izCSQI) + +### Excellent article about your dream Product ... + +Excellent article about your dream Product Manager: Why every software team needs a product manager to thrive via @wallabagapp + +[https://testdouble.com/insights/w...elerate-improve-software-delivery](https://testdouble.com/insights/why-product-managers-accelerate-improve-software-delivery) + +### I just finished reading all chapters of CPU ... + +I just finished reading all chapters of CPU land: ... not claiming to remember every detail, but it is a great refresher how CPUs and operating systems actually work under the hood when you execute a program, which we tend to forget in our higher abstraction world. I liked the "story" and some of the jokes along the way! Size wise, it is pretty digestable (not talking about books, but only 7 web articles/chapters)! `#cpu` `#linux` `#unix` `#kernel` `#macOS` + +[https://cpu.land/](https://cpu.land/) + +### Indeed, useful to know this stuff! `#sre` ... + +Indeed, useful to know this stuff! `#sre` + +[https://biriukov.dev/docs/resolve...vers-and-dual-stack-applications/](https://biriukov.dev/docs/resolver-dual-stack-application/0-sre-should-know-about-gnu-linux-resolvers-and-dual-stack-applications/) + +### It's the small things, which make Unix like ... + +It's the small things, which make Unix like systems, like GNU/Linux, interesting. Didn't know about this `#GNU` `#Tar` behaviour yet: + +[https://xeiaso.net/notes/2024/pop-quiz-tar/](https://xeiaso.net/notes/2024/pop-quiz-tar/) + +### My New Year's resolution is not to start any ... + +My New Year's resolution is not to start any new non-fiction books (or only very few) but to re-read and listen to my favorites, which I read to reflect on and see things from different perspectives. Every time you re-read a book, you gain new insights.15419 + +E-Mail your comments to `paul@nospam.buetow.org` :-) + +[Back to the main site](../) diff --git a/gemfeed/index.md b/gemfeed/index.md index 87fb3f92..eeaa7d8c 100644 --- a/gemfeed/index.md +++ b/gemfeed/index.md @@ -2,6 +2,7 @@ ## To be in the .zone! +[2025-01-01 - Posts from October to December 2024](./2025-01-01-posts-from-october-to-december-2024.md) [2024-12-15 - Random Helix Themes](./2024-12-15-random-helix-themes.md) [2024-12-03 - f3s: Kubernetes with FreeBSD - Part 2: Hardware and base installation](./2024-12-03-f3s-kubernetes-with-freebsd-part-2.md) [2024-11-17 - f3s: Kubernetes with FreeBSD - Part 1: Setting the stage](./2024-11-17-f3s-kubernetes-with-freebsd-part-1.md) -- cgit v1.2.3 From 30838cf4f6eeeec1600cc1b3abec5c50800cc169 Mon Sep 17 00:00:00 2001 From: Paul Buetow Date: Tue, 31 Dec 2024 18:26:29 +0200 Subject: Update content for md --- gemfeed/2025-01-01-posts-from-october-to-december-2024.md | 5 +++++ 1 file changed, 5 insertions(+) (limited to 'gemfeed') diff --git a/gemfeed/2025-01-01-posts-from-october-to-december-2024.md b/gemfeed/2025-01-01-posts-from-october-to-december-2024.md index f35f7cc3..4f939315 100644 --- a/gemfeed/2025-01-01-posts-from-october-to-december-2024.md +++ b/gemfeed/2025-01-01-posts-from-october-to-december-2024.md @@ -319,6 +319,11 @@ It's the small things, which make Unix like systems, like GNU/Linux, interesting My plan for the New Year is not to start any new non-fiction books (or only a few) but to re-read and listen to my favorites, which I read to reflect on and see things from different perspectives. Every time you re-read a book, you gain new insights. +Other related posts: + +[2025-01-01 Posts from October to December 2024 (You are currently reading this)](./2025-01-01-posts-from-october-to-december-2024.md) +[20250101-posts-from Posts from October to December 2024](./20250101-posts-from-october-to-december-2024.md) + E-Mail your comments to `paul@nospam.buetow.org` :-) [Back to the main site](../) -- cgit v1.2.3 From 5144fa271eb010589585e37debb7c2f08d2c72c7 Mon Sep 17 00:00:00 2001 From: Paul Buetow Date: Tue, 31 Dec 2024 18:28:26 +0200 Subject: Update content for md --- ...25-01-01-posts-from-october-to-december-2024.md | 1 - ...20250101-posts-from-october-to-december-2024.md | 326 --------------------- 2 files changed, 327 deletions(-) delete mode 100644 gemfeed/20250101-posts-from-october-to-december-2024.md (limited to 'gemfeed') diff --git a/gemfeed/2025-01-01-posts-from-october-to-december-2024.md b/gemfeed/2025-01-01-posts-from-october-to-december-2024.md index 4f939315..4a19bf61 100644 --- a/gemfeed/2025-01-01-posts-from-october-to-december-2024.md +++ b/gemfeed/2025-01-01-posts-from-october-to-december-2024.md @@ -322,7 +322,6 @@ My plan for the New Year is not to start any new non-fiction books (or only a fe Other related posts: [2025-01-01 Posts from October to December 2024 (You are currently reading this)](./2025-01-01-posts-from-october-to-december-2024.md) -[20250101-posts-from Posts from October to December 2024](./20250101-posts-from-october-to-december-2024.md) E-Mail your comments to `paul@nospam.buetow.org` :-) diff --git a/gemfeed/20250101-posts-from-october-to-december-2024.md b/gemfeed/20250101-posts-from-october-to-december-2024.md deleted file mode 100644 index a7d5b5d6..00000000 --- a/gemfeed/20250101-posts-from-october-to-december-2024.md +++ /dev/null @@ -1,326 +0,0 @@ -# Posts from October to December 2024 - -These are my social media posts from the last three months. I keep them here to reflect on them and also to not lose them. Social media networks come and go and are not under my control, but my domain is here to stay. - -These are from Mastodon and LinkedIn. Have a look at my about page for my social media profiles. - -[../about/index.md](../about/index.md) - -## Table of Contents - -* [⇢ Posts from October to December 2024](#posts-from-october-to-december-2024) -* [⇢ ⇢ October 2024](#october-2024) -* [⇢ ⇢ ⇢ First on-call experience in a startup. Doesn't ...](#first-on-call-experience-in-a-startup-doesn-t-) -* [⇢ ⇢ ⇢ Reviewing your own PR or MR before asking ...](#reviewing-your-own-pr-or-mr-before-asking-) -* [⇢ ⇢ ⇢ Fun with defer in `#golang`, I did't know, that ...](#fun-with-defer-in-golang-i-did-t-know-that-) -* [⇢ ⇢ ⇢ I have been in incidents. Understandably, ...](#i-have-been-in-incidents-understandably-) -* [⇢ ⇢ ⇢ Little tips using strings in `#golang` and I ...](#little-tips-using-strings-in-golang-and-i-) -* [⇢ ⇢ ⇢ Reading this post about `#rust` (especially the ...](#reading-this-post-about-rust-especially-the-) -* [⇢ ⇢ ⇢ The opposite of `#ChaosMonkey` ... ...](#the-opposite-of-chaosmonkey--) -* [⇢ ⇢ November 2024](#november-2024) -* [⇢ ⇢ ⇢ I just became a Silver Patreon for OSnews. What ...](#i-just-became-a-silver-patreon-for-osnews-what-) -* [⇢ ⇢ ⇢ Until now, I wasn't aware, that Go is under a ...](#until-now-i-wasn-t-aware-that-go-is-under-a-) -* [⇢ ⇢ ⇢ These are some book notes from "Staff Engineer" ...](#these-are-some-book-notes-from-staff-engineer-) -* [⇢ ⇢ ⇢ Looking at `#Kubernetes`, it's pretty much ...](#looking-at-kubernetes-it-s-pretty-much-) -* [⇢ ⇢ ⇢ There has been an outage at the upstream ...](#there-has-been-an-outage-at-the-upstream-) -* [⇢ ⇢ ⇢ One of the more confusing parts in Go, nil ...](#one-of-the-more-confusing-parts-in-go-nil-) -* [⇢ ⇢ ⇢ Agreeably, writing down with Diagrams helps you ...](#agreeably-writing-down-with-diagrams-helps-you-) -* [⇢ ⇢ ⇢ I like the idea of types in Ruby. Raku is ...](#i-like-the-idea-of-types-in-ruby-raku-is-) -* [⇢ ⇢ ⇢ So, `#Haskell` is better suited for general ...](#so-haskell-is-better-suited-for-general-) -* [⇢ ⇢ ⇢ At first, functional options add a bit of ...](#at-first-functional-options-add-a-bit-of-) -* [⇢ ⇢ ⇢ Revamping my home lab a little bit. `#freebsd` ...](#revamping-my-home-lab-a-little-bit-freebsd-) -* [⇢ ⇢ ⇢ Revamping my home lab a little bit. `#freebsd` ...](#revamping-my-home-lab-a-little-bit-freebsd-) -* [⇢ ⇢ ⇢ Wondering to which `#web` `#browser` I should ...](#wondering-to-which-web-browser-i-should-) -* [⇢ ⇢ ⇢ eks-node-viewer is a nifty tool, showing the ...](#eks-node-viewer-is-a-nifty-tool-showing-the-) -* [⇢ ⇢ ⇢ Have put more Photos on - On my static photo ...](#have-put-more-photos-on---on-my-static-photo-) -* [⇢ ⇢ ⇢ In Go, passing pointers are not automatically ...](#in-go-passing-pointers-are-not-automatically-) -* [⇢ ⇢ ⇢ Myself being part of an on-call rotations over ...](#myself-being-part-of-an-on-call-rotations-over-) -* [⇢ ⇢ ⇢ Feels good to code in my old love `#Perl` again ...](#feels-good-to-code-in-my-old-love-perl-again-) -* [⇢ ⇢ ⇢ This is an interactive summary of the Go ...](#this-is-an-interactive-summary-of-the-go-) -* [⇢ ⇢ December 2024](#december-2024) -* [⇢ ⇢ ⇢ Thats unexpected, you cant remove a NaN key ...](#thats-unexpected-you-cant-remove-a-nan-key-) -* [⇢ ⇢ ⇢ My second blog post about revamping my home lab ...](#my-second-blog-post-about-revamping-my-home-lab-) -* [⇢ ⇢ ⇢ Very insightful article about tech hiring in ...](#very-insightful-article-about-tech-hiring-in-) -* [⇢ ⇢ ⇢ for `#bpf` `#ebpf` performance debugging, have ...](#for-bpf-ebpf-performance-debugging-have-) -* [⇢ ⇢ ⇢ 89 things he/she knows about Git commits is a ...](#89-things-heshe-knows-about-git-commits-is-a-) -* [⇢ ⇢ ⇢ I found that working on multiple side projects ...](#i-found-that-working-on-multiple-side-projects-) -* [⇢ ⇢ ⇢ Agreed? Agreed. Besides `#Ruby`, I would also ...](#agreed-agreed-besides-ruby-i-would-also-) -* [⇢ ⇢ ⇢ Plan9 assembly format in Go, but wait, it's not ...](#plan9-assembly-format-in-go-but-wait-it-s-not-) -* [⇢ ⇢ ⇢ This is a neat blog post about the Helix text ...](#this-is-a-neat-blog-post-about-the-helix-text-) -* [⇢ ⇢ ⇢ This blog post is basically a rant against ...](#this-blog-post-is-basically-a-rant-against-) -* [⇢ ⇢ ⇢ Quick trick to get Helix themes selected ...](#quick-trick-to-get-helix-themes-selected-) -* [⇢ ⇢ ⇢ Example where complexity attacks you from ...](#example-where-complexity-attacks-you-from-) -* [⇢ ⇢ ⇢ LLMs for Ops? Summaries of logs, probabilities ...](#llms-for-ops-summaries-of-logs-probabilities-) -* [⇢ ⇢ ⇢ Excellent article about your dream Product ...](#excellent-article-about-your-dream-product-) -* [⇢ ⇢ ⇢ I just finished reading all chapters of CPU ...](#i-just-finished-reading-all-chapters-of-cpu-) -* [⇢ ⇢ ⇢ Indeed, useful to know this stuff! `#sre` ...](#indeed-useful-to-know-this-stuff-sre-) -* [⇢ ⇢ ⇢ It's the small things, which make Unix like ...](#it-s-the-small-things-which-make-unix-like-) -* [⇢ ⇢ ⇢ My New Year's resolution is not to start any ...](#my-new-year-s-resolution-is-not-to-start-any-) - -## October 2024 - -### First on-call experience in a startup. Doesn't ... - -First on-call experience in a startup. Doesn't sound a lot of fun! But the lessons were learned! `#sre` - -[https://ntietz.com/blog/lessons-from-my-first-on-call/](https://ntietz.com/blog/lessons-from-my-first-on-call/) - -### Reviewing your own PR or MR before asking ... - -Reviewing your own PR or MR before asking others to review it makes a lot of sense. Have seen so many silly mistakes which would have been avoided. Saving time for the real reviewer. - -[https://www.jvt.me/posts/2019/01/12/self-code-review/](https://www.jvt.me/posts/2019/01/12/self-code-review/) - -### Fun with defer in `#golang`, I did't know, that ... - -Fun with defer in `#golang`, I did't know, that a defer object can either be heap or stack allocated. And there are some rules for inlining, too. - -[https://victoriametrics.com/blog/defer-in-go/](https://victoriametrics.com/blog/defer-in-go/) - -### I have been in incidents. Understandably, ... - -I have been in incidents. Understandably, everyone wants the issue to be resolved as quickly and others want to know how long TTR will be. IMHO, providing no estimates at all is no solution either. So maybe give a rough estimate but clearly communicate that the estimate is rough and that X, Y, and Z can interfere, meaning there is a chance it will take longer to resolve the incident. Just my thought. What's yours? - -[https://firehydrant.com/blog/hot-...de-incident-resolution-estimates/](https://firehydrant.com/blog/hot-take-dont-provide-incident-resolution-estimates/) - -### Little tips using strings in `#golang` and I ... - -Little tips using strings in `#golang` and I personally think one must look more into the std lib (not just for strings, also for slices, maps,...), there are tons of useful helper functions. - -[https://www.calhoun.io/6-tips-for-using-strings-in-go/](https://www.calhoun.io/6-tips-for-using-strings-in-go/) - -### Reading this post about `#rust` (especially the ... - -Reading this post about `#rust` (especially the first part), I think I made a good choice in deciding to dive into `#golang` instead. There was a point where I wanted to learn a new programming language, and Rust was on my list of choices. I think the Go project does a much better job of deciding what goes into the language and how. What are your thoughts? - -[https://josephg.com/blog/rewriting-rust/](https://josephg.com/blog/rewriting-rust/) - -### The opposite of `#ChaosMonkey` ... ... - -The opposite of `#ChaosMonkey` ... automatically repairing and healing services helping to reduce manual toil work. Runbooks and scripts are only the first step, followed by a fully blown service written in Go. Could be useful, but IMHO why not rather address the root causes of the manual toil work? `#sre` - -[https://blog.cloudflare.com/nl-nl...latform-resilience-at-cloudflare/](https://blog.cloudflare.com/nl-nl/improving-platform-resilience-at-cloudflare/) - -## November 2024 - -### I just became a Silver Patreon for OSnews. What ... - -I just became a Silver Patreon for OSnews. What is OSnews? It is an independent news site about IT. It is slightly independent and, at times, alternative. I have enjoyed it since my early student days. This one and other projects I financially support are listed here: - -[https://foo.zone/gemfeed/2024-09-07-projects-i-support.html](https://foo.zone/gemfeed/2024-09-07-projects-i-support.html) - -### Until now, I wasn't aware, that Go is under a ... - -Until now, I wasn't aware, that Go is under a BSD-style license (3-clause as it seems). Neat. I don't know why, but I always was under the impression it would be MIT. `#bsd` `#golang` - -[https://go.dev/LICENSE](https://go.dev/LICENSE) - -### These are some book notes from "Staff Engineer" ... - -These are some book notes from "Staff Engineer" – there is some really good insight into what is expected from a Staff Engineer and beyond in the industry. I wish I had read the book earlier. - -[https://foo.zone/gemfeed/2024-10-24-staff-engineer-book-notes.html](https://foo.zone/gemfeed/2024-10-24-staff-engineer-book-notes.html) - -### Looking at `#Kubernetes`, it's pretty much ... - -Looking at `#Kubernetes`, it's pretty much following the Unix way of doing things. It has many tools, but each tool has its own single purpose: DNS, scheduling, container runtime, various controllers, networking, observability, alerting, and more services in the control plane. Everything is managed by different services or plugins, mostly running in their dedicated pods. They don't communicate through pipes, but network sockets, though. `#k8s` - -### There has been an outage at the upstream ... - -There has been an outage at the upstream network provider for OpenBSD.Amsterdam (hoster, I am using). This was the first real-world test for my KISS HA setup, and it worked flawlessly! All my sites and services failed over automatically to my other `#OpenBSD` VM! - -[https://foo.zone/gemfeed/2024-04-...gh-availability-with-OpenBSD.html](https://foo.zone/gemfeed/2024-04-01-KISS-high-availability-with-OpenBSD.html) -[https://openbsd.amsterdam/](https://openbsd.amsterdam/) - -### One of the more confusing parts in Go, nil ... - -One of the more confusing parts in Go, nil values vs nil errors: `#golang` - -[https://unexpected-go.com/nil-errors-that-are-non-nil-errors.html](https://unexpected-go.com/nil-errors-that-are-non-nil-errors.html) - -### Agreeably, writing down with Diagrams helps you ... - -Agreeably, writing down with Diagrams helps you to think things more through. And keeps others on the same page. Only worth for projects from a certain size, IMHO. - -[https://ntietz.com/blog/reasons-to-write-design-docs/](https://ntietz.com/blog/reasons-to-write-design-docs/) - -### I like the idea of types in Ruby. Raku is ... - -I like the idea of types in Ruby. Raku is supports that already, but in Ruby, you must specify the types in a separate .rbs file, which is, in my opinion, cumbersome and is a reason not to use it extensively for now. I believe there are efforts to embed the type information in the standard .rb files, and that the .rbs is just an experiment to see how types could work out without introducing changes into the core Ruby language itself right now? `#Ruby` `#RakuLang` - -[https://github.com/ruby/rbs](https://github.com/ruby/rbs) - -### So, `#Haskell` is better suited for general ... - -So, `#Haskell` is better suited for general purpose than `#Rust`? I thought deploying something in Haskell means publishing an academic paper :-) Interesting rant about Rust, though: - -[https://chrisdone.com/posts/rust/](https://chrisdone.com/posts/rust/) - -### At first, functional options add a bit of ... - -At first, functional options add a bit of boilerplate, but they turn out to be quite neat, especially when you have very long parameter lists that need to be made neat and tidy. `#golang` - -[https://www.calhoun.io/using-func...instead-of-method-chaining-in-go/](https://www.calhoun.io/using-functional-options-instead-of-method-chaining-in-go/) - -### Revamping my home lab a little bit. `#freebsd` ... - -Revamping my home lab a little bit. `#freebsd` `#bhyve` `#rocky` `#linux` `#vm` `#k3s` `#kuberbetes` `#wireguard` `#zfs` `#nfs` `#ha` `#relayd` `#k8s` `#selfhosting` `#self`-hosting `#homelab` `#home`-lab - -[https://foo.zone/gemfeed/2024-11-...bernetes-with-freebsd-part-1.html](https://foo.zone/gemfeed/2024-11-17-f3s-kubernetes-with-freebsd-part-1.html) - -### Revamping my home lab a little bit. `#freebsd` ... - -Revamping my home lab a little bit. `#freebsd` `#bhyve` `#rocky` `#linux` `#vm` `#k3s` `#kubernetes` `#wireguard` `#zfs` `#nfs` `#ha` `#relayd` `#k8s` `#selfhosting` `#homelab` - -[https://foo.zone/gemfeed/2024-11-...bernetes-with-freebsd-part-1.html](https://foo.zone/gemfeed/2024-11-17-f3s-kubernetes-with-freebsd-part-1.html) - -### Wondering to which `#web` `#browser` I should ... - -Wondering to which `#web` `#browser` I should switch now personally ... - -[https://www.osnews.com/story/1411...cy-for-open-web-privacy-and-more/](https://www.osnews.com/story/141100/mozilla-foundation-lays-off-30-of-its-employees-ends-advocacy-for-open-web-privacy-and-more/) - -### eks-node-viewer is a nifty tool, showing the ... - -eks-node-viewer is a nifty tool, showing the compute nodes currently in use in the `#EKS` cluster. especially useful when dynamically allocating nodes with `#karpenter` or auto scaling groups. - -[https://github.com/awslabs/eks-node-viewer](https://github.com/awslabs/eks-node-viewer) - -### Have put more Photos on - On my static photo ... - -Have put more Photos on - On my static photo sites - Generated with a `#bash` script - -[https://irregular.ninja](https://irregular.ninja) - -### In Go, passing pointers are not automatically ... - -In Go, passing pointers are not automatically faster than values. Pointers often force the memory to be allocated on the heap, adding GC overhad. With values, Go can determine whether to put the memory on the stack instead. But with large structs/objects (how you want to call them) or if you want to modify state, then pointers are the semantic to use. `#golang` - -[https://blog.boot.dev/golang/pointers-faster-than-values/](https://blog.boot.dev/golang/pointers-faster-than-values/) - -### Myself being part of an on-call rotations over ... - -Myself being part of an on-call rotations over my whole professional life, just have learned this lesson "Tell people who are new to on-call: Just have fun" :-) This is a neat blog post to read: - -[https://ntietz.com/blog/what-i-tell-people-new-to-oncall/](https://ntietz.com/blog/what-i-tell-people-new-to-oncall/) - -### Feels good to code in my old love `#Perl` again ... - -Feels good to code in my old love `#Perl` again after a while. I am implementing a log parser for generating site stats of my personal homepage! :-) @Perl - -### This is an interactive summary of the Go ... - -This is an interactive summary of the Go release, with a lot of examples utilising iterators in the slices and map packages. Love it! `#golang` - -[https://antonz.org/go-1-23/](https://antonz.org/go-1-23/) - -## December 2024 - -### Thats unexpected, you cant remove a NaN key ... - -Thats unexpected, you cant remove a NaN key from a map without clearing it! `#golang` - -[https://unexpected-go.com/you-can...om-a-map-without-clearing-it.html](https://unexpected-go.com/you-cant-remove-a-nan-key-from-a-map-without-clearing-it.html) - -### My second blog post about revamping my home lab ... - -My second blog post about revamping my home lab a little bit just hit the net. `#FreeBSD` `#ZFS` `#n100` `#k8s` `#k3s` `#kubernetes` - -[https://foo.zone/gemfeed/2024-12-...bernetes-with-freebsd-part-2.html](https://foo.zone/gemfeed/2024-12-03-f3s-kubernetes-with-freebsd-part-2.html) - -### Very insightful article about tech hiring in ... - -Very insightful article about tech hiring in the age of LLMs. As an interviewer, I have experienced some of the scrnarios already first hand... - -[https://newsletter.pragmaticengin...m/p/how-genai-changes-tech-hiring](https://newsletter.pragmaticengineer.com/p/how-genai-changes-tech-hiring) - -### for `#bpf` `#ebpf` performance debugging, have ... - -for `#bpf` `#ebpf` performance debugging, have a look at bpftop from Netflix. A neat tool showing you the estimated CPU time and other performance statistics for all the BPF programs currently loaded into the `#linux` kernel. Highly recommend! - -[https://github.com/Netflix/bpftop](https://github.com/Netflix/bpftop) - -### 89 things he/she knows about Git commits is a ... - -89 things he/she knows about Git commits is a neat list of `#Git` wisdoms - -[https://www.jvt.me/posts/2024/07/12/things-know-commits/](https://www.jvt.me/posts/2024/07/12/things-know-commits/) - -### I found that working on multiple side projects ... - -I found that working on multiple side projects concurrently is better than concentrating on just one. This seems inefficient at first, but whenever you tend to lose motivation, you can temporarily switch to another one with full élan. However, remember to stop starting and start finishing. This doesn't mean you should be working on 10+ (and a growing list of) side projects concurrently! Select your projects and commit to finishing them before starting the next thing. For example, my current limit of concurrent side projects is around five. - -### Agreed? Agreed. Besides `#Ruby`, I would also ... - -Agreed? Agreed. Besides `#Ruby`, I would also add `#RakuLang` and `#Perl` @Perl to the list of languages that are great for shell scripts - "Making Easy Things Easy and Hard Things Possible" - -[https://lucasoshiro.github.io/posts-en/2024-06-17-ruby-shellscript/](https://lucasoshiro.github.io/posts-en/2024-06-17-ruby-shellscript/) - -### Plan9 assembly format in Go, but wait, it's not ... - -Plan9 assembly format in Go, but wait, it's not the Operating System Plan9! `#golang` `#rabbithole` - -[https://www.osnews.com/story/1409...emo-speeding-up-calculations-450/](https://www.osnews.com/story/140941/go-plan9-memo-speeding-up-calculations-450/) - -### This is a neat blog post about the Helix text ... - -This is a neat blog post about the Helix text editor, to which I personally switched around a year ago (from NeoVim). I should blog about my experience as well. To summarize: I am using it together with the terminal multiplexer `#tmux`. It doesn't bother me that Helix is purely terminal-based and therefore everything has to be in the same font. `#HelixEditor` - -[https://jonathan-frere.com/posts/helix/](https://jonathan-frere.com/posts/helix/) - -### This blog post is basically a rant against ... - -This blog post is basically a rant against DataDog... Personally, I don't have much experience with DataDog (actually, I have never used it), but one reason to work with logs at my day job (with over 2,000 physical server machines) and to be cost-effective is by using dtail! `#dtail` `#logs` `#logmanagement` - -[https://crys.site/blog/2024/reinventint-the-weel/](https://crys.site/blog/2024/reinventint-the-weel/) -[https://dtail.dev](https://dtail.dev) - -### Quick trick to get Helix themes selected ... - -Quick trick to get Helix themes selected randomly `#HelixEditor` - -[https://foo.zone/gemfeed/2024-12-15-random-helix-themes.html](https://foo.zone/gemfeed/2024-12-15-random-helix-themes.html) - -### Example where complexity attacks you from ... - -Example where complexity attacks you from behind `#k8s` `#kubernetes` `#OpenAI` - -[https://surfingcomplexity.blog/20...-openai-public-incident-write-up/](https://surfingcomplexity.blog/2024/12/14/quick-takes-on-the-recent-openai-public-incident-write-up/) - -### LLMs for Ops? Summaries of logs, probabilities ... - -LLMs for Ops? Summaries of logs, probabilities about correctness, auto-generating Ansible, some uses cases are there. Wouldn't trust it fully, though. - -[https://youtu.be/WodaffxVq-E?si=noY0egrfl5izCSQI](https://youtu.be/WodaffxVq-E?si=noY0egrfl5izCSQI) - -### Excellent article about your dream Product ... - -Excellent article about your dream Product Manager: Why every software team needs a product manager to thrive via @wallabagapp - -[https://testdouble.com/insights/w...elerate-improve-software-delivery](https://testdouble.com/insights/why-product-managers-accelerate-improve-software-delivery) - -### I just finished reading all chapters of CPU ... - -I just finished reading all chapters of CPU land: ... not claiming to remember every detail, but it is a great refresher how CPUs and operating systems actually work under the hood when you execute a program, which we tend to forget in our higher abstraction world. I liked the "story" and some of the jokes along the way! Size wise, it is pretty digestable (not talking about books, but only 7 web articles/chapters)! `#cpu` `#linux` `#unix` `#kernel` `#macOS` - -[https://cpu.land/](https://cpu.land/) - -### Indeed, useful to know this stuff! `#sre` ... - -Indeed, useful to know this stuff! `#sre` - -[https://biriukov.dev/docs/resolve...vers-and-dual-stack-applications/](https://biriukov.dev/docs/resolver-dual-stack-application/0-sre-should-know-about-gnu-linux-resolvers-and-dual-stack-applications/) - -### It's the small things, which make Unix like ... - -It's the small things, which make Unix like systems, like GNU/Linux, interesting. Didn't know about this `#GNU` `#Tar` behaviour yet: - -[https://xeiaso.net/notes/2024/pop-quiz-tar/](https://xeiaso.net/notes/2024/pop-quiz-tar/) - -### My New Year's resolution is not to start any ... - -My New Year's resolution is not to start any new non-fiction books (or only very few) but to re-read and listen to my favorites, which I read to reflect on and see things from different perspectives. Every time you re-read a book, you gain new insights.15419 - -E-Mail your comments to `paul@nospam.buetow.org` :-) - -[Back to the main site](../) -- cgit v1.2.3 From 1b29a70cef62671faf3960a3cccdc31e0a822fee Mon Sep 17 00:00:00 2001 From: Paul Buetow Date: Tue, 31 Dec 2024 18:43:13 +0200 Subject: Update content for md --- ...25-01-01-posts-from-october-to-december-2024.md | 80 ++++++++++++---------- 1 file changed, 45 insertions(+), 35 deletions(-) (limited to 'gemfeed') diff --git a/gemfeed/2025-01-01-posts-from-october-to-december-2024.md b/gemfeed/2025-01-01-posts-from-october-to-december-2024.md index 4a19bf61..2edc9d3e 100644 --- a/gemfeed/2025-01-01-posts-from-october-to-december-2024.md +++ b/gemfeed/2025-01-01-posts-from-october-to-december-2024.md @@ -11,9 +11,12 @@ These are from Mastodon and LinkedIn. Have a look at my about page for my social [My about page](../about/index.md) [https://codeberg.org/snonux/gos](https://codeberg.org/snonux/gos) +# Posts for 202410 202411 202412 + ## Table of Contents * [⇢ Posts from October to December 2024](#posts-from-october-to-december-2024) +* [⇢ Posts for 202410 202411 202412](#posts-for-202410-202411-202412) * [⇢ ⇢ October 2024](#october-2024) * [⇢ ⇢ ⇢ First on-call experience in a startup. Doesn't ...](#first-on-call-experience-in-a-startup-doesn-t-) * [⇢ ⇢ ⇢ Reviewing your own PR or MR before asking ...](#reviewing-your-own-pr-or-mr-before-asking-) @@ -34,6 +37,7 @@ These are from Mastodon and LinkedIn. Have a look at my about page for my social * [⇢ ⇢ ⇢ So, `#Haskell` is better suited for general ...](#so-haskell-is-better-suited-for-general-) * [⇢ ⇢ ⇢ At first, functional options add a bit of ...](#at-first-functional-options-add-a-bit-of-) * [⇢ ⇢ ⇢ Revamping my home lab a little bit. `#freebsd` ...](#revamping-my-home-lab-a-little-bit-freebsd-) +* [⇢ ⇢ ⇢ Revamping my home lab a little bit. `#freebsd` ...](#revamping-my-home-lab-a-little-bit-freebsd-) * [⇢ ⇢ ⇢ Wondering to which `#web` `#browser` I should ...](#wondering-to-which-web-browser-i-should-) * [⇢ ⇢ ⇢ eks-node-viewer is a nifty tool, showing the ...](#eks-node-viewer-is-a-nifty-tool-showing-the-) * [⇢ ⇢ ⇢ Have put more Photos on - On my static photo ...](#have-put-more-photos-on---on-my-static-photo-) @@ -67,43 +71,43 @@ These are from Mastodon and LinkedIn. Have a look at my about page for my social First on-call experience in a startup. Doesn't sound a lot of fun! But the lessons were learned! `#sre` -[https://ntietz.com/blog/lessons-from-my-first-on-call/](https://ntietz.com/blog/lessons-from-my-first-on-call/) +[https://ntiet...irst-on-call/](https://ntietz.com/blog/lessons-from-my-first-on-call/) ### Reviewing your own PR or MR before asking ... Reviewing your own PR or MR before asking others to review it makes a lot of sense. Have seen so many silly mistakes which would have been avoided. Saving time for the real reviewer. -[https://www.jvt.me/posts/2019/01/12/self-code-review/](https://www.jvt.me/posts/2019/01/12/self-code-review/) +[https://www.j...-code-review/](https://www.jvt.me/posts/2019/01/12/self-code-review/) ### Fun with defer in `#golang`, I did't know, that ... Fun with defer in `#golang`, I did't know, that a defer object can either be heap or stack allocated. And there are some rules for inlining, too. -[https://victoriametrics.com/blog/defer-in-go/](https://victoriametrics.com/blog/defer-in-go/) +[https://victo.../defer-in-go/](https://victoriametrics.com/blog/defer-in-go/) ### I have been in incidents. Understandably, ... I have been in incidents. Understandably, everyone wants the issue to be resolved as quickly and others want to know how long TTR will be. IMHO, providing no estimates at all is no solution either. So maybe give a rough estimate but clearly communicate that the estimate is rough and that X, Y, and Z can interfere, meaning there is a chance it will take longer to resolve the incident. Just my thought. What's yours? -[https://firehydrant.com/blog/hot-...de-incident-resolution-estimates/](https://firehydrant.com/blog/hot-take-dont-provide-incident-resolution-estimates/) +[https://fireh...on-estimates/](https://firehydrant.com/blog/hot-take-dont-provide-incident-resolution-estimates/) ### Little tips using strings in `#golang` and I ... Little tips using strings in `#golang` and I personally think one must look more into the std lib (not just for strings, also for slices, maps,...), there are tons of useful helper functions. -[https://www.calhoun.io/6-tips-for-using-strings-in-go/](https://www.calhoun.io/6-tips-for-using-strings-in-go/) +[https://www.c...trings-in-go/](https://www.calhoun.io/6-tips-for-using-strings-in-go/) ### Reading this post about `#rust` (especially the ... Reading this post about `#rust` (especially the first part), I think I made a good choice in deciding to dive into `#golang` instead. There was a point where I wanted to learn a new programming language, and Rust was on my list of choices. I think the Go project does a much better job of deciding what goes into the language and how. What are your thoughts? -[https://josephg.com/blog/rewriting-rust/](https://josephg.com/blog/rewriting-rust/) +[https://josep...writing-rust/](https://josephg.com/blog/rewriting-rust/) ### The opposite of `#ChaosMonkey` ... ... The opposite of `#ChaosMonkey` ... automatically repairing and healing services helping to reduce manual toil work. Runbooks and scripts are only the first step, followed by a fully blown service written in Go. Could be useful, but IMHO why not rather address the root causes of the manual toil work? `#sre` -[https://blog.cloudflare.com/nl-nl...latform-resilience-at-cloudflare/](https://blog.cloudflare.com/nl-nl/improving-platform-resilience-at-cloudflare/) +[https://blog....t-cloudflare/](https://blog.cloudflare.com/nl-nl/improving-platform-resilience-at-cloudflare/) ## November 2024 @@ -111,7 +115,7 @@ The opposite of `#ChaosMonkey` ... automatically repairing and healing services I just became a Silver Patreon for OSnews. What is OSnews? It is an independent news site about IT. It is slightly independent and, at times, alternative. I have enjoyed it since my early student days. This one and other projects I financially support are listed here: -[https://foo.zone/gemfeed/2024-09-07-projects-i-support.html](https://foo.zone/gemfeed/2024-09-07-projects-i-support.html) +[https://foo.z...-support.html](https://foo.zone/gemfeed/2024-09-07-projects-i-support.html) ### Until now, I wasn't aware, that Go is under a ... @@ -123,7 +127,7 @@ Until now, I wasn't aware, that Go is under a BSD-style license (3-clause as it These are some book notes from "Staff Engineer" – there is some really good insight into what is expected from a Staff Engineer and beyond in the industry. I wish I had read the book earlier. -[https://foo.zone/gemfeed/2024-10-24-staff-engineer-book-notes.html](https://foo.zone/gemfeed/2024-10-24-staff-engineer-book-notes.html) +[https://foo.z...ok-notes.html](https://foo.zone/gemfeed/2024-10-24-staff-engineer-book-notes.html) ### Looking at `#Kubernetes`, it's pretty much ... @@ -133,20 +137,20 @@ Looking at `#Kubernetes`, it's pretty much following the Unix way of doing thing There has been an outage at the upstream network provider for OpenBSD.Amsterdam (hoster, I am using). This was the first real-world test for my KISS HA setup, and it worked flawlessly! All my sites and services failed over automatically to my other `#OpenBSD` VM! -[https://foo.zone/gemfeed/2024-04-...gh-availability-with-OpenBSD.html](https://foo.zone/gemfeed/2024-04-01-KISS-high-availability-with-OpenBSD.html) +[https://foo.z...-OpenBSD.html](https://foo.zone/gemfeed/2024-04-01-KISS-high-availability-with-OpenBSD.html) [https://openbsd.amsterdam/](https://openbsd.amsterdam/) ### One of the more confusing parts in Go, nil ... One of the more confusing parts in Go, nil values vs nil errors: `#golang` -[https://unexpected-go.com/nil-errors-that-are-non-nil-errors.html](https://unexpected-go.com/nil-errors-that-are-non-nil-errors.html) +[https://unexp...l-errors.html](https://unexpected-go.com/nil-errors-that-are-non-nil-errors.html) ### Agreeably, writing down with Diagrams helps you ... Agreeably, writing down with Diagrams helps you to think things more through. And keeps others on the same page. Only worth for projects from a certain size, IMHO. -[https://ntietz.com/blog/reasons-to-write-design-docs/](https://ntietz.com/blog/reasons-to-write-design-docs/) +[https://ntiet...-design-docs/](https://ntietz.com/blog/reasons-to-write-design-docs/) ### I like the idea of types in Ruby. Raku is ... @@ -158,31 +162,37 @@ I like the idea of types in Ruby. Raku is supports that already, but in Ruby, yo So, `#Haskell` is better suited for general purpose than `#Rust`? I thought deploying something in Haskell means publishing an academic paper :-) Interesting rant about Rust, though: -[https://chrisdone.com/posts/rust/](https://chrisdone.com/posts/rust/) +[https://chris...m/posts/rust/](https://chrisdone.com/posts/rust/) ### At first, functional options add a bit of ... At first, functional options add a bit of boilerplate, but they turn out to be quite neat, especially when you have very long parameter lists that need to be made neat and tidy. `#golang` -[https://www.calhoun.io/using-func...instead-of-method-chaining-in-go/](https://www.calhoun.io/using-functional-options-instead-of-method-chaining-in-go/) +[https://www.c...aining-in-go/](https://www.calhoun.io/using-functional-options-instead-of-method-chaining-in-go/) ### Revamping my home lab a little bit. `#freebsd` ... Revamping my home lab a little bit. `#freebsd` `#bhyve` `#rocky` `#linux` `#vm` `#k3s` `#kuberbetes` `#wireguard` `#zfs` `#nfs` `#ha` `#relayd` `#k8s` `#selfhosting` `#self`-hosting `#homelab` `#home`-lab -[https://foo.zone/gemfeed/2024-11-...bernetes-with-freebsd-part-1.html](https://foo.zone/gemfeed/2024-11-17-f3s-kubernetes-with-freebsd-part-1.html) +[https://foo.z...d-part-1.html](https://foo.zone/gemfeed/2024-11-17-f3s-kubernetes-with-freebsd-part-1.html) + +### Revamping my home lab a little bit. `#freebsd` ... + +Revamping my home lab a little bit. `#freebsd` `#bhyve` `#rocky` `#linux` `#vm` `#k3s` `#kubernetes` `#wireguard` `#zfs` `#nfs` `#ha` `#relayd` `#k8s` `#selfhosting` `#homelab` + +[https://foo.z...d-part-1.html](https://foo.zone/gemfeed/2024-11-17-f3s-kubernetes-with-freebsd-part-1.html) ### Wondering to which `#web` `#browser` I should ... Wondering to which `#web` `#browser` I should switch now personally ... -[https://www.osnews.com/story/1411...cy-for-open-web-privacy-and-more/](https://www.osnews.com/story/141100/mozilla-foundation-lays-off-30-of-its-employees-ends-advocacy-for-open-web-privacy-and-more/) +[https://www.o...acy-and-more/](https://www.osnews.com/story/141100/mozilla-foundation-lays-off-30-of-its-employees-ends-advocacy-for-open-web-privacy-and-more/) ### eks-node-viewer is a nifty tool, showing the ... eks-node-viewer is a nifty tool, showing the compute nodes currently in use in the `#EKS` cluster. especially useful when dynamically allocating nodes with `#karpenter` or auto scaling groups. -[https://github.com/awslabs/eks-node-viewer](https://github.com/awslabs/eks-node-viewer) +[https://githu...s-node-viewer](https://github.com/awslabs/eks-node-viewer) ### Have put more Photos on - On my static photo ... @@ -194,13 +204,13 @@ Have put more Photos on - On my static photo sites - Generated with a `#bash` sc In Go, passing pointers are not automatically faster than values. Pointers often force the memory to be allocated on the heap, adding GC overhad. With values, Go can determine whether to put the memory on the stack instead. But with large structs/objects (how you want to call them) or if you want to modify state, then pointers are the semantic to use. `#golang` -[https://blog.boot.dev/golang/pointers-faster-than-values/](https://blog.boot.dev/golang/pointers-faster-than-values/) +[https://blog....-than-values/](https://blog.boot.dev/golang/pointers-faster-than-values/) ### Myself being part of an on-call rotations over ... Myself being part of an on-call rotations over my whole professional life, just have learned this lesson "Tell people who are new to on-call: Just have fun" :-) This is a neat blog post to read: -[https://ntietz.com/blog/what-i-tell-people-new-to-oncall/](https://ntietz.com/blog/what-i-tell-people-new-to-oncall/) +[https://ntiet...ew-to-oncall/](https://ntietz.com/blog/what-i-tell-people-new-to-oncall/) ### Feels good to code in my old love `#Perl` again ... @@ -218,31 +228,31 @@ This is an interactive summary of the Go release, with a lot of examples utilisi Thats unexpected, you cant remove a NaN key from a map without clearing it! `#golang` -[https://unexpected-go.com/you-can...om-a-map-without-clearing-it.html](https://unexpected-go.com/you-cant-remove-a-nan-key-from-a-map-without-clearing-it.html) +[https://unexp...aring-it.html](https://unexpected-go.com/you-cant-remove-a-nan-key-from-a-map-without-clearing-it.html) ### My second blog post about revamping my home lab ... My second blog post about revamping my home lab a little bit just hit the net. `#FreeBSD` `#ZFS` `#n100` `#k8s` `#k3s` `#kubernetes` -[https://foo.zone/gemfeed/2024-12-...bernetes-with-freebsd-part-2.html](https://foo.zone/gemfeed/2024-12-03-f3s-kubernetes-with-freebsd-part-2.html) +[https://foo.z...d-part-2.html](https://foo.zone/gemfeed/2024-12-03-f3s-kubernetes-with-freebsd-part-2.html) ### Very insightful article about tech hiring in ... Very insightful article about tech hiring in the age of LLMs. As an interviewer, I have experienced some of the scrnarios already first hand... -[https://newsletter.pragmaticengin...m/p/how-genai-changes-tech-hiring](https://newsletter.pragmaticengineer.com/p/how-genai-changes-tech-hiring) +[https://newsl...s-tech-hiring](https://newsletter.pragmaticengineer.com/p/how-genai-changes-tech-hiring) ### for `#bpf` `#ebpf` performance debugging, have ... for `#bpf` `#ebpf` performance debugging, have a look at bpftop from Netflix. A neat tool showing you the estimated CPU time and other performance statistics for all the BPF programs currently loaded into the `#linux` kernel. Highly recommend! -[https://github.com/Netflix/bpftop](https://github.com/Netflix/bpftop) +[https://githu...etflix/bpftop](https://github.com/Netflix/bpftop) ### 89 things he/she knows about Git commits is a ... 89 things he/she knows about Git commits is a neat list of `#Git` wisdoms -[https://www.jvt.me/posts/2024/07/12/things-know-commits/](https://www.jvt.me/posts/2024/07/12/things-know-commits/) +[https://www.j...know-commits/](https://www.jvt.me/posts/2024/07/12/things-know-commits/) ### I found that working on multiple side projects ... @@ -252,50 +262,50 @@ I found that working on multiple side projects concurrently is better than conce Agreed? Agreed. Besides `#Ruby`, I would also add `#RakuLang` and `#Perl` @Perl to the list of languages that are great for shell scripts - "Making Easy Things Easy and Hard Things Possible" -[https://lucasoshiro.github.io/posts-en/2024-06-17-ruby-shellscript/](https://lucasoshiro.github.io/posts-en/2024-06-17-ruby-shellscript/) +[https://lucas...-shellscript/](https://lucasoshiro.github.io/posts-en/2024-06-17-ruby-shellscript/) ### Plan9 assembly format in Go, but wait, it's not ... Plan9 assembly format in Go, but wait, it's not the Operating System Plan9! `#golang` `#rabbithole` -[https://www.osnews.com/story/1409...emo-speeding-up-calculations-450/](https://www.osnews.com/story/140941/go-plan9-memo-speeding-up-calculations-450/) +[https://www.o...ulations-450/](https://www.osnews.com/story/140941/go-plan9-memo-speeding-up-calculations-450/) ### This is a neat blog post about the Helix text ... This is a neat blog post about the Helix text editor, to which I personally switched around a year ago (from NeoVim). I should blog about my experience as well. To summarize: I am using it together with the terminal multiplexer `#tmux`. It doesn't bother me that Helix is purely terminal-based and therefore everything has to be in the same font. `#HelixEditor` -[https://jonathan-frere.com/posts/helix/](https://jonathan-frere.com/posts/helix/) +[https://jonat.../posts/helix/](https://jonathan-frere.com/posts/helix/) ### This blog post is basically a rant against ... This blog post is basically a rant against DataDog... Personally, I don't have much experience with DataDog (actually, I have never used it), but one reason to work with logs at my day job (with over 2,000 physical server machines) and to be cost-effective is by using dtail! `#dtail` `#logs` `#logmanagement` -[https://crys.site/blog/2024/reinventint-the-weel/](https://crys.site/blog/2024/reinventint-the-weel/) +[https://crys....int-the-weel/](https://crys.site/blog/2024/reinventint-the-weel/) [https://dtail.dev](https://dtail.dev) ### Quick trick to get Helix themes selected ... Quick trick to get Helix themes selected randomly `#HelixEditor` -[https://foo.zone/gemfeed/2024-12-15-random-helix-themes.html](https://foo.zone/gemfeed/2024-12-15-random-helix-themes.html) +[https://foo.z...x-themes.html](https://foo.zone/gemfeed/2024-12-15-random-helix-themes.html) ### Example where complexity attacks you from ... Example where complexity attacks you from behind `#k8s` `#kubernetes` `#OpenAI` -[https://surfingcomplexity.blog/20...-openai-public-incident-write-up/](https://surfingcomplexity.blog/2024/12/14/quick-takes-on-the-recent-openai-public-incident-write-up/) +[https://surfi...ent-write-up/](https://surfingcomplexity.blog/2024/12/14/quick-takes-on-the-recent-openai-public-incident-write-up/) ### LLMs for Ops? Summaries of logs, probabilities ... LLMs for Ops? Summaries of logs, probabilities about correctness, auto-generating Ansible, some uses cases are there. Wouldn't trust it fully, though. -[https://youtu.be/WodaffxVq-E?si=noY0egrfl5izCSQI](https://youtu.be/WodaffxVq-E?si=noY0egrfl5izCSQI) +[https://youtu...0egrfl5izCSQI](https://youtu.be/WodaffxVq-E?si=noY0egrfl5izCSQI) ### Excellent article about your dream Product ... Excellent article about your dream Product Manager: Why every software team needs a product manager to thrive via @wallabagapp -[https://testdouble.com/insights/w...elerate-improve-software-delivery](https://testdouble.com/insights/why-product-managers-accelerate-improve-software-delivery) +[https://testd...ware-delivery](https://testdouble.com/insights/why-product-managers-accelerate-improve-software-delivery) ### I just finished reading all chapters of CPU ... @@ -307,17 +317,17 @@ I just finished reading all chapters of CPU land: ... not claiming to remember e Indeed, useful to know this stuff! `#sre` -[https://biriukov.dev/docs/resolve...vers-and-dual-stack-applications/](https://biriukov.dev/docs/resolver-dual-stack-application/0-sre-should-know-about-gnu-linux-resolvers-and-dual-stack-applications/) +[https://biriu...applications/](https://biriukov.dev/docs/resolver-dual-stack-application/0-sre-should-know-about-gnu-linux-resolvers-and-dual-stack-applications/) ### It's the small things, which make Unix like ... It's the small things, which make Unix like systems, like GNU/Linux, interesting. Didn't know about this `#GNU` `#Tar` behaviour yet: -[https://xeiaso.net/notes/2024/pop-quiz-tar/](https://xeiaso.net/notes/2024/pop-quiz-tar/) +[https://xeias...pop-quiz-tar/](https://xeiaso.net/notes/2024/pop-quiz-tar/) ### My New Year's resolution is not to start any ... -My plan for the New Year is not to start any new non-fiction books (or only a few) but to re-read and listen to my favorites, which I read to reflect on and see things from different perspectives. Every time you re-read a book, you gain new insights. +My New Year's resolution is not to start any new non-fiction books (or only very few) but to re-read and listen to my favorites, which I read to reflect on and see things from different perspectives. Every time you re-read a book, you gain new insights. Other related posts: -- cgit v1.2.3 From 5199c955fe9cf39af2f19225cb3747186f9f00a3 Mon Sep 17 00:00:00 2001 From: Paul Buetow Date: Tue, 31 Dec 2024 18:47:43 +0200 Subject: Update content for md --- ...25-01-01-posts-from-october-to-december-2024.md | 73 +++++++++++----------- 1 file changed, 35 insertions(+), 38 deletions(-) (limited to 'gemfeed') diff --git a/gemfeed/2025-01-01-posts-from-october-to-december-2024.md b/gemfeed/2025-01-01-posts-from-october-to-december-2024.md index 2edc9d3e..eee5b7a1 100644 --- a/gemfeed/2025-01-01-posts-from-october-to-december-2024.md +++ b/gemfeed/2025-01-01-posts-from-october-to-december-2024.md @@ -11,12 +11,9 @@ These are from Mastodon and LinkedIn. Have a look at my about page for my social [My about page](../about/index.md) [https://codeberg.org/snonux/gos](https://codeberg.org/snonux/gos) -# Posts for 202410 202411 202412 - ## Table of Contents * [⇢ Posts from October to December 2024](#posts-from-october-to-december-2024) -* [⇢ Posts for 202410 202411 202412](#posts-for-202410-202411-202412) * [⇢ ⇢ October 2024](#october-2024) * [⇢ ⇢ ⇢ First on-call experience in a startup. Doesn't ...](#first-on-call-experience-in-a-startup-doesn-t-) * [⇢ ⇢ ⇢ Reviewing your own PR or MR before asking ...](#reviewing-your-own-pr-or-mr-before-asking-) @@ -71,43 +68,43 @@ These are from Mastodon and LinkedIn. Have a look at my about page for my social First on-call experience in a startup. Doesn't sound a lot of fun! But the lessons were learned! `#sre` -[https://ntiet...irst-on-call/](https://ntietz.com/blog/lessons-from-my-first-on-call/) +[ntietz.com/bl...irst-on-call/](https://ntietz.com/blog/lessons-from-my-first-on-call/) ### Reviewing your own PR or MR before asking ... Reviewing your own PR or MR before asking others to review it makes a lot of sense. Have seen so many silly mistakes which would have been avoided. Saving time for the real reviewer. -[https://www.j...-code-review/](https://www.jvt.me/posts/2019/01/12/self-code-review/) +[www.jvt.me/po...-code-review/](https://www.jvt.me/posts/2019/01/12/self-code-review/) ### Fun with defer in `#golang`, I did't know, that ... Fun with defer in `#golang`, I did't know, that a defer object can either be heap or stack allocated. And there are some rules for inlining, too. -[https://victo.../defer-in-go/](https://victoriametrics.com/blog/defer-in-go/) +[victoriametri.../defer-in-go/](https://victoriametrics.com/blog/defer-in-go/) ### I have been in incidents. Understandably, ... I have been in incidents. Understandably, everyone wants the issue to be resolved as quickly and others want to know how long TTR will be. IMHO, providing no estimates at all is no solution either. So maybe give a rough estimate but clearly communicate that the estimate is rough and that X, Y, and Z can interfere, meaning there is a chance it will take longer to resolve the incident. Just my thought. What's yours? -[https://fireh...on-estimates/](https://firehydrant.com/blog/hot-take-dont-provide-incident-resolution-estimates/) +[firehydrant.c...on-estimates/](https://firehydrant.com/blog/hot-take-dont-provide-incident-resolution-estimates/) ### Little tips using strings in `#golang` and I ... Little tips using strings in `#golang` and I personally think one must look more into the std lib (not just for strings, also for slices, maps,...), there are tons of useful helper functions. -[https://www.c...trings-in-go/](https://www.calhoun.io/6-tips-for-using-strings-in-go/) +[www.calhoun.i...trings-in-go/](https://www.calhoun.io/6-tips-for-using-strings-in-go/) ### Reading this post about `#rust` (especially the ... Reading this post about `#rust` (especially the first part), I think I made a good choice in deciding to dive into `#golang` instead. There was a point where I wanted to learn a new programming language, and Rust was on my list of choices. I think the Go project does a much better job of deciding what goes into the language and how. What are your thoughts? -[https://josep...writing-rust/](https://josephg.com/blog/rewriting-rust/) +[josephg.com/b...writing-rust/](https://josephg.com/blog/rewriting-rust/) ### The opposite of `#ChaosMonkey` ... ... The opposite of `#ChaosMonkey` ... automatically repairing and healing services helping to reduce manual toil work. Runbooks and scripts are only the first step, followed by a fully blown service written in Go. Could be useful, but IMHO why not rather address the root causes of the manual toil work? `#sre` -[https://blog....t-cloudflare/](https://blog.cloudflare.com/nl-nl/improving-platform-resilience-at-cloudflare/) +[blog.cloudfla...t-cloudflare/](https://blog.cloudflare.com/nl-nl/improving-platform-resilience-at-cloudflare/) ## November 2024 @@ -115,7 +112,7 @@ The opposite of `#ChaosMonkey` ... automatically repairing and healing services I just became a Silver Patreon for OSnews. What is OSnews? It is an independent news site about IT. It is slightly independent and, at times, alternative. I have enjoyed it since my early student days. This one and other projects I financially support are listed here: -[https://foo.z...-support.html](https://foo.zone/gemfeed/2024-09-07-projects-i-support.html) +[foo.zone/gemf...-support.html](https://foo.zone/gemfeed/2024-09-07-projects-i-support.html) ### Until now, I wasn't aware, that Go is under a ... @@ -127,7 +124,7 @@ Until now, I wasn't aware, that Go is under a BSD-style license (3-clause as it These are some book notes from "Staff Engineer" – there is some really good insight into what is expected from a Staff Engineer and beyond in the industry. I wish I had read the book earlier. -[https://foo.z...ok-notes.html](https://foo.zone/gemfeed/2024-10-24-staff-engineer-book-notes.html) +[foo.zone/gemf...ok-notes.html](https://foo.zone/gemfeed/2024-10-24-staff-engineer-book-notes.html) ### Looking at `#Kubernetes`, it's pretty much ... @@ -137,20 +134,20 @@ Looking at `#Kubernetes`, it's pretty much following the Unix way of doing thing There has been an outage at the upstream network provider for OpenBSD.Amsterdam (hoster, I am using). This was the first real-world test for my KISS HA setup, and it worked flawlessly! All my sites and services failed over automatically to my other `#OpenBSD` VM! -[https://foo.z...-OpenBSD.html](https://foo.zone/gemfeed/2024-04-01-KISS-high-availability-with-OpenBSD.html) +[foo.zone/gemf...-OpenBSD.html](https://foo.zone/gemfeed/2024-04-01-KISS-high-availability-with-OpenBSD.html) [https://openbsd.amsterdam/](https://openbsd.amsterdam/) ### One of the more confusing parts in Go, nil ... One of the more confusing parts in Go, nil values vs nil errors: `#golang` -[https://unexp...l-errors.html](https://unexpected-go.com/nil-errors-that-are-non-nil-errors.html) +[unexpected-go...l-errors.html](https://unexpected-go.com/nil-errors-that-are-non-nil-errors.html) ### Agreeably, writing down with Diagrams helps you ... Agreeably, writing down with Diagrams helps you to think things more through. And keeps others on the same page. Only worth for projects from a certain size, IMHO. -[https://ntiet...-design-docs/](https://ntietz.com/blog/reasons-to-write-design-docs/) +[ntietz.com/bl...-design-docs/](https://ntietz.com/blog/reasons-to-write-design-docs/) ### I like the idea of types in Ruby. Raku is ... @@ -162,37 +159,37 @@ I like the idea of types in Ruby. Raku is supports that already, but in Ruby, yo So, `#Haskell` is better suited for general purpose than `#Rust`? I thought deploying something in Haskell means publishing an academic paper :-) Interesting rant about Rust, though: -[https://chris...m/posts/rust/](https://chrisdone.com/posts/rust/) +[chrisdone.com...m/posts/rust/](https://chrisdone.com/posts/rust/) ### At first, functional options add a bit of ... At first, functional options add a bit of boilerplate, but they turn out to be quite neat, especially when you have very long parameter lists that need to be made neat and tidy. `#golang` -[https://www.c...aining-in-go/](https://www.calhoun.io/using-functional-options-instead-of-method-chaining-in-go/) +[www.calhoun.i...aining-in-go/](https://www.calhoun.io/using-functional-options-instead-of-method-chaining-in-go/) ### Revamping my home lab a little bit. `#freebsd` ... Revamping my home lab a little bit. `#freebsd` `#bhyve` `#rocky` `#linux` `#vm` `#k3s` `#kuberbetes` `#wireguard` `#zfs` `#nfs` `#ha` `#relayd` `#k8s` `#selfhosting` `#self`-hosting `#homelab` `#home`-lab -[https://foo.z...d-part-1.html](https://foo.zone/gemfeed/2024-11-17-f3s-kubernetes-with-freebsd-part-1.html) +[foo.zone/gemf...d-part-1.html](https://foo.zone/gemfeed/2024-11-17-f3s-kubernetes-with-freebsd-part-1.html) ### Revamping my home lab a little bit. `#freebsd` ... Revamping my home lab a little bit. `#freebsd` `#bhyve` `#rocky` `#linux` `#vm` `#k3s` `#kubernetes` `#wireguard` `#zfs` `#nfs` `#ha` `#relayd` `#k8s` `#selfhosting` `#homelab` -[https://foo.z...d-part-1.html](https://foo.zone/gemfeed/2024-11-17-f3s-kubernetes-with-freebsd-part-1.html) +[foo.zone/gemf...d-part-1.html](https://foo.zone/gemfeed/2024-11-17-f3s-kubernetes-with-freebsd-part-1.html) ### Wondering to which `#web` `#browser` I should ... Wondering to which `#web` `#browser` I should switch now personally ... -[https://www.o...acy-and-more/](https://www.osnews.com/story/141100/mozilla-foundation-lays-off-30-of-its-employees-ends-advocacy-for-open-web-privacy-and-more/) +[www.osnews.co...acy-and-more/](https://www.osnews.com/story/141100/mozilla-foundation-lays-off-30-of-its-employees-ends-advocacy-for-open-web-privacy-and-more/) ### eks-node-viewer is a nifty tool, showing the ... eks-node-viewer is a nifty tool, showing the compute nodes currently in use in the `#EKS` cluster. especially useful when dynamically allocating nodes with `#karpenter` or auto scaling groups. -[https://githu...s-node-viewer](https://github.com/awslabs/eks-node-viewer) +[github.com/aw...s-node-viewer](https://github.com/awslabs/eks-node-viewer) ### Have put more Photos on - On my static photo ... @@ -204,13 +201,13 @@ Have put more Photos on - On my static photo sites - Generated with a `#bash` sc In Go, passing pointers are not automatically faster than values. Pointers often force the memory to be allocated on the heap, adding GC overhad. With values, Go can determine whether to put the memory on the stack instead. But with large structs/objects (how you want to call them) or if you want to modify state, then pointers are the semantic to use. `#golang` -[https://blog....-than-values/](https://blog.boot.dev/golang/pointers-faster-than-values/) +[blog.boot.dev...-than-values/](https://blog.boot.dev/golang/pointers-faster-than-values/) ### Myself being part of an on-call rotations over ... Myself being part of an on-call rotations over my whole professional life, just have learned this lesson "Tell people who are new to on-call: Just have fun" :-) This is a neat blog post to read: -[https://ntiet...ew-to-oncall/](https://ntietz.com/blog/what-i-tell-people-new-to-oncall/) +[ntietz.com/bl...ew-to-oncall/](https://ntietz.com/blog/what-i-tell-people-new-to-oncall/) ### Feels good to code in my old love `#Perl` again ... @@ -228,31 +225,31 @@ This is an interactive summary of the Go release, with a lot of examples utilisi Thats unexpected, you cant remove a NaN key from a map without clearing it! `#golang` -[https://unexp...aring-it.html](https://unexpected-go.com/you-cant-remove-a-nan-key-from-a-map-without-clearing-it.html) +[unexpected-go...aring-it.html](https://unexpected-go.com/you-cant-remove-a-nan-key-from-a-map-without-clearing-it.html) ### My second blog post about revamping my home lab ... My second blog post about revamping my home lab a little bit just hit the net. `#FreeBSD` `#ZFS` `#n100` `#k8s` `#k3s` `#kubernetes` -[https://foo.z...d-part-2.html](https://foo.zone/gemfeed/2024-12-03-f3s-kubernetes-with-freebsd-part-2.html) +[foo.zone/gemf...d-part-2.html](https://foo.zone/gemfeed/2024-12-03-f3s-kubernetes-with-freebsd-part-2.html) ### Very insightful article about tech hiring in ... Very insightful article about tech hiring in the age of LLMs. As an interviewer, I have experienced some of the scrnarios already first hand... -[https://newsl...s-tech-hiring](https://newsletter.pragmaticengineer.com/p/how-genai-changes-tech-hiring) +[newsletter.pr...s-tech-hiring](https://newsletter.pragmaticengineer.com/p/how-genai-changes-tech-hiring) ### for `#bpf` `#ebpf` performance debugging, have ... for `#bpf` `#ebpf` performance debugging, have a look at bpftop from Netflix. A neat tool showing you the estimated CPU time and other performance statistics for all the BPF programs currently loaded into the `#linux` kernel. Highly recommend! -[https://githu...etflix/bpftop](https://github.com/Netflix/bpftop) +[github.com/Ne...etflix/bpftop](https://github.com/Netflix/bpftop) ### 89 things he/she knows about Git commits is a ... 89 things he/she knows about Git commits is a neat list of `#Git` wisdoms -[https://www.j...know-commits/](https://www.jvt.me/posts/2024/07/12/things-know-commits/) +[www.jvt.me/po...know-commits/](https://www.jvt.me/posts/2024/07/12/things-know-commits/) ### I found that working on multiple side projects ... @@ -262,50 +259,50 @@ I found that working on multiple side projects concurrently is better than conce Agreed? Agreed. Besides `#Ruby`, I would also add `#RakuLang` and `#Perl` @Perl to the list of languages that are great for shell scripts - "Making Easy Things Easy and Hard Things Possible" -[https://lucas...-shellscript/](https://lucasoshiro.github.io/posts-en/2024-06-17-ruby-shellscript/) +[lucasoshiro.g...-shellscript/](https://lucasoshiro.github.io/posts-en/2024-06-17-ruby-shellscript/) ### Plan9 assembly format in Go, but wait, it's not ... Plan9 assembly format in Go, but wait, it's not the Operating System Plan9! `#golang` `#rabbithole` -[https://www.o...ulations-450/](https://www.osnews.com/story/140941/go-plan9-memo-speeding-up-calculations-450/) +[www.osnews.co...ulations-450/](https://www.osnews.com/story/140941/go-plan9-memo-speeding-up-calculations-450/) ### This is a neat blog post about the Helix text ... This is a neat blog post about the Helix text editor, to which I personally switched around a year ago (from NeoVim). I should blog about my experience as well. To summarize: I am using it together with the terminal multiplexer `#tmux`. It doesn't bother me that Helix is purely terminal-based and therefore everything has to be in the same font. `#HelixEditor` -[https://jonat.../posts/helix/](https://jonathan-frere.com/posts/helix/) +[jonathan-frer.../posts/helix/](https://jonathan-frere.com/posts/helix/) ### This blog post is basically a rant against ... This blog post is basically a rant against DataDog... Personally, I don't have much experience with DataDog (actually, I have never used it), but one reason to work with logs at my day job (with over 2,000 physical server machines) and to be cost-effective is by using dtail! `#dtail` `#logs` `#logmanagement` -[https://crys....int-the-weel/](https://crys.site/blog/2024/reinventint-the-weel/) +[crys.site/blo...int-the-weel/](https://crys.site/blog/2024/reinventint-the-weel/) [https://dtail.dev](https://dtail.dev) ### Quick trick to get Helix themes selected ... Quick trick to get Helix themes selected randomly `#HelixEditor` -[https://foo.z...x-themes.html](https://foo.zone/gemfeed/2024-12-15-random-helix-themes.html) +[foo.zone/gemf...x-themes.html](https://foo.zone/gemfeed/2024-12-15-random-helix-themes.html) ### Example where complexity attacks you from ... Example where complexity attacks you from behind `#k8s` `#kubernetes` `#OpenAI` -[https://surfi...ent-write-up/](https://surfingcomplexity.blog/2024/12/14/quick-takes-on-the-recent-openai-public-incident-write-up/) +[surfingcomple...ent-write-up/](https://surfingcomplexity.blog/2024/12/14/quick-takes-on-the-recent-openai-public-incident-write-up/) ### LLMs for Ops? Summaries of logs, probabilities ... LLMs for Ops? Summaries of logs, probabilities about correctness, auto-generating Ansible, some uses cases are there. Wouldn't trust it fully, though. -[https://youtu...0egrfl5izCSQI](https://youtu.be/WodaffxVq-E?si=noY0egrfl5izCSQI) +[youtu.be/Woda...0egrfl5izCSQI](https://youtu.be/WodaffxVq-E?si=noY0egrfl5izCSQI) ### Excellent article about your dream Product ... Excellent article about your dream Product Manager: Why every software team needs a product manager to thrive via @wallabagapp -[https://testd...ware-delivery](https://testdouble.com/insights/why-product-managers-accelerate-improve-software-delivery) +[testdouble.co...ware-delivery](https://testdouble.com/insights/why-product-managers-accelerate-improve-software-delivery) ### I just finished reading all chapters of CPU ... @@ -317,13 +314,13 @@ I just finished reading all chapters of CPU land: ... not claiming to remember e Indeed, useful to know this stuff! `#sre` -[https://biriu...applications/](https://biriukov.dev/docs/resolver-dual-stack-application/0-sre-should-know-about-gnu-linux-resolvers-and-dual-stack-applications/) +[biriukov.dev/...applications/](https://biriukov.dev/docs/resolver-dual-stack-application/0-sre-should-know-about-gnu-linux-resolvers-and-dual-stack-applications/) ### It's the small things, which make Unix like ... It's the small things, which make Unix like systems, like GNU/Linux, interesting. Didn't know about this `#GNU` `#Tar` behaviour yet: -[https://xeias...pop-quiz-tar/](https://xeiaso.net/notes/2024/pop-quiz-tar/) +[xeiaso.net/no...pop-quiz-tar/](https://xeiaso.net/notes/2024/pop-quiz-tar/) ### My New Year's resolution is not to start any ... -- cgit v1.2.3 From 582a47dca61a00a4480b31aea13a841357bf8e10 Mon Sep 17 00:00:00 2001 From: Paul Buetow Date: Tue, 31 Dec 2024 18:49:19 +0200 Subject: Update content for md --- .../2025-01-01-posts-from-october-to-december-2024.md | 18 +++++++++--------- 1 file changed, 9 insertions(+), 9 deletions(-) (limited to 'gemfeed') diff --git a/gemfeed/2025-01-01-posts-from-october-to-december-2024.md b/gemfeed/2025-01-01-posts-from-october-to-december-2024.md index eee5b7a1..475add72 100644 --- a/gemfeed/2025-01-01-posts-from-october-to-december-2024.md +++ b/gemfeed/2025-01-01-posts-from-october-to-december-2024.md @@ -118,7 +118,7 @@ I just became a Silver Patreon for OSnews. What is OSnews? It is an independent Until now, I wasn't aware, that Go is under a BSD-style license (3-clause as it seems). Neat. I don't know why, but I always was under the impression it would be MIT. `#bsd` `#golang` -[https://go.dev/LICENSE](https://go.dev/LICENSE) +[go.dev/LICENSE](https://go.dev/LICENSE) ### These are some book notes from "Staff Engineer" ... @@ -135,7 +135,7 @@ Looking at `#Kubernetes`, it's pretty much following the Unix way of doing thing There has been an outage at the upstream network provider for OpenBSD.Amsterdam (hoster, I am using). This was the first real-world test for my KISS HA setup, and it worked flawlessly! All my sites and services failed over automatically to my other `#OpenBSD` VM! [foo.zone/gemf...-OpenBSD.html](https://foo.zone/gemfeed/2024-04-01-KISS-high-availability-with-OpenBSD.html) -[https://openbsd.amsterdam/](https://openbsd.amsterdam/) +[openbsd.amsterdam/](https://openbsd.amsterdam/) ### One of the more confusing parts in Go, nil ... @@ -153,13 +153,13 @@ Agreeably, writing down with Diagrams helps you to think things more through. An I like the idea of types in Ruby. Raku is supports that already, but in Ruby, you must specify the types in a separate .rbs file, which is, in my opinion, cumbersome and is a reason not to use it extensively for now. I believe there are efforts to embed the type information in the standard .rb files, and that the .rbs is just an experiment to see how types could work out without introducing changes into the core Ruby language itself right now? `#Ruby` `#RakuLang` -[https://github.com/ruby/rbs](https://github.com/ruby/rbs) +[github.com/ruby/rbs](https://github.com/ruby/rbs) ### So, `#Haskell` is better suited for general ... So, `#Haskell` is better suited for general purpose than `#Rust`? I thought deploying something in Haskell means publishing an academic paper :-) Interesting rant about Rust, though: -[chrisdone.com...m/posts/rust/](https://chrisdone.com/posts/rust/) +[chrisdone.com/posts/rust/](https://chrisdone.com/posts/rust/) ### At first, functional options add a bit of ... @@ -195,7 +195,7 @@ eks-node-viewer is a nifty tool, showing the compute nodes currently in use in t Have put more Photos on - On my static photo sites - Generated with a `#bash` script -[https://irregular.ninja](https://irregular.ninja) +[irregular.ninja](https://irregular.ninja) ### In Go, passing pointers are not automatically ... @@ -217,7 +217,7 @@ Feels good to code in my old love `#Perl` again after a while. I am implementing This is an interactive summary of the Go release, with a lot of examples utilising iterators in the slices and map packages. Love it! `#golang` -[https://antonz.org/go-1-23/](https://antonz.org/go-1-23/) +[antonz.org/go-1-23/](https://antonz.org/go-1-23/) ## December 2024 @@ -243,7 +243,7 @@ Very insightful article about tech hiring in the age of LLMs. As an interviewer, for `#bpf` `#ebpf` performance debugging, have a look at bpftop from Netflix. A neat tool showing you the estimated CPU time and other performance statistics for all the BPF programs currently loaded into the `#linux` kernel. Highly recommend! -[github.com/Ne...etflix/bpftop](https://github.com/Netflix/bpftop) +[github.com/Netflix/bpftop](https://github.com/Netflix/bpftop) ### 89 things he/she knows about Git commits is a ... @@ -278,7 +278,7 @@ This is a neat blog post about the Helix text editor, to which I personally swit This blog post is basically a rant against DataDog... Personally, I don't have much experience with DataDog (actually, I have never used it), but one reason to work with logs at my day job (with over 2,000 physical server machines) and to be cost-effective is by using dtail! `#dtail` `#logs` `#logmanagement` [crys.site/blo...int-the-weel/](https://crys.site/blog/2024/reinventint-the-weel/) -[https://dtail.dev](https://dtail.dev) +[dtail.dev](https://dtail.dev) ### Quick trick to get Helix themes selected ... @@ -308,7 +308,7 @@ Excellent article about your dream Product Manager: Why every software team need I just finished reading all chapters of CPU land: ... not claiming to remember every detail, but it is a great refresher how CPUs and operating systems actually work under the hood when you execute a program, which we tend to forget in our higher abstraction world. I liked the "story" and some of the jokes along the way! Size wise, it is pretty digestable (not talking about books, but only 7 web articles/chapters)! `#cpu` `#linux` `#unix` `#kernel` `#macOS` -[https://cpu.land/](https://cpu.land/) +[cpu.land/](https://cpu.land/) ### Indeed, useful to know this stuff! `#sre` ... -- cgit v1.2.3 From 9336352dee368ecbbc45aa990a41ed1ba68e6f71 Mon Sep 17 00:00:00 2001 From: Paul Buetow Date: Tue, 31 Dec 2024 19:00:58 +0200 Subject: Update content for md --- gemfeed/2025-01-01-posts-from-october-to-december-2024.md | 9 +-------- 1 file changed, 1 insertion(+), 8 deletions(-) (limited to 'gemfeed') diff --git a/gemfeed/2025-01-01-posts-from-october-to-december-2024.md b/gemfeed/2025-01-01-posts-from-october-to-december-2024.md index 475add72..e22fa3f7 100644 --- a/gemfeed/2025-01-01-posts-from-october-to-december-2024.md +++ b/gemfeed/2025-01-01-posts-from-october-to-december-2024.md @@ -34,7 +34,6 @@ These are from Mastodon and LinkedIn. Have a look at my about page for my social * [⇢ ⇢ ⇢ So, `#Haskell` is better suited for general ...](#so-haskell-is-better-suited-for-general-) * [⇢ ⇢ ⇢ At first, functional options add a bit of ...](#at-first-functional-options-add-a-bit-of-) * [⇢ ⇢ ⇢ Revamping my home lab a little bit. `#freebsd` ...](#revamping-my-home-lab-a-little-bit-freebsd-) -* [⇢ ⇢ ⇢ Revamping my home lab a little bit. `#freebsd` ...](#revamping-my-home-lab-a-little-bit-freebsd-) * [⇢ ⇢ ⇢ Wondering to which `#web` `#browser` I should ...](#wondering-to-which-web-browser-i-should-) * [⇢ ⇢ ⇢ eks-node-viewer is a nifty tool, showing the ...](#eks-node-viewer-is-a-nifty-tool-showing-the-) * [⇢ ⇢ ⇢ Have put more Photos on - On my static photo ...](#have-put-more-photos-on---on-my-static-photo-) @@ -169,12 +168,6 @@ At first, functional options add a bit of boilerplate, but they turn out to be q ### Revamping my home lab a little bit. `#freebsd` ... -Revamping my home lab a little bit. `#freebsd` `#bhyve` `#rocky` `#linux` `#vm` `#k3s` `#kuberbetes` `#wireguard` `#zfs` `#nfs` `#ha` `#relayd` `#k8s` `#selfhosting` `#self`-hosting `#homelab` `#home`-lab - -[foo.zone/gemf...d-part-1.html](https://foo.zone/gemfeed/2024-11-17-f3s-kubernetes-with-freebsd-part-1.html) - -### Revamping my home lab a little bit. `#freebsd` ... - Revamping my home lab a little bit. `#freebsd` `#bhyve` `#rocky` `#linux` `#vm` `#k3s` `#kubernetes` `#wireguard` `#zfs` `#nfs` `#ha` `#relayd` `#k8s` `#selfhosting` `#homelab` [foo.zone/gemf...d-part-1.html](https://foo.zone/gemfeed/2024-11-17-f3s-kubernetes-with-freebsd-part-1.html) @@ -324,7 +317,7 @@ It's the small things, which make Unix like systems, like GNU/Linux, interesting ### My New Year's resolution is not to start any ... -My New Year's resolution is not to start any new non-fiction books (or only very few) but to re-read and listen to my favorites, which I read to reflect on and see things from different perspectives. Every time you re-read a book, you gain new insights. +A plan of mine for next year is not to start any new non-fiction books (or only very few) but to re-read and listen to my favorites, which I read to reflect on and see things from different perspectives. Every time you re-read a book, you gain new insights. Other related posts: -- cgit v1.2.3 From 56a66c1d071df2f60fdb0338d601694342b417ef Mon Sep 17 00:00:00 2001 From: Paul Buetow Date: Sat, 4 Jan 2025 15:51:18 +0200 Subject: Update content for md --- gemfeed/DRAFT-f3s-kubernetes-with-freebsd-bhyve.md | 132 +++++++++ ...T-f3s-kubernetes-with-freebsd-hardware-setup.md | 41 --- gemfeed/DRAFT-summary-for-202410-202411-202410.md | 311 --------------------- 3 files changed, 132 insertions(+), 352 deletions(-) create mode 100644 gemfeed/DRAFT-f3s-kubernetes-with-freebsd-bhyve.md delete mode 100644 gemfeed/DRAFT-f3s-kubernetes-with-freebsd-hardware-setup.md delete mode 100644 gemfeed/DRAFT-summary-for-202410-202411-202410.md (limited to 'gemfeed') diff --git a/gemfeed/DRAFT-f3s-kubernetes-with-freebsd-bhyve.md b/gemfeed/DRAFT-f3s-kubernetes-with-freebsd-bhyve.md new file mode 100644 index 00000000..4d769fe2 --- /dev/null +++ b/gemfeed/DRAFT-f3s-kubernetes-with-freebsd-bhyve.md @@ -0,0 +1,132 @@ +# f3s: Kubernetes with FreeBSD - Rocky Linux Bhyve VMs - Part 3 + +This is the third blog post about my f3s series for my self-hosting demands in my home lab. f3s? The "f" stands for FreeBSD, and the "3s" stands for k3s, the Kubernetes distribution we will use on FreeBSD-based physical machines. + +[2024-11-17 f3s: Kubernetes with FreeBSD - Part 1: Setting the stage](./2024-11-17-f3s-kubernetes-with-freebsd-part-1.md) +[2024-12-03 f3s: Kubernetes with FreeBSD - Part 2: Hardware and base installation](./2024-12-03-f3s-kubernetes-with-freebsd-part-2.md) + +[![f3s logo](./f3s-kubernetes-with-frhyveeebsd-part-1/f3slogo.png "f3s logo")](./f3s-kubernetes-with-frhyveeebsd-part-1/f3slogo.png) + +## Table of Contents + +* [⇢ f3s: Kubernetes with FreeBSD - Rocky Linux Bhyve VMs - Part 3](#f3s-kubernetes-with-freebsd---rocky-linux-bhyve-vms---part-3) +* [⇢ ⇢ Introduction](#introduction) +* [⇢ ⇢ Basic Bhyve setup](#basic-bhyve-setup) +* [⇢ ⇢ Rocky Linux VMs](#rocky-linux-vms) +* [⇢ ⇢ ⇢ ISO download](#iso-download) +* [⇢ ⇢ ⇢ VM configuration](#vm-configuration) +* [⇢ ⇢ ⇢ VM installation](#vm-installation) + +## Introduction + +In this blog post, we are going to install the Bhyve hypervisor. + +The FreeBSD Bhyve hypervisor is a lightweight, modern hypervisor that enables virtualization on FreeBSD systems. Bhyve's strengths include its minimal overhead, which allows it to achieve near-native performance for virtual machines. It is designed to be efficient and lightweight, leveraging the capabilities of the FreeBSD operating system for performance and network management. + +Bhyve supports running a variety of guest operating systems, including FreeBSD, Linux, and Windows, on hardware platforms that support hardware virtualization extensions (such as Intel VT-x or AMD-V). In our case, we are going to virtualize Rocky Linux, which later on in this series will be used to run k3s. + +## Basic Bhyve setup + +For the management of the Bhyve VMs, we are using `vm-bhyve`, a tool not part of the FreeBSD operating system but available as a ready-to-use package. It eases VM management and reduces a lot of the overhead. We also install the required package to make Bhyve work with the UEFI firmware. + +[https://github.com/churchers/vm-bhyve](https://github.com/churchers/vm-bhyve) + +The following commands are executed on all three hosts `f0`, `f1`, and `f2`, where `re0` is the name of the Ethernet interface (which may need to be adjusted if your hardware is different): + +```sh +paul@f2:~ % doas pkg install vm-bhyve bhyve-firmware +paul@f2:~ % doas sysrc vm_enable=YES +vm_enable: -> YES +paul@f2:~ % doas sysrc vm_dir=zfs:zroot/bhyve +vm_dir: -> zfs:zroot/bhyve +paul@f2:~ % doas zfs create zroot/bhyve +paul@f2:~ % doas vm init +paul@f2:~ % doas vm create public +paul@f2:~ % doas vm switch add public re0 +``` + +Bhyve stores all it's data in the `/bhyve` of the `zroot` ZFS pool: + +```sh +paul@f2:~ % zfs list | grep bhyve +zroot/bhyve 1.74M 453G 1.74M /zroot/bhyve +``` + +For convenience, we also create this symlink: + +```sh +paul@f2:~ % doas ln -s /zroot/bhyve/ /bhyve + +``` + +Now, Bhyve is ready to rumble, but no VMs are there yet: + +```sh +paul@f2:~ % doas vm list +NAME DATASTORE LOADER CPU MEMORY VNC AUTO STATE +``` + +## Rocky Linux VMs + +### ISO download + +We're going to install the Rocky Linux from the latest minimal iso: + +```sh +paul@f2:~ % doas vm iso \ + https://download.rockylinux.org/pub/rocky/9/isos/x86_64/Rocky-9.5-x86_64-minimal.iso +/zroot/bhyve/.iso/Rocky-9.5-x86_64-minimal.iso 1808 MB 4780 kBps 06m28s +paul@f2:/bhyve % doas vm create rocky +``` +### VM configuration + +The default configuration looks like this now: + +```sh +paul@f2:/bhyve/rocky % cat rocky.conf +loader="bhyveload" +cpu=1 +memory=256M +network0_type="virtio-net" +network0_switch="public" +disk0_type="virtio-blk" +disk0_name="disk0.img" +uuid="1c4655ac-c828-11ef-a920-e8ff1ed71ca0" +network0_mac="58:9c:fc:0d:13:3f" +``` + +but in order to make Rocky Linux boot, it... + +### VM installation + +```sh +paul@f2:~ % doas vm install rocky Rocky-9.5-x86_64-minimal.iso +Starting rocky + * found guest in /zroot/bhyve/rocky + * booting... + +paul@f0:/bhyve/rocky % doas vm list +NAME DATASTORE LOADER CPU MEMORY VNC AUTO STATE +rocky default uefi 4 14G 0.0.0.0:5900 No Locked (f0.lan.buetow.org) + +paul@f0:/bhyve/rocky % doas sockstat -4 | grep 5900 +root bhyve 6079 8 tcp4 *:5900 *:* +``` + +Port 5900 is now also open for VNC connections, so we connect to it with a VNC client and run through the installation dialogs. I'm sure this could be done unattended or more automated, but we have only 3 VMs to install, and the automation doesn't seem worth it as we are doing it only once. + + + +Other *BSD-related posts: + +[2016-04-09 Jails and ZFS with Puppet on FreeBSD](./2016-04-09-jails-and-zfs-on-freebsd-with-puppet.md) +[2022-07-30 Let's Encrypt with OpenBSD and Rex](./2022-07-30-lets-encrypt-with-openbsd-and-rex.md) +[2022-10-30 Installing DTail on OpenBSD](./2022-10-30-installing-dtail-on-openbsd.md) +[2024-01-13 One reason why I love OpenBSD](./2024-01-13-one-reason-why-i-love-openbsd.md) +[2024-04-01 KISS high-availability with OpenBSD](./2024-04-01-KISS-high-availability-with-OpenBSD.md) +[2024-11-17 f3s: Kubernetes with FreeBSD - Part 1: Setting the stage](./2024-11-17-f3s-kubernetes-with-freebsd-part-1.md) +[2024-12-03 f3s: Kubernetes with FreeBSD - Part 2: Hardware and base installation](./2024-12-03-f3s-kubernetes-with-freebsd-part-2.md) + +E-Mail your comments to `paul@nospam.buetow.org` :-) + +[Back to the main site](../) diff --git a/gemfeed/DRAFT-f3s-kubernetes-with-freebsd-hardware-setup.md b/gemfeed/DRAFT-f3s-kubernetes-with-freebsd-hardware-setup.md deleted file mode 100644 index 4a1b3422..00000000 --- a/gemfeed/DRAFT-f3s-kubernetes-with-freebsd-hardware-setup.md +++ /dev/null @@ -1,41 +0,0 @@ -# f3s: Kubernetes with FreeBSD - Setting the stage - Part 1 - -> Published at 2024-11-16T23:20:14+02:00 - -This is the second blog post about my f3s series for my self-hosting demands in my home lab. f3s? The "f" stands for FreeBSD, and the "3s" stands for k3s, the Kubernetes distribution I will use on FreeBSD-based physical machines. - -I will post a new entry every month or so (there are too many other side projects for more frequent updates—I bet you can understand). - -[2024-11-17 f3s: Kubernetes with FreeBSD - Part 1: Setting the stage](./2024-11-17-f3s-kubernetes-with-freebsd-part-1.md) -[2024-12-03 f3s: Kubernetes with FreeBSD - Part 2: Hardware and base installation](./2024-12-03-f3s-kubernetes-with-freebsd-part-2.md) - -[![f3s logo](./f3s-kubernetes-with-freebsd-part-1/f3slogo.png "f3s logo")](./f3s-kubernetes-with-freebsd-part-1/f3slogo.png) - -Let's begin... - -## Table of Contents - -* [⇢ f3s: Kubernetes with FreeBSD - Setting the stage - Part 1](#f3s-kubernetes-with-freebsd---setting-the-stage---part-1) - -## - -Hardware + photos + basic unpacking -Base os insallation (FreeBSD) -* static IPs -* utimed -* bhyve setup -* minimal rocky linux installs, with staic IPs - -Other *BSD-related posts: - -[2016-04-09 Jails and ZFS with Puppet on FreeBSD](./2016-04-09-jails-and-zfs-on-freebsd-with-puppet.md) -[2022-07-30 Let's Encrypt with OpenBSD and Rex](./2022-07-30-lets-encrypt-with-openbsd-and-rex.md) -[2022-10-30 Installing DTail on OpenBSD](./2022-10-30-installing-dtail-on-openbsd.md) -[2024-01-13 One reason why I love OpenBSD](./2024-01-13-one-reason-why-i-love-openbsd.md) -[2024-04-01 KISS high-availability with OpenBSD](./2024-04-01-KISS-high-availability-with-OpenBSD.md) -[2024-11-17 f3s: Kubernetes with FreeBSD - Part 1: Setting the stage](./2024-11-17-f3s-kubernetes-with-freebsd-part-1.md) -[2024-12-03 f3s: Kubernetes with FreeBSD - Part 2: Hardware and base installation](./2024-12-03-f3s-kubernetes-with-freebsd-part-2.md) - -E-Mail your comments to `paul@nospam.buetow.org` :-) - -[Back to the main site](../) diff --git a/gemfeed/DRAFT-summary-for-202410-202411-202410.md b/gemfeed/DRAFT-summary-for-202410-202411-202410.md deleted file mode 100644 index 0f1aefc4..00000000 --- a/gemfeed/DRAFT-summary-for-202410-202411-202410.md +++ /dev/null @@ -1,311 +0,0 @@ -# Summary for 202410 202411 202412 - -## Table of Contents - -* [⇢ Summary for 202410 202411 202412](#summary-for-202410-202411-202412) -* [⇢ ⇢ October 2024](#october-2024) -* [⇢ ⇢ ⇢ First on-call experience in a startup. Doesn't ...](#first-on-call-experience-in-a-startup-doesn-t-) -* [⇢ ⇢ ⇢ Reviewing your own PR or MR before asking ...](#reviewing-your-own-pr-or-mr-before-asking-) -* [⇢ ⇢ ⇢ Fun with defer in `#golang`, I did't know, that ...](#fun-with-defer-in-golang-i-did-t-know-that-) -* [⇢ ⇢ ⇢ I have been in incidents. Understandably, ...](#i-have-been-in-incidents-understandably-) -* [⇢ ⇢ ⇢ Little tips using strings in `#golang` and I ...](#little-tips-using-strings-in-golang-and-i-) -* [⇢ ⇢ ⇢ Reading this post about `#rust` (especially the ...](#reading-this-post-about-rust-especially-the-) -* [⇢ ⇢ ⇢ The opposite of `#ChaosMonkey` ... ...](#the-opposite-of-chaosmonkey--) -* [⇢ ⇢ November 2024](#november-2024) -* [⇢ ⇢ ⇢ I just became a Silver Patreon for OSnews. What ...](#i-just-became-a-silver-patreon-for-osnews-what-) -* [⇢ ⇢ ⇢ Until now, I wasn't aware, that Go is under a ...](#until-now-i-wasn-t-aware-that-go-is-under-a-) -* [⇢ ⇢ ⇢ These are some book notes from "Staff Engineer" ...](#these-are-some-book-notes-from-staff-engineer-) -* [⇢ ⇢ ⇢ Looking at `#Kubernetes`, it's pretty much ...](#looking-at-kubernetes-it-s-pretty-much-) -* [⇢ ⇢ ⇢ There has been an outage at the upstream ...](#there-has-been-an-outage-at-the-upstream-) -* [⇢ ⇢ ⇢ One of the more confusing parts in Go, nil ...](#one-of-the-more-confusing-parts-in-go-nil-) -* [⇢ ⇢ ⇢ Agreeably, writing down with Diagrams helps you ...](#agreeably-writing-down-with-diagrams-helps-you-) -* [⇢ ⇢ ⇢ I like the idea of types in Ruby. Raku is ...](#i-like-the-idea-of-types-in-ruby-raku-is-) -* [⇢ ⇢ ⇢ So, `#Haskell` is better suited for general ...](#so-haskell-is-better-suited-for-general-) -* [⇢ ⇢ ⇢ At first, functional options add a bit of ...](#at-first-functional-options-add-a-bit-of-) -* [⇢ ⇢ ⇢ Revamping my home lab a little bit. `#freebsd` ...](#revamping-my-home-lab-a-little-bit-freebsd-) -* [⇢ ⇢ ⇢ Revamping my home lab a little bit. `#freebsd` ...](#revamping-my-home-lab-a-little-bit-freebsd-) -* [⇢ ⇢ ⇢ Wondering to which `#web` `#browser` I should ...](#wondering-to-which-web-browser-i-should-) -* [⇢ ⇢ ⇢ eks-node-viewer is a nifty tool, showing the ...](#eks-node-viewer-is-a-nifty-tool-showing-the-) -* [⇢ ⇢ ⇢ Have put more Photos on - On my static photo ...](#have-put-more-photos-on---on-my-static-photo-) -* [⇢ ⇢ ⇢ In Go, passing pointers are not automatically ...](#in-go-passing-pointers-are-not-automatically-) -* [⇢ ⇢ ⇢ Myself being part of an on-call rotations over ...](#myself-being-part-of-an-on-call-rotations-over-) -* [⇢ ⇢ ⇢ Feels good to code in my old love `#Perl` again ...](#feels-good-to-code-in-my-old-love-perl-again-) -* [⇢ ⇢ ⇢ This is an interactive summary of the Go ...](#this-is-an-interactive-summary-of-the-go-) -* [⇢ ⇢ December 2024](#december-2024) -* [⇢ ⇢ ⇢ Thats unexpected, you cant remove a NaN key ...](#thats-unexpected-you-cant-remove-a-nan-key-) -* [⇢ ⇢ ⇢ My second blog post about revamping my home lab ...](#my-second-blog-post-about-revamping-my-home-lab-) -* [⇢ ⇢ ⇢ Very insightful article about tech hiring in ...](#very-insightful-article-about-tech-hiring-in-) -* [⇢ ⇢ ⇢ for `#bpf` `#ebpf` performance debugging, have ...](#for-bpf-ebpf-performance-debugging-have-) -* [⇢ ⇢ ⇢ 89 things he/she knows about Git commits is a ...](#89-things-heshe-knows-about-git-commits-is-a-) -* [⇢ ⇢ ⇢ I found that working on multiple side projects ...](#i-found-that-working-on-multiple-side-projects-) -* [⇢ ⇢ ⇢ Agreed? Agreed. Besides `#Ruby`, I would also ...](#agreed-agreed-besides-ruby-i-would-also-) -* [⇢ ⇢ ⇢ Plan9 assembly format in Go, but wait, it's not ...](#plan9-assembly-format-in-go-but-wait-it-s-not-) -* [⇢ ⇢ ⇢ This is a neat blog post about the Helix text ...](#this-is-a-neat-blog-post-about-the-helix-text-) -* [⇢ ⇢ ⇢ This blog post is basically a rant against ...](#this-blog-post-is-basically-a-rant-against-) -* [⇢ ⇢ ⇢ Quick trick to get Helix themes selected ...](#quick-trick-to-get-helix-themes-selected-) -* [⇢ ⇢ ⇢ Example where complexity attacks you from ...](#example-where-complexity-attacks-you-from-) -* [⇢ ⇢ ⇢ LLMs for Ops? Summaries of logs, probabilities ...](#llms-for-ops-summaries-of-logs-probabilities-) -* [⇢ ⇢ ⇢ Excellent article about your dream Product ...](#excellent-article-about-your-dream-product-) -* [⇢ ⇢ ⇢ I just finished reading all chapters of CPU ...](#i-just-finished-reading-all-chapters-of-cpu-) -* [⇢ ⇢ ⇢ Indeed, useful to know this stuff! `#sre` ...](#indeed-useful-to-know-this-stuff-sre-) -* [⇢ ⇢ ⇢ It's the small things, which make Unix like ...](#it-s-the-small-things-which-make-unix-like-) - -## October 2024 - -### First on-call experience in a startup. Doesn't ... - -First on-call experience in a startup. Doesn't sound a lot of fun! But the lessons were learned! `#sre` - -[https://ntietz.com/blog/lessons-from-my-first-on-call/](https://ntietz.com/blog/lessons-from-my-first-on-call/) - -### Reviewing your own PR or MR before asking ... - -Reviewing your own PR or MR before asking others to review it makes a lot of sense. Have seen so many silly mistakes which would have been avoided. Saving time for the real reviewer. - -[https://www.jvt.me/posts/2019/01/12/self-code-review/](https://www.jvt.me/posts/2019/01/12/self-code-review/) - -### Fun with defer in `#golang`, I did't know, that ... - -Fun with defer in `#golang`, I did't know, that a defer object can either be heap or stack allocated. And there are some rules for inlining, too. - -[https://victoriametrics.com/blog/defer-in-go/](https://victoriametrics.com/blog/defer-in-go/) - -### I have been in incidents. Understandably, ... - -I have been in incidents. Understandably, everyone wants the issue to be resolved as quickly and others want to know how long TTR will be. IMHO, providing no estimates at all is no solution either. So maybe give a rough estimate but clearly communicate that the estimate is rough and that X, Y, and Z can interfere, meaning there is a chance it will take longer to resolve the incident. Just my thought. What's yours? - -[https://firehydrant.com/blog/hot-...de-incident-resolution-estimates/](https://firehydrant.com/blog/hot-take-dont-provide-incident-resolution-estimates/) - -### Little tips using strings in `#golang` and I ... - -Little tips using strings in `#golang` and I personally think one must look more into the std lib (not just for strings, also for slices, maps,...), there are tons of useful helper functions. - -[https://www.calhoun.io/6-tips-for-using-strings-in-go/](https://www.calhoun.io/6-tips-for-using-strings-in-go/) - -### Reading this post about `#rust` (especially the ... - -Reading this post about `#rust` (especially the first part), I think I made a good choice in deciding to dive into `#golang` instead. There was a point where I wanted to learn a new programming language, and Rust was on my list of choices. I think the Go project does a much better job of deciding what goes into the language and how. What are your thoughts? - -[https://josephg.com/blog/rewriting-rust/](https://josephg.com/blog/rewriting-rust/) - -### The opposite of `#ChaosMonkey` ... ... - -The opposite of `#ChaosMonkey` ... automatically repairing and healing services helping to reduce manual toil work. Runbooks and scripts are only the first step, followed by a fully blown service written in Go. Could be useful, but IMHO why not rather address the root causes of the manual toil work? `#sre` - -[https://blog.cloudflare.com/nl-nl...latform-resilience-at-cloudflare/](https://blog.cloudflare.com/nl-nl/improving-platform-resilience-at-cloudflare/) - -## November 2024 - -### I just became a Silver Patreon for OSnews. What ... - -I just became a Silver Patreon for OSnews. What is OSnews? It is an independent news site about IT. It is slightly independent and, at times, alternative. I have enjoyed it since my early student days. This one and other projects I financially support are listed here: - -[https://foo.zone/gemfeed/2024-09-07-projects-i-support.html](https://foo.zone/gemfeed/2024-09-07-projects-i-support.html) - -### Until now, I wasn't aware, that Go is under a ... - -Until now, I wasn't aware, that Go is under a BSD-style license (3-clause as it seems). Neat. I don't know why, but I always was under the impression it would be MIT. `#bsd` `#golang` - -[https://go.dev/LICENSE](https://go.dev/LICENSE) - -### These are some book notes from "Staff Engineer" ... - -These are some book notes from "Staff Engineer" – there is some really good insight into what is expected from a Staff Engineer and beyond in the industry. I wish I had read the book earlier. - -[https://foo.zone/gemfeed/2024-10-24-staff-engineer-book-notes.html](https://foo.zone/gemfeed/2024-10-24-staff-engineer-book-notes.html) - -### Looking at `#Kubernetes`, it's pretty much ... - -Looking at `#Kubernetes`, it's pretty much following the Unix way of doing things. It has many tools, but each tool has its own single purpose: DNS, scheduling, container runtime, various controllers, networking, observability, alerting, and more services in the control plane. Everything is managed by different services or plugins, mostly running in their dedicated pods. They don't communicate through pipes, but network sockets, though. `#k8s` - -### There has been an outage at the upstream ... - -There has been an outage at the upstream network provider for OpenBSD.Amsterdam (hoster, I am using). This was the first real-world test for my KISS HA setup, and it worked flawlessly! All my sites and services failed over automatically to my other `#OpenBSD` VM! - -[https://foo.zone/gemfeed/2024-04-...gh-availability-with-OpenBSD.html](https://foo.zone/gemfeed/2024-04-01-KISS-high-availability-with-OpenBSD.html) -[https://openbsd.amsterdam/](https://openbsd.amsterdam/) - -### One of the more confusing parts in Go, nil ... - -One of the more confusing parts in Go, nil values vs nil errors: `#golang` - -[https://unexpected-go.com/nil-errors-that-are-non-nil-errors.html](https://unexpected-go.com/nil-errors-that-are-non-nil-errors.html) - -### Agreeably, writing down with Diagrams helps you ... - -Agreeably, writing down with Diagrams helps you to think things more through. And keeps others on the same page. Only worth for projects from a certain size, IMHO. - -[https://ntietz.com/blog/reasons-to-write-design-docs/](https://ntietz.com/blog/reasons-to-write-design-docs/) - -### I like the idea of types in Ruby. Raku is ... - -I like the idea of types in Ruby. Raku is supports that already, but in Ruby, you must specify the types in a separate .rbs file, which is, in my opinion, cumbersome and is a reason not to use it extensively for now. I believe there are efforts to embed the type information in the standard .rb files, and that the .rbs is just an experiment to see how types could work out without introducing changes into the core Ruby language itself right now? `#Ruby` `#RakuLang` - -[https://github.com/ruby/rbs](https://github.com/ruby/rbs) - -### So, `#Haskell` is better suited for general ... - -So, `#Haskell` is better suited for general purpose than `#Rust`? I thought deploying something in Haskell means publishing an academic paper :-) Interesting rant about Rust, though: - -[https://chrisdone.com/posts/rust/](https://chrisdone.com/posts/rust/) - -### At first, functional options add a bit of ... - -At first, functional options add a bit of boilerplate, but they turn out to be quite neat, especially when you have very long parameter lists that need to be made neat and tidy. `#golang` - -[https://www.calhoun.io/using-func...instead-of-method-chaining-in-go/](https://www.calhoun.io/using-functional-options-instead-of-method-chaining-in-go/) - -### Revamping my home lab a little bit. `#freebsd` ... - -Revamping my home lab a little bit. `#freebsd` `#bhyve` `#rocky` `#linux` `#vm` `#k3s` `#kuberbetes` `#wireguard` `#zfs` `#nfs` `#ha` `#relayd` `#k8s` `#selfhosting` `#self`-hosting `#homelab` `#home`-lab - -[https://foo.zone/gemfeed/2024-11-...bernetes-with-freebsd-part-1.html](https://foo.zone/gemfeed/2024-11-17-f3s-kubernetes-with-freebsd-part-1.html) - -### Revamping my home lab a little bit. `#freebsd` ... - -Revamping my home lab a little bit. `#freebsd` `#bhyve` `#rocky` `#linux` `#vm` `#k3s` `#kubernetes` `#wireguard` `#zfs` `#nfs` `#ha` `#relayd` `#k8s` `#selfhosting` `#homelab` - -[https://foo.zone/gemfeed/2024-11-...bernetes-with-freebsd-part-1.html](https://foo.zone/gemfeed/2024-11-17-f3s-kubernetes-with-freebsd-part-1.html) - -### Wondering to which `#web` `#browser` I should ... - -Wondering to which `#web` `#browser` I should switch now personally ... - -[https://www.osnews.com/story/1411...cy-for-open-web-privacy-and-more/](https://www.osnews.com/story/141100/mozilla-foundation-lays-off-30-of-its-employees-ends-advocacy-for-open-web-privacy-and-more/) - -### eks-node-viewer is a nifty tool, showing the ... - -eks-node-viewer is a nifty tool, showing the compute nodes currently in use in the `#EKS` cluster. especially useful when dynamically allocating nodes with `#karpenter` or auto scaling groups. - -[https://github.com/awslabs/eks-node-viewer](https://github.com/awslabs/eks-node-viewer) - -### Have put more Photos on - On my static photo ... - -Have put more Photos on - On my static photo sites - Generated with a `#bash` script - -[https://irregular.ninja](https://irregular.ninja) - -### In Go, passing pointers are not automatically ... - -In Go, passing pointers are not automatically faster than values. Pointers often force the memory to be allocated on the heap, adding GC overhad. With values, Go can determine whether to put the memory on the stack instead. But with large structs/objects (how you want to call them) or if you want to modify state, then pointers are the semantic to use. `#golang` - -[https://blog.boot.dev/golang/pointers-faster-than-values/](https://blog.boot.dev/golang/pointers-faster-than-values/) - -### Myself being part of an on-call rotations over ... - -Myself being part of an on-call rotations over my whole professional life, just have learned this lesson "Tell people who are new to on-call: Just have fun" :-) This is a neat blog post to read: - -[https://ntietz.com/blog/what-i-tell-people-new-to-oncall/](https://ntietz.com/blog/what-i-tell-people-new-to-oncall/) - -### Feels good to code in my old love `#Perl` again ... - -Feels good to code in my old love `#Perl` again after a while. I am implementing a log parser for generating site stats of my personal homepage! :-) @Perl - -### This is an interactive summary of the Go ... - -This is an interactive summary of the Go release, with a lot of examples utilising iterators in the slices and map packages. Love it! `#golang` - -[https://antonz.org/go-1-23/](https://antonz.org/go-1-23/) - -## December 2024 - -### Thats unexpected, you cant remove a NaN key ... - -Thats unexpected, you cant remove a NaN key from a map without clearing it! `#golang` - -[https://unexpected-go.com/you-can...om-a-map-without-clearing-it.html](https://unexpected-go.com/you-cant-remove-a-nan-key-from-a-map-without-clearing-it.html) - -### My second blog post about revamping my home lab ... - -My second blog post about revamping my home lab a little bit just hit the net. `#FreeBSD` `#ZFS` `#n100` `#k8s` `#k3s` `#kubernetes` - -[https://foo.zone/gemfeed/2024-12-...bernetes-with-freebsd-part-2.html](https://foo.zone/gemfeed/2024-12-03-f3s-kubernetes-with-freebsd-part-2.html) - -### Very insightful article about tech hiring in ... - -Very insightful article about tech hiring in the age of LLMs. As an interviewer, I have experienced some of the scrnarios already first hand... - -[https://newsletter.pragmaticengin...m/p/how-genai-changes-tech-hiring](https://newsletter.pragmaticengineer.com/p/how-genai-changes-tech-hiring) - -### for `#bpf` `#ebpf` performance debugging, have ... - -for `#bpf` `#ebpf` performance debugging, have a look at bpftop from Netflix. A neat tool showing you the estimated CPU time and other performance statistics for all the BPF programs currently loaded into the `#linux` kernel. Highly recommend! - -[https://github.com/Netflix/bpftop](https://github.com/Netflix/bpftop) - -### 89 things he/she knows about Git commits is a ... - -89 things he/she knows about Git commits is a neat list of `#Git` wisdoms - -[https://www.jvt.me/posts/2024/07/12/things-know-commits/](https://www.jvt.me/posts/2024/07/12/things-know-commits/) - -### I found that working on multiple side projects ... - -I found that working on multiple side projects concurrently is better than concentrating on just one. This seems inefficient at first, but whenever you tend to lose motivation, you can temporarily switch to another one with full élan. However, remember to stop starting and start finishing. This doesn't mean you should be working on 10+ (and a growing list of) side projects concurrently! Select your projects and commit to finishing them before starting the next thing. For example, my current limit of concurrent side projects is around five. - -### Agreed? Agreed. Besides `#Ruby`, I would also ... - -Agreed? Agreed. Besides `#Ruby`, I would also add `#RakuLang` and `#Perl` @Perl to the list of languages that are great for shell scripts - "Making Easy Things Easy and Hard Things Possible" - -[https://lucasoshiro.github.io/posts-en/2024-06-17-ruby-shellscript/](https://lucasoshiro.github.io/posts-en/2024-06-17-ruby-shellscript/) - -### Plan9 assembly format in Go, but wait, it's not ... - -Plan9 assembly format in Go, but wait, it's not the Operating System Plan9! `#golang` `#rabbithole` - -[https://www.osnews.com/story/1409...emo-speeding-up-calculations-450/](https://www.osnews.com/story/140941/go-plan9-memo-speeding-up-calculations-450/) - -### This is a neat blog post about the Helix text ... - -This is a neat blog post about the Helix text editor, to which I personally switched around a year ago (from NeoVim). I should blog about my experience as well. To summarize: I am using it together with the terminal multiplexer `#tmux`. It doesn't bother me that Helix is purely terminal-based and therefore everything has to be in the same font. `#HelixEditor` - -[https://jonathan-frere.com/posts/helix/](https://jonathan-frere.com/posts/helix/) - -### This blog post is basically a rant against ... - -This blog post is basically a rant against DataDog... Personally, I don't have much experience with DataDog (actually, I have never used it), but one reason to work with logs at my day job (with over 2,000 physical server machines) and to be cost-effective is by using dtail! `#dtail` `#logs` `#logmanagement` - -[https://crys.site/blog/2024/reinventint-the-weel/](https://crys.site/blog/2024/reinventint-the-weel/) -[https://dtail.dev](https://dtail.dev) - -### Quick trick to get Helix themes selected ... - -Quick trick to get Helix themes selected randomly `#HelixEditor` - -[https://foo.zone/gemfeed/2024-12-15-random-helix-themes.html](https://foo.zone/gemfeed/2024-12-15-random-helix-themes.html) - -### Example where complexity attacks you from ... - -Example where complexity attacks you from behind `#k8s` `#kubernetes` `#OpenAI` - -[https://surfingcomplexity.blog/20...-openai-public-incident-write-up/](https://surfingcomplexity.blog/2024/12/14/quick-takes-on-the-recent-openai-public-incident-write-up/) - -### LLMs for Ops? Summaries of logs, probabilities ... - -LLMs for Ops? Summaries of logs, probabilities about correctness, auto-generating Ansible, some uses cases are there. Wouldn't trust it fully, though. - -[https://youtu.be/WodaffxVq-E?si=noY0egrfl5izCSQI](https://youtu.be/WodaffxVq-E?si=noY0egrfl5izCSQI) - -### Excellent article about your dream Product ... - -Excellent article about your dream Product Manager: Why every software team needs a product manager to thrive via @wallabagapp - -[https://testdouble.com/insights/w...elerate-improve-software-delivery](https://testdouble.com/insights/why-product-managers-accelerate-improve-software-delivery) - -### I just finished reading all chapters of CPU ... - -I just finished reading all chapters of CPU land: ... not claiming to remember every detail, but it is a great refresher how CPUs and operating systems actually work under the hood when you execute a program, which we tend to forget in our higher abstraction world. I liked the "story" and some of the jokes along the way! Size wise, it is pretty digestable (not talking about books, but only 7 web articles/chapters)! `#cpu` `#linux` `#unix` `#kernel` `#macOS` - -[https://cpu.land/](https://cpu.land/) - -### Indeed, useful to know this stuff! `#sre` ... - -Indeed, useful to know this stuff! `#sre` - -[https://biriukov.dev/docs/resolve...vers-and-dual-stack-applications/](https://biriukov.dev/docs/resolver-dual-stack-application/0-sre-should-know-about-gnu-linux-resolvers-and-dual-stack-applications/) - -### It's the small things, which make Unix like ... - -It's the small things, which make Unix like systems, like GNU/Linux, interesting. Didn't know about this `#GNU` `#Tar` behaviour yet: - -[https://xeiaso.net/notes/2024/pop-quiz-tar/15110](https://xeiaso.net/notes/2024/pop-quiz-tar/15110) -- cgit v1.2.3 From 26dd99a97c483ffdacba22fcda2faa8a10148c0f Mon Sep 17 00:00:00 2001 From: Paul Buetow Date: Wed, 15 Jan 2025 00:17:16 +0200 Subject: Update content for md --- ...024-12-03-f3s-kubernetes-with-freebsd-part-2.md | 3 + .../2025-01-15-working-with-an-sre-interview.md | 177 +++++++++++++++++++++ gemfeed/DRAFT-f3s-kubernetes-with-freebsd-bhyve.md | 91 +++++++++-- gemfeed/index.md | 1 + 4 files changed, 256 insertions(+), 16 deletions(-) create mode 100644 gemfeed/2025-01-15-working-with-an-sre-interview.md (limited to 'gemfeed') diff --git a/gemfeed/2024-12-03-f3s-kubernetes-with-freebsd-part-2.md b/gemfeed/2024-12-03-f3s-kubernetes-with-freebsd-part-2.md index 23dd19fa..06c11371 100644 --- a/gemfeed/2024-12-03-f3s-kubernetes-with-freebsd-part-2.md +++ b/gemfeed/2024-12-03-f3s-kubernetes-with-freebsd-part-2.md @@ -131,6 +131,7 @@ root@f0:~ # freebsd-update reboot ``` I also added the following entries for the three FreeBSD boxes to the `/etc/hosts` file: + ```sh root@f0:~ # cat <>/etc/hosts 192.168.1.130 f0 f0.lan f0.lan.buetow.org @@ -139,6 +140,8 @@ root@f0:~ # cat <>/etc/hosts END ``` +You might wonder why bother using the hosts file? Why not use DNS properly? The reason is simplicity. I don't manage 100 hosts, only a few here and there. Having an OpenWRT router in my home, I could also configure everything there, but maybe I'll do that later. For now, keep it simple and straightforward. + ## After install After that, I installed the following additional packages: diff --git a/gemfeed/2025-01-15-working-with-an-sre-interview.md b/gemfeed/2025-01-15-working-with-an-sre-interview.md new file mode 100644 index 00000000..e9556cfb --- /dev/null +++ b/gemfeed/2025-01-15-working-with-an-sre-interview.md @@ -0,0 +1,177 @@ +# Working with an SRE Interview + +> Published at 2025-01-15T00:16:04+02:00 + +I have been interviewed by Florian Buetow about what it's like working with a Site Reliability Engineer from the point of view of a Software Engineer, Data Scientist, and AI Engineer. + +[See original interview here](https://www.cracking-ai-engineering.com/writing/2025/01/12/working-with-an-sre-interview/) + +Below, I am posting the interview here on my blog as well. + +## Table of Contents + +* [⇢ Working with an SRE Interview](#working-with-an-sre-interview) +* [⇢ ⇢ Preamble ](#preamble-) +* [⇢ ⇢ Introducing Paul](#introducing-paul) +* [⇢ ⇢ How did you get started?](#how-did-you-get-started) +* [⇢ ⇢ Roles and Career Progression](#roles-and-career-progression) +* [⇢ ⇢ Anecdotes and Best Practices](#anecdotes-and-best-practices) +* [⇢ ⇢ Working with Different Teams](#working-with-different-teams) +* [⇢ ⇢ Using AI Tools](#using-ai-tools) +* [⇢ ⇢ SRE Learning Resources](#sre-learning-resources) +* [⇢ ⇢ Blogging](#blogging) +* [⇢ ⇢ Wrap-up](#wrap-up) +* [⇢ ⇢ Closing comments](#closing-comments) + +## Preamble + +In this insightful interview, Paul Bütow, a Principal Site Reliability Engineer at Mimecast, shares over a decade of experience in the field. Paul highlights the role of an Embedded SRE, emphasizing the importance of automation, observability, and effective incident management. We also focused on the key question of how you can work effectively with an SRE weather you are an individual contributor or a manager, a software engineer or data scientist. And how you can learn more about site reliability engineering. + +## Introducing Paul + +Hi Paul, please introduce yourself briefly to the audience. Who are you, what do you do for a living, and where do you work? + +> My name is Paul Bütow, I work at Mimecast, and I’m a Principal Site Reliability Engineer there. I’ve been with Mimecast for almost ten years now. The company specializes in email security, including things like archiving, phishing detection, malware protection, and spam filtering. + +You mentioned that you’re an ‘Embedded SRE.’ What does that mean exactly? + +> It means that I’m directly part of the software engineering team, not in a separate Ops department. I ensure that nothing is deployed manually, and everything runs through automation. I also set up monitoring and observability. These are two distinct aspects: monitoring alerts us when something breaks, while observability helps us identify trends. I also create runbooks so we know what to do when specific incidents occur frequently. + +> Infrastructure SREs on the other hand handle the foundational setup, like providing the Kubernetes cluster itself or ensuring the operating systems are installed. They don't work on the application directly but ensure the base infrastructure is there for others to use. This works well when a company has multiple teams that need shared infrastructure. + +## How did you get started? + +How did your interest in Linux or FreeBSD start? + +> It began during my school days. We had a PC with DOS at home, and I eventually bought Suse Linux 5.3. Shortly after, I discovered FreeBSD because I liked its handbook so much. I wanted to understand exactly how everything worked, so I also tried Linux from Scratch. That involves installing every package manually to gain a better understanding of operating systems. + +[https://www.FreeBSD.org](https://www.FreeBSD.org) +[https://linuxfromscratch.org/](https://linuxfromscratch.org/) + +And after school, you pursued computer science, correct? + +> Exactly. I wasn’t sure at first whether I wanted to be a software developer or a system administrator. I applied for both and eventually accepted an offer as a Linux system administrator. This was before 'SRE' became a buzzword, but much of what I did back then-automation, infrastructure as code, monitoring-is now considered part of the typical SRE role. + +## Roles and Career Progression + +Tell us about how you joined Mimecast. When did you fully embrace the SRE role? + +> I started as a Linux sysadmin at 1&1. I managed an ad server farm with hundreds of systems and later handled load balancers. Together with an architect, we managed F5 load balancers distributing around 2,000 services, including for portals like web.de and GMX. I also led the operations team technically for a while before moving to London to join Mimecast. + +> At Mimecast, the job title was explicitly 'Site Reliability Engineer.' The biggest difference was that I was no longer in a separate Ops department but embedded directly within the storage and search backend team. I loved that because we could plan features together-from automation to measurability and observability. Mimecast also operates thousands of physical servers for email archiving, which was fascinating since I already had experience with large distributed systems at 1&1. It was the right step for me because it allowed me to work close to the code while remaining hands-on with infrastructure. + +What are the differences between SRE, DevOps, SysAdmin, and Architects? + +> SREs are like the next step after SysAdmins. A SysAdmin might manually install servers, replace disks, or use simple scripts for automation, while SREs use infrastructure as code and focus on reliability through SLIs, SLOs, and automation. DevOps isn’t really a job-it’s more of a way of working, where developers are involved in operations tasks like setting up CI/CD pipelines or on-call shifts. Architects focus on designing systems and infrastructures, such as load balancers or distributed systems, working alongside SREs to ensure the systems meet the reliability and scalability requirements. The specific responsibilities of each role depend on the company, and there is often overlap. + +What are the most important reliability lessons you’ve learned so far? + +* Don’t leave SRE aspects as an afterthought. It’s much better to discuss automation, monitoring, SLIs, and SLOs early on. Traditional sysadmins often installed systems manually, but today, we do everything via infrastructure as code-using tools like Terraform or Puppet. +* I also distinguish between monitoring and observability. Monitoring tells us, 'The server is down, alarm!' Observability dives deeper, showing trends like increasing latency so we can act proactively. +* SLI, SLO, and SLA are core elements. We focus on what users actually experience-for example, how quickly an email is sent-and set our goals accordingly. +* Runbooks are also crucial. When something goes wrong at night, you don’t want to start from scratch. A runbook outlines how to debug and resolve specific problems, saving time and reducing downtime. + +## Anecdotes and Best Practices + +Runbooks sound very practical. Can you explain how they’re used day-to-day? + +> Runbooks are essentially guides for handling specific incidents. For instance, if a service won’t start, the runbook will specify where the logs are and which commands to use. Observability takes it a step further, helping us spot changes early-like rising error rates or latency-so we can address issues before they escalate. + +When should you decide to put something into a runbook, and when is it unnecessary? + +> If an issue happens frequently, it should be documented in a runbook so that anyone, even someone new, can follow the steps to fix it. The idea is that 90% of the common incidents should be covered. For example, if a service is down, the runbook would specify where to find logs, which commands to check, and what actions to take. On the other hand, rare or complex issues, where the resolution depends heavily on context or varies each time, don’t make sense to include in detail. For those, it’s better to focus on general troubleshooting steps. + +How do you search for and find the correct runbooks? + +> Runbooks should be linked directly in the alert you receive. For example, if you get an alert about a service not running, the alert will have a link to the runbook that tells you what to check, like logs or commands to run. Runbooks are best stored in an internal wiki, so if you don’t find the link in the alert, you know where to search. The important thing is that runbooks are easy to find and up to date because that’s what makes them useful during incidents. + +Do you have an interesting war story you can share with us? + +> Sure. At 1&1, we had a proprietary ad server software that ran a SQL query during startup. The query got slower over time, eventually timing out and preventing the server from starting. Since we couldn’t access the source code, we searched the binary for the SQL and patched it. By pinpointing the issue, a developer was able to adjust the SQL. This collaboration between sysadmin and developer perspectives highlights the value of SRE work. + +## Working with Different Teams + +You’re embedded in a team-how does collaboration with developers work practically? + +> We plan everything together from the start. If there’s a new feature, we discuss infrastructure, automated deployments, and monitoring right away. Developers are experts in the code, and I bring the infrastructure expertise. This avoids unpleasant surprises before going live. + +How about working with data scientists or ML engineers? Are there differences? + +> The principles are the same. ML models also need to be deployed and monitored. You deal with monitoring, resource allocation, and identifying performance drops. Whether it’s a microservice or an ML job, at the end of the day, it’s all running on servers or clusters that must remain stable. + +What about working with managers or the FinOps team? + +> We often discuss costs, especially in the cloud, where scaling up resources is easy. It’s crucial to know our metrics: do we have enough capacity? Do we need all instances? Or is the CPU only at 5% utilization? This data helps managers decide whether the budget is sufficient or if optimizations are needed. + +Do you have practical tips for working with SREs? + +> Yes, I have a few: + +* Early involvement: Include SREs from the beginning in your project. +* Runbooks & documentation: Document recurring errors. +* Try first: Try to understand the issue yourself before immediately asking the SRE. +* Basic infra knowledge: Kubernetes and Terraform aren’t magic. Some basic understanding helps every developer. + +## Using AI Tools + +Let’s talk about AI. How do you use it in your daily work? + +> For boilerplate code, like Terraform snippets, I often use ChatGPT. It saves time, although I always review and adjust the output. Log analysis is another exciting application. Instead of manually going through millions of lines, AI can summarize key outliers or errors. + +Do you think AI could largely replace SREs or significantly change the role? + +> I see AI as an additional tool. SRE requires a deep understanding of how distributed systems work internally. While AI can assist with routine tasks or quickly detect anomalies, human expertise is indispensable for complex issues. + +## SRE Learning Resources + +What resources would you recommend for learning about SRE? + +> The Google SRE book is a classic, though a bit dry. I really like 'Seeking SRE,' as it offers various perspectives on SRE, with many practical stories from different companies. + +[https://sre.google/books/](https://sre.google/books/) +[Seeking SRE](https://www.oreilly.com/library/view/seeking-sre/9781491978856) + +Do you have a podcast recommendation? + +> The Google SRE prodcast is quite interesting. It offers insights into how Google approaches SRE, along with perspectives from external guests. + +[https://sre.google/prodcast/](https://sre.google/prodcast/) + +## Blogging + +You also have a blog. What motivates you to write regularly? + +> Writing helps me learn the most. It also serves as a personal reference. Sometimes I look up how I solved a problem a year ago. And of course, others tackling similar projects might find inspiration in my posts. + +What do you blog about? + +> Mostly technical topics I find exciting, like homelab projects, Kubernetes, or book summaries on IT and productivity. It’s a personal blog, so I write about what I enjoy. + +## Wrap-up + +To wrap up, what are three things every team should keep in mind for stability? + +> First, maintain runbooks and documentation to avoid chaos at night. Second, automate everything-manual installs in production are risky. Third, define SLIs, SLOs, and SLAs early so everyone knows what we’re monitoring and guaranteeing. + +Is there a motto or mindset that particularly inspires you as an SRE? + +> "Keep it simple and stupid"-KISS. Not everything has to be overly complex. And always stay curious. I’m still fascinated by how systems work under the hood. + +Where can people find you online? + +> You can find links to my socials on my website paul.buetow.org +> I regularly post articles and link to everything else I’m working on outside of work. + +[https://paul.buetow.org](https://paul.buetow.org) + +Thank you very much for your time and this insightful interview into the world of site reliability engineering + +> My pleasure, this was fun. + +## Closing comments + +Dear reader, I hope this conversation with Paul Bütow provided an exciting peak into the world of Site Reliability Engineering. Whether you’re a software developer, data scientist, ML engineer, or manager, reliable systems are always a team effort. Hopefully, you’ve taken some insights or tips from Paul’s experiences for your own team or next project. Thanks for joining us, and best of luck refining your own SRE practices! + +E-Mail your comments to `paul@nospam.buetow.org` :-) + +[Back to the main site](../) diff --git a/gemfeed/DRAFT-f3s-kubernetes-with-freebsd-bhyve.md b/gemfeed/DRAFT-f3s-kubernetes-with-freebsd-bhyve.md index 4d769fe2..d9932801 100644 --- a/gemfeed/DRAFT-f3s-kubernetes-with-freebsd-bhyve.md +++ b/gemfeed/DRAFT-f3s-kubernetes-with-freebsd-bhyve.md @@ -16,12 +16,15 @@ This is the third blog post about my f3s series for my self-hosting demands in m * [⇢ ⇢ ⇢ ISO download](#iso-download) * [⇢ ⇢ ⇢ VM configuration](#vm-configuration) * [⇢ ⇢ ⇢ VM installation](#vm-installation) +* [⇢ ⇢ ⇢ Increase of the disk image](#increase-of-the-disk-image) +* [⇢ ⇢ ⇢ Connect to VPN](#connect-to-vpn) +* [⇢ ⇢ After install](#after-install) ## Introduction In this blog post, we are going to install the Bhyve hypervisor. -The FreeBSD Bhyve hypervisor is a lightweight, modern hypervisor that enables virtualization on FreeBSD systems. Bhyve's strengths include its minimal overhead, which allows it to achieve near-native performance for virtual machines. It is designed to be efficient and lightweight, leveraging the capabilities of the FreeBSD operating system for performance and network management. +The FreeBSD Bhyve hypervisor is a lightweight, modern hypervisor that enables virtualization on FreeBSD systems. Bhyve's strengths include its minimal overhead, which allows it to achieve near-native performance for virtual machines. It is designed to be efficient and lightweight, leveraging the capabilities of the FreeBSD operating system for performance and network management. Bhyve supports running a variety of guest operating systems, including FreeBSD, Linux, and Windows, on hardware platforms that support hardware virtualization extensions (such as Intel VT-x or AMD-V). In our case, we are going to virtualize Rocky Linux, which later on in this series will be used to run k3s. @@ -34,35 +37,35 @@ For the management of the Bhyve VMs, we are using `vm-bhyve`, a tool not part of The following commands are executed on all three hosts `f0`, `f1`, and `f2`, where `re0` is the name of the Ethernet interface (which may need to be adjusted if your hardware is different): ```sh -paul@f2:~ % doas pkg install vm-bhyve bhyve-firmware -paul@f2:~ % doas sysrc vm_enable=YES +paul@f0:~ % doas pkg install vm-bhyve bhyve-firmware +paul@f0:~ % doas sysrc vm_enable=YES vm_enable: -> YES -paul@f2:~ % doas sysrc vm_dir=zfs:zroot/bhyve +paul@f0:~ % doas sysrc vm_dir=zfs:zroot/bhyve vm_dir: -> zfs:zroot/bhyve -paul@f2:~ % doas zfs create zroot/bhyve -paul@f2:~ % doas vm init -paul@f2:~ % doas vm create public -paul@f2:~ % doas vm switch add public re0 +paul@f0:~ % doas zfs create zroot/bhyve +paul@f0:~ % doas vm init +paul@f0:~ % doas vm switch create public +paul@f0:~ % doas vm switch add public re0 ``` Bhyve stores all it's data in the `/bhyve` of the `zroot` ZFS pool: ```sh -paul@f2:~ % zfs list | grep bhyve +paul@f0:~ % zfs list | grep bhyve zroot/bhyve 1.74M 453G 1.74M /zroot/bhyve ``` For convenience, we also create this symlink: ```sh -paul@f2:~ % doas ln -s /zroot/bhyve/ /bhyve +paul@f0:~ % doas ln -s /zroot/bhyve/ /bhyve ``` Now, Bhyve is ready to rumble, but no VMs are there yet: ```sh -paul@f2:~ % doas vm list +paul@f0:~ % doas vm list NAME DATASTORE LOADER CPU MEMORY VNC AUTO STATE ``` @@ -73,17 +76,17 @@ NAME DATASTORE LOADER CPU MEMORY VNC AUTO STATE We're going to install the Rocky Linux from the latest minimal iso: ```sh -paul@f2:~ % doas vm iso \ +paul@f0:~ % doas vm iso \ https://download.rockylinux.org/pub/rocky/9/isos/x86_64/Rocky-9.5-x86_64-minimal.iso /zroot/bhyve/.iso/Rocky-9.5-x86_64-minimal.iso 1808 MB 4780 kBps 06m28s -paul@f2:/bhyve % doas vm create rocky +paul@f0:/bhyve % doas vm create rocky ``` ### VM configuration The default configuration looks like this now: ```sh -paul@f2:/bhyve/rocky % cat rocky.conf +paul@f0:/bhyve/rocky % cat rocky.conf loader="bhyveload" cpu=1 memory=256M @@ -95,12 +98,30 @@ uuid="1c4655ac-c828-11ef-a920-e8ff1ed71ca0" network0_mac="58:9c:fc:0d:13:3f" ``` -but in order to make Rocky Linux boot, it... +Whereas the `uuid` and the `network0_mac` differ on each of the 3 hosts. + +but in order to make Rocky Linux boot it (plus some other adjustments, e.g. as I am intending to run the majority of the workload in the k3s cluster running on those linux VMs, I give them beefy specs like 4 CPU cores and 14GB RAM), I modified it to: + +```sh +guest="linux" +loader="uefi" +uefi_vars="yes" +cpu=4 +memory=14G +network0_type="virtio-net" +network0_switch="public" +disk0_type="virtio-blk" +disk0_name="disk0.img" +graphics="yes" +graphics_vga=io +uuid="1c45400b-c828-11ef-8871-e8ff1ed71cac" +network0_mac="58:9c:fc:0d:13:3f" +``` ### VM installation ```sh -paul@f2:~ % doas vm install rocky Rocky-9.5-x86_64-minimal.iso +paul@f0:~ % doas vm install rocky Rocky-9.5-x86_64-minimal.iso Starting rocky * found guest in /zroot/bhyve/rocky * booting... @@ -115,6 +136,44 @@ root bhyve 6079 8 tcp4 *:5900 *:* Port 5900 is now also open for VNC connections, so we connect to it with a VNC client and run through the installation dialogs. I'm sure this could be done unattended or more automated, but we have only 3 VMs to install, and the automation doesn't seem worth it as we are doing it only once. +### Increase of the disk image + +By default the VMs disk image is only 20G, which is a bit small for my purposes, so I stopped the VMs again and run `truncate` on the image file to enlarge them to 100G, and re-started the installation: + +```sh +paul@f0:/bhyve/rocky % doas vm stop rocky +paul@f0:/bhyve/rocky % doas truncate -s 100G disk0.img +paul@f0:/bhyve/rocky % doas vm install rocky Rocky-9.5-x86_64-minimal.iso +``` + +### Connect to VPN + +For the installation, I opened the VPN client on my Fedora laptop (GNOME comes with a simple VPN client) and ran through the base installation for each of the VMs manually. I am sure this could have been automated a bit more, but there were just 3 VMs, and it wasn't worth the effort. The three VNC addresses of the VMs were: `vnc://f0:5900`, `vnc://f1:5900`, and `vnc://f0:5900`. + +I mostly selected the default settings (auto partitioning on the 100GB drive and a root user password). After the installation, the VMs were rebooted. + +## After install + +After that, I changed the network configuration to be static here as well. + +As per previous post of this series, the 3 FreeBSD hosts were already in my `/etc/hosts` file: + +``` +192.168.1.130 f0 f0.lan f0.lan.buetow.org +192.168.1.131 f1 f1.lan f1.lan.buetow.org +192.168.1.132 f2 f2.lan f2.lan.buetow.org +``` + +For the Rocky VMs I added those: + +```sh +cat <>/etc/hosts +192.168.1.120 r0 r0.lan r0.lan.buetow.org +192.168.1.121 r1 r1.lan r1.lan.buetow.org +192.168.1.122 r2 r2.lan r2.lan.buetow.org +END +``` +and configured the IPs accordingly on the VMs themselves. Other *BSD-related posts: diff --git a/gemfeed/index.md b/gemfeed/index.md index eeaa7d8c..1650a18b 100644 --- a/gemfeed/index.md +++ b/gemfeed/index.md @@ -2,6 +2,7 @@ ## To be in the .zone! +[2025-01-15 - Working with an SRE Interview](./2025-01-15-working-with-an-sre-interview.md) [2025-01-01 - Posts from October to December 2024](./2025-01-01-posts-from-october-to-december-2024.md) [2024-12-15 - Random Helix Themes](./2024-12-15-random-helix-themes.md) [2024-12-03 - f3s: Kubernetes with FreeBSD - Part 2: Hardware and base installation](./2024-12-03-f3s-kubernetes-with-freebsd-part-2.md) -- cgit v1.2.3 From 9d2fe20897110f973732bacdea4ae26b68543e14 Mon Sep 17 00:00:00 2001 From: Paul Buetow Date: Wed, 15 Jan 2025 00:23:46 +0200 Subject: Update content for md --- gemfeed/2025-01-15-working-with-an-sre-interview.md | 3 ++- 1 file changed, 2 insertions(+), 1 deletion(-) (limited to 'gemfeed') diff --git a/gemfeed/2025-01-15-working-with-an-sre-interview.md b/gemfeed/2025-01-15-working-with-an-sre-interview.md index e9556cfb..b16c4a57 100644 --- a/gemfeed/2025-01-15-working-with-an-sre-interview.md +++ b/gemfeed/2025-01-15-working-with-an-sre-interview.md @@ -2,9 +2,10 @@ > Published at 2025-01-15T00:16:04+02:00 -I have been interviewed by Florian Buetow about what it's like working with a Site Reliability Engineer from the point of view of a Software Engineer, Data Scientist, and AI Engineer. +I have been interviewed by Florian Buetow on `cracking-ai-engineering.com` about what it's like working with a Site Reliability Engineer from the point of view of a Software Engineer, Data Scientist, and AI Engineer. [See original interview here](https://www.cracking-ai-engineering.com/writing/2025/01/12/working-with-an-sre-interview/) +[Cracking AI Engineering](https://www.cracking-ai-engineering.com) Below, I am posting the interview here on my blog as well. -- cgit v1.2.3 From 2c7f1e38a39a19961a484db26a530584f5c91ee9 Mon Sep 17 00:00:00 2001 From: Paul Buetow Date: Wed, 15 Jan 2025 00:29:09 +0200 Subject: Update content for md --- gemfeed/2025-01-15-working-with-an-sre-interview.md | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) (limited to 'gemfeed') diff --git a/gemfeed/2025-01-15-working-with-an-sre-interview.md b/gemfeed/2025-01-15-working-with-an-sre-interview.md index b16c4a57..bf2e27d3 100644 --- a/gemfeed/2025-01-15-working-with-an-sre-interview.md +++ b/gemfeed/2025-01-15-working-with-an-sre-interview.md @@ -173,6 +173,6 @@ Thank you very much for your time and this insightful interview into the world o Dear reader, I hope this conversation with Paul Bütow provided an exciting peak into the world of Site Reliability Engineering. Whether you’re a software developer, data scientist, ML engineer, or manager, reliable systems are always a team effort. Hopefully, you’ve taken some insights or tips from Paul’s experiences for your own team or next project. Thanks for joining us, and best of luck refining your own SRE practices! -E-Mail your comments to `paul@nospam.buetow.org` :-) +E-Mail your comments to `paul@nospam.buetow.org` or contact Florian via the Cracking AI Engineering :-) [Back to the main site](../) -- cgit v1.2.3 From da27cb13ff8e7cec31de76122d769207773597a9 Mon Sep 17 00:00:00 2001 From: Paul Buetow Date: Thu, 16 Jan 2025 22:58:50 +0200 Subject: Update content for md --- ...024-12-03-f3s-kubernetes-with-freebsd-part-2.md | 30 +++++++++------------- 1 file changed, 12 insertions(+), 18 deletions(-) (limited to 'gemfeed') diff --git a/gemfeed/2024-12-03-f3s-kubernetes-with-freebsd-part-2.md b/gemfeed/2024-12-03-f3s-kubernetes-with-freebsd-part-2.md index 06c11371..b45dbe81 100644 --- a/gemfeed/2024-12-03-f3s-kubernetes-with-freebsd-part-2.md +++ b/gemfeed/2024-12-03-f3s-kubernetes-with-freebsd-part-2.md @@ -171,24 +171,18 @@ root@f0:~ # cp /usr/local/etc/doas.conf.sample /usr/local/etc/doas.conf `zfs-periodic` is a nifty tool for automatically creating ZFS snapshots. I decided to go with the following configuration here: ```sh -root@f0:~ # sysrc daily_zfs_snapshot_enable=YES -daily_zfs_snapshot_enable: -> YES -root@f0:~ # sysrc daily_zfs_snapshot_pools=zroot -daily_zfs_snapshot_pools: -> zroot -root@f0:~ # sysrc daily_zfs_snapshot_keep=7 -daily_zfs_snapshot_keep: -> 7 -root@f0:~ # sysrc weekly_zfs_snapshot_enable=YES -weekly_zfs_snapshot_enable: -> YES -root@f0:~ # sysrc weekly_zfs_snapshot_pools=zroot -weekly_zfs_snapshot_pools: -> zroot -root@f0:~ # sysrc weekly_zfs_snapshot_keep=5 -weekly_zfs_snapshot_keep: -> 5 -root@f0:~ # sysrc monthly_zfs_snapshot_enable=YES -monthly_zfs_snapshot_enable: -> YES -root@f0:~ # sysrc monthly_zfs_snapshot_pools=zroot -monthly_zfs_snapshot_pools: -> zroot -root@f0:~ # sysrc monthly_zfs_snapshot_keep=6 -monthly_zfs_snapshot_keep: 2 -> 6 +root@f0:~ # +cat <>/etc/periodic.conf +daily_zfs_snapshot_enable="YES" +daily_zfs_snapshot_pools="zroot" +daily_zfs_snapshot_keep="7" +weekly_zfs_snapshot_enable="YES" +weekly_zfs_snapshot_pools="zroot" +weekly_zfs_snapshot_keep="5" +monthly_zfs_snapshot_enable="YES" +monthly_zfs_snapshot_pools="zroot" +monthly_zfs_snapshot_keep="6" +END ``` [https://github.com/ross/zfs-periodic](https://github.com/ross/zfs-periodic) -- cgit v1.2.3 From a8dc34f1200892637acbfae95372931ad688baf5 Mon Sep 17 00:00:00 2001 From: Paul Buetow Date: Sun, 19 Jan 2025 13:22:36 +0200 Subject: Update content for md --- gemfeed/2024-12-03-f3s-kubernetes-with-freebsd-part-2.md | 3 +-- gemfeed/2025-01-01-posts-from-october-to-december-2024.md | 11 ++++++++++- 2 files changed, 11 insertions(+), 3 deletions(-) (limited to 'gemfeed') diff --git a/gemfeed/2024-12-03-f3s-kubernetes-with-freebsd-part-2.md b/gemfeed/2024-12-03-f3s-kubernetes-with-freebsd-part-2.md index b45dbe81..34ef8a29 100644 --- a/gemfeed/2024-12-03-f3s-kubernetes-with-freebsd-part-2.md +++ b/gemfeed/2024-12-03-f3s-kubernetes-with-freebsd-part-2.md @@ -171,8 +171,7 @@ root@f0:~ # cp /usr/local/etc/doas.conf.sample /usr/local/etc/doas.conf `zfs-periodic` is a nifty tool for automatically creating ZFS snapshots. I decided to go with the following configuration here: ```sh -root@f0:~ # -cat <>/etc/periodic.conf +root@f0:~ # cat <>/etc/periodic.conf daily_zfs_snapshot_enable="YES" daily_zfs_snapshot_pools="zroot" daily_zfs_snapshot_keep="7" diff --git a/gemfeed/2025-01-01-posts-from-october-to-december-2024.md b/gemfeed/2025-01-01-posts-from-october-to-december-2024.md index e22fa3f7..ba9ae92d 100644 --- a/gemfeed/2025-01-01-posts-from-october-to-december-2024.md +++ b/gemfeed/2025-01-01-posts-from-october-to-december-2024.md @@ -14,6 +14,7 @@ These are from Mastodon and LinkedIn. Have a look at my about page for my social ## Table of Contents * [⇢ Posts from October to December 2024](#posts-from-october-to-december-2024) +* [⇢ Posts for 202410 202411 202412](#posts-for-202410-202411-202412) * [⇢ ⇢ October 2024](#october-2024) * [⇢ ⇢ ⇢ First on-call experience in a startup. Doesn't ...](#first-on-call-experience-in-a-startup-doesn-t-) * [⇢ ⇢ ⇢ Reviewing your own PR or MR before asking ...](#reviewing-your-own-pr-or-mr-before-asking-) @@ -61,6 +62,8 @@ These are from Mastodon and LinkedIn. Have a look at my about page for my social * [⇢ ⇢ ⇢ It's the small things, which make Unix like ...](#it-s-the-small-things-which-make-unix-like-) * [⇢ ⇢ ⇢ My New Year's resolution is not to start any ...](#my-new-year-s-resolution-is-not-to-start-any-) +# Posts for 202410 202411 202412 + ## October 2024 ### First on-call experience in a startup. Doesn't ... @@ -111,6 +114,7 @@ The opposite of `#ChaosMonkey` ... automatically repairing and healing services I just became a Silver Patreon for OSnews. What is OSnews? It is an independent news site about IT. It is slightly independent and, at times, alternative. I have enjoyed it since my early student days. This one and other projects I financially support are listed here: +[foo.zone/gemf...i-support.gmi (Gemini)](gemini://foo.zone/gemfeed/2024-09-07-projects-i-support.gmi) [foo.zone/gemf...-support.html](https://foo.zone/gemfeed/2024-09-07-projects-i-support.html) ### Until now, I wasn't aware, that Go is under a ... @@ -123,6 +127,7 @@ Until now, I wasn't aware, that Go is under a BSD-style license (3-clause as it These are some book notes from "Staff Engineer" – there is some really good insight into what is expected from a Staff Engineer and beyond in the industry. I wish I had read the book earlier. +[foo.zone/gemf...ook-notes.gmi (Gemini)](gemini://foo.zone/gemfeed/2024-10-24-staff-engineer-book-notes.gmi) [foo.zone/gemf...ok-notes.html](https://foo.zone/gemfeed/2024-10-24-staff-engineer-book-notes.html) ### Looking at `#Kubernetes`, it's pretty much ... @@ -133,6 +138,7 @@ Looking at `#Kubernetes`, it's pretty much following the Unix way of doing thing There has been an outage at the upstream network provider for OpenBSD.Amsterdam (hoster, I am using). This was the first real-world test for my KISS HA setup, and it worked flawlessly! All my sites and services failed over automatically to my other `#OpenBSD` VM! +[foo.zone/gemf...h-OpenBSD.gmi (Gemini)](gemini://foo.zone/gemfeed/2024-04-01-KISS-high-availability-with-OpenBSD.gmi) [foo.zone/gemf...-OpenBSD.html](https://foo.zone/gemfeed/2024-04-01-KISS-high-availability-with-OpenBSD.html) [openbsd.amsterdam/](https://openbsd.amsterdam/) @@ -170,6 +176,7 @@ At first, functional options add a bit of boilerplate, but they turn out to be q Revamping my home lab a little bit. `#freebsd` `#bhyve` `#rocky` `#linux` `#vm` `#k3s` `#kubernetes` `#wireguard` `#zfs` `#nfs` `#ha` `#relayd` `#k8s` `#selfhosting` `#homelab` +[foo.zone/gemf...sd-part-1.gmi (Gemini)](gemini://foo.zone/gemfeed/2024-11-17-f3s-kubernetes-with-freebsd-part-1.gmi) [foo.zone/gemf...d-part-1.html](https://foo.zone/gemfeed/2024-11-17-f3s-kubernetes-with-freebsd-part-1.html) ### Wondering to which `#web` `#browser` I should ... @@ -224,6 +231,7 @@ Thats unexpected, you cant remove a NaN key from a map without clearing it! `#go My second blog post about revamping my home lab a little bit just hit the net. `#FreeBSD` `#ZFS` `#n100` `#k8s` `#k3s` `#kubernetes` +[foo.zone/gemf...sd-part-2.gmi (Gemini)](gemini://foo.zone/gemfeed/2024-12-03-f3s-kubernetes-with-freebsd-part-2.gmi) [foo.zone/gemf...d-part-2.html](https://foo.zone/gemfeed/2024-12-03-f3s-kubernetes-with-freebsd-part-2.html) ### Very insightful article about tech hiring in ... @@ -277,6 +285,7 @@ This blog post is basically a rant against DataDog... Personally, I don't have m Quick trick to get Helix themes selected randomly `#HelixEditor` +[foo.zone/gemf...ix-themes.gmi (Gemini)](gemini://foo.zone/gemfeed/2024-12-15-random-helix-themes.gmi) [foo.zone/gemf...x-themes.html](https://foo.zone/gemfeed/2024-12-15-random-helix-themes.html) ### Example where complexity attacks you from ... @@ -317,7 +326,7 @@ It's the small things, which make Unix like systems, like GNU/Linux, interesting ### My New Year's resolution is not to start any ... -A plan of mine for next year is not to start any new non-fiction books (or only very few) but to re-read and listen to my favorites, which I read to reflect on and see things from different perspectives. Every time you re-read a book, you gain new insights. +My New Year's resolution is not to start any new non-fiction books (or only very few) but to re-read and listen to my favorites, which I read to reflect on and see things from different perspectives. Every time you re-read a book, you gain new insights.16350 Other related posts: -- cgit v1.2.3 From ad5aa880195a3efcd031d276009c630e02e2aff4 Mon Sep 17 00:00:00 2001 From: Paul Buetow Date: Sun, 26 Jan 2025 23:22:25 +0200 Subject: Update content for md --- gemfeed/4 | 239 ++++++++++++++ gemfeed/DRAFT-f3s-kubernetes-with-freebsd-bhyve.md | 191 ----------- .../DRAFT-f3s-kubernetes-with-freebsd-part-3.md | 360 +++++++++++++++++++++ .../apc-back-ups.jpg | Bin 0 -> 295558 bytes .../f3s-changes.jpg | Bin 0 -> 54543 bytes 5 files changed, 599 insertions(+), 191 deletions(-) create mode 100644 gemfeed/4 delete mode 100644 gemfeed/DRAFT-f3s-kubernetes-with-freebsd-bhyve.md create mode 100644 gemfeed/DRAFT-f3s-kubernetes-with-freebsd-part-3.md create mode 100644 gemfeed/f3s-kubernetes-with-freebsd-part-3/apc-back-ups.jpg create mode 100644 gemfeed/f3s-kubernetes-with-freebsd-part-3/f3s-changes.jpg (limited to 'gemfeed') diff --git a/gemfeed/4 b/gemfeed/4 new file mode 100644 index 00000000..f4c59789 --- /dev/null +++ b/gemfeed/4 @@ -0,0 +1,239 @@ +# f3s: Kubernetes with FreeBSD - Rocky Linux Bhyve VMs - Part 3 + +This is the third blog post about my f3s series for my self-hosting demands in my home lab. f3s? The "f" stands for FreeBSD, and the "3s" stands for k3s, the Kubernetes distribution we will use on FreeBSD-based physical machines. + +<< template::inline::index f3s-kubernetes-with-freebsd-part + +=> ./f3s-kubernetes-with-frhyveeebsd-part-1/f3slogo.png f3s logo + +<< template::inline::toc + +## Introduction + +In this blog post, we are going to install the Bhyve hypervisor. + +The FreeBSD Bhyve hypervisor is a lightweight, modern hypervisor that enables virtualization on FreeBSD systems. Bhyve's strengths include its minimal overhead, which allows it to achieve near-native performance for virtual machines. It is designed to be efficient and lightweight, leveraging the capabilities of the FreeBSD operating system for performance and network management. + +Bhyve supports running a variety of guest operating systems, including FreeBSD, Linux, and Windows, on hardware platforms that support hardware virtualization extensions (such as Intel VT-x or AMD-V). In our case, we are going to virtualize Rocky Linux, which later on in this series will be used to run k3s. + +## Basic Bhyve setup + +For the management of the Bhyve VMs, we are using `vm-bhyve`, a tool not part of the FreeBSD operating system but available as a ready-to-use package. It eases VM management and reduces a lot of the overhead. We also install the required package to make Bhyve work with the UEFI firmware. + +=> https://github.com/churchers/vm-bhyve + +The following commands are executed on all three hosts `f0`, `f1`, and `f2`, where `re0` is the name of the Ethernet interface (which may need to be adjusted if your hardware is different): + +```sh +paul@f0:~ % doas pkg install vm-bhyve bhyve-firmware +paul@f0:~ % doas sysrc vm_enable=YES +vm_enable: -> YES +paul@f0:~ % doas sysrc vm_dir=zfs:zroot/bhyve +vm_dir: -> zfs:zroot/bhyve +paul@f0:~ % doas zfs create zroot/bhyve +paul@f0:~ % doas vm init +paul@f0:~ % doas vm switch create public +paul@f0:~ % doas vm switch add public re0 +``` + +Bhyve stores all it's data in the `/bhyve` of the `zroot` ZFS pool: + +```sh +paul@f0:~ % zfs list | grep bhyve +zroot/bhyve 1.74M 453G 1.74M /zroot/bhyve +``` + +For convenience, we also create this symlink: + +```sh +paul@f0:~ % doas ln -s /zroot/bhyve/ /bhyve + +``` + +Now, Bhyve is ready to rumble, but no VMs are there yet: + +```sh +paul@f0:~ % doas vm list +NAME DATASTORE LOADER CPU MEMORY VNC AUTO STATE +``` + +## Rocky Linux VMs + +### ISO download + +We're going to install the Rocky Linux from the latest minimal iso: + +```sh +paul@f0:~ % doas vm iso \ + https://download.rockylinux.org/pub/rocky/9/isos/x86_64/Rocky-9.5-x86_64-minimal.iso +/zroot/bhyve/.iso/Rocky-9.5-x86_64-minimal.iso 1808 MB 4780 kBps 06m28s +paul@f0:/bhyve % doas vm create rocky +``` +### VM configuration + +The default configuration looks like this now: + +```sh +paul@f0:/bhyve/rocky % cat rocky.conf +loader="bhyveload" +cpu=1 +memory=256M +network0_type="virtio-net" +network0_switch="public" +disk0_type="virtio-blk" +disk0_name="disk0.img" +uuid="1c4655ac-c828-11ef-a920-e8ff1ed71ca0" +network0_mac="58:9c:fc:0d:13:3f" +``` + +Whereas the `uuid` and the `network0_mac` differ on each of the 3 hosts. + +but in order to make Rocky Linux boot it (plus some other adjustments, e.g. as I am intending to run the majority of the workload in the k3s cluster running on those linux VMs, I give them beefy specs like 4 CPU cores and 14GB RAM), I run `doas vm configure rocky` and modified it to: + +``` +guest="linux" +loader="uefi" +uefi_vars="yes" +cpu=4 +memory=14G +network0_type="virtio-net" +network0_switch="public" +disk0_type="virtio-blk" +disk0_name="disk0.img" +graphics="yes" +graphics_vga=io +uuid="1c45400b-c828-11ef-8871-e8ff1ed71cac" +network0_mac="58:9c:fc:0d:13:3f" +``` + +### VM installation + +To start the installer from the downloaded ISO, I run: + +```sh +paul@f0:~ % doas vm install rocky Rocky-9.5-x86_64-minimal.iso +Starting rocky + * found guest in /zroot/bhyve/rocky + * booting... + +paul@f0:/bhyve/rocky % doas vm list +NAME DATASTORE LOADER CPU MEMORY VNC AUTO STATE +rocky default uefi 4 14G 0.0.0.0:5900 No Locked (f0.lan.buetow.org) + +paul@f0:/bhyve/rocky % doas sockstat -4 | grep 5900 +root bhyve 6079 8 tcp4 *:5900 *:* +``` + +Port 5900 now also opened for VNC connections, so I connected to it with a VNC client and run through the installation dialogs. I'm sure this could be done unattended or more automated, there are only 3 VMs to install, and the automation doesn't seem worth it as we are doing it only once in a year or less often. + +### Increase of the disk image + +By default the VMs disk image is only 20G, which is a bit small for my purposes, so I stopped the VMs again and run `truncate` on the image file to enlarge them to 100G, and re-started the installation: + +```sh +paul@f0:/bhyve/rocky % doas vm stop rocky +paul@f0:/bhyve/rocky % doas truncate -s 100G disk0.img +paul@f0:/bhyve/rocky % doas vm install rocky Rocky-9.5-x86_64-minimal.iso +``` + +### Connect to VPN + +For the installation, I opened the VPN client on my Fedora laptop (GNOME comes with a simple VPN client) and ran through the base installation for each of the VMs manually. Again, I am sure this could have been automated a bit more, but there were just 3 VMs, and it wasn't worth the effort. The three VNC addresses of the VMs were: `vnc://f0:5900`, `vnc://f1:5900`, and `vnc://f0:5900`. + +I mostly selected the default settings (auto partitioning on the 100GB drive and a root user password). After the installation, the VMs were rebooted. + +## After install + +I performed the following steps for all 3 VMs. In the following, the examples are all executed on `f0` (bzw the VM `r0` running on `f0`): + +### VM auto-start after host reboot + +To automatically start the VM on the servers I added the following to the `rc.conf` on the FreeBSD hosts: + +```sh + +paul@f0:/bhyve/rocky % cat <>/etc/hosts +192.168.1.120 r0 r0.lan r0.lan.buetow.org +192.168.1.121 r1 r1.lan r1.lan.buetow.org +192.168.1.122 r2 r2.lan r2.lan.buetow.org +END +```` + +Whereas: + +* `192.168.1.120` is the IP of the VM itself (here: `r0.lan.buetow.org`) +* `192.168.1.1` is the address of my home router, which also does DNS. + +### Permitting root login + +As these VMs arent directly reachable via SSH from the internet, I enabled `root` login by adding a line with `PermitRootLogin yes` to `/etc/sshd/sshd_config`. + +Once done, I rebooted the VM by running `reboot` inside of the vm to test whether everything was configured and persisted correctly. + +After reboot, I copied my public key from my Laptop to the 3 VMs: + +```sh +% for i in 0 1 2; do ssh-copy-id root@r$i.lan.buetow.org; done +``` + +And then I edited the `/etc/ssh/sshd_config` file again on all 3 VMs and configured `PasswordAuthentication no`, to only allow SSH key authentication from now on. + +### Install latest updates + +```sh +[root@r0 ~] % dnf update +[root@r0 ~] % dreboot +``` + +CPU STRESS TESTER VM VS NOT VM + +Other *BSD-related posts: + +<< template::inline::index bsd + +E-Mail your comments to `paul@nospam.buetow.org` :-) + +=> ../ Back to the main site diff --git a/gemfeed/DRAFT-f3s-kubernetes-with-freebsd-bhyve.md b/gemfeed/DRAFT-f3s-kubernetes-with-freebsd-bhyve.md deleted file mode 100644 index d9932801..00000000 --- a/gemfeed/DRAFT-f3s-kubernetes-with-freebsd-bhyve.md +++ /dev/null @@ -1,191 +0,0 @@ -# f3s: Kubernetes with FreeBSD - Rocky Linux Bhyve VMs - Part 3 - -This is the third blog post about my f3s series for my self-hosting demands in my home lab. f3s? The "f" stands for FreeBSD, and the "3s" stands for k3s, the Kubernetes distribution we will use on FreeBSD-based physical machines. - -[2024-11-17 f3s: Kubernetes with FreeBSD - Part 1: Setting the stage](./2024-11-17-f3s-kubernetes-with-freebsd-part-1.md) -[2024-12-03 f3s: Kubernetes with FreeBSD - Part 2: Hardware and base installation](./2024-12-03-f3s-kubernetes-with-freebsd-part-2.md) - -[![f3s logo](./f3s-kubernetes-with-frhyveeebsd-part-1/f3slogo.png "f3s logo")](./f3s-kubernetes-with-frhyveeebsd-part-1/f3slogo.png) - -## Table of Contents - -* [⇢ f3s: Kubernetes with FreeBSD - Rocky Linux Bhyve VMs - Part 3](#f3s-kubernetes-with-freebsd---rocky-linux-bhyve-vms---part-3) -* [⇢ ⇢ Introduction](#introduction) -* [⇢ ⇢ Basic Bhyve setup](#basic-bhyve-setup) -* [⇢ ⇢ Rocky Linux VMs](#rocky-linux-vms) -* [⇢ ⇢ ⇢ ISO download](#iso-download) -* [⇢ ⇢ ⇢ VM configuration](#vm-configuration) -* [⇢ ⇢ ⇢ VM installation](#vm-installation) -* [⇢ ⇢ ⇢ Increase of the disk image](#increase-of-the-disk-image) -* [⇢ ⇢ ⇢ Connect to VPN](#connect-to-vpn) -* [⇢ ⇢ After install](#after-install) - -## Introduction - -In this blog post, we are going to install the Bhyve hypervisor. - -The FreeBSD Bhyve hypervisor is a lightweight, modern hypervisor that enables virtualization on FreeBSD systems. Bhyve's strengths include its minimal overhead, which allows it to achieve near-native performance for virtual machines. It is designed to be efficient and lightweight, leveraging the capabilities of the FreeBSD operating system for performance and network management. - -Bhyve supports running a variety of guest operating systems, including FreeBSD, Linux, and Windows, on hardware platforms that support hardware virtualization extensions (such as Intel VT-x or AMD-V). In our case, we are going to virtualize Rocky Linux, which later on in this series will be used to run k3s. - -## Basic Bhyve setup - -For the management of the Bhyve VMs, we are using `vm-bhyve`, a tool not part of the FreeBSD operating system but available as a ready-to-use package. It eases VM management and reduces a lot of the overhead. We also install the required package to make Bhyve work with the UEFI firmware. - -[https://github.com/churchers/vm-bhyve](https://github.com/churchers/vm-bhyve) - -The following commands are executed on all three hosts `f0`, `f1`, and `f2`, where `re0` is the name of the Ethernet interface (which may need to be adjusted if your hardware is different): - -```sh -paul@f0:~ % doas pkg install vm-bhyve bhyve-firmware -paul@f0:~ % doas sysrc vm_enable=YES -vm_enable: -> YES -paul@f0:~ % doas sysrc vm_dir=zfs:zroot/bhyve -vm_dir: -> zfs:zroot/bhyve -paul@f0:~ % doas zfs create zroot/bhyve -paul@f0:~ % doas vm init -paul@f0:~ % doas vm switch create public -paul@f0:~ % doas vm switch add public re0 -``` - -Bhyve stores all it's data in the `/bhyve` of the `zroot` ZFS pool: - -```sh -paul@f0:~ % zfs list | grep bhyve -zroot/bhyve 1.74M 453G 1.74M /zroot/bhyve -``` - -For convenience, we also create this symlink: - -```sh -paul@f0:~ % doas ln -s /zroot/bhyve/ /bhyve - -``` - -Now, Bhyve is ready to rumble, but no VMs are there yet: - -```sh -paul@f0:~ % doas vm list -NAME DATASTORE LOADER CPU MEMORY VNC AUTO STATE -``` - -## Rocky Linux VMs - -### ISO download - -We're going to install the Rocky Linux from the latest minimal iso: - -```sh -paul@f0:~ % doas vm iso \ - https://download.rockylinux.org/pub/rocky/9/isos/x86_64/Rocky-9.5-x86_64-minimal.iso -/zroot/bhyve/.iso/Rocky-9.5-x86_64-minimal.iso 1808 MB 4780 kBps 06m28s -paul@f0:/bhyve % doas vm create rocky -``` -### VM configuration - -The default configuration looks like this now: - -```sh -paul@f0:/bhyve/rocky % cat rocky.conf -loader="bhyveload" -cpu=1 -memory=256M -network0_type="virtio-net" -network0_switch="public" -disk0_type="virtio-blk" -disk0_name="disk0.img" -uuid="1c4655ac-c828-11ef-a920-e8ff1ed71ca0" -network0_mac="58:9c:fc:0d:13:3f" -``` - -Whereas the `uuid` and the `network0_mac` differ on each of the 3 hosts. - -but in order to make Rocky Linux boot it (plus some other adjustments, e.g. as I am intending to run the majority of the workload in the k3s cluster running on those linux VMs, I give them beefy specs like 4 CPU cores and 14GB RAM), I modified it to: - -```sh -guest="linux" -loader="uefi" -uefi_vars="yes" -cpu=4 -memory=14G -network0_type="virtio-net" -network0_switch="public" -disk0_type="virtio-blk" -disk0_name="disk0.img" -graphics="yes" -graphics_vga=io -uuid="1c45400b-c828-11ef-8871-e8ff1ed71cac" -network0_mac="58:9c:fc:0d:13:3f" -``` - -### VM installation - -```sh -paul@f0:~ % doas vm install rocky Rocky-9.5-x86_64-minimal.iso -Starting rocky - * found guest in /zroot/bhyve/rocky - * booting... - -paul@f0:/bhyve/rocky % doas vm list -NAME DATASTORE LOADER CPU MEMORY VNC AUTO STATE -rocky default uefi 4 14G 0.0.0.0:5900 No Locked (f0.lan.buetow.org) - -paul@f0:/bhyve/rocky % doas sockstat -4 | grep 5900 -root bhyve 6079 8 tcp4 *:5900 *:* -``` - -Port 5900 is now also open for VNC connections, so we connect to it with a VNC client and run through the installation dialogs. I'm sure this could be done unattended or more automated, but we have only 3 VMs to install, and the automation doesn't seem worth it as we are doing it only once. - -### Increase of the disk image - -By default the VMs disk image is only 20G, which is a bit small for my purposes, so I stopped the VMs again and run `truncate` on the image file to enlarge them to 100G, and re-started the installation: - -```sh -paul@f0:/bhyve/rocky % doas vm stop rocky -paul@f0:/bhyve/rocky % doas truncate -s 100G disk0.img -paul@f0:/bhyve/rocky % doas vm install rocky Rocky-9.5-x86_64-minimal.iso -``` - -### Connect to VPN - -For the installation, I opened the VPN client on my Fedora laptop (GNOME comes with a simple VPN client) and ran through the base installation for each of the VMs manually. I am sure this could have been automated a bit more, but there were just 3 VMs, and it wasn't worth the effort. The three VNC addresses of the VMs were: `vnc://f0:5900`, `vnc://f1:5900`, and `vnc://f0:5900`. - -I mostly selected the default settings (auto partitioning on the 100GB drive and a root user password). After the installation, the VMs were rebooted. - -## After install - -After that, I changed the network configuration to be static here as well. - -As per previous post of this series, the 3 FreeBSD hosts were already in my `/etc/hosts` file: - -``` -192.168.1.130 f0 f0.lan f0.lan.buetow.org -192.168.1.131 f1 f1.lan f1.lan.buetow.org -192.168.1.132 f2 f2.lan f2.lan.buetow.org -``` - -For the Rocky VMs I added those: - -```sh -cat <>/etc/hosts -192.168.1.120 r0 r0.lan r0.lan.buetow.org -192.168.1.121 r1 r1.lan r1.lan.buetow.org -192.168.1.122 r2 r2.lan r2.lan.buetow.org -END -``` -and configured the IPs accordingly on the VMs themselves. - - -Other *BSD-related posts: - -[2016-04-09 Jails and ZFS with Puppet on FreeBSD](./2016-04-09-jails-and-zfs-on-freebsd-with-puppet.md) -[2022-07-30 Let's Encrypt with OpenBSD and Rex](./2022-07-30-lets-encrypt-with-openbsd-and-rex.md) -[2022-10-30 Installing DTail on OpenBSD](./2022-10-30-installing-dtail-on-openbsd.md) -[2024-01-13 One reason why I love OpenBSD](./2024-01-13-one-reason-why-i-love-openbsd.md) -[2024-04-01 KISS high-availability with OpenBSD](./2024-04-01-KISS-high-availability-with-OpenBSD.md) -[2024-11-17 f3s: Kubernetes with FreeBSD - Part 1: Setting the stage](./2024-11-17-f3s-kubernetes-with-freebsd-part-1.md) -[2024-12-03 f3s: Kubernetes with FreeBSD - Part 2: Hardware and base installation](./2024-12-03-f3s-kubernetes-with-freebsd-part-2.md) - -E-Mail your comments to `paul@nospam.buetow.org` :-) - -[Back to the main site](../) diff --git a/gemfeed/DRAFT-f3s-kubernetes-with-freebsd-part-3.md b/gemfeed/DRAFT-f3s-kubernetes-with-freebsd-part-3.md new file mode 100644 index 00000000..55595bcb --- /dev/null +++ b/gemfeed/DRAFT-f3s-kubernetes-with-freebsd-part-3.md @@ -0,0 +1,360 @@ +# f3s: Kubernetes with FreeBSD - Part 3: Protecting from power cuts + +This is the third blog post about my f3s series for my self-hosting demands in my home lab. f3s? The "f" stands for FreeBSD, and the "3s" stands for k3s, the Kubernetes distribution we will use on FreeBSD-based physical machines. + +[2024-11-17 f3s: Kubernetes with FreeBSD - Part 1: Setting the stage](./2024-11-17-f3s-kubernetes-with-freebsd-part-1.md) +[2024-12-03 f3s: Kubernetes with FreeBSD - Part 2: Hardware and base installation](./2024-12-03-f3s-kubernetes-with-freebsd-part-2.md) + +[![f3s logo](./f3s-kubernetes-with-freebsd-part-1/f3slogo.png "f3s logo")](./f3s-kubernetes-with-freebsd-part-1/f3slogo.png) + +## Table of Contents + +* [⇢ f3s: Kubernetes with FreeBSD - Part 3: Protecting from power cuts](#f3s-kubernetes-with-freebsd---part-3-protecting-from-power-cuts) +* [⇢ ⇢ Introduction](#introduction) +* [⇢ ⇢ Changes since last time](#changes-since-last-time) +* [⇢ ⇢ ⇢ FreeBSD upgrade from 14.1 to 14.2](#freebsd-upgrade-from-141-to-142) +* [⇢ ⇢ ⇢ A new home (behind the TV)](#a-new-home-behind-the-tv) +* [⇢ ⇢ The UPS hardware](#the-ups-hardware) +* [⇢ ⇢ Configuring FreeBSD to Work with the UPS](#configuring-freebsd-to-work-with-the-ups) +* [⇢ ⇢ ⇢ USB Device Detection](#usb-device-detection) +* [⇢ ⇢ ⇢ `apcupsd` Installation](#apcupsd-installation) +* [⇢ ⇢ ⇢ UPS Connectivity Test](#ups-connectivity-test) +* [⇢ ⇢ APC Info on Partner Nodes:](#apc-info-on-partner-nodes) +* [⇢ ⇢ ⇢ Installation on partners](#installation-on-partners) +* [⇢ ⇢ Power outage simulation](#power-outage-simulation) +* [⇢ ⇢ ⇢ Pulling the plug](#pulling-the-plug) +* [⇢ ⇢ ⇢ Restoring power](#restoring-power) + +## Introduction + +In this blog post, we are setting up the UPS for the cluster. A UPS, or Uninterruptible Power Supply, safeguards my cluster from unexpected power outages and surges. It acts as a backup battery that kicks in when the electricity cuts out—especially useful in my area, where power cuts are frequent—allowing for a graceful system shutdown and preventing data loss and corruption. This is especially important since I will also store some of my data on the f3s nodes. + +## Changes since last time + +### FreeBSD upgrade from 14.1 to 14.2 + +There has been a new release since the last blog post in this series. The upgrade from 14.1 was as easy as: + +```sh +paul@f0: ~ % doas freebsd-update fetch +paul@f0: ~ % doas freebsd-update install +paul@f0: ~ % doas freebsd-update -r 14.2-RELEASE upgrade +paul@f0: ~ % doas freebsd-update install +paul@f0: ~ % doas shutdown -r now +``` + +And after rebooting, I ran: + +```sh +paul@f0: ~ % doas freebsd-update install +paul@f0: ~ % doas pkg update +paul@f0: ~ % doas pkg upgrade +paul@f0: ~ % doas shutdown -r now +``` + +And after another reboot, I was on 14.2: + +```sh +paul@f0:~ % uname -a +FreeBSD f0.lan.buetow.org 14.2-RELEASE FreeBSD 14.2-RELEASE + releng/14.2-n269506-c8918d6c7412 GENERIC amd64 +``` + +And, of course, I ran this on all 3 nodes! + +### A new home (behind the TV) + +I've put all the infrastructure behind my TV, as plenty of space is available. The TV hides most of the setup, which drastically improved the SAF (spouse acceptance factor). + +[![New hardware placement arrangement](./f3s-kubernetes-with-freebsd-part-3/f3s-changes.jpg "New hardware placement arrangement")](./f3s-kubernetes-with-freebsd-part-3/f3s-changes.jpg) + +I got rid of the mini-switch I mentioned in the previous blog post. I have the TP-Link EAP615-Wall mounted on the wall nearby, which is my OpenWrt-powered Wi-Fi hotspot. It also has 3 Ethernet ports, to which I connected the Beelink nodes. That's the device you see at the very top. + +The Ethernet cables go downward through the cable boxes to the Beelink nodes. In addition to the Beelink f3s nodes, I connected the TP-Link to the UPS as well (not discussed further in this blog post, but the positive side effect is that my Wi-Fi will still work during a power loss for some time—and during a power cut, the Beelink nodes will still be able to communicate with each other). + +On the very left (the black box) is the UPS, with four power outlets. Three go to the Beelink nodes, and one goes to the TP-Link. A USB output is also connected to the first Beelink node, `f0`. + +On the very right (halfway hidden behind the TV) are the 3 Beelink nodes stacked on top of each other. The only downside (or upside?) is that my 14-month-old daughter is now chaos-testing the Beelink nodes, as the red power buttons (now reachable for her) are very attractive for her to press when passing by randomly. :-) Luckily, that will only cause graceful system shutdowns! + +## The UPS hardware + +I wanted a UPS that I could connect to via FreeBSD, and that would provide enough backup power to operate the cluster for a couple of minutes (it turned out to be around an hour, but this time will likely be shortened after future hardware upgrades, like additional drives and a backup enclosure) and to automatically initiate the shutdown of all the f3s nodes. + +I decided on the APC Back-UPS BX750MI model because: + +* Zero noise level when there is no power cut (some light noise when the battery is in operation during a power cut). +* Cost: It is relatively affordable (not costing thousands). +* USB connectivity: Can be connected via USB to one of the FreeBSD hosts to read the UPS status. +* A power output of 750VA (or 410 watts), suitable for an hour of runtime for my f3s nodes (plus the Wi-Fi router). +* Multiple power outlets: Can connect all 3 f3s nodes directly. +* User-replaceable batteries: I can replace the batteries myself after two years or more (depending on usage). +* Its compact design. Overall, I like how it looks. + +[![The APC Back-UPS BX750MI in operation.](./f3s-kubernetes-with-freebsd-part-3/apc-back-ups.jpg "The APC Back-UPS BX750MI in operation.")](./f3s-kubernetes-with-freebsd-part-3/apc-back-ups.jpg) + +## Configuring FreeBSD to Work with the UPS + +### USB Device Detection + +Once plugged in via USB on FreeBSD, I could see the following in the kernel messages: + +```sh +paul@f0: ~ % doas dmesg | grep UPS +ugen0.2: at usbus0 +``` + +### `apcupsd` Installation + +To make use of the USB connection, the `apcupsd` package had to be installed: + +```sh +paul@f0: ~ % doas install apcupsd +``` + +I have made the following modifications to the configuration file so that the UPS can be used via the USB interface: + +```sh +paul@f0:/usr/local/etc/apcupsd % diff -u apcupsd.conf.sample apcupsd.conf +--- apcupsd.conf.sample 2024-11-01 16:40:42.000000000 +0200 ++++ apcupsd.conf 2024-12-03 10:58:24.009501000 +0200 +@@ -31,7 +31,7 @@ + # 940-1524C, 940-0024G, 940-0095A, 940-0095B, + # 940-0095C, 940-0625A, M-04-02-2000 + # +-UPSCABLE smart ++UPSCABLE usb + + # To get apcupsd to work, in addition to defining the cable + # above, you must also define a UPSTYPE, which corresponds to +@@ -88,8 +88,10 @@ + # that apcupsd binds to that particular unit + # (helpful if you have more than one USB UPS). + # +-UPSTYPE apcsmart +-DEVICE /dev/usv ++UPSTYPE usb ++DEVICE + + # POLLTIME + # Interval (in seconds) at which apcupsd polls the UPS for status. This +``` + +I left the remaining settings as the default ones; for example, the following are of main interest: + +``` +# If during a power failure, the remaining battery percentage +# (as reported by the UPS) is below or equal to BATTERYLEVEL, +# apcupsd will initiate a system shutdown. +BATTERYLEVEL 5 + +# If during a power failure, the remaining runtime in minutes +# (as calculated internally by the UPS) is below or equal to MINUTES, +# apcupsd, will initiate a system shutdown. +MINUTES 3 +``` + +I then enabled and started the daemon: + +```sh +paul@f0:/usr/local/etc/apcupsd % doas sysrc apcupsd_enable=YES +apcupsd_enable: -> YES +paul@f0:/usr/local/etc/apcupsd % doas service apcupsd start +Starting apcupsd. +``` + +### UPS Connectivity Test + +And voila, I could now access the UPS information via the `apcaccess` command; how convenient :-) (I also read through the manual page, which provides a good understanding of what else can be done with it!). + +```sh +paul@f0:~ % apcaccess +APC : 001,035,0857 +DATE : 2025-01-26 14:43:27 +0200 +HOSTNAME : f0.lan.buetow.org +VERSION : 3.14.14 (31 May 2016) freebsd +UPSNAME : f0.lan.buetow.org +CABLE : USB Cable +DRIVER : USB UPS Driver +UPSMODE : Stand Alone +STARTTIME: 2025-01-26 14:43:25 +0200 +MODEL : Back-UPS BX750MI +STATUS : ONLINE +LINEV : 230.0 Volts +LOADPCT : 4.0 Percent +BCHARGE : 100.0 Percent +TIMELEFT : 65.3 Minutes +MBATTCHG : 5 Percent +MINTIMEL : 3 Minutes +MAXTIME : 0 Seconds +SENSE : Medium +LOTRANS : 145.0 Volts +HITRANS : 295.0 Volts +ALARMDEL : No alarm +BATTV : 13.6 Volts +LASTXFER : Automatic or explicit self test +NUMXFERS : 0 +TONBATT : 0 Seconds +CUMONBATT: 0 Seconds +XOFFBATT : N/A +SELFTEST : NG +STATFLAG : 0x05000008 +SERIALNO : 9B2414A03599 +BATTDATE : 2001-01-01 +NOMINV : 230 Volts +NOMBATTV : 12.0 Volts +NOMPOWER : 410 Watts +END APC : 2025-01-26 14:44:06 +0200 +``` + +## APC Info on Partner Nodes: + +So far, so good. Host `f0` would shut down itself when short on power. But what about the `f1` and `f2` nodes? They aren't connected directly to the UPS and, therefore, wouldn't know that their power is about to be cut off. For this, `apcupsd` running on the `f1` and `f2` nodes can be configured to retrieve UPS information via the network from the `apcupsd` server running on the `f0` node, which is connected directly to the APC via USB. + +Of course, this won't work when `f0` is down. In this case, no operational node would be connected to the UPS via USB; therefore, the current power status would not be known. However, I consider this a rare circumstance. Furthermore, in case of an `f0` system crash, sudden power outages on the two other nodes would occur at different times, making real data loss (the main concern here) effectively impossible. + +### Installation on partners + +To do this, I installed `apcupsd` via `doas pkg install apcupsd` on `f1` and `f2`, and then I could connect to it this way: + +```sh +paul@f1:~ % apcaccess -h f0.lan.buetow.org | grep Percent +LOADPCT : 12.0 Percent +BCHARGE : 94.0 Percent +MBATTCHG : 5 Percent +``` + +But I want the daemon to be configured and enabled in such a way that it connects to the master UPS node (the one with the UPS connected via USB) so that it can also initiate a system shutdown when the UPS battery reaches low levels. For that, `apcupsd` itself needs to be aware of the UPS status. + +On `f1` and `f2`, I changed the configuration to use `f0` (where `apcupsd` is listening) as a remote device. I also changed the `MINUTES` setting from 3 to 6 and the `BATTERYLEVEL` setting from 5 to 10 to ensure that the `f1` and `f2` nodes could still connect to the `f0` node for UPS information before `f0` decides to shut down itself. So `f1` and `f2` must shut down earlier than `f0`: + +```sh +paul@f2:/usr/local/etc/apcupsd % diff -u apcupsd.conf.sample apcupsd.conf +--- apcupsd.conf.sample 2024-11-01 16:40:42.000000000 +0200 ++++ apcupsd.conf 2025-01-26 15:52:45.108469000 +0200 +@@ -31,7 +31,7 @@ + # 940-1524C, 940-0024G, 940-0095A, 940-0095B, + # 940-0095C, 940-0625A, M-04-02-2000 + # +-UPSCABLE smart ++UPSCABLE ether + + # To get apcupsd to work, in addition to defining the cable + # above, you must also define a UPSTYPE, which corresponds to +@@ -52,7 +52,6 @@ + # Network Information Server. This is used if the + # UPS powering your computer is connected to a + # different computer for monitoring. +-# + # snmp hostname:port:vendor:community + # SNMP network link to an SNMP-enabled UPS device. + # Hostname is the ip address or hostname of the UPS +@@ -88,8 +87,8 @@ + # that apcupsd binds to that particular unit + # (helpful if you have more than one USB UPS). + # +-UPSTYPE apcsmart +-DEVICE /dev/usv ++UPSTYPE net ++DEVICE f0.lan.buetow.org:3551 + + # POLLTIME + # Interval (in seconds) at which apcupsd polls the UPS for status. This +@@ -147,12 +146,12 @@ + # If during a power failure, the remaining battery percentage + # (as reported by the UPS) is below or equal to BATTERYLEVEL, + # apcupsd will initiate a system shutdown. +-BATTERYLEVEL 5 ++BATTERYLEVEL 10 + + # If during a power failure, the remaining runtime in minutes + # (as calculated internally by the UPS) is below or equal to MINUTES, + # apcupsd, will initiate a system shutdown. +-MINUTES 3 ++MINUTES 6 + + # If during a power failure, the UPS has run on batteries for TIMEOUT + # many seconds or longer, apcupsd will initiate a system shutdown. + +``` +So I also ran the following commands on `f1` and `f2`: + +```sh +paul@f1:/usr/local/etc/apcupsd % doas sysrc apcupsd_enable=YES +apcupsd_enable: -> YES +paul@f1:/usr/local/etc/apcupsd % doas service apcupsd start +Starting apcupsd. +``` + +And then I was able to connect to localhost via the `apcaccess` command: + +```sh +paul@f1:~ % doas apcaccess | grep Percent +LOADPCT : 5.0 Percent +BCHARGE : 95.0 Percent +MBATTCHG : 5 Percent +``` + +## Power outage simulation + +### Pulling the plug + +I simulated a power outage by removing the power input from the APC. Immediately, the following message appeared on all the nodes: + +```` +Broadcast Message from root@f0.lan.buetow.org + (no tty) at 15:03 EET... + +Power failure. Running on UPS batteries. +``` + +I ran the following command to confirm the available battery time: + +```sh +paul@f0:/usr/local/etc/apcupsd % apcaccess -p TIMELEFT +63.9 Minutes +``` + +And after almost 60 minutes (`f1` and `f2` a bit earlier, `f0` a bit later due to the different `BATTERYLEVEL` and `MINUTES` settings outlined earlier), the following broadcast was sent out: + +``` +Broadcast Message from root@f0.lan.buetow.org + (no tty) at 15:08 EET... + + *** FINAL System shutdown message from paul@f1.lan.buetow.org *** + +System going down IMMEDIATELY + +apcupsd initiated shutdown +``` + +And all the nodes shut down safely before the UPS ran out of battery! + +### Restoring power + +After restoring power, I checked the logs in `/var/log/daemon.log` and found the following on all 3 nodes: + +``` +Jan 26 17:36:24 f2 apcupsd[2159]: Power failure. +Jan 26 17:36:30 f2 apcupsd[2159]: Running on UPS batteries. +Jan 26 17:36:30 f2 apcupsd[2159]: Battery charge below low limit. +Jan 26 17:36:30 f2 apcupsd[2159]: Initiating system shutdown! +Jan 26 17:36:30 f2 apcupsd[2159]: User logins prohibited +Jan 26 17:36:32 f2 apcupsd[2159]: apcupsd exiting, signal 15 +Jan 26 17:36:32 f2 apcupsd[2159]: apcupsd shutdown succeeded +``` + +All good :-) + +Other BSD related posts are: + +[2016-04-09 Jails and ZFS with Puppet on FreeBSD](./2016-04-09-jails-and-zfs-on-freebsd-with-puppet.md) +[2022-07-30 Let's Encrypt with OpenBSD and Rex](./2022-07-30-lets-encrypt-with-openbsd-and-rex.md) +[2022-10-30 Installing DTail on OpenBSD](./2022-10-30-installing-dtail-on-openbsd.md) +[2024-01-13 One reason why I love OpenBSD](./2024-01-13-one-reason-why-i-love-openbsd.md) +[2024-04-01 KISS high-availability with OpenBSD](./2024-04-01-KISS-high-availability-with-OpenBSD.md) +[2024-11-17 f3s: Kubernetes with FreeBSD - Part 1: Setting the stage](./2024-11-17-f3s-kubernetes-with-freebsd-part-1.md) +[2024-12-03 f3s: Kubernetes with FreeBSD - Part 2: Hardware and base installation](./2024-12-03-f3s-kubernetes-with-freebsd-part-2.md) + +E-Mail your comments to `paul@nospam.buetow.org` :-) + +[Back to the main site](../) diff --git a/gemfeed/f3s-kubernetes-with-freebsd-part-3/apc-back-ups.jpg b/gemfeed/f3s-kubernetes-with-freebsd-part-3/apc-back-ups.jpg new file mode 100644 index 00000000..15b1ca78 Binary files /dev/null and b/gemfeed/f3s-kubernetes-with-freebsd-part-3/apc-back-ups.jpg differ diff --git a/gemfeed/f3s-kubernetes-with-freebsd-part-3/f3s-changes.jpg b/gemfeed/f3s-kubernetes-with-freebsd-part-3/f3s-changes.jpg new file mode 100644 index 00000000..5752f2fc Binary files /dev/null and b/gemfeed/f3s-kubernetes-with-freebsd-part-3/f3s-changes.jpg differ -- cgit v1.2.3 From 1798a57ca2e813b5523107576b57ee1d7f00699e Mon Sep 17 00:00:00 2001 From: Paul Buetow Date: Wed, 29 Jan 2025 08:03:14 +0200 Subject: Update content for md --- ...024-11-17-f3s-kubernetes-with-freebsd-part-1.md | 10 +- .../DRAFT-f3s-kubernetes-with-freebsd-part-3.md | 6 +- gemfeed/f3s-kubernetes-with-freebsd-part-4.md | 261 +++++++++++++++++++++ 3 files changed, 272 insertions(+), 5 deletions(-) create mode 100644 gemfeed/f3s-kubernetes-with-freebsd-part-4.md (limited to 'gemfeed') diff --git a/gemfeed/2024-11-17-f3s-kubernetes-with-freebsd-part-1.md b/gemfeed/2024-11-17-f3s-kubernetes-with-freebsd-part-1.md index 568813dd..25cdc7c4 100644 --- a/gemfeed/2024-11-17-f3s-kubernetes-with-freebsd-part-1.md +++ b/gemfeed/2024-11-17-f3s-kubernetes-with-freebsd-part-1.md @@ -10,6 +10,7 @@ These are all the posts so far: [2024-11-17 f3s: Kubernetes with FreeBSD - Part 1: Setting the stage (You are currently reading this)](./2024-11-17-f3s-kubernetes-with-freebsd-part-1.md) [2024-12-03 f3s: Kubernetes with FreeBSD - Part 2: Hardware and base installation](./2024-12-03-f3s-kubernetes-with-freebsd-part-2.md) +[f3s-kubernetes-with f3s: Kubernetes with FreeBSD - Rocky Linux Bhyve VMs - Part 4](./f3s-kubernetes-with-freebsd-part-4.md) [![f3s logo](./f3s-kubernetes-with-freebsd-part-1/f3slogo.png "f3s logo")](./f3s-kubernetes-with-freebsd-part-1/f3slogo.png) @@ -38,7 +39,7 @@ Let's begin... My previous setup was great for learning Terraform and AWS, but it is too expensive. Costs are under control there, but only because I am shutting down all containers after use (so they are offline ninety percent of the time and still cost around $20 monthly). With the new setup, I could run all containers 24/7 at home, which would still be cheaper in terms of electricity consumption. I have a 50 MBit/s uplink (I could have more if I wanted, but it is plenty for my use case already). -[From `babylon5.buetow.org` to `.cloud`](https://foo.zone/gemfeed/2024-02-04-from-babylon5.buetow.org-to-.cloud.html) +[From `babylon5.buetow.org` to `.cloud`](./2024-02-04-from-babylon5.buetow.org-to-.cloud.html) Migrating off all my containers from AWS ECS means I need a reliable and scalable environment to host my workloads. I wanted something: @@ -96,8 +97,8 @@ All of this (every Linux VM to every OpenBSD box) will be connected via WireGuar So, when I want to access a service running in k3s, I will hit an external DNS endpoint (with the authoritative DNS servers being the OpenBSD boxes). The DNS will resolve to the master OpenBSD VM (see my KISS highly-available with OpenBSD blog post), and from there, the `relayd` process (with a Let's Encrypt certificate—see my Let's Encrypt with OpenBSD and Rex blog post) will accept the TCP connection and forward it through the WireGuard tunnel to a reachable node port of one of the k3s nodes, thus serving the traffic. -[KISS high-availability with OpenBSD](https://foo.zone/gemfeed/2024-04-01-KISS-high-availability-with-OpenBSD.html) -[Let's Encrypt with OpenBSD and Rex](https://foo.zone/gemfeed/2022-07-30-lets-encrypt-with-openbsd-and-rex.html) +[KISS high-availability with OpenBSD](./2024-04-01-KISS-high-availability-with-OpenBSD.html) +[Let's Encrypt with OpenBSD and Rex](./2022-07-30-lets-encrypt-with-openbsd-and-rex.html) The OpenBSD setup described here already exists and is ready to use. The only thing that does not yet exist is the configuration of `relayd` to forward requests to k3s through the WireGuard tunnel(s). @@ -137,7 +138,7 @@ For visualization, Grafana will be deployed alongside Prometheus. Grafana lets m Alerts generated by Prometheus are forwarded to Alertmanager, which I will configure to work with Gogios, a lightweight monitoring and alerting system I wrote myself. Gogios runs on one of my OpenBSD VMs. At regular intervals, Gogios scrapes the alerts generated in the k3s cluster and notifies me via Email. -[KISS server monitoring with Gogios](https://foo.zone/gemfeed/2023-06-01-kiss-server-monitoring-with-gogios.html) +[KISS server monitoring with Gogios](./2023-06-01-kiss-server-monitoring-with-gogios.html) Ironically, I implemented Gogios to avoid using more complex alerting systems like Prometheus, but here we go—it integrates well now. @@ -165,6 +166,7 @@ Other *BSD-related posts: [2024-04-01 KISS high-availability with OpenBSD](./2024-04-01-KISS-high-availability-with-OpenBSD.md) [2024-11-17 f3s: Kubernetes with FreeBSD - Part 1: Setting the stage (You are currently reading this)](./2024-11-17-f3s-kubernetes-with-freebsd-part-1.md) [2024-12-03 f3s: Kubernetes with FreeBSD - Part 2: Hardware and base installation](./2024-12-03-f3s-kubernetes-with-freebsd-part-2.md) +[f3s-kubernetes-with f3s: Kubernetes with FreeBSD - Rocky Linux Bhyve VMs - Part 4](./f3s-kubernetes-with-freebsd-part-4.md) E-Mail your comments to `paul@nospam.buetow.org` :-) diff --git a/gemfeed/DRAFT-f3s-kubernetes-with-freebsd-part-3.md b/gemfeed/DRAFT-f3s-kubernetes-with-freebsd-part-3.md index 55595bcb..5e84286a 100644 --- a/gemfeed/DRAFT-f3s-kubernetes-with-freebsd-part-3.md +++ b/gemfeed/DRAFT-f3s-kubernetes-with-freebsd-part-3.md @@ -4,6 +4,7 @@ This is the third blog post about my f3s series for my self-hosting demands in m [2024-11-17 f3s: Kubernetes with FreeBSD - Part 1: Setting the stage](./2024-11-17-f3s-kubernetes-with-freebsd-part-1.md) [2024-12-03 f3s: Kubernetes with FreeBSD - Part 2: Hardware and base installation](./2024-12-03-f3s-kubernetes-with-freebsd-part-2.md) +[f3s-kubernetes-with f3s: Kubernetes with FreeBSD - Rocky Linux Bhyve VMs - Part 4](./f3s-kubernetes-with-freebsd-part-4.md) [![f3s logo](./f3s-kubernetes-with-freebsd-part-1/f3slogo.png "f3s logo")](./f3s-kubernetes-with-freebsd-part-1/f3slogo.png) @@ -212,6 +213,8 @@ So far, so good. Host `f0` would shut down itself when short on power. But what Of course, this won't work when `f0` is down. In this case, no operational node would be connected to the UPS via USB; therefore, the current power status would not be known. However, I consider this a rare circumstance. Furthermore, in case of an `f0` system crash, sudden power outages on the two other nodes would occur at different times, making real data loss (the main concern here) effectively impossible. +And if `f0` is down and `f1` and `f2` receive new data and crash midway, it's likely that a client (e.g., an Android app or another laptop) still has the data stored on it, making data loss recoverable. I'd receive an alert if any of the nodes go down (more on monitoring later in this blog series). + ### Installation on partners To do this, I installed `apcupsd` via `doas pkg install apcupsd` on `f1` and `f2`, and then I could connect to it this way: @@ -320,7 +323,7 @@ And after almost 60 minutes (`f1` and `f2` a bit earlier, `f0` a bit later due t Broadcast Message from root@f0.lan.buetow.org (no tty) at 15:08 EET... - *** FINAL System shutdown message from paul@f1.lan.buetow.org *** + *** FINAL System shutdown message from root@f0.lan.buetow.org *** System going down IMMEDIATELY @@ -354,6 +357,7 @@ Other BSD related posts are: [2024-04-01 KISS high-availability with OpenBSD](./2024-04-01-KISS-high-availability-with-OpenBSD.md) [2024-11-17 f3s: Kubernetes with FreeBSD - Part 1: Setting the stage](./2024-11-17-f3s-kubernetes-with-freebsd-part-1.md) [2024-12-03 f3s: Kubernetes with FreeBSD - Part 2: Hardware and base installation](./2024-12-03-f3s-kubernetes-with-freebsd-part-2.md) +[f3s-kubernetes-with f3s: Kubernetes with FreeBSD - Rocky Linux Bhyve VMs - Part 4](./f3s-kubernetes-with-freebsd-part-4.md) E-Mail your comments to `paul@nospam.buetow.org` :-) diff --git a/gemfeed/f3s-kubernetes-with-freebsd-part-4.md b/gemfeed/f3s-kubernetes-with-freebsd-part-4.md new file mode 100644 index 00000000..a5a34769 --- /dev/null +++ b/gemfeed/f3s-kubernetes-with-freebsd-part-4.md @@ -0,0 +1,261 @@ +# f3s: Kubernetes with FreeBSD - Rocky Linux Bhyve VMs - Part 4 + +This is the thourth blog post about my f3s series for my self-hosting demands in my home lab. f3s? The "f" stands for FreeBSD, and the "3s" stands for k3s, the Kubernetes distribution we will use on FreeBSD-based physical machines. + +[2024-11-17 f3s: Kubernetes with FreeBSD - Part 1: Setting the stage](./2024-11-17-f3s-kubernetes-with-freebsd-part-1.md) +[2024-12-03 f3s: Kubernetes with FreeBSD - Part 2: Hardware and base installation](./2024-12-03-f3s-kubernetes-with-freebsd-part-2.md) + +[![f3s logo](./f3s-kubernetes-with-frhyveeebsd-part-1/f3slogo.png "f3s logo")](./f3s-kubernetes-with-frhyveeebsd-part-1/f3slogo.png) + +## Table of Contents + +* [⇢ f3s: Kubernetes with FreeBSD - Rocky Linux Bhyve VMs - Part 4](#f3s-kubernetes-with-freebsd---rocky-linux-bhyve-vms---part-4) +* [⇢ ⇢ Introduction](#introduction) +* [⇢ ⇢ Basic Bhyve setup](#basic-bhyve-setup) +* [⇢ ⇢ Rocky Linux VMs](#rocky-linux-vms) +* [⇢ ⇢ ⇢ ISO download](#iso-download) +* [⇢ ⇢ ⇢ VM configuration](#vm-configuration) +* [⇢ ⇢ ⇢ VM installation](#vm-installation) +* [⇢ ⇢ ⇢ Increase of the disk image](#increase-of-the-disk-image) +* [⇢ ⇢ ⇢ Connect to VPN](#connect-to-vpn) +* [⇢ ⇢ After install](#after-install) +* [⇢ ⇢ ⇢ VM auto-start after host reboot](#vm-auto-start-after-host-reboot) +* [⇢ ⇢ ⇢ Static IP configuration](#static-ip-configuration) +* [⇢ ⇢ ⇢ Permitting root login](#permitting-root-login) +* [⇢ ⇢ ⇢ Install latest updates](#install-latest-updates) + +## Introduction + +In this blog post, we are going to install the Bhyve hypervisor. + +The FreeBSD Bhyve hypervisor is a lightweight, modern hypervisor that enables virtualization on FreeBSD systems. Bhyve's strengths include its minimal overhead, which allows it to achieve near-native performance for virtual machines. It is designed to be efficient and lightweight, leveraging the capabilities of the FreeBSD operating system for performance and network management. + +Bhyve supports running a variety of guest operating systems, including FreeBSD, Linux, and Windows, on hardware platforms that support hardware virtualization extensions (such as Intel VT-x or AMD-V). In our case, we are going to virtualize Rocky Linux, which later on in this series will be used to run k3s. + +## Basic Bhyve setup + +For the management of the Bhyve VMs, we are using `vm-bhyve`, a tool not part of the FreeBSD operating system but available as a ready-to-use package. It eases VM management and reduces a lot of the overhead. We also install the required package to make Bhyve work with the UEFI firmware. + +[https://github.com/churchers/vm-bhyve](https://github.com/churchers/vm-bhyve) + +The following commands are executed on all three hosts `f0`, `f1`, and `f2`, where `re0` is the name of the Ethernet interface (which may need to be adjusted if your hardware is different): + +```sh +paul@f0:~ % doas pkg install vm-bhyve bhyve-firmware +paul@f0:~ % doas sysrc vm_enable=YES +vm_enable: -> YES +paul@f0:~ % doas sysrc vm_dir=zfs:zroot/bhyve +vm_dir: -> zfs:zroot/bhyve +paul@f0:~ % doas zfs create zroot/bhyve +paul@f0:~ % doas vm init +paul@f0:~ % doas vm switch create public +paul@f0:~ % doas vm switch add public re0 +``` + +Bhyve stores all it's data in the `/bhyve` of the `zroot` ZFS pool: + +```sh +paul@f0:~ % zfs list | grep bhyve +zroot/bhyve 1.74M 453G 1.74M /zroot/bhyve +``` + +For convenience, we also create this symlink: + +```sh +paul@f0:~ % doas ln -s /zroot/bhyve/ /bhyve + +``` + +Now, Bhyve is ready to rumble, but no VMs are there yet: + +```sh +paul@f0:~ % doas vm list +NAME DATASTORE LOADER CPU MEMORY VNC AUTO STATE +``` + +## Rocky Linux VMs + +### ISO download + +We're going to install the Rocky Linux from the latest minimal iso: + +```sh +paul@f0:~ % doas vm iso \ + https://download.rockylinux.org/pub/rocky/9/isos/x86_64/Rocky-9.5-x86_64-minimal.iso +/zroot/bhyve/.iso/Rocky-9.5-x86_64-minimal.iso 1808 MB 4780 kBps 06m28s +paul@f0:/bhyve % doas vm create rocky +``` +### VM configuration + +The default configuration looks like this now: + +```sh +paul@f0:/bhyve/rocky % cat rocky.conf +loader="bhyveload" +cpu=1 +memory=256M +network0_type="virtio-net" +network0_switch="public" +disk0_type="virtio-blk" +disk0_name="disk0.img" +uuid="1c4655ac-c828-11ef-a920-e8ff1ed71ca0" +network0_mac="58:9c:fc:0d:13:3f" +``` + +Whereas the `uuid` and the `network0_mac` differ on each of the 3 hosts. + +but in order to make Rocky Linux boot it (plus some other adjustments, e.g. as I am intending to run the majority of the workload in the k3s cluster running on those linux VMs, I give them beefy specs like 4 CPU cores and 14GB RAM), I run `doas vm configure rocky` and modified it to: + +``` +guest="linux" +loader="uefi" +uefi_vars="yes" +cpu=4 +memory=14G +network0_type="virtio-net" +network0_switch="public" +disk0_type="virtio-blk" +disk0_name="disk0.img" +graphics="yes" +graphics_vga=io +uuid="1c45400b-c828-11ef-8871-e8ff1ed71cac" +network0_mac="58:9c:fc:0d:13:3f" +``` + +### VM installation + +To start the installer from the downloaded ISO, I run: + +```sh +paul@f0:~ % doas vm install rocky Rocky-9.5-x86_64-minimal.iso +Starting rocky + * found guest in /zroot/bhyve/rocky + * booting... + +paul@f0:/bhyve/rocky % doas vm list +NAME DATASTORE LOADER CPU MEMORY VNC AUTO STATE +rocky default uefi 4 14G 0.0.0.0:5900 No Locked (f0.lan.buetow.org) + +paul@f0:/bhyve/rocky % doas sockstat -4 | grep 5900 +root bhyve 6079 8 tcp4 *:5900 *:* +``` + +Port 5900 now also opened for VNC connections, so I connected to it with a VNC client and run through the installation dialogs. I'm sure this could be done unattended or more automated, there are only 3 VMs to install, and the automation doesn't seem worth it as we are doing it only once in a year or less often. + +### Increase of the disk image + +By default the VMs disk image is only 20G, which is a bit small for my purposes, so I stopped the VMs again and run `truncate` on the image file to enlarge them to 100G, and re-started the installation: + +```sh +paul@f0:/bhyve/rocky % doas vm stop rocky +paul@f0:/bhyve/rocky % doas truncate -s 100G disk0.img +paul@f0:/bhyve/rocky % doas vm install rocky Rocky-9.5-x86_64-minimal.iso +``` + +### Connect to VPN + +For the installation, I opened the VPN client on my Fedora laptop (GNOME comes with a simple VPN client) and ran through the base installation for each of the VMs manually. Again, I am sure this could have been automated a bit more, but there were just 3 VMs, and it wasn't worth the effort. The three VNC addresses of the VMs were: `vnc://f0:5900`, `vnc://f1:5900`, and `vnc://f0:5900`. + +I mostly selected the default settings (auto partitioning on the 100GB drive and a root user password). After the installation, the VMs were rebooted. + +## After install + +I performed the following steps for all 3 VMs. In the following, the examples are all executed on `f0` (bzw the VM `r0` running on `f0`): + +### VM auto-start after host reboot + +To automatically start the VM on the servers I added the following to the `rc.conf` on the FreeBSD hosts: + +```sh + +paul@f0:/bhyve/rocky % cat <>/etc/hosts +192.168.1.120 r0 r0.lan r0.lan.buetow.org +192.168.1.121 r1 r1.lan r1.lan.buetow.org +192.168.1.122 r2 r2.lan r2.lan.buetow.org +END +```` + +Whereas: + +* `192.168.1.120` is the IP of the VM itself (here: `r0.lan.buetow.org`) +* `192.168.1.1` is the address of my home router, which also does DNS. + +### Permitting root login + +As these VMs arent directly reachable via SSH from the internet, I enabled `root` login by adding a line with `PermitRootLogin yes` to `/etc/sshd/sshd_config`. + +Once done, I rebooted the VM by running `reboot` inside of the vm to test whether everything was configured and persisted correctly. + +After reboot, I copied my public key from my Laptop to the 3 VMs: + +```sh +% for i in 0 1 2; do ssh-copy-id root@r$i.lan.buetow.org; done +``` + +And then I edited the `/etc/ssh/sshd_config` file again on all 3 VMs and configured `PasswordAuthentication no`, to only allow SSH key authentication from now on. + +### Install latest updates + +```sh +[root@r0 ~] % dnf update +[root@r0 ~] % dreboot +``` + +CPU STRESS TESTER VM VS NOT VM + +Other *BSD-related posts: + +[2016-04-09 Jails and ZFS with Puppet on FreeBSD](./2016-04-09-jails-and-zfs-on-freebsd-with-puppet.md) +[2022-07-30 Let's Encrypt with OpenBSD and Rex](./2022-07-30-lets-encrypt-with-openbsd-and-rex.md) +[2022-10-30 Installing DTail on OpenBSD](./2022-10-30-installing-dtail-on-openbsd.md) +[2024-01-13 One reason why I love OpenBSD](./2024-01-13-one-reason-why-i-love-openbsd.md) +[2024-04-01 KISS high-availability with OpenBSD](./2024-04-01-KISS-high-availability-with-OpenBSD.md) +[2024-11-17 f3s: Kubernetes with FreeBSD - Part 1: Setting the stage](./2024-11-17-f3s-kubernetes-with-freebsd-part-1.md) +[2024-12-03 f3s: Kubernetes with FreeBSD - Part 2: Hardware and base installation](./2024-12-03-f3s-kubernetes-with-freebsd-part-2.md) + +E-Mail your comments to `paul@nospam.buetow.org` :-) + +[Back to the main site](../) -- cgit v1.2.3 From 1966f87b266f093fb5a46a6f09e0b63041dc88a1 Mon Sep 17 00:00:00 2001 From: Paul Buetow Date: Wed, 29 Jan 2025 08:05:23 +0200 Subject: Update content for md --- gemfeed/2016-04-09-jails-and-zfs-on-freebsd-with-puppet.md | 1 + gemfeed/2022-07-30-lets-encrypt-with-openbsd-and-rex.md | 1 + gemfeed/2024-01-13-one-reason-why-i-love-openbsd.md | 1 + gemfeed/2024-04-01-KISS-high-availability-with-OpenBSD.md | 1 + gemfeed/2024-11-17-f3s-kubernetes-with-freebsd-part-1.md | 8 ++++---- gemfeed/2024-12-03-f3s-kubernetes-with-freebsd-part-2.md | 2 ++ gemfeed/f3s-kubernetes-with-freebsd-part-4.md | 2 ++ 7 files changed, 12 insertions(+), 4 deletions(-) (limited to 'gemfeed') diff --git a/gemfeed/2016-04-09-jails-and-zfs-on-freebsd-with-puppet.md b/gemfeed/2016-04-09-jails-and-zfs-on-freebsd-with-puppet.md index 80ee2f80..e013c3c9 100644 --- a/gemfeed/2016-04-09-jails-and-zfs-on-freebsd-with-puppet.md +++ b/gemfeed/2016-04-09-jails-and-zfs-on-freebsd-with-puppet.md @@ -404,5 +404,6 @@ Other *BSD related posts are: [2024-04-01 KISS high-availability with OpenBSD](./2024-04-01-KISS-high-availability-with-OpenBSD.md) [2024-11-17 f3s: Kubernetes with FreeBSD - Part 1: Setting the stage](./2024-11-17-f3s-kubernetes-with-freebsd-part-1.md) [2024-12-03 f3s: Kubernetes with FreeBSD - Part 2: Hardware and base installation](./2024-12-03-f3s-kubernetes-with-freebsd-part-2.md) +[f3s-kubernetes-with f3s: Kubernetes with FreeBSD - Rocky Linux Bhyve VMs - Part 4](./f3s-kubernetes-with-freebsd-part-4.md) [Back to the main site](../) diff --git a/gemfeed/2022-07-30-lets-encrypt-with-openbsd-and-rex.md b/gemfeed/2022-07-30-lets-encrypt-with-openbsd-and-rex.md index 6cd856e3..17952046 100644 --- a/gemfeed/2022-07-30-lets-encrypt-with-openbsd-and-rex.md +++ b/gemfeed/2022-07-30-lets-encrypt-with-openbsd-and-rex.md @@ -683,5 +683,6 @@ Other *BSD related posts are: [2024-04-01 KISS high-availability with OpenBSD](./2024-04-01-KISS-high-availability-with-OpenBSD.md) [2024-11-17 f3s: Kubernetes with FreeBSD - Part 1: Setting the stage](./2024-11-17-f3s-kubernetes-with-freebsd-part-1.md) [2024-12-03 f3s: Kubernetes with FreeBSD - Part 2: Hardware and base installation](./2024-12-03-f3s-kubernetes-with-freebsd-part-2.md) +[f3s-kubernetes-with f3s: Kubernetes with FreeBSD - Rocky Linux Bhyve VMs - Part 4](./f3s-kubernetes-with-freebsd-part-4.md) [Back to the main site](../) diff --git a/gemfeed/2024-01-13-one-reason-why-i-love-openbsd.md b/gemfeed/2024-01-13-one-reason-why-i-love-openbsd.md index 56dc6c7f..0c339e5d 100644 --- a/gemfeed/2024-01-13-one-reason-why-i-love-openbsd.md +++ b/gemfeed/2024-01-13-one-reason-why-i-love-openbsd.md @@ -58,5 +58,6 @@ Other *BSD related posts are: [2024-04-01 KISS high-availability with OpenBSD](./2024-04-01-KISS-high-availability-with-OpenBSD.md) [2024-11-17 f3s: Kubernetes with FreeBSD - Part 1: Setting the stage](./2024-11-17-f3s-kubernetes-with-freebsd-part-1.md) [2024-12-03 f3s: Kubernetes with FreeBSD - Part 2: Hardware and base installation](./2024-12-03-f3s-kubernetes-with-freebsd-part-2.md) +[f3s-kubernetes-with f3s: Kubernetes with FreeBSD - Rocky Linux Bhyve VMs - Part 4](./f3s-kubernetes-with-freebsd-part-4.md) [Back to the main site](../) diff --git a/gemfeed/2024-04-01-KISS-high-availability-with-OpenBSD.md b/gemfeed/2024-04-01-KISS-high-availability-with-OpenBSD.md index 50de8943..7d56e460 100644 --- a/gemfeed/2024-04-01-KISS-high-availability-with-OpenBSD.md +++ b/gemfeed/2024-04-01-KISS-high-availability-with-OpenBSD.md @@ -309,5 +309,6 @@ Other *BSD and KISS related posts are: [2024-04-01 KISS high-availability with OpenBSD (You are currently reading this)](./2024-04-01-KISS-high-availability-with-OpenBSD.md) [2024-11-17 f3s: Kubernetes with FreeBSD - Part 1: Setting the stage](./2024-11-17-f3s-kubernetes-with-freebsd-part-1.md) [2024-12-03 f3s: Kubernetes with FreeBSD - Part 2: Hardware and base installation](./2024-12-03-f3s-kubernetes-with-freebsd-part-2.md) +[f3s-kubernetes-with f3s: Kubernetes with FreeBSD - Rocky Linux Bhyve VMs - Part 4](./f3s-kubernetes-with-freebsd-part-4.md) [Back to the main site](../) diff --git a/gemfeed/2024-11-17-f3s-kubernetes-with-freebsd-part-1.md b/gemfeed/2024-11-17-f3s-kubernetes-with-freebsd-part-1.md index 25cdc7c4..1314bfcd 100644 --- a/gemfeed/2024-11-17-f3s-kubernetes-with-freebsd-part-1.md +++ b/gemfeed/2024-11-17-f3s-kubernetes-with-freebsd-part-1.md @@ -39,7 +39,7 @@ Let's begin... My previous setup was great for learning Terraform and AWS, but it is too expensive. Costs are under control there, but only because I am shutting down all containers after use (so they are offline ninety percent of the time and still cost around $20 monthly). With the new setup, I could run all containers 24/7 at home, which would still be cheaper in terms of electricity consumption. I have a 50 MBit/s uplink (I could have more if I wanted, but it is plenty for my use case already). -[From `babylon5.buetow.org` to `.cloud`](./2024-02-04-from-babylon5.buetow.org-to-.cloud.html) +[From `babylon5.buetow.org` to `.cloud`](./2024-02-04-from-babylon5.buetow.org-to-.cloud.md) Migrating off all my containers from AWS ECS means I need a reliable and scalable environment to host my workloads. I wanted something: @@ -97,8 +97,8 @@ All of this (every Linux VM to every OpenBSD box) will be connected via WireGuar So, when I want to access a service running in k3s, I will hit an external DNS endpoint (with the authoritative DNS servers being the OpenBSD boxes). The DNS will resolve to the master OpenBSD VM (see my KISS highly-available with OpenBSD blog post), and from there, the `relayd` process (with a Let's Encrypt certificate—see my Let's Encrypt with OpenBSD and Rex blog post) will accept the TCP connection and forward it through the WireGuard tunnel to a reachable node port of one of the k3s nodes, thus serving the traffic. -[KISS high-availability with OpenBSD](./2024-04-01-KISS-high-availability-with-OpenBSD.html) -[Let's Encrypt with OpenBSD and Rex](./2022-07-30-lets-encrypt-with-openbsd-and-rex.html) +[KISS high-availability with OpenBSD](./2024-04-01-KISS-high-availability-with-OpenBSD.md) +[Let's Encrypt with OpenBSD and Rex](./2022-07-30-lets-encrypt-with-openbsd-and-rex.md) The OpenBSD setup described here already exists and is ready to use. The only thing that does not yet exist is the configuration of `relayd` to forward requests to k3s through the WireGuard tunnel(s). @@ -138,7 +138,7 @@ For visualization, Grafana will be deployed alongside Prometheus. Grafana lets m Alerts generated by Prometheus are forwarded to Alertmanager, which I will configure to work with Gogios, a lightweight monitoring and alerting system I wrote myself. Gogios runs on one of my OpenBSD VMs. At regular intervals, Gogios scrapes the alerts generated in the k3s cluster and notifies me via Email. -[KISS server monitoring with Gogios](./2023-06-01-kiss-server-monitoring-with-gogios.html) +[KISS server monitoring with Gogios](./2023-06-01-kiss-server-monitoring-with-gogios.md) Ironically, I implemented Gogios to avoid using more complex alerting systems like Prometheus, but here we go—it integrates well now. diff --git a/gemfeed/2024-12-03-f3s-kubernetes-with-freebsd-part-2.md b/gemfeed/2024-12-03-f3s-kubernetes-with-freebsd-part-2.md index 34ef8a29..4844180b 100644 --- a/gemfeed/2024-12-03-f3s-kubernetes-with-freebsd-part-2.md +++ b/gemfeed/2024-12-03-f3s-kubernetes-with-freebsd-part-2.md @@ -10,6 +10,7 @@ These are all the posts so far: [2024-11-17 f3s: Kubernetes with FreeBSD - Part 1: Setting the stage](./2024-11-17-f3s-kubernetes-with-freebsd-part-1.md) [2024-12-03 f3s: Kubernetes with FreeBSD - Part 2: Hardware and base installation (You are currently reading this)](./2024-12-03-f3s-kubernetes-with-freebsd-part-2.md) +[f3s-kubernetes-with f3s: Kubernetes with FreeBSD - Rocky Linux Bhyve VMs - Part 4](./f3s-kubernetes-with-freebsd-part-4.md) [![f3s logo](./f3s-kubernetes-with-freebsd-part-1/f3slogo.png "f3s logo")](./f3s-kubernetes-with-freebsd-part-1/f3slogo.png) @@ -302,6 +303,7 @@ Other *BSD-related posts: [2024-04-01 KISS high-availability with OpenBSD](./2024-04-01-KISS-high-availability-with-OpenBSD.md) [2024-11-17 f3s: Kubernetes with FreeBSD - Part 1: Setting the stage](./2024-11-17-f3s-kubernetes-with-freebsd-part-1.md) [2024-12-03 f3s: Kubernetes with FreeBSD - Part 2: Hardware and base installation (You are currently reading this)](./2024-12-03-f3s-kubernetes-with-freebsd-part-2.md) +[f3s-kubernetes-with f3s: Kubernetes with FreeBSD - Rocky Linux Bhyve VMs - Part 4](./f3s-kubernetes-with-freebsd-part-4.md) E-Mail your comments to `paul@nospam.buetow.org` :-) diff --git a/gemfeed/f3s-kubernetes-with-freebsd-part-4.md b/gemfeed/f3s-kubernetes-with-freebsd-part-4.md index a5a34769..0b922c41 100644 --- a/gemfeed/f3s-kubernetes-with-freebsd-part-4.md +++ b/gemfeed/f3s-kubernetes-with-freebsd-part-4.md @@ -4,6 +4,7 @@ This is the thourth blog post about my f3s series for my self-hosting demands in [2024-11-17 f3s: Kubernetes with FreeBSD - Part 1: Setting the stage](./2024-11-17-f3s-kubernetes-with-freebsd-part-1.md) [2024-12-03 f3s: Kubernetes with FreeBSD - Part 2: Hardware and base installation](./2024-12-03-f3s-kubernetes-with-freebsd-part-2.md) +[f3s-kubernetes-with f3s: Kubernetes with FreeBSD - Rocky Linux Bhyve VMs - Part 4 (You are currently reading this)](./f3s-kubernetes-with-freebsd-part-4.md) [![f3s logo](./f3s-kubernetes-with-frhyveeebsd-part-1/f3slogo.png "f3s logo")](./f3s-kubernetes-with-frhyveeebsd-part-1/f3slogo.png) @@ -255,6 +256,7 @@ Other *BSD-related posts: [2024-04-01 KISS high-availability with OpenBSD](./2024-04-01-KISS-high-availability-with-OpenBSD.md) [2024-11-17 f3s: Kubernetes with FreeBSD - Part 1: Setting the stage](./2024-11-17-f3s-kubernetes-with-freebsd-part-1.md) [2024-12-03 f3s: Kubernetes with FreeBSD - Part 2: Hardware and base installation](./2024-12-03-f3s-kubernetes-with-freebsd-part-2.md) +[f3s-kubernetes-with f3s: Kubernetes with FreeBSD - Rocky Linux Bhyve VMs - Part 4 (You are currently reading this)](./f3s-kubernetes-with-freebsd-part-4.md) E-Mail your comments to `paul@nospam.buetow.org` :-) -- cgit v1.2.3 From 563b9052e2190df1025197909d6ad630a3d3c356 Mon Sep 17 00:00:00 2001 From: Paul Buetow Date: Thu, 30 Jan 2025 09:33:10 +0200 Subject: Update content for md --- ...6-04-09-jails-and-zfs-on-freebsd-with-puppet.md | 2 +- ...2022-07-30-lets-encrypt-with-openbsd-and-rex.md | 2 +- .../2024-01-13-one-reason-why-i-love-openbsd.md | 2 +- ...24-04-01-KISS-high-availability-with-OpenBSD.md | 2 +- ...024-11-17-f3s-kubernetes-with-freebsd-part-1.md | 4 +- ...024-12-03-f3s-kubernetes-with-freebsd-part-2.md | 8 +- ...025-02-01-f3s-kubernetes-with-freebsd-part-3.md | 366 +++++++++++++++++++++ .../DRAFT-f3s-kubernetes-with-freebsd-part-3.md | 364 -------------------- .../DRAFT-f3s-kubernetes-with-freebsd-part-4.md | 279 ++++++++++++++++ gemfeed/f3s-kubernetes-with-freebsd-part-4.md | 263 --------------- gemfeed/index.md | 1 + 11 files changed, 657 insertions(+), 636 deletions(-) create mode 100644 gemfeed/2025-02-01-f3s-kubernetes-with-freebsd-part-3.md delete mode 100644 gemfeed/DRAFT-f3s-kubernetes-with-freebsd-part-3.md create mode 100644 gemfeed/DRAFT-f3s-kubernetes-with-freebsd-part-4.md delete mode 100644 gemfeed/f3s-kubernetes-with-freebsd-part-4.md (limited to 'gemfeed') diff --git a/gemfeed/2016-04-09-jails-and-zfs-on-freebsd-with-puppet.md b/gemfeed/2016-04-09-jails-and-zfs-on-freebsd-with-puppet.md index e013c3c9..e21375d1 100644 --- a/gemfeed/2016-04-09-jails-and-zfs-on-freebsd-with-puppet.md +++ b/gemfeed/2016-04-09-jails-and-zfs-on-freebsd-with-puppet.md @@ -404,6 +404,6 @@ Other *BSD related posts are: [2024-04-01 KISS high-availability with OpenBSD](./2024-04-01-KISS-high-availability-with-OpenBSD.md) [2024-11-17 f3s: Kubernetes with FreeBSD - Part 1: Setting the stage](./2024-11-17-f3s-kubernetes-with-freebsd-part-1.md) [2024-12-03 f3s: Kubernetes with FreeBSD - Part 2: Hardware and base installation](./2024-12-03-f3s-kubernetes-with-freebsd-part-2.md) -[f3s-kubernetes-with f3s: Kubernetes with FreeBSD - Rocky Linux Bhyve VMs - Part 4](./f3s-kubernetes-with-freebsd-part-4.md) +[2025-02-01 f3s: Kubernetes with FreeBSD - Part 3: Protecting from power cuts](./2025-02-01-f3s-kubernetes-with-freebsd-part-3.md) [Back to the main site](../) diff --git a/gemfeed/2022-07-30-lets-encrypt-with-openbsd-and-rex.md b/gemfeed/2022-07-30-lets-encrypt-with-openbsd-and-rex.md index 17952046..40deb0fc 100644 --- a/gemfeed/2022-07-30-lets-encrypt-with-openbsd-and-rex.md +++ b/gemfeed/2022-07-30-lets-encrypt-with-openbsd-and-rex.md @@ -683,6 +683,6 @@ Other *BSD related posts are: [2024-04-01 KISS high-availability with OpenBSD](./2024-04-01-KISS-high-availability-with-OpenBSD.md) [2024-11-17 f3s: Kubernetes with FreeBSD - Part 1: Setting the stage](./2024-11-17-f3s-kubernetes-with-freebsd-part-1.md) [2024-12-03 f3s: Kubernetes with FreeBSD - Part 2: Hardware and base installation](./2024-12-03-f3s-kubernetes-with-freebsd-part-2.md) -[f3s-kubernetes-with f3s: Kubernetes with FreeBSD - Rocky Linux Bhyve VMs - Part 4](./f3s-kubernetes-with-freebsd-part-4.md) +[2025-02-01 f3s: Kubernetes with FreeBSD - Part 3: Protecting from power cuts](./2025-02-01-f3s-kubernetes-with-freebsd-part-3.md) [Back to the main site](../) diff --git a/gemfeed/2024-01-13-one-reason-why-i-love-openbsd.md b/gemfeed/2024-01-13-one-reason-why-i-love-openbsd.md index 0c339e5d..92598532 100644 --- a/gemfeed/2024-01-13-one-reason-why-i-love-openbsd.md +++ b/gemfeed/2024-01-13-one-reason-why-i-love-openbsd.md @@ -58,6 +58,6 @@ Other *BSD related posts are: [2024-04-01 KISS high-availability with OpenBSD](./2024-04-01-KISS-high-availability-with-OpenBSD.md) [2024-11-17 f3s: Kubernetes with FreeBSD - Part 1: Setting the stage](./2024-11-17-f3s-kubernetes-with-freebsd-part-1.md) [2024-12-03 f3s: Kubernetes with FreeBSD - Part 2: Hardware and base installation](./2024-12-03-f3s-kubernetes-with-freebsd-part-2.md) -[f3s-kubernetes-with f3s: Kubernetes with FreeBSD - Rocky Linux Bhyve VMs - Part 4](./f3s-kubernetes-with-freebsd-part-4.md) +[2025-02-01 f3s: Kubernetes with FreeBSD - Part 3: Protecting from power cuts](./2025-02-01-f3s-kubernetes-with-freebsd-part-3.md) [Back to the main site](../) diff --git a/gemfeed/2024-04-01-KISS-high-availability-with-OpenBSD.md b/gemfeed/2024-04-01-KISS-high-availability-with-OpenBSD.md index 7d56e460..66e17f82 100644 --- a/gemfeed/2024-04-01-KISS-high-availability-with-OpenBSD.md +++ b/gemfeed/2024-04-01-KISS-high-availability-with-OpenBSD.md @@ -309,6 +309,6 @@ Other *BSD and KISS related posts are: [2024-04-01 KISS high-availability with OpenBSD (You are currently reading this)](./2024-04-01-KISS-high-availability-with-OpenBSD.md) [2024-11-17 f3s: Kubernetes with FreeBSD - Part 1: Setting the stage](./2024-11-17-f3s-kubernetes-with-freebsd-part-1.md) [2024-12-03 f3s: Kubernetes with FreeBSD - Part 2: Hardware and base installation](./2024-12-03-f3s-kubernetes-with-freebsd-part-2.md) -[f3s-kubernetes-with f3s: Kubernetes with FreeBSD - Rocky Linux Bhyve VMs - Part 4](./f3s-kubernetes-with-freebsd-part-4.md) +[2025-02-01 f3s: Kubernetes with FreeBSD - Part 3: Protecting from power cuts](./2025-02-01-f3s-kubernetes-with-freebsd-part-3.md) [Back to the main site](../) diff --git a/gemfeed/2024-11-17-f3s-kubernetes-with-freebsd-part-1.md b/gemfeed/2024-11-17-f3s-kubernetes-with-freebsd-part-1.md index 1314bfcd..230a77d0 100644 --- a/gemfeed/2024-11-17-f3s-kubernetes-with-freebsd-part-1.md +++ b/gemfeed/2024-11-17-f3s-kubernetes-with-freebsd-part-1.md @@ -10,7 +10,7 @@ These are all the posts so far: [2024-11-17 f3s: Kubernetes with FreeBSD - Part 1: Setting the stage (You are currently reading this)](./2024-11-17-f3s-kubernetes-with-freebsd-part-1.md) [2024-12-03 f3s: Kubernetes with FreeBSD - Part 2: Hardware and base installation](./2024-12-03-f3s-kubernetes-with-freebsd-part-2.md) -[f3s-kubernetes-with f3s: Kubernetes with FreeBSD - Rocky Linux Bhyve VMs - Part 4](./f3s-kubernetes-with-freebsd-part-4.md) +[2025-02-01 f3s: Kubernetes with FreeBSD - Part 3: Protecting from power cuts](./2025-02-01-f3s-kubernetes-with-freebsd-part-3.md) [![f3s logo](./f3s-kubernetes-with-freebsd-part-1/f3slogo.png "f3s logo")](./f3s-kubernetes-with-freebsd-part-1/f3slogo.png) @@ -166,7 +166,7 @@ Other *BSD-related posts: [2024-04-01 KISS high-availability with OpenBSD](./2024-04-01-KISS-high-availability-with-OpenBSD.md) [2024-11-17 f3s: Kubernetes with FreeBSD - Part 1: Setting the stage (You are currently reading this)](./2024-11-17-f3s-kubernetes-with-freebsd-part-1.md) [2024-12-03 f3s: Kubernetes with FreeBSD - Part 2: Hardware and base installation](./2024-12-03-f3s-kubernetes-with-freebsd-part-2.md) -[f3s-kubernetes-with f3s: Kubernetes with FreeBSD - Rocky Linux Bhyve VMs - Part 4](./f3s-kubernetes-with-freebsd-part-4.md) +[2025-02-01 f3s: Kubernetes with FreeBSD - Part 3: Protecting from power cuts](./2025-02-01-f3s-kubernetes-with-freebsd-part-3.md) E-Mail your comments to `paul@nospam.buetow.org` :-) diff --git a/gemfeed/2024-12-03-f3s-kubernetes-with-freebsd-part-2.md b/gemfeed/2024-12-03-f3s-kubernetes-with-freebsd-part-2.md index 4844180b..161f4a1a 100644 --- a/gemfeed/2024-12-03-f3s-kubernetes-with-freebsd-part-2.md +++ b/gemfeed/2024-12-03-f3s-kubernetes-with-freebsd-part-2.md @@ -10,7 +10,7 @@ These are all the posts so far: [2024-11-17 f3s: Kubernetes with FreeBSD - Part 1: Setting the stage](./2024-11-17-f3s-kubernetes-with-freebsd-part-1.md) [2024-12-03 f3s: Kubernetes with FreeBSD - Part 2: Hardware and base installation (You are currently reading this)](./2024-12-03-f3s-kubernetes-with-freebsd-part-2.md) -[f3s-kubernetes-with f3s: Kubernetes with FreeBSD - Rocky Linux Bhyve VMs - Part 4](./f3s-kubernetes-with-freebsd-part-4.md) +[2025-02-01 f3s: Kubernetes with FreeBSD - Part 3: Protecting from power cuts](./2025-02-01-f3s-kubernetes-with-freebsd-part-3.md) [![f3s logo](./f3s-kubernetes-with-freebsd-part-1/f3slogo.png "f3s logo")](./f3s-kubernetes-with-freebsd-part-1/f3slogo.png) @@ -292,7 +292,9 @@ The Beelink S12 Pro with Intel N100 CPUs checks all the boxes for a k3s project: To ease cable management, I need to get shorter ethernet cables. I will place the tower on my shelf, where most of the cables will be hidden (together with a UPS, which will also be added to the setup). -What will be covered in the next post of this series? Maybe ttttbhyve/Rocky Linux and WireGuard setup as described in part 1 of this series... +Read the next post of this series: + +[f3s: Kubernetes with FreeBSD - Part 3: Protecting from power cuts](./2025-02-01-f3s-kubernetes-with-freebsd-part-3.md) Other *BSD-related posts: @@ -303,7 +305,7 @@ Other *BSD-related posts: [2024-04-01 KISS high-availability with OpenBSD](./2024-04-01-KISS-high-availability-with-OpenBSD.md) [2024-11-17 f3s: Kubernetes with FreeBSD - Part 1: Setting the stage](./2024-11-17-f3s-kubernetes-with-freebsd-part-1.md) [2024-12-03 f3s: Kubernetes with FreeBSD - Part 2: Hardware and base installation (You are currently reading this)](./2024-12-03-f3s-kubernetes-with-freebsd-part-2.md) -[f3s-kubernetes-with f3s: Kubernetes with FreeBSD - Rocky Linux Bhyve VMs - Part 4](./f3s-kubernetes-with-freebsd-part-4.md) +[2025-02-01 f3s: Kubernetes with FreeBSD - Part 3: Protecting from power cuts](./2025-02-01-f3s-kubernetes-with-freebsd-part-3.md) E-Mail your comments to `paul@nospam.buetow.org` :-) diff --git a/gemfeed/2025-02-01-f3s-kubernetes-with-freebsd-part-3.md b/gemfeed/2025-02-01-f3s-kubernetes-with-freebsd-part-3.md new file mode 100644 index 00000000..db891ddb --- /dev/null +++ b/gemfeed/2025-02-01-f3s-kubernetes-with-freebsd-part-3.md @@ -0,0 +1,366 @@ +# f3s: Kubernetes with FreeBSD - Part 3: Protecting from power cuts + +> Published at 2025-01-30T09:22:06+02:00 + +This is the third blog post about my f3s series for my self-hosting demands in my home lab. f3s? The "f" stands for FreeBSD, and the "3s" stands for k3s, the Kubernetes distribution we will use on FreeBSD-based physical machines. + +[2024-11-17 f3s: Kubernetes with FreeBSD - Part 1: Setting the stage](./2024-11-17-f3s-kubernetes-with-freebsd-part-1.md) +[2024-12-03 f3s: Kubernetes with FreeBSD - Part 2: Hardware and base installation](./2024-12-03-f3s-kubernetes-with-freebsd-part-2.md) +[2025-02-01 f3s: Kubernetes with FreeBSD - Part 3: Protecting from power cuts (You are currently reading this)](./2025-02-01-f3s-kubernetes-with-freebsd-part-3.md) + +[![f3s logo](./f3s-kubernetes-with-freebsd-part-1/f3slogo.png "f3s logo")](./f3s-kubernetes-with-freebsd-part-1/f3slogo.png) + +## Table of Contents + +* [⇢ f3s: Kubernetes with FreeBSD - Part 3: Protecting from power cuts](#f3s-kubernetes-with-freebsd---part-3-protecting-from-power-cuts) +* [⇢ ⇢ Introduction](#introduction) +* [⇢ ⇢ Changes since last time](#changes-since-last-time) +* [⇢ ⇢ ⇢ FreeBSD upgrade from 14.1 to 14.2](#freebsd-upgrade-from-141-to-142) +* [⇢ ⇢ ⇢ A new home (behind the TV)](#a-new-home-behind-the-tv) +* [⇢ ⇢ The UPS hardware](#the-ups-hardware) +* [⇢ ⇢ Configuring FreeBSD to Work with the UPS](#configuring-freebsd-to-work-with-the-ups) +* [⇢ ⇢ ⇢ USB Device Detection](#usb-device-detection) +* [⇢ ⇢ ⇢ `apcupsd` Installation](#apcupsd-installation) +* [⇢ ⇢ ⇢ UPS Connectivity Test](#ups-connectivity-test) +* [⇢ ⇢ APC Info on Partner Nodes:](#apc-info-on-partner-nodes) +* [⇢ ⇢ ⇢ Installation on partners](#installation-on-partners) +* [⇢ ⇢ Power outage simulation](#power-outage-simulation) +* [⇢ ⇢ ⇢ Pulling the plug](#pulling-the-plug) +* [⇢ ⇢ ⇢ Restoring power](#restoring-power) + +## Introduction + +In this blog post, we are setting up the UPS for the cluster. A UPS, or Uninterruptible Power Supply, safeguards my cluster from unexpected power outages and surges. It acts as a backup battery that kicks in when the electricity cuts out—especially useful in my area, where power cuts are frequent—allowing for a graceful system shutdown and preventing data loss and corruption. This is especially important since I will also store some of my data on the f3s nodes. + +## Changes since last time + +### FreeBSD upgrade from 14.1 to 14.2 + +There has been a new release since the last blog post in this series. The upgrade from 14.1 was as easy as: + +```sh +paul@f0: ~ % doas freebsd-update fetch +paul@f0: ~ % doas freebsd-update install +paul@f0: ~ % doas freebsd-update -r 14.2-RELEASE upgrade +paul@f0: ~ % doas freebsd-update install +paul@f0: ~ % doas shutdown -r now +``` + +And after rebooting, I ran: + +```sh +paul@f0: ~ % doas freebsd-update install +paul@f0: ~ % doas pkg update +paul@f0: ~ % doas pkg upgrade +paul@f0: ~ % doas shutdown -r now +``` + +And after another reboot, I was on 14.2: + +```sh +paul@f0:~ % uname -a +FreeBSD f0.lan.buetow.org 14.2-RELEASE FreeBSD 14.2-RELEASE + releng/14.2-n269506-c8918d6c7412 GENERIC amd64 +``` + +And, of course, I ran this on all 3 nodes! + +### A new home (behind the TV) + +I've put all the infrastructure behind my TV, as plenty of space is available. The TV hides most of the setup, which drastically improved the SAF (spouse acceptance factor). + +[![New hardware placement arrangement](./f3s-kubernetes-with-freebsd-part-3/f3s-changes.jpg "New hardware placement arrangement")](./f3s-kubernetes-with-freebsd-part-3/f3s-changes.jpg) + +I got rid of the mini-switch I mentioned in the previous blog post. I have the TP-Link EAP615-Wall mounted on the wall nearby, which is my OpenWrt-powered Wi-Fi hotspot. It also has 3 Ethernet ports, to which I connected the Beelink nodes. That's the device you see at the very top. + +The Ethernet cables go downward through the cable boxes to the Beelink nodes. In addition to the Beelink f3s nodes, I connected the TP-Link to the UPS as well (not discussed further in this blog post, but the positive side effect is that my Wi-Fi will still work during a power loss for some time—and during a power cut, the Beelink nodes will still be able to communicate with each other). + +On the very left (the black box) is the UPS, with four power outlets. Three go to the Beelink nodes, and one goes to the TP-Link. A USB output is also connected to the first Beelink node, `f0`. + +On the very right (halfway hidden behind the TV) are the 3 Beelink nodes stacked on top of each other. The only downside (or upside?) is that my 14-month-old daughter is now chaos-testing the Beelink nodes, as the red power buttons (now reachable for her) are very attractive for her to press when passing by randomly. :-) Luckily, that will only cause graceful system shutdowns! + +## The UPS hardware + +I wanted a UPS that I could connect to via FreeBSD, and that would provide enough backup power to operate the cluster for a couple of minutes (it turned out to be around an hour, but this time will likely be shortened after future hardware upgrades, like additional drives and a backup enclosure) and to automatically initiate the shutdown of all the f3s nodes. + +I decided on the APC Back-UPS BX750MI model because: + +* Zero noise level when there is no power cut (some light noise when the battery is in operation during a power cut). +* Cost: It is relatively affordable (not costing thousands). +* USB connectivity: Can be connected via USB to one of the FreeBSD hosts to read the UPS status. +* A power output of 750VA (or 410 watts), suitable for an hour of runtime for my f3s nodes (plus the Wi-Fi router). +* Multiple power outlets: Can connect all 3 f3s nodes directly. +* User-replaceable batteries: I can replace the batteries myself after two years or more (depending on usage). +* Its compact design. Overall, I like how it looks. + +[![The APC Back-UPS BX750MI in operation.](./f3s-kubernetes-with-freebsd-part-3/apc-back-ups.jpg "The APC Back-UPS BX750MI in operation.")](./f3s-kubernetes-with-freebsd-part-3/apc-back-ups.jpg) + +## Configuring FreeBSD to Work with the UPS + +### USB Device Detection + +Once plugged in via USB on FreeBSD, I could see the following in the kernel messages: + +```sh +paul@f0: ~ % doas dmesg | grep UPS +ugen0.2: at usbus0 +``` + +### `apcupsd` Installation + +To make use of the USB connection, the `apcupsd` package had to be installed: + +```sh +paul@f0: ~ % doas install apcupsd +``` + +I have made the following modifications to the configuration file so that the UPS can be used via the USB interface: + +```sh +paul@f0:/usr/local/etc/apcupsd % diff -u apcupsd.conf.sample apcupsd.conf +--- apcupsd.conf.sample 2024-11-01 16:40:42.000000000 +0200 ++++ apcupsd.conf 2024-12-03 10:58:24.009501000 +0200 +@@ -31,7 +31,7 @@ + # 940-1524C, 940-0024G, 940-0095A, 940-0095B, + # 940-0095C, 940-0625A, M-04-02-2000 + # +-UPSCABLE smart ++UPSCABLE usb + + # To get apcupsd to work, in addition to defining the cable + # above, you must also define a UPSTYPE, which corresponds to +@@ -88,8 +88,10 @@ + # that apcupsd binds to that particular unit + # (helpful if you have more than one USB UPS). + # +-UPSTYPE apcsmart +-DEVICE /dev/usv ++UPSTYPE usb ++DEVICE + + # POLLTIME + # Interval (in seconds) at which apcupsd polls the UPS for status. This +``` + +I left the remaining settings as the default ones; for example, the following are of main interest: + +``` +# If during a power failure, the remaining battery percentage +# (as reported by the UPS) is below or equal to BATTERYLEVEL, +# apcupsd will initiate a system shutdown. +BATTERYLEVEL 5 + +# If during a power failure, the remaining runtime in minutes +# (as calculated internally by the UPS) is below or equal to MINUTES, +# apcupsd, will initiate a system shutdown. +MINUTES 3 +``` + +I then enabled and started the daemon: + +```sh +paul@f0:/usr/local/etc/apcupsd % doas sysrc apcupsd_enable=YES +apcupsd_enable: -> YES +paul@f0:/usr/local/etc/apcupsd % doas service apcupsd start +Starting apcupsd. +``` + +### UPS Connectivity Test + +And voila, I could now access the UPS information via the `apcaccess` command; how convenient :-) (I also read through the manual page, which provides a good understanding of what else can be done with it!). + +```sh +paul@f0:~ % apcaccess +APC : 001,035,0857 +DATE : 2025-01-26 14:43:27 +0200 +HOSTNAME : f0.lan.buetow.org +VERSION : 3.14.14 (31 May 2016) freebsd +UPSNAME : f0.lan.buetow.org +CABLE : USB Cable +DRIVER : USB UPS Driver +UPSMODE : Stand Alone +STARTTIME: 2025-01-26 14:43:25 +0200 +MODEL : Back-UPS BX750MI +STATUS : ONLINE +LINEV : 230.0 Volts +LOADPCT : 4.0 Percent +BCHARGE : 100.0 Percent +TIMELEFT : 65.3 Minutes +MBATTCHG : 5 Percent +MINTIMEL : 3 Minutes +MAXTIME : 0 Seconds +SENSE : Medium +LOTRANS : 145.0 Volts +HITRANS : 295.0 Volts +ALARMDEL : No alarm +BATTV : 13.6 Volts +LASTXFER : Automatic or explicit self test +NUMXFERS : 0 +TONBATT : 0 Seconds +CUMONBATT: 0 Seconds +XOFFBATT : N/A +SELFTEST : NG +STATFLAG : 0x05000008 +SERIALNO : 9B2414A03599 +BATTDATE : 2001-01-01 +NOMINV : 230 Volts +NOMBATTV : 12.0 Volts +NOMPOWER : 410 Watts +END APC : 2025-01-26 14:44:06 +0200 +``` + +## APC Info on Partner Nodes: + +So far, so good. Host `f0` would shut down itself when short on power. But what about the `f1` and `f2` nodes? They aren't connected directly to the UPS and, therefore, wouldn't know that their power is about to be cut off. For this, `apcupsd` running on the `f1` and `f2` nodes can be configured to retrieve UPS information via the network from the `apcupsd` server running on the `f0` node, which is connected directly to the APC via USB. + +Of course, this won't work when `f0` is down. In this case, no operational node would be connected to the UPS via USB; therefore, the current power status would not be known. However, I consider this a rare circumstance. Furthermore, in case of an `f0` system crash, sudden power outages on the two other nodes would occur at different times making real data loss (the main concern here) less likely. + +And if `f0` is down and `f1` and `f2` receive new data and crash midway, it's likely that a client (e.g., an Android app or another laptop) still has the data stored on it, making data recoverable and data loss overall nearly impossible. I'd receive an alert if any of the nodes go down (more on monitoring later in this blog series). + +### Installation on partners + +To do this, I installed `apcupsd` via `doas pkg install apcupsd` on `f1` and `f2`, and then I could connect to it this way: + +```sh +paul@f1:~ % apcaccess -h f0.lan.buetow.org | grep Percent +LOADPCT : 12.0 Percent +BCHARGE : 94.0 Percent +MBATTCHG : 5 Percent +``` + +But I want the daemon to be configured and enabled in such a way that it connects to the master UPS node (the one with the UPS connected via USB) so that it can also initiate a system shutdown when the UPS battery reaches low levels. For that, `apcupsd` itself needs to be aware of the UPS status. + +On `f1` and `f2`, I changed the configuration to use `f0` (where `apcupsd` is listening) as a remote device. I also changed the `MINUTES` setting from 3 to 6 and the `BATTERYLEVEL` setting from 5 to 10 to ensure that the `f1` and `f2` nodes could still connect to the `f0` node for UPS information before `f0` decides to shut down itself. So `f1` and `f2` must shut down earlier than `f0`: + +```sh +paul@f2:/usr/local/etc/apcupsd % diff -u apcupsd.conf.sample apcupsd.conf +--- apcupsd.conf.sample 2024-11-01 16:40:42.000000000 +0200 ++++ apcupsd.conf 2025-01-26 15:52:45.108469000 +0200 +@@ -31,7 +31,7 @@ + # 940-1524C, 940-0024G, 940-0095A, 940-0095B, + # 940-0095C, 940-0625A, M-04-02-2000 + # +-UPSCABLE smart ++UPSCABLE ether + + # To get apcupsd to work, in addition to defining the cable + # above, you must also define a UPSTYPE, which corresponds to +@@ -52,7 +52,6 @@ + # Network Information Server. This is used if the + # UPS powering your computer is connected to a + # different computer for monitoring. +-# + # snmp hostname:port:vendor:community + # SNMP network link to an SNMP-enabled UPS device. + # Hostname is the ip address or hostname of the UPS +@@ -88,8 +87,8 @@ + # that apcupsd binds to that particular unit + # (helpful if you have more than one USB UPS). + # +-UPSTYPE apcsmart +-DEVICE /dev/usv ++UPSTYPE net ++DEVICE f0.lan.buetow.org:3551 + + # POLLTIME + # Interval (in seconds) at which apcupsd polls the UPS for status. This +@@ -147,12 +146,12 @@ + # If during a power failure, the remaining battery percentage + # (as reported by the UPS) is below or equal to BATTERYLEVEL, + # apcupsd will initiate a system shutdown. +-BATTERYLEVEL 5 ++BATTERYLEVEL 10 + + # If during a power failure, the remaining runtime in minutes + # (as calculated internally by the UPS) is below or equal to MINUTES, + # apcupsd, will initiate a system shutdown. +-MINUTES 3 ++MINUTES 6 + + # If during a power failure, the UPS has run on batteries for TIMEOUT + # many seconds or longer, apcupsd will initiate a system shutdown. + +``` +So I also ran the following commands on `f1` and `f2`: + +```sh +paul@f1:/usr/local/etc/apcupsd % doas sysrc apcupsd_enable=YES +apcupsd_enable: -> YES +paul@f1:/usr/local/etc/apcupsd % doas service apcupsd start +Starting apcupsd. +``` + +And then I was able to connect to localhost via the `apcaccess` command: + +```sh +paul@f1:~ % doas apcaccess | grep Percent +LOADPCT : 5.0 Percent +BCHARGE : 95.0 Percent +MBATTCHG : 5 Percent +``` + +## Power outage simulation + +### Pulling the plug + +I simulated a power outage by removing the power input from the APC. Immediately, the following message appeared on all the nodes: + +```` +Broadcast Message from root@f0.lan.buetow.org + (no tty) at 15:03 EET... + +Power failure. Running on UPS batteries. +``` + +I ran the following command to confirm the available battery time: + +```sh +paul@f0:/usr/local/etc/apcupsd % apcaccess -p TIMELEFT +63.9 Minutes +``` + +And after almost 60 minutes (`f1` and `f2` a bit earlier, `f0` a bit later due to the different `BATTERYLEVEL` and `MINUTES` settings outlined earlier), the following broadcast was sent out: + +``` +Broadcast Message from root@f0.lan.buetow.org + (no tty) at 15:08 EET... + + *** FINAL System shutdown message from root@f0.lan.buetow.org *** + +System going down IMMEDIATELY + +apcupsd initiated shutdown +``` + +And all the nodes shut down safely before the UPS ran out of battery! + +### Restoring power + +After restoring power, I checked the logs in `/var/log/daemon.log` and found the following on all 3 nodes: + +``` +Jan 26 17:36:24 f2 apcupsd[2159]: Power failure. +Jan 26 17:36:30 f2 apcupsd[2159]: Running on UPS batteries. +Jan 26 17:36:30 f2 apcupsd[2159]: Battery charge below low limit. +Jan 26 17:36:30 f2 apcupsd[2159]: Initiating system shutdown! +Jan 26 17:36:30 f2 apcupsd[2159]: User logins prohibited +Jan 26 17:36:32 f2 apcupsd[2159]: apcupsd exiting, signal 15 +Jan 26 17:36:32 f2 apcupsd[2159]: apcupsd shutdown succeeded +``` + +All good :-) See you in the next post of this series! + +Other BSD related posts are: + +[2016-04-09 Jails and ZFS with Puppet on FreeBSD](./2016-04-09-jails-and-zfs-on-freebsd-with-puppet.md) +[2022-07-30 Let's Encrypt with OpenBSD and Rex](./2022-07-30-lets-encrypt-with-openbsd-and-rex.md) +[2022-10-30 Installing DTail on OpenBSD](./2022-10-30-installing-dtail-on-openbsd.md) +[2024-01-13 One reason why I love OpenBSD](./2024-01-13-one-reason-why-i-love-openbsd.md) +[2024-04-01 KISS high-availability with OpenBSD](./2024-04-01-KISS-high-availability-with-OpenBSD.md) +[2024-11-17 f3s: Kubernetes with FreeBSD - Part 1: Setting the stage](./2024-11-17-f3s-kubernetes-with-freebsd-part-1.md) +[2024-12-03 f3s: Kubernetes with FreeBSD - Part 2: Hardware and base installation](./2024-12-03-f3s-kubernetes-with-freebsd-part-2.md) +[2025-02-01 f3s: Kubernetes with FreeBSD - Part 3: Protecting from power cuts (You are currently reading this)](./2025-02-01-f3s-kubernetes-with-freebsd-part-3.md) + +E-Mail your comments to `paul@nospam.buetow.org` :-) + +[Back to the main site](../) diff --git a/gemfeed/DRAFT-f3s-kubernetes-with-freebsd-part-3.md b/gemfeed/DRAFT-f3s-kubernetes-with-freebsd-part-3.md deleted file mode 100644 index 5e84286a..00000000 --- a/gemfeed/DRAFT-f3s-kubernetes-with-freebsd-part-3.md +++ /dev/null @@ -1,364 +0,0 @@ -# f3s: Kubernetes with FreeBSD - Part 3: Protecting from power cuts - -This is the third blog post about my f3s series for my self-hosting demands in my home lab. f3s? The "f" stands for FreeBSD, and the "3s" stands for k3s, the Kubernetes distribution we will use on FreeBSD-based physical machines. - -[2024-11-17 f3s: Kubernetes with FreeBSD - Part 1: Setting the stage](./2024-11-17-f3s-kubernetes-with-freebsd-part-1.md) -[2024-12-03 f3s: Kubernetes with FreeBSD - Part 2: Hardware and base installation](./2024-12-03-f3s-kubernetes-with-freebsd-part-2.md) -[f3s-kubernetes-with f3s: Kubernetes with FreeBSD - Rocky Linux Bhyve VMs - Part 4](./f3s-kubernetes-with-freebsd-part-4.md) - -[![f3s logo](./f3s-kubernetes-with-freebsd-part-1/f3slogo.png "f3s logo")](./f3s-kubernetes-with-freebsd-part-1/f3slogo.png) - -## Table of Contents - -* [⇢ f3s: Kubernetes with FreeBSD - Part 3: Protecting from power cuts](#f3s-kubernetes-with-freebsd---part-3-protecting-from-power-cuts) -* [⇢ ⇢ Introduction](#introduction) -* [⇢ ⇢ Changes since last time](#changes-since-last-time) -* [⇢ ⇢ ⇢ FreeBSD upgrade from 14.1 to 14.2](#freebsd-upgrade-from-141-to-142) -* [⇢ ⇢ ⇢ A new home (behind the TV)](#a-new-home-behind-the-tv) -* [⇢ ⇢ The UPS hardware](#the-ups-hardware) -* [⇢ ⇢ Configuring FreeBSD to Work with the UPS](#configuring-freebsd-to-work-with-the-ups) -* [⇢ ⇢ ⇢ USB Device Detection](#usb-device-detection) -* [⇢ ⇢ ⇢ `apcupsd` Installation](#apcupsd-installation) -* [⇢ ⇢ ⇢ UPS Connectivity Test](#ups-connectivity-test) -* [⇢ ⇢ APC Info on Partner Nodes:](#apc-info-on-partner-nodes) -* [⇢ ⇢ ⇢ Installation on partners](#installation-on-partners) -* [⇢ ⇢ Power outage simulation](#power-outage-simulation) -* [⇢ ⇢ ⇢ Pulling the plug](#pulling-the-plug) -* [⇢ ⇢ ⇢ Restoring power](#restoring-power) - -## Introduction - -In this blog post, we are setting up the UPS for the cluster. A UPS, or Uninterruptible Power Supply, safeguards my cluster from unexpected power outages and surges. It acts as a backup battery that kicks in when the electricity cuts out—especially useful in my area, where power cuts are frequent—allowing for a graceful system shutdown and preventing data loss and corruption. This is especially important since I will also store some of my data on the f3s nodes. - -## Changes since last time - -### FreeBSD upgrade from 14.1 to 14.2 - -There has been a new release since the last blog post in this series. The upgrade from 14.1 was as easy as: - -```sh -paul@f0: ~ % doas freebsd-update fetch -paul@f0: ~ % doas freebsd-update install -paul@f0: ~ % doas freebsd-update -r 14.2-RELEASE upgrade -paul@f0: ~ % doas freebsd-update install -paul@f0: ~ % doas shutdown -r now -``` - -And after rebooting, I ran: - -```sh -paul@f0: ~ % doas freebsd-update install -paul@f0: ~ % doas pkg update -paul@f0: ~ % doas pkg upgrade -paul@f0: ~ % doas shutdown -r now -``` - -And after another reboot, I was on 14.2: - -```sh -paul@f0:~ % uname -a -FreeBSD f0.lan.buetow.org 14.2-RELEASE FreeBSD 14.2-RELEASE - releng/14.2-n269506-c8918d6c7412 GENERIC amd64 -``` - -And, of course, I ran this on all 3 nodes! - -### A new home (behind the TV) - -I've put all the infrastructure behind my TV, as plenty of space is available. The TV hides most of the setup, which drastically improved the SAF (spouse acceptance factor). - -[![New hardware placement arrangement](./f3s-kubernetes-with-freebsd-part-3/f3s-changes.jpg "New hardware placement arrangement")](./f3s-kubernetes-with-freebsd-part-3/f3s-changes.jpg) - -I got rid of the mini-switch I mentioned in the previous blog post. I have the TP-Link EAP615-Wall mounted on the wall nearby, which is my OpenWrt-powered Wi-Fi hotspot. It also has 3 Ethernet ports, to which I connected the Beelink nodes. That's the device you see at the very top. - -The Ethernet cables go downward through the cable boxes to the Beelink nodes. In addition to the Beelink f3s nodes, I connected the TP-Link to the UPS as well (not discussed further in this blog post, but the positive side effect is that my Wi-Fi will still work during a power loss for some time—and during a power cut, the Beelink nodes will still be able to communicate with each other). - -On the very left (the black box) is the UPS, with four power outlets. Three go to the Beelink nodes, and one goes to the TP-Link. A USB output is also connected to the first Beelink node, `f0`. - -On the very right (halfway hidden behind the TV) are the 3 Beelink nodes stacked on top of each other. The only downside (or upside?) is that my 14-month-old daughter is now chaos-testing the Beelink nodes, as the red power buttons (now reachable for her) are very attractive for her to press when passing by randomly. :-) Luckily, that will only cause graceful system shutdowns! - -## The UPS hardware - -I wanted a UPS that I could connect to via FreeBSD, and that would provide enough backup power to operate the cluster for a couple of minutes (it turned out to be around an hour, but this time will likely be shortened after future hardware upgrades, like additional drives and a backup enclosure) and to automatically initiate the shutdown of all the f3s nodes. - -I decided on the APC Back-UPS BX750MI model because: - -* Zero noise level when there is no power cut (some light noise when the battery is in operation during a power cut). -* Cost: It is relatively affordable (not costing thousands). -* USB connectivity: Can be connected via USB to one of the FreeBSD hosts to read the UPS status. -* A power output of 750VA (or 410 watts), suitable for an hour of runtime for my f3s nodes (plus the Wi-Fi router). -* Multiple power outlets: Can connect all 3 f3s nodes directly. -* User-replaceable batteries: I can replace the batteries myself after two years or more (depending on usage). -* Its compact design. Overall, I like how it looks. - -[![The APC Back-UPS BX750MI in operation.](./f3s-kubernetes-with-freebsd-part-3/apc-back-ups.jpg "The APC Back-UPS BX750MI in operation.")](./f3s-kubernetes-with-freebsd-part-3/apc-back-ups.jpg) - -## Configuring FreeBSD to Work with the UPS - -### USB Device Detection - -Once plugged in via USB on FreeBSD, I could see the following in the kernel messages: - -```sh -paul@f0: ~ % doas dmesg | grep UPS -ugen0.2: at usbus0 -``` - -### `apcupsd` Installation - -To make use of the USB connection, the `apcupsd` package had to be installed: - -```sh -paul@f0: ~ % doas install apcupsd -``` - -I have made the following modifications to the configuration file so that the UPS can be used via the USB interface: - -```sh -paul@f0:/usr/local/etc/apcupsd % diff -u apcupsd.conf.sample apcupsd.conf ---- apcupsd.conf.sample 2024-11-01 16:40:42.000000000 +0200 -+++ apcupsd.conf 2024-12-03 10:58:24.009501000 +0200 -@@ -31,7 +31,7 @@ - # 940-1524C, 940-0024G, 940-0095A, 940-0095B, - # 940-0095C, 940-0625A, M-04-02-2000 - # --UPSCABLE smart -+UPSCABLE usb - - # To get apcupsd to work, in addition to defining the cable - # above, you must also define a UPSTYPE, which corresponds to -@@ -88,8 +88,10 @@ - # that apcupsd binds to that particular unit - # (helpful if you have more than one USB UPS). - # --UPSTYPE apcsmart --DEVICE /dev/usv -+UPSTYPE usb -+DEVICE - - # POLLTIME - # Interval (in seconds) at which apcupsd polls the UPS for status. This -``` - -I left the remaining settings as the default ones; for example, the following are of main interest: - -``` -# If during a power failure, the remaining battery percentage -# (as reported by the UPS) is below or equal to BATTERYLEVEL, -# apcupsd will initiate a system shutdown. -BATTERYLEVEL 5 - -# If during a power failure, the remaining runtime in minutes -# (as calculated internally by the UPS) is below or equal to MINUTES, -# apcupsd, will initiate a system shutdown. -MINUTES 3 -``` - -I then enabled and started the daemon: - -```sh -paul@f0:/usr/local/etc/apcupsd % doas sysrc apcupsd_enable=YES -apcupsd_enable: -> YES -paul@f0:/usr/local/etc/apcupsd % doas service apcupsd start -Starting apcupsd. -``` - -### UPS Connectivity Test - -And voila, I could now access the UPS information via the `apcaccess` command; how convenient :-) (I also read through the manual page, which provides a good understanding of what else can be done with it!). - -```sh -paul@f0:~ % apcaccess -APC : 001,035,0857 -DATE : 2025-01-26 14:43:27 +0200 -HOSTNAME : f0.lan.buetow.org -VERSION : 3.14.14 (31 May 2016) freebsd -UPSNAME : f0.lan.buetow.org -CABLE : USB Cable -DRIVER : USB UPS Driver -UPSMODE : Stand Alone -STARTTIME: 2025-01-26 14:43:25 +0200 -MODEL : Back-UPS BX750MI -STATUS : ONLINE -LINEV : 230.0 Volts -LOADPCT : 4.0 Percent -BCHARGE : 100.0 Percent -TIMELEFT : 65.3 Minutes -MBATTCHG : 5 Percent -MINTIMEL : 3 Minutes -MAXTIME : 0 Seconds -SENSE : Medium -LOTRANS : 145.0 Volts -HITRANS : 295.0 Volts -ALARMDEL : No alarm -BATTV : 13.6 Volts -LASTXFER : Automatic or explicit self test -NUMXFERS : 0 -TONBATT : 0 Seconds -CUMONBATT: 0 Seconds -XOFFBATT : N/A -SELFTEST : NG -STATFLAG : 0x05000008 -SERIALNO : 9B2414A03599 -BATTDATE : 2001-01-01 -NOMINV : 230 Volts -NOMBATTV : 12.0 Volts -NOMPOWER : 410 Watts -END APC : 2025-01-26 14:44:06 +0200 -``` - -## APC Info on Partner Nodes: - -So far, so good. Host `f0` would shut down itself when short on power. But what about the `f1` and `f2` nodes? They aren't connected directly to the UPS and, therefore, wouldn't know that their power is about to be cut off. For this, `apcupsd` running on the `f1` and `f2` nodes can be configured to retrieve UPS information via the network from the `apcupsd` server running on the `f0` node, which is connected directly to the APC via USB. - -Of course, this won't work when `f0` is down. In this case, no operational node would be connected to the UPS via USB; therefore, the current power status would not be known. However, I consider this a rare circumstance. Furthermore, in case of an `f0` system crash, sudden power outages on the two other nodes would occur at different times, making real data loss (the main concern here) effectively impossible. - -And if `f0` is down and `f1` and `f2` receive new data and crash midway, it's likely that a client (e.g., an Android app or another laptop) still has the data stored on it, making data loss recoverable. I'd receive an alert if any of the nodes go down (more on monitoring later in this blog series). - -### Installation on partners - -To do this, I installed `apcupsd` via `doas pkg install apcupsd` on `f1` and `f2`, and then I could connect to it this way: - -```sh -paul@f1:~ % apcaccess -h f0.lan.buetow.org | grep Percent -LOADPCT : 12.0 Percent -BCHARGE : 94.0 Percent -MBATTCHG : 5 Percent -``` - -But I want the daemon to be configured and enabled in such a way that it connects to the master UPS node (the one with the UPS connected via USB) so that it can also initiate a system shutdown when the UPS battery reaches low levels. For that, `apcupsd` itself needs to be aware of the UPS status. - -On `f1` and `f2`, I changed the configuration to use `f0` (where `apcupsd` is listening) as a remote device. I also changed the `MINUTES` setting from 3 to 6 and the `BATTERYLEVEL` setting from 5 to 10 to ensure that the `f1` and `f2` nodes could still connect to the `f0` node for UPS information before `f0` decides to shut down itself. So `f1` and `f2` must shut down earlier than `f0`: - -```sh -paul@f2:/usr/local/etc/apcupsd % diff -u apcupsd.conf.sample apcupsd.conf ---- apcupsd.conf.sample 2024-11-01 16:40:42.000000000 +0200 -+++ apcupsd.conf 2025-01-26 15:52:45.108469000 +0200 -@@ -31,7 +31,7 @@ - # 940-1524C, 940-0024G, 940-0095A, 940-0095B, - # 940-0095C, 940-0625A, M-04-02-2000 - # --UPSCABLE smart -+UPSCABLE ether - - # To get apcupsd to work, in addition to defining the cable - # above, you must also define a UPSTYPE, which corresponds to -@@ -52,7 +52,6 @@ - # Network Information Server. This is used if the - # UPS powering your computer is connected to a - # different computer for monitoring. --# - # snmp hostname:port:vendor:community - # SNMP network link to an SNMP-enabled UPS device. - # Hostname is the ip address or hostname of the UPS -@@ -88,8 +87,8 @@ - # that apcupsd binds to that particular unit - # (helpful if you have more than one USB UPS). - # --UPSTYPE apcsmart --DEVICE /dev/usv -+UPSTYPE net -+DEVICE f0.lan.buetow.org:3551 - - # POLLTIME - # Interval (in seconds) at which apcupsd polls the UPS for status. This -@@ -147,12 +146,12 @@ - # If during a power failure, the remaining battery percentage - # (as reported by the UPS) is below or equal to BATTERYLEVEL, - # apcupsd will initiate a system shutdown. --BATTERYLEVEL 5 -+BATTERYLEVEL 10 - - # If during a power failure, the remaining runtime in minutes - # (as calculated internally by the UPS) is below or equal to MINUTES, - # apcupsd, will initiate a system shutdown. --MINUTES 3 -+MINUTES 6 - - # If during a power failure, the UPS has run on batteries for TIMEOUT - # many seconds or longer, apcupsd will initiate a system shutdown. - -``` -So I also ran the following commands on `f1` and `f2`: - -```sh -paul@f1:/usr/local/etc/apcupsd % doas sysrc apcupsd_enable=YES -apcupsd_enable: -> YES -paul@f1:/usr/local/etc/apcupsd % doas service apcupsd start -Starting apcupsd. -``` - -And then I was able to connect to localhost via the `apcaccess` command: - -```sh -paul@f1:~ % doas apcaccess | grep Percent -LOADPCT : 5.0 Percent -BCHARGE : 95.0 Percent -MBATTCHG : 5 Percent -``` - -## Power outage simulation - -### Pulling the plug - -I simulated a power outage by removing the power input from the APC. Immediately, the following message appeared on all the nodes: - -```` -Broadcast Message from root@f0.lan.buetow.org - (no tty) at 15:03 EET... - -Power failure. Running on UPS batteries. -``` - -I ran the following command to confirm the available battery time: - -```sh -paul@f0:/usr/local/etc/apcupsd % apcaccess -p TIMELEFT -63.9 Minutes -``` - -And after almost 60 minutes (`f1` and `f2` a bit earlier, `f0` a bit later due to the different `BATTERYLEVEL` and `MINUTES` settings outlined earlier), the following broadcast was sent out: - -``` -Broadcast Message from root@f0.lan.buetow.org - (no tty) at 15:08 EET... - - *** FINAL System shutdown message from root@f0.lan.buetow.org *** - -System going down IMMEDIATELY - -apcupsd initiated shutdown -``` - -And all the nodes shut down safely before the UPS ran out of battery! - -### Restoring power - -After restoring power, I checked the logs in `/var/log/daemon.log` and found the following on all 3 nodes: - -``` -Jan 26 17:36:24 f2 apcupsd[2159]: Power failure. -Jan 26 17:36:30 f2 apcupsd[2159]: Running on UPS batteries. -Jan 26 17:36:30 f2 apcupsd[2159]: Battery charge below low limit. -Jan 26 17:36:30 f2 apcupsd[2159]: Initiating system shutdown! -Jan 26 17:36:30 f2 apcupsd[2159]: User logins prohibited -Jan 26 17:36:32 f2 apcupsd[2159]: apcupsd exiting, signal 15 -Jan 26 17:36:32 f2 apcupsd[2159]: apcupsd shutdown succeeded -``` - -All good :-) - -Other BSD related posts are: - -[2016-04-09 Jails and ZFS with Puppet on FreeBSD](./2016-04-09-jails-and-zfs-on-freebsd-with-puppet.md) -[2022-07-30 Let's Encrypt with OpenBSD and Rex](./2022-07-30-lets-encrypt-with-openbsd-and-rex.md) -[2022-10-30 Installing DTail on OpenBSD](./2022-10-30-installing-dtail-on-openbsd.md) -[2024-01-13 One reason why I love OpenBSD](./2024-01-13-one-reason-why-i-love-openbsd.md) -[2024-04-01 KISS high-availability with OpenBSD](./2024-04-01-KISS-high-availability-with-OpenBSD.md) -[2024-11-17 f3s: Kubernetes with FreeBSD - Part 1: Setting the stage](./2024-11-17-f3s-kubernetes-with-freebsd-part-1.md) -[2024-12-03 f3s: Kubernetes with FreeBSD - Part 2: Hardware and base installation](./2024-12-03-f3s-kubernetes-with-freebsd-part-2.md) -[f3s-kubernetes-with f3s: Kubernetes with FreeBSD - Rocky Linux Bhyve VMs - Part 4](./f3s-kubernetes-with-freebsd-part-4.md) - -E-Mail your comments to `paul@nospam.buetow.org` :-) - -[Back to the main site](../) diff --git a/gemfeed/DRAFT-f3s-kubernetes-with-freebsd-part-4.md b/gemfeed/DRAFT-f3s-kubernetes-with-freebsd-part-4.md new file mode 100644 index 00000000..4fc1bc63 --- /dev/null +++ b/gemfeed/DRAFT-f3s-kubernetes-with-freebsd-part-4.md @@ -0,0 +1,279 @@ +# f3s: Kubernetes with FreeBSD - Rocky Linux Bhyve VMs - Part 4 + +This is the thourth blog post about my f3s series for my self-hosting demands in my home lab. f3s? The "f" stands for FreeBSD, and the "3s" stands for k3s, the Kubernetes distribution we will use on FreeBSD-based physical machines. + +[2024-11-17 f3s: Kubernetes with FreeBSD - Part 1: Setting the stage](./2024-11-17-f3s-kubernetes-with-freebsd-part-1.md) +[2024-12-03 f3s: Kubernetes with FreeBSD - Part 2: Hardware and base installation](./2024-12-03-f3s-kubernetes-with-freebsd-part-2.md) +[2025-02-01 f3s: Kubernetes with FreeBSD - Part 3: Protecting from power cuts](./2025-02-01-f3s-kubernetes-with-freebsd-part-3.md) + +[![f3s logo](./f3s-kubernetes-with-frhyveeebsd-part-1/f3slogo.png "f3s logo")](./f3s-kubernetes-with-frhyveeebsd-part-1/f3slogo.png) + +## Table of Contents + +* [⇢ f3s: Kubernetes with FreeBSD - Rocky Linux Bhyve VMs - Part 4](#f3s-kubernetes-with-freebsd---rocky-linux-bhyve-vms---part-4) +* [⇢ ⇢ Introduction](#introduction) +* [⇢ ⇢ Check for `POPCNT` CPU support](#check-for-popcnt-cpu-support) +* [⇢ ⇢ Basic Bhyve setup](#basic-bhyve-setup) +* [⇢ ⇢ Rocky Linux VMs](#rocky-linux-vms) +* [⇢ ⇢ ⇢ ISO download](#iso-download) +* [⇢ ⇢ ⇢ VM configuration](#vm-configuration) +* [⇢ ⇢ ⇢ VM installation](#vm-installation) +* [⇢ ⇢ ⇢ Increase of the disk image](#increase-of-the-disk-image) +* [⇢ ⇢ ⇢ Connect to VPN](#connect-to-vpn) +* [⇢ ⇢ After install](#after-install) +* [⇢ ⇢ ⇢ VM auto-start after host reboot](#vm-auto-start-after-host-reboot) +* [⇢ ⇢ ⇢ Static IP configuration](#static-ip-configuration) +* [⇢ ⇢ ⇢ Permitting root login](#permitting-root-login) +* [⇢ ⇢ ⇢ Install latest updates](#install-latest-updates) + +## Introduction + +In this blog post, we are going to install the Bhyve hypervisor. + +The FreeBSD Bhyve hypervisor is a lightweight, modern hypervisor that enables virtualization on FreeBSD systems. Bhyve's strengths include its minimal overhead, which allows it to achieve near-native performance for virtual machines. It is designed to be efficient and lightweight, leveraging the capabilities of the FreeBSD operating system for performance and network management. + +Bhyve supports running a variety of guest operating systems, including FreeBSD, Linux, and Windows, on hardware platforms that support hardware virtualization extensions (such as Intel VT-x or AMD-V). In our case, we are going to virtualize Rocky Linux, which later on in this series will be used to run k3s. + +## Check for `POPCNT` CPU support + +POPCNT is a CPU instruction that counts the number of set bits (ones) in a binary number. In terms of CPU virtualization and Bhyve support for the POPCNT instruction is important because guest operating systems utilize this instruction to perform various tasks more efficiently. If the host CPU supports POPCNT, Bhyve can pass this capability to virtual machines to for better performance. Without POPCNT support, some applications might not run, or they might perform suboptimally in virtualized environments. + +To check for `POPCNT` support, I run: + +```sh +paul@f0:~ % dmesg | grep 'Features2=.*POPCNT' + Features2=0x7ffafbbf +``` + +So it's there! All good. + +## Basic Bhyve setup + +For the management of the Bhyve VMs, we are using `vm-bhyve`, a tool not part of the FreeBSD operating system but available as a ready-to-use package. It eases VM management and reduces a lot of the overhead. We also install the required package to make Bhyve work with the UEFI firmware. + +[https://github.com/churchers/vm-bhyve](https://github.com/churchers/vm-bhyve) + +The following commands are executed on all three hosts `f0`, `f1`, and `f2`, where `re0` is the name of the Ethernet interface (which may need to be adjusted if your hardware is different): + +```sh +paul@f0:~ % doas pkg install vm-bhyve bhyve-firmware +paul@f0:~ % doas sysrc vm_enable=YES +vm_enable: -> YES +paul@f0:~ % doas sysrc vm_dir=zfs:zroot/bhyve +vm_dir: -> zfs:zroot/bhyve +paul@f0:~ % doas zfs create zroot/bhyve +paul@f0:~ % doas vm init +paul@f0:~ % doas vm switch create public +paul@f0:~ % doas vm switch add public re0 +``` + +Bhyve stores all it's data in the `/bhyve` of the `zroot` ZFS pool: + +```sh +paul@f0:~ % zfs list | grep bhyve +zroot/bhyve 1.74M 453G 1.74M /zroot/bhyve +``` + +For convenience, we also create this symlink: + +```sh +paul@f0:~ % doas ln -s /zroot/bhyve/ /bhyve + +``` + +Now, Bhyve is ready to rumble, but no VMs are there yet: + +```sh +paul@f0:~ % doas vm list +NAME DATASTORE LOADER CPU MEMORY VNC AUTO STATE +``` + +## Rocky Linux VMs + +### ISO download + +We're going to install the Rocky Linux from the latest minimal iso: + +```sh +paul@f0:~ % doas vm iso \ + https://download.rockylinux.org/pub/rocky/9/isos/x86_64/Rocky-9.5-x86_64-minimal.iso +/zroot/bhyve/.iso/Rocky-9.5-x86_64-minimal.iso 1808 MB 4780 kBps 06m28s +paul@f0:/bhyve % doas vm create rocky +``` +### VM configuration + +The default configuration looks like this now: + +```sh +paul@f0:/bhyve/rocky % cat rocky.conf +loader="bhyveload" +cpu=1 +memory=256M +network0_type="virtio-net" +network0_switch="public" +disk0_type="virtio-blk" +disk0_name="disk0.img" +uuid="1c4655ac-c828-11ef-a920-e8ff1ed71ca0" +network0_mac="58:9c:fc:0d:13:3f" +``` + +Whereas the `uuid` and the `network0_mac` differ on each of the 3 hosts. + +but in order to make Rocky Linux boot it (plus some other adjustments, e.g. as I am intending to run the majority of the workload in the k3s cluster running on those linux VMs, I give them beefy specs like 4 CPU cores and 14GB RAM), I run `doas vm configure rocky` and modified it to: + +``` +guest="linux" +loader="uefi" +uefi_vars="yes" +cpu=4 +memory=14G +network0_type="virtio-net" +network0_switch="public" +disk0_type="virtio-blk" +disk0_name="disk0.img" +graphics="yes" +graphics_vga=io +uuid="1c45400b-c828-11ef-8871-e8ff1ed71cac" +network0_mac="58:9c:fc:0d:13:3f" +``` + +### VM installation + +To start the installer from the downloaded ISO, I run: + +```sh +paul@f0:~ % doas vm install rocky Rocky-9.5-x86_64-minimal.iso +Starting rocky + * found guest in /zroot/bhyve/rocky + * booting... + +paul@f0:/bhyve/rocky % doas vm list +NAME DATASTORE LOADER CPU MEMORY VNC AUTO STATE +rocky default uefi 4 14G 0.0.0.0:5900 No Locked (f0.lan.buetow.org) + +paul@f0:/bhyve/rocky % doas sockstat -4 | grep 5900 +root bhyve 6079 8 tcp4 *:5900 *:* +``` + +Port 5900 now also opened for VNC connections, so I connected to it with a VNC client and run through the installation dialogs. I'm sure this could be done unattended or more automated, there are only 3 VMs to install, and the automation doesn't seem worth it as we are doing it only once in a year or less often. + +### Increase of the disk image + +By default the VMs disk image is only 20G, which is a bit small for my purposes, so I stopped the VMs again and run `truncate` on the image file to enlarge them to 100G, and re-started the installation: + +```sh +paul@f0:/bhyve/rocky % doas vm stop rocky +paul@f0:/bhyve/rocky % doas truncate -s 100G disk0.img +paul@f0:/bhyve/rocky % doas vm install rocky Rocky-9.5-x86_64-minimal.iso +``` + +### Connect to VPN + +For the installation, I opened the VPN client on my Fedora laptop (GNOME comes with a simple VPN client) and ran through the base installation for each of the VMs manually. Again, I am sure this could have been automated a bit more, but there were just 3 VMs, and it wasn't worth the effort. The three VNC addresses of the VMs were: `vnc://f0:5900`, `vnc://f1:5900`, and `vnc://f0:5900`. + +I mostly selected the default settings (auto partitioning on the 100GB drive and a root user password). After the installation, the VMs were rebooted. + +## After install + +I performed the following steps for all 3 VMs. In the following, the examples are all executed on `f0` (bzw the VM `r0` running on `f0`): + +### VM auto-start after host reboot + +To automatically start the VM on the servers I added the following to the `rc.conf` on the FreeBSD hosts: + +```sh + +paul@f0:/bhyve/rocky % cat <>/etc/hosts +192.168.1.120 r0 r0.lan r0.lan.buetow.org +192.168.1.121 r1 r1.lan r1.lan.buetow.org +192.168.1.122 r2 r2.lan r2.lan.buetow.org +END +```` + +Whereas: + +* `192.168.1.120` is the IP of the VM itself (here: `r0.lan.buetow.org`) +* `192.168.1.1` is the address of my home router, which also does DNS. + +### Permitting root login + +As these VMs arent directly reachable via SSH from the internet, I enabled `root` login by adding a line with `PermitRootLogin yes` to `/etc/sshd/sshd_config`. + +Once done, I rebooted the VM by running `reboot` inside of the vm to test whether everything was configured and persisted correctly. + +After reboot, I copied my public key from my Laptop to the 3 VMs: + +```sh +% for i in 0 1 2; do ssh-copy-id root@r$i.lan.buetow.org; done +``` + +And then I edited the `/etc/ssh/sshd_config` file again on all 3 VMs and configured `PasswordAuthentication no`, to only allow SSH key authentication from now on. + +### Install latest updates + +```sh +[root@r0 ~] % dnf update +[root@r0 ~] % dreboot +``` + +CPU STRESS TESTER VM VS NOT VM + +Other *BSD-related posts: + +[2016-04-09 Jails and ZFS with Puppet on FreeBSD](./2016-04-09-jails-and-zfs-on-freebsd-with-puppet.md) +[2022-07-30 Let's Encrypt with OpenBSD and Rex](./2022-07-30-lets-encrypt-with-openbsd-and-rex.md) +[2022-10-30 Installing DTail on OpenBSD](./2022-10-30-installing-dtail-on-openbsd.md) +[2024-01-13 One reason why I love OpenBSD](./2024-01-13-one-reason-why-i-love-openbsd.md) +[2024-04-01 KISS high-availability with OpenBSD](./2024-04-01-KISS-high-availability-with-OpenBSD.md) +[2024-11-17 f3s: Kubernetes with FreeBSD - Part 1: Setting the stage](./2024-11-17-f3s-kubernetes-with-freebsd-part-1.md) +[2024-12-03 f3s: Kubernetes with FreeBSD - Part 2: Hardware and base installation](./2024-12-03-f3s-kubernetes-with-freebsd-part-2.md) +[2025-02-01 f3s: Kubernetes with FreeBSD - Part 3: Protecting from power cuts](./2025-02-01-f3s-kubernetes-with-freebsd-part-3.md) + +E-Mail your comments to `paul@nospam.buetow.org` :-) + +[Back to the main site](../) diff --git a/gemfeed/f3s-kubernetes-with-freebsd-part-4.md b/gemfeed/f3s-kubernetes-with-freebsd-part-4.md deleted file mode 100644 index 0b922c41..00000000 --- a/gemfeed/f3s-kubernetes-with-freebsd-part-4.md +++ /dev/null @@ -1,263 +0,0 @@ -# f3s: Kubernetes with FreeBSD - Rocky Linux Bhyve VMs - Part 4 - -This is the thourth blog post about my f3s series for my self-hosting demands in my home lab. f3s? The "f" stands for FreeBSD, and the "3s" stands for k3s, the Kubernetes distribution we will use on FreeBSD-based physical machines. - -[2024-11-17 f3s: Kubernetes with FreeBSD - Part 1: Setting the stage](./2024-11-17-f3s-kubernetes-with-freebsd-part-1.md) -[2024-12-03 f3s: Kubernetes with FreeBSD - Part 2: Hardware and base installation](./2024-12-03-f3s-kubernetes-with-freebsd-part-2.md) -[f3s-kubernetes-with f3s: Kubernetes with FreeBSD - Rocky Linux Bhyve VMs - Part 4 (You are currently reading this)](./f3s-kubernetes-with-freebsd-part-4.md) - -[![f3s logo](./f3s-kubernetes-with-frhyveeebsd-part-1/f3slogo.png "f3s logo")](./f3s-kubernetes-with-frhyveeebsd-part-1/f3slogo.png) - -## Table of Contents - -* [⇢ f3s: Kubernetes with FreeBSD - Rocky Linux Bhyve VMs - Part 4](#f3s-kubernetes-with-freebsd---rocky-linux-bhyve-vms---part-4) -* [⇢ ⇢ Introduction](#introduction) -* [⇢ ⇢ Basic Bhyve setup](#basic-bhyve-setup) -* [⇢ ⇢ Rocky Linux VMs](#rocky-linux-vms) -* [⇢ ⇢ ⇢ ISO download](#iso-download) -* [⇢ ⇢ ⇢ VM configuration](#vm-configuration) -* [⇢ ⇢ ⇢ VM installation](#vm-installation) -* [⇢ ⇢ ⇢ Increase of the disk image](#increase-of-the-disk-image) -* [⇢ ⇢ ⇢ Connect to VPN](#connect-to-vpn) -* [⇢ ⇢ After install](#after-install) -* [⇢ ⇢ ⇢ VM auto-start after host reboot](#vm-auto-start-after-host-reboot) -* [⇢ ⇢ ⇢ Static IP configuration](#static-ip-configuration) -* [⇢ ⇢ ⇢ Permitting root login](#permitting-root-login) -* [⇢ ⇢ ⇢ Install latest updates](#install-latest-updates) - -## Introduction - -In this blog post, we are going to install the Bhyve hypervisor. - -The FreeBSD Bhyve hypervisor is a lightweight, modern hypervisor that enables virtualization on FreeBSD systems. Bhyve's strengths include its minimal overhead, which allows it to achieve near-native performance for virtual machines. It is designed to be efficient and lightweight, leveraging the capabilities of the FreeBSD operating system for performance and network management. - -Bhyve supports running a variety of guest operating systems, including FreeBSD, Linux, and Windows, on hardware platforms that support hardware virtualization extensions (such as Intel VT-x or AMD-V). In our case, we are going to virtualize Rocky Linux, which later on in this series will be used to run k3s. - -## Basic Bhyve setup - -For the management of the Bhyve VMs, we are using `vm-bhyve`, a tool not part of the FreeBSD operating system but available as a ready-to-use package. It eases VM management and reduces a lot of the overhead. We also install the required package to make Bhyve work with the UEFI firmware. - -[https://github.com/churchers/vm-bhyve](https://github.com/churchers/vm-bhyve) - -The following commands are executed on all three hosts `f0`, `f1`, and `f2`, where `re0` is the name of the Ethernet interface (which may need to be adjusted if your hardware is different): - -```sh -paul@f0:~ % doas pkg install vm-bhyve bhyve-firmware -paul@f0:~ % doas sysrc vm_enable=YES -vm_enable: -> YES -paul@f0:~ % doas sysrc vm_dir=zfs:zroot/bhyve -vm_dir: -> zfs:zroot/bhyve -paul@f0:~ % doas zfs create zroot/bhyve -paul@f0:~ % doas vm init -paul@f0:~ % doas vm switch create public -paul@f0:~ % doas vm switch add public re0 -``` - -Bhyve stores all it's data in the `/bhyve` of the `zroot` ZFS pool: - -```sh -paul@f0:~ % zfs list | grep bhyve -zroot/bhyve 1.74M 453G 1.74M /zroot/bhyve -``` - -For convenience, we also create this symlink: - -```sh -paul@f0:~ % doas ln -s /zroot/bhyve/ /bhyve - -``` - -Now, Bhyve is ready to rumble, but no VMs are there yet: - -```sh -paul@f0:~ % doas vm list -NAME DATASTORE LOADER CPU MEMORY VNC AUTO STATE -``` - -## Rocky Linux VMs - -### ISO download - -We're going to install the Rocky Linux from the latest minimal iso: - -```sh -paul@f0:~ % doas vm iso \ - https://download.rockylinux.org/pub/rocky/9/isos/x86_64/Rocky-9.5-x86_64-minimal.iso -/zroot/bhyve/.iso/Rocky-9.5-x86_64-minimal.iso 1808 MB 4780 kBps 06m28s -paul@f0:/bhyve % doas vm create rocky -``` -### VM configuration - -The default configuration looks like this now: - -```sh -paul@f0:/bhyve/rocky % cat rocky.conf -loader="bhyveload" -cpu=1 -memory=256M -network0_type="virtio-net" -network0_switch="public" -disk0_type="virtio-blk" -disk0_name="disk0.img" -uuid="1c4655ac-c828-11ef-a920-e8ff1ed71ca0" -network0_mac="58:9c:fc:0d:13:3f" -``` - -Whereas the `uuid` and the `network0_mac` differ on each of the 3 hosts. - -but in order to make Rocky Linux boot it (plus some other adjustments, e.g. as I am intending to run the majority of the workload in the k3s cluster running on those linux VMs, I give them beefy specs like 4 CPU cores and 14GB RAM), I run `doas vm configure rocky` and modified it to: - -``` -guest="linux" -loader="uefi" -uefi_vars="yes" -cpu=4 -memory=14G -network0_type="virtio-net" -network0_switch="public" -disk0_type="virtio-blk" -disk0_name="disk0.img" -graphics="yes" -graphics_vga=io -uuid="1c45400b-c828-11ef-8871-e8ff1ed71cac" -network0_mac="58:9c:fc:0d:13:3f" -``` - -### VM installation - -To start the installer from the downloaded ISO, I run: - -```sh -paul@f0:~ % doas vm install rocky Rocky-9.5-x86_64-minimal.iso -Starting rocky - * found guest in /zroot/bhyve/rocky - * booting... - -paul@f0:/bhyve/rocky % doas vm list -NAME DATASTORE LOADER CPU MEMORY VNC AUTO STATE -rocky default uefi 4 14G 0.0.0.0:5900 No Locked (f0.lan.buetow.org) - -paul@f0:/bhyve/rocky % doas sockstat -4 | grep 5900 -root bhyve 6079 8 tcp4 *:5900 *:* -``` - -Port 5900 now also opened for VNC connections, so I connected to it with a VNC client and run through the installation dialogs. I'm sure this could be done unattended or more automated, there are only 3 VMs to install, and the automation doesn't seem worth it as we are doing it only once in a year or less often. - -### Increase of the disk image - -By default the VMs disk image is only 20G, which is a bit small for my purposes, so I stopped the VMs again and run `truncate` on the image file to enlarge them to 100G, and re-started the installation: - -```sh -paul@f0:/bhyve/rocky % doas vm stop rocky -paul@f0:/bhyve/rocky % doas truncate -s 100G disk0.img -paul@f0:/bhyve/rocky % doas vm install rocky Rocky-9.5-x86_64-minimal.iso -``` - -### Connect to VPN - -For the installation, I opened the VPN client on my Fedora laptop (GNOME comes with a simple VPN client) and ran through the base installation for each of the VMs manually. Again, I am sure this could have been automated a bit more, but there were just 3 VMs, and it wasn't worth the effort. The three VNC addresses of the VMs were: `vnc://f0:5900`, `vnc://f1:5900`, and `vnc://f0:5900`. - -I mostly selected the default settings (auto partitioning on the 100GB drive and a root user password). After the installation, the VMs were rebooted. - -## After install - -I performed the following steps for all 3 VMs. In the following, the examples are all executed on `f0` (bzw the VM `r0` running on `f0`): - -### VM auto-start after host reboot - -To automatically start the VM on the servers I added the following to the `rc.conf` on the FreeBSD hosts: - -```sh - -paul@f0:/bhyve/rocky % cat <>/etc/hosts -192.168.1.120 r0 r0.lan r0.lan.buetow.org -192.168.1.121 r1 r1.lan r1.lan.buetow.org -192.168.1.122 r2 r2.lan r2.lan.buetow.org -END -```` - -Whereas: - -* `192.168.1.120` is the IP of the VM itself (here: `r0.lan.buetow.org`) -* `192.168.1.1` is the address of my home router, which also does DNS. - -### Permitting root login - -As these VMs arent directly reachable via SSH from the internet, I enabled `root` login by adding a line with `PermitRootLogin yes` to `/etc/sshd/sshd_config`. - -Once done, I rebooted the VM by running `reboot` inside of the vm to test whether everything was configured and persisted correctly. - -After reboot, I copied my public key from my Laptop to the 3 VMs: - -```sh -% for i in 0 1 2; do ssh-copy-id root@r$i.lan.buetow.org; done -``` - -And then I edited the `/etc/ssh/sshd_config` file again on all 3 VMs and configured `PasswordAuthentication no`, to only allow SSH key authentication from now on. - -### Install latest updates - -```sh -[root@r0 ~] % dnf update -[root@r0 ~] % dreboot -``` - -CPU STRESS TESTER VM VS NOT VM - -Other *BSD-related posts: - -[2016-04-09 Jails and ZFS with Puppet on FreeBSD](./2016-04-09-jails-and-zfs-on-freebsd-with-puppet.md) -[2022-07-30 Let's Encrypt with OpenBSD and Rex](./2022-07-30-lets-encrypt-with-openbsd-and-rex.md) -[2022-10-30 Installing DTail on OpenBSD](./2022-10-30-installing-dtail-on-openbsd.md) -[2024-01-13 One reason why I love OpenBSD](./2024-01-13-one-reason-why-i-love-openbsd.md) -[2024-04-01 KISS high-availability with OpenBSD](./2024-04-01-KISS-high-availability-with-OpenBSD.md) -[2024-11-17 f3s: Kubernetes with FreeBSD - Part 1: Setting the stage](./2024-11-17-f3s-kubernetes-with-freebsd-part-1.md) -[2024-12-03 f3s: Kubernetes with FreeBSD - Part 2: Hardware and base installation](./2024-12-03-f3s-kubernetes-with-freebsd-part-2.md) -[f3s-kubernetes-with f3s: Kubernetes with FreeBSD - Rocky Linux Bhyve VMs - Part 4 (You are currently reading this)](./f3s-kubernetes-with-freebsd-part-4.md) - -E-Mail your comments to `paul@nospam.buetow.org` :-) - -[Back to the main site](../) diff --git a/gemfeed/index.md b/gemfeed/index.md index 1650a18b..fd0b09be 100644 --- a/gemfeed/index.md +++ b/gemfeed/index.md @@ -2,6 +2,7 @@ ## To be in the .zone! +[2025-02-01 - f3s: Kubernetes with FreeBSD - Part 3: Protecting from power cuts](./2025-02-01-f3s-kubernetes-with-freebsd-part-3.md) [2025-01-15 - Working with an SRE Interview](./2025-01-15-working-with-an-sre-interview.md) [2025-01-01 - Posts from October to December 2024](./2025-01-01-posts-from-october-to-december-2024.md) [2024-12-15 - Random Helix Themes](./2024-12-15-random-helix-themes.md) -- cgit v1.2.3 From 2c9b8ed56e3c314ffc5874649b8285684dc0d8ee Mon Sep 17 00:00:00 2001 From: Paul Buetow Date: Thu, 30 Jan 2025 09:40:57 +0200 Subject: Update content for md --- gemfeed/2025-02-01-f3s-kubernetes-with-freebsd-part-3.md | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) (limited to 'gemfeed') diff --git a/gemfeed/2025-02-01-f3s-kubernetes-with-freebsd-part-3.md b/gemfeed/2025-02-01-f3s-kubernetes-with-freebsd-part-3.md index db891ddb..a464f44f 100644 --- a/gemfeed/2025-02-01-f3s-kubernetes-with-freebsd-part-3.md +++ b/gemfeed/2025-02-01-f3s-kubernetes-with-freebsd-part-3.md @@ -319,7 +319,7 @@ paul@f0:/usr/local/etc/apcupsd % apcaccess -p TIMELEFT 63.9 Minutes ``` -And after almost 60 minutes (`f1` and `f2` a bit earlier, `f0` a bit later due to the different `BATTERYLEVEL` and `MINUTES` settings outlined earlier), the following broadcast was sent out: +And after around one hour (`f1` and `f2` a bit earlier, `f0` a bit later due to the different `BATTERYLEVEL` and `MINUTES` settings outlined earlier), the following broadcast was sent out: ``` Broadcast Message from root@f0.lan.buetow.org -- cgit v1.2.3 From 37097c57e23d79f444123324b54124c1d9710ff2 Mon Sep 17 00:00:00 2001 From: Paul Buetow Date: Sun, 2 Feb 2025 10:47:37 +0200 Subject: Update content for md --- gemfeed/2008-06-26-perl-poetry.md | 4 ++-- gemfeed/2011-05-07-perl-daemon-service-framework.md | 4 ++-- .../2016-04-09-jails-and-zfs-on-freebsd-with-puppet.md | 14 +++++++------- ...021-04-22-dtail-the-distributed-log-tail-program.md | 6 +++--- gemfeed/2021-04-24-welcome-to-the-geminispace.md | 10 +++++----- gemfeed/2021-05-16-personal-bash-coding-style-guide.md | 8 ++++---- ...1-06-05-gemtexter-one-bash-script-to-rule-it-all.md | 18 +++++++++--------- gemfeed/2021-09-12-keep-it-simple-and-stupid.md | 6 +++--- gemfeed/2021-11-29-bash-golf-part-1.md | 12 ++++++------ gemfeed/2022-01-01-bash-golf-part-2.md | 12 ++++++------ gemfeed/2022-03-06-the-release-of-dtail-4.0.0.md | 6 +++--- gemfeed/2022-05-27-perl-is-still-a-great-choice.md | 6 +++--- .../2022-07-30-lets-encrypt-with-openbsd-and-rex.md | 14 +++++++------- .../2022-08-27-gemtexter-1.1.0-lets-gemtext-again.md | 10 +++++----- gemfeed/2022-10-30-installing-dtail-on-openbsd.md | 6 +++--- .../2023-03-16-the-pragmatic-programmer-book-notes.md | 14 +++++++------- .../2023-03-25-gemtexter-2.0.0-lets-gemtext-again-2.md | 10 +++++----- ...2023-04-01-never-split-the-difference-book-notes.md | 14 +++++++------- ...1-unveiling-guprecords:-uptime-records-with-raku.md | 8 ++++---- .../2023-05-06-the-obstacle-is-the-way-book-notes.md | 14 +++++++------- .../2023-06-01-kiss-server-monitoring-with-gogios.md | 6 +++--- ...23-07-17-career-guide-and-soft-skills-book-notes.md | 14 +++++++------- .../2023-07-21-gemtexter-2.1.0-lets-gemtext-again-3.md | 10 +++++----- .../2023-08-18-site-reliability-engineering-part-1.md | 6 +++--- gemfeed/2023-09-25-dtail-usage-examples.md | 6 +++--- ...-kiss-static-web-photo-albums-with-photoalbum.sh.md | 16 ++++++++-------- gemfeed/2023-11-11-mind-management-book-notes.md | 14 +++++++------- .../2023-11-19-site-reliability-engineering-part-2.md | 6 +++--- gemfeed/2023-12-10-bash-golf-part-3.md | 12 ++++++------ .../2024-01-09-site-reliability-engineering-part-3.md | 6 +++--- gemfeed/2024-01-13-one-reason-why-i-love-openbsd.md | 14 +++++++------- .../2024-04-01-KISS-high-availability-with-OpenBSD.md | 18 +++++++++--------- gemfeed/2024-05-01-slow-productivity-book-notes.md | 14 +++++++------- gemfeed/2024-07-07-the-stoic-challenge-book-notes.md | 14 +++++++------- .../2024-09-07-site-reliability-engineering-part-4.md | 6 +++--- .../2024-10-02-gemtexter-3.0.0-lets-gemtext-again-4.md | 10 +++++----- gemfeed/2024-10-24-staff-engineer-book-notes.md | 14 +++++++------- .../2024-11-17-f3s-kubernetes-with-freebsd-part-1.md | 18 +++++++++--------- .../2024-12-03-f3s-kubernetes-with-freebsd-part-2.md | 18 +++++++++--------- .../2025-02-01-f3s-kubernetes-with-freebsd-part-3.md | 18 +++++++++--------- gemfeed/DRAFT-f3s-kubernetes-with-freebsd-part-4.md | 18 +++++++++--------- 41 files changed, 227 insertions(+), 227 deletions(-) (limited to 'gemfeed') diff --git a/gemfeed/2008-06-26-perl-poetry.md b/gemfeed/2008-06-26-perl-poetry.md index e64cd0f4..5256e765 100644 --- a/gemfeed/2008-06-26-perl-poetry.md +++ b/gemfeed/2008-06-26-perl-poetry.md @@ -173,8 +173,8 @@ E-Mail your comments to `paul@nospam.buetow.org` :-) Other related posts are: -[2008-06-26 Perl Poetry (You are currently reading this)](./2008-06-26-perl-poetry.md) -[2011-05-07 Perl Daemon (Service Framework)](./2011-05-07-perl-daemon-service-framework.md) [2022-05-27 Perl is still a great choice](./2022-05-27-perl-is-still-a-great-choice.md) +[2011-05-07 Perl Daemon (Service Framework)](./2011-05-07-perl-daemon-service-framework.md) +[2008-06-26 Perl Poetry (You are currently reading this)](./2008-06-26-perl-poetry.md) [Back to the main site](../) diff --git a/gemfeed/2011-05-07-perl-daemon-service-framework.md b/gemfeed/2011-05-07-perl-daemon-service-framework.md index 7364826f..10588124 100644 --- a/gemfeed/2011-05-07-perl-daemon-service-framework.md +++ b/gemfeed/2011-05-07-perl-daemon-service-framework.md @@ -175,8 +175,8 @@ E-Mail your comments to `paul@nospam.buetow.org` :-) Other related posts are: -[2008-06-26 Perl Poetry](./2008-06-26-perl-poetry.md) -[2011-05-07 Perl Daemon (Service Framework) (You are currently reading this)](./2011-05-07-perl-daemon-service-framework.md) [2022-05-27 Perl is still a great choice](./2022-05-27-perl-is-still-a-great-choice.md) +[2011-05-07 Perl Daemon (Service Framework) (You are currently reading this)](./2011-05-07-perl-daemon-service-framework.md) +[2008-06-26 Perl Poetry](./2008-06-26-perl-poetry.md) [Back to the main site](../) diff --git a/gemfeed/2016-04-09-jails-and-zfs-on-freebsd-with-puppet.md b/gemfeed/2016-04-09-jails-and-zfs-on-freebsd-with-puppet.md index e21375d1..793ee5a7 100644 --- a/gemfeed/2016-04-09-jails-and-zfs-on-freebsd-with-puppet.md +++ b/gemfeed/2016-04-09-jails-and-zfs-on-freebsd-with-puppet.md @@ -397,13 +397,13 @@ E-Mail your comments to `paul@nospam.buetow.org` :-) Other *BSD related posts are: -[2016-04-09 Jails and ZFS with Puppet on FreeBSD (You are currently reading this)](./2016-04-09-jails-and-zfs-on-freebsd-with-puppet.md) -[2022-07-30 Let's Encrypt with OpenBSD and Rex](./2022-07-30-lets-encrypt-with-openbsd-and-rex.md) -[2022-10-30 Installing DTail on OpenBSD](./2022-10-30-installing-dtail-on-openbsd.md) -[2024-01-13 One reason why I love OpenBSD](./2024-01-13-one-reason-why-i-love-openbsd.md) -[2024-04-01 KISS high-availability with OpenBSD](./2024-04-01-KISS-high-availability-with-OpenBSD.md) -[2024-11-17 f3s: Kubernetes with FreeBSD - Part 1: Setting the stage](./2024-11-17-f3s-kubernetes-with-freebsd-part-1.md) -[2024-12-03 f3s: Kubernetes with FreeBSD - Part 2: Hardware and base installation](./2024-12-03-f3s-kubernetes-with-freebsd-part-2.md) [2025-02-01 f3s: Kubernetes with FreeBSD - Part 3: Protecting from power cuts](./2025-02-01-f3s-kubernetes-with-freebsd-part-3.md) +[2024-12-03 f3s: Kubernetes with FreeBSD - Part 2: Hardware and base installation](./2024-12-03-f3s-kubernetes-with-freebsd-part-2.md) +[2024-11-17 f3s: Kubernetes with FreeBSD - Part 1: Setting the stage](./2024-11-17-f3s-kubernetes-with-freebsd-part-1.md) +[2024-04-01 KISS high-availability with OpenBSD](./2024-04-01-KISS-high-availability-with-OpenBSD.md) +[2024-01-13 One reason why I love OpenBSD](./2024-01-13-one-reason-why-i-love-openbsd.md) +[2022-10-30 Installing DTail on OpenBSD](./2022-10-30-installing-dtail-on-openbsd.md) +[2022-07-30 Let's Encrypt with OpenBSD and Rex](./2022-07-30-lets-encrypt-with-openbsd-and-rex.md) +[2016-04-09 Jails and ZFS with Puppet on FreeBSD (You are currently reading this)](./2016-04-09-jails-and-zfs-on-freebsd-with-puppet.md) [Back to the main site](../) diff --git a/gemfeed/2021-04-22-dtail-the-distributed-log-tail-program.md b/gemfeed/2021-04-22-dtail-the-distributed-log-tail-program.md index 0caa64b0..d5147829 100644 --- a/gemfeed/2021-04-22-dtail-the-distributed-log-tail-program.md +++ b/gemfeed/2021-04-22-dtail-the-distributed-log-tail-program.md @@ -120,9 +120,9 @@ E-Mail your comments to `paul@nospam.buetow.org` :-) Other related posts are: -[2021-04-22 DTail - The distributed log tail program (You are currently reading this)](./2021-04-22-dtail-the-distributed-log-tail-program.md) -[2022-03-06 The release of DTail 4.0.0](./2022-03-06-the-release-of-dtail-4.0.0.md) -[2022-10-30 Installing DTail on OpenBSD](./2022-10-30-installing-dtail-on-openbsd.md) [2023-09-25 DTail usage examples](./2023-09-25-dtail-usage-examples.md) +[2022-10-30 Installing DTail on OpenBSD](./2022-10-30-installing-dtail-on-openbsd.md) +[2022-03-06 The release of DTail 4.0.0](./2022-03-06-the-release-of-dtail-4.0.0.md) +[2021-04-22 DTail - The distributed log tail program (You are currently reading this)](./2021-04-22-dtail-the-distributed-log-tail-program.md) [Back to the main site](../) diff --git a/gemfeed/2021-04-24-welcome-to-the-geminispace.md b/gemfeed/2021-04-24-welcome-to-the-geminispace.md index 17d3291f..662328da 100644 --- a/gemfeed/2021-04-24-welcome-to-the-geminispace.md +++ b/gemfeed/2021-04-24-welcome-to-the-geminispace.md @@ -94,11 +94,11 @@ E-Mail your comments to `paul@nospam.buetow.org` :-) Other related posts are: -[2021-04-24 Welcome to the Geminispace (You are currently reading this)](./2021-04-24-welcome-to-the-geminispace.md) -[2021-06-05 Gemtexter - One Bash script to rule it all](./2021-06-05-gemtexter-one-bash-script-to-rule-it-all.md) -[2022-08-27 Gemtexter 1.1.0 - Let's Gemtext again](./2022-08-27-gemtexter-1.1.0-lets-gemtext-again.md) -[2023-03-25 Gemtexter 2.0.0 - Let's Gemtext again²](./2023-03-25-gemtexter-2.0.0-lets-gemtext-again-2.md) -[2023-07-21 Gemtexter 2.1.0 - Let's Gemtext again³](./2023-07-21-gemtexter-2.1.0-lets-gemtext-again-3.md) [2024-10-02 Gemtexter 3.0.0 - Let's Gemtext again⁴](./2024-10-02-gemtexter-3.0.0-lets-gemtext-again-4.md) +[2023-07-21 Gemtexter 2.1.0 - Let's Gemtext again³](./2023-07-21-gemtexter-2.1.0-lets-gemtext-again-3.md) +[2023-03-25 Gemtexter 2.0.0 - Let's Gemtext again²](./2023-03-25-gemtexter-2.0.0-lets-gemtext-again-2.md) +[2022-08-27 Gemtexter 1.1.0 - Let's Gemtext again](./2022-08-27-gemtexter-1.1.0-lets-gemtext-again.md) +[2021-06-05 Gemtexter - One Bash script to rule it all](./2021-06-05-gemtexter-one-bash-script-to-rule-it-all.md) +[2021-04-24 Welcome to the Geminispace (You are currently reading this)](./2021-04-24-welcome-to-the-geminispace.md) [Back to the main site](../) diff --git a/gemfeed/2021-05-16-personal-bash-coding-style-guide.md b/gemfeed/2021-05-16-personal-bash-coding-style-guide.md index d2c0f050..4f1b8152 100644 --- a/gemfeed/2021-05-16-personal-bash-coding-style-guide.md +++ b/gemfeed/2021-05-16-personal-bash-coding-style-guide.md @@ -409,10 +409,10 @@ E-Mail your comments to `paul@nospam.buetow.org` :-) Other related posts are: -[2021-05-16 Personal Bash coding style guide (You are currently reading this)](./2021-05-16-personal-bash-coding-style-guide.md) -[2021-06-05 Gemtexter - One Bash script to rule it all](./2021-06-05-gemtexter-one-bash-script-to-rule-it-all.md) -[2021-11-29 Bash Golf Part 1](./2021-11-29-bash-golf-part-1.md) -[2022-01-01 Bash Golf Part 2](./2022-01-01-bash-golf-part-2.md) [2023-12-10 Bash Golf Part 3](./2023-12-10-bash-golf-part-3.md) +[2022-01-01 Bash Golf Part 2](./2022-01-01-bash-golf-part-2.md) +[2021-11-29 Bash Golf Part 1](./2021-11-29-bash-golf-part-1.md) +[2021-06-05 Gemtexter - One Bash script to rule it all](./2021-06-05-gemtexter-one-bash-script-to-rule-it-all.md) +[2021-05-16 Personal Bash coding style guide (You are currently reading this)](./2021-05-16-personal-bash-coding-style-guide.md) [Back to the main site](../) diff --git a/gemfeed/2021-06-05-gemtexter-one-bash-script-to-rule-it-all.md b/gemfeed/2021-06-05-gemtexter-one-bash-script-to-rule-it-all.md index 1766c067..56e8df6a 100644 --- a/gemfeed/2021-06-05-gemtexter-one-bash-script-to-rule-it-all.md +++ b/gemfeed/2021-06-05-gemtexter-one-bash-script-to-rule-it-all.md @@ -183,15 +183,15 @@ E-Mail your comments to `paul@nospam.buetow.org` :-) Other related posts are: -[2021-04-24 Welcome to the Geminispace](./2021-04-24-welcome-to-the-geminispace.md) -[2021-05-16 Personal Bash coding style guide](./2021-05-16-personal-bash-coding-style-guide.md) -[2021-06-05 Gemtexter - One Bash script to rule it all (You are currently reading this)](./2021-06-05-gemtexter-one-bash-script-to-rule-it-all.md) -[2021-11-29 Bash Golf Part 1](./2021-11-29-bash-golf-part-1.md) -[2022-01-01 Bash Golf Part 2](./2022-01-01-bash-golf-part-2.md) -[2022-08-27 Gemtexter 1.1.0 - Let's Gemtext again](./2022-08-27-gemtexter-1.1.0-lets-gemtext-again.md) -[2023-03-25 Gemtexter 2.0.0 - Let's Gemtext again²](./2023-03-25-gemtexter-2.0.0-lets-gemtext-again-2.md) -[2023-07-21 Gemtexter 2.1.0 - Let's Gemtext again³](./2023-07-21-gemtexter-2.1.0-lets-gemtext-again-3.md) -[2023-12-10 Bash Golf Part 3](./2023-12-10-bash-golf-part-3.md) [2024-10-02 Gemtexter 3.0.0 - Let's Gemtext again⁴](./2024-10-02-gemtexter-3.0.0-lets-gemtext-again-4.md) +[2023-12-10 Bash Golf Part 3](./2023-12-10-bash-golf-part-3.md) +[2023-07-21 Gemtexter 2.1.0 - Let's Gemtext again³](./2023-07-21-gemtexter-2.1.0-lets-gemtext-again-3.md) +[2023-03-25 Gemtexter 2.0.0 - Let's Gemtext again²](./2023-03-25-gemtexter-2.0.0-lets-gemtext-again-2.md) +[2022-08-27 Gemtexter 1.1.0 - Let's Gemtext again](./2022-08-27-gemtexter-1.1.0-lets-gemtext-again.md) +[2022-01-01 Bash Golf Part 2](./2022-01-01-bash-golf-part-2.md) +[2021-11-29 Bash Golf Part 1](./2021-11-29-bash-golf-part-1.md) +[2021-06-05 Gemtexter - One Bash script to rule it all (You are currently reading this)](./2021-06-05-gemtexter-one-bash-script-to-rule-it-all.md) +[2021-05-16 Personal Bash coding style guide](./2021-05-16-personal-bash-coding-style-guide.md) +[2021-04-24 Welcome to the Geminispace](./2021-04-24-welcome-to-the-geminispace.md) [Back to the main site](../) diff --git a/gemfeed/2021-09-12-keep-it-simple-and-stupid.md b/gemfeed/2021-09-12-keep-it-simple-and-stupid.md index a8617c16..8663debe 100644 --- a/gemfeed/2021-09-12-keep-it-simple-and-stupid.md +++ b/gemfeed/2021-09-12-keep-it-simple-and-stupid.md @@ -115,10 +115,10 @@ E-Mail your comments to `paul@nospam.buetow.org` :-) Other KISS-related posts are: -[2021-09-12 Keep it simple and stupid (You are currently reading this)](./2021-09-12-keep-it-simple-and-stupid.md) -[2023-06-01 KISS server monitoring with Gogios](./2023-06-01-kiss-server-monitoring-with-gogios.md) -[2023-10-29 KISS static web photo albums with `photoalbum.sh`](./2023-10-29-kiss-static-web-photo-albums-with-photoalbum.sh.md) [2024-04-01 KISS high-availability with OpenBSD](./2024-04-01-KISS-high-availability-with-OpenBSD.md) +[2023-10-29 KISS static web photo albums with `photoalbum.sh`](./2023-10-29-kiss-static-web-photo-albums-with-photoalbum.sh.md) +[2023-06-01 KISS server monitoring with Gogios](./2023-06-01-kiss-server-monitoring-with-gogios.md) +[2021-09-12 Keep it simple and stupid (You are currently reading this)](./2021-09-12-keep-it-simple-and-stupid.md) > Controversially, a lack of features is a feature. Enjoy your peace an quiet. - Michael W Lucas diff --git a/gemfeed/2021-11-29-bash-golf-part-1.md b/gemfeed/2021-11-29-bash-golf-part-1.md index a9f0c793..b7959f14 100644 --- a/gemfeed/2021-11-29-bash-golf-part-1.md +++ b/gemfeed/2021-11-29-bash-golf-part-1.md @@ -4,9 +4,9 @@ This is the first blog post about my Bash Golf series. This series is about random Bash tips, tricks and weirdnesses I came across. It's a collection of smaller articles I wrote in an older (in German language) blog, which I translated and refreshed with some new content. -[2021-11-29 Bash Golf Part 1 (You are currently reading this)](./2021-11-29-bash-golf-part-1.md) -[2022-01-01 Bash Golf Part 2](./2022-01-01-bash-golf-part-2.md) [2023-12-10 Bash Golf Part 3](./2023-12-10-bash-golf-part-3.md) +[2022-01-01 Bash Golf Part 2](./2022-01-01-bash-golf-part-2.md) +[2021-11-29 Bash Golf Part 1 (You are currently reading this)](./2021-11-29-bash-golf-part-1.md) ``` @@ -480,10 +480,10 @@ E-Mail your comments to `paul@nospam.buetow.org` :-) Other related posts are: -[2021-05-16 Personal Bash coding style guide](./2021-05-16-personal-bash-coding-style-guide.md) -[2021-06-05 Gemtexter - One Bash script to rule it all](./2021-06-05-gemtexter-one-bash-script-to-rule-it-all.md) -[2021-11-29 Bash Golf Part 1 (You are currently reading this)](./2021-11-29-bash-golf-part-1.md) -[2022-01-01 Bash Golf Part 2](./2022-01-01-bash-golf-part-2.md) [2023-12-10 Bash Golf Part 3](./2023-12-10-bash-golf-part-3.md) +[2022-01-01 Bash Golf Part 2](./2022-01-01-bash-golf-part-2.md) +[2021-11-29 Bash Golf Part 1 (You are currently reading this)](./2021-11-29-bash-golf-part-1.md) +[2021-06-05 Gemtexter - One Bash script to rule it all](./2021-06-05-gemtexter-one-bash-script-to-rule-it-all.md) +[2021-05-16 Personal Bash coding style guide](./2021-05-16-personal-bash-coding-style-guide.md) [Back to the main site](../) diff --git a/gemfeed/2022-01-01-bash-golf-part-2.md b/gemfeed/2022-01-01-bash-golf-part-2.md index d1330128..1f028f18 100644 --- a/gemfeed/2022-01-01-bash-golf-part-2.md +++ b/gemfeed/2022-01-01-bash-golf-part-2.md @@ -4,9 +4,9 @@ This is the second blog post about my Bash Golf series. This series is random Bash tips, tricks and weirdnesses I came across. It's a collection of smaller articles I wrote in an older (in German language) blog, which I translated and refreshed with some new content. -[2021-11-29 Bash Golf Part 1](./2021-11-29-bash-golf-part-1.md) -[2022-01-01 Bash Golf Part 2 (You are currently reading this)](./2022-01-01-bash-golf-part-2.md) [2023-12-10 Bash Golf Part 3](./2023-12-10-bash-golf-part-3.md) +[2022-01-01 Bash Golf Part 2 (You are currently reading this)](./2022-01-01-bash-golf-part-2.md) +[2021-11-29 Bash Golf Part 1](./2021-11-29-bash-golf-part-1.md) ``` @@ -498,10 +498,10 @@ E-Mail your comments to `paul@nospam.buetow.org` :-) Other related posts are: -[2021-05-16 Personal Bash coding style guide](./2021-05-16-personal-bash-coding-style-guide.md) -[2021-06-05 Gemtexter - One Bash script to rule it all](./2021-06-05-gemtexter-one-bash-script-to-rule-it-all.md) -[2021-11-29 Bash Golf Part 1](./2021-11-29-bash-golf-part-1.md) -[2022-01-01 Bash Golf Part 2 (You are currently reading this)](./2022-01-01-bash-golf-part-2.md) [2023-12-10 Bash Golf Part 3](./2023-12-10-bash-golf-part-3.md) +[2022-01-01 Bash Golf Part 2 (You are currently reading this)](./2022-01-01-bash-golf-part-2.md) +[2021-11-29 Bash Golf Part 1](./2021-11-29-bash-golf-part-1.md) +[2021-06-05 Gemtexter - One Bash script to rule it all](./2021-06-05-gemtexter-one-bash-script-to-rule-it-all.md) +[2021-05-16 Personal Bash coding style guide](./2021-05-16-personal-bash-coding-style-guide.md) [Back to the main site](../) diff --git a/gemfeed/2022-03-06-the-release-of-dtail-4.0.0.md b/gemfeed/2022-03-06-the-release-of-dtail-4.0.0.md index 98b238d0..e3de21e0 100644 --- a/gemfeed/2022-03-06-the-release-of-dtail-4.0.0.md +++ b/gemfeed/2022-03-06-the-release-of-dtail-4.0.0.md @@ -307,10 +307,10 @@ E-Mail your comments to `paul@nospam.buetow.org` :-) Other related posts are: -[2021-04-22 DTail - The distributed log tail program](./2021-04-22-dtail-the-distributed-log-tail-program.md) -[2022-03-06 The release of DTail 4.0.0 (You are currently reading this)](./2022-03-06-the-release-of-dtail-4.0.0.md) -[2022-10-30 Installing DTail on OpenBSD](./2022-10-30-installing-dtail-on-openbsd.md) [2023-09-25 DTail usage examples](./2023-09-25-dtail-usage-examples.md) +[2022-10-30 Installing DTail on OpenBSD](./2022-10-30-installing-dtail-on-openbsd.md) +[2022-03-06 The release of DTail 4.0.0 (You are currently reading this)](./2022-03-06-the-release-of-dtail-4.0.0.md) +[2021-04-22 DTail - The distributed log tail program](./2021-04-22-dtail-the-distributed-log-tail-program.md) Thanks! diff --git a/gemfeed/2022-05-27-perl-is-still-a-great-choice.md b/gemfeed/2022-05-27-perl-is-still-a-great-choice.md index b7ba1644..aa856001 100644 --- a/gemfeed/2022-05-27-perl-is-still-a-great-choice.md +++ b/gemfeed/2022-05-27-perl-is-still-a-great-choice.md @@ -147,9 +147,9 @@ E-Mail your comments to `paul@nospam.buetow.org` :-) Other related posts are: -[2008-06-26 Perl Poetry](./2008-06-26-perl-poetry.md) -[2011-05-07 Perl Daemon (Service Framework)](./2011-05-07-perl-daemon-service-framework.md) -[2022-05-27 Perl is still a great choice (You are currently reading this)](./2022-05-27-perl-is-still-a-great-choice.md) [2023-05-01 Unveiling `guprecords.raku`: Global Uptime Records with Raku](./2023-05-01-unveiling-guprecords:-uptime-records-with-raku.md) +[2022-05-27 Perl is still a great choice (You are currently reading this)](./2022-05-27-perl-is-still-a-great-choice.md) +[2011-05-07 Perl Daemon (Service Framework)](./2011-05-07-perl-daemon-service-framework.md) +[2008-06-26 Perl Poetry](./2008-06-26-perl-poetry.md) [Back to the main site](../) diff --git a/gemfeed/2022-07-30-lets-encrypt-with-openbsd-and-rex.md b/gemfeed/2022-07-30-lets-encrypt-with-openbsd-and-rex.md index 40deb0fc..0399e072 100644 --- a/gemfeed/2022-07-30-lets-encrypt-with-openbsd-and-rex.md +++ b/gemfeed/2022-07-30-lets-encrypt-with-openbsd-and-rex.md @@ -676,13 +676,13 @@ E-Mail your comments to `paul@nospam.buetow.org` :-) Other *BSD related posts are: -[2016-04-09 Jails and ZFS with Puppet on FreeBSD](./2016-04-09-jails-and-zfs-on-freebsd-with-puppet.md) -[2022-07-30 Let's Encrypt with OpenBSD and Rex (You are currently reading this)](./2022-07-30-lets-encrypt-with-openbsd-and-rex.md) -[2022-10-30 Installing DTail on OpenBSD](./2022-10-30-installing-dtail-on-openbsd.md) -[2024-01-13 One reason why I love OpenBSD](./2024-01-13-one-reason-why-i-love-openbsd.md) -[2024-04-01 KISS high-availability with OpenBSD](./2024-04-01-KISS-high-availability-with-OpenBSD.md) -[2024-11-17 f3s: Kubernetes with FreeBSD - Part 1: Setting the stage](./2024-11-17-f3s-kubernetes-with-freebsd-part-1.md) -[2024-12-03 f3s: Kubernetes with FreeBSD - Part 2: Hardware and base installation](./2024-12-03-f3s-kubernetes-with-freebsd-part-2.md) [2025-02-01 f3s: Kubernetes with FreeBSD - Part 3: Protecting from power cuts](./2025-02-01-f3s-kubernetes-with-freebsd-part-3.md) +[2024-12-03 f3s: Kubernetes with FreeBSD - Part 2: Hardware and base installation](./2024-12-03-f3s-kubernetes-with-freebsd-part-2.md) +[2024-11-17 f3s: Kubernetes with FreeBSD - Part 1: Setting the stage](./2024-11-17-f3s-kubernetes-with-freebsd-part-1.md) +[2024-04-01 KISS high-availability with OpenBSD](./2024-04-01-KISS-high-availability-with-OpenBSD.md) +[2024-01-13 One reason why I love OpenBSD](./2024-01-13-one-reason-why-i-love-openbsd.md) +[2022-10-30 Installing DTail on OpenBSD](./2022-10-30-installing-dtail-on-openbsd.md) +[2022-07-30 Let's Encrypt with OpenBSD and Rex (You are currently reading this)](./2022-07-30-lets-encrypt-with-openbsd-and-rex.md) +[2016-04-09 Jails and ZFS with Puppet on FreeBSD](./2016-04-09-jails-and-zfs-on-freebsd-with-puppet.md) [Back to the main site](../) diff --git a/gemfeed/2022-08-27-gemtexter-1.1.0-lets-gemtext-again.md b/gemfeed/2022-08-27-gemtexter-1.1.0-lets-gemtext-again.md index fa08c841..e0a55c37 100644 --- a/gemfeed/2022-08-27-gemtexter-1.1.0-lets-gemtext-again.md +++ b/gemfeed/2022-08-27-gemtexter-1.1.0-lets-gemtext-again.md @@ -102,11 +102,11 @@ E-Mail your comments to `paul@nospam.buetow.org` :-) Other related posts are: -[2021-04-24 Welcome to the Geminispace](./2021-04-24-welcome-to-the-geminispace.md) -[2021-06-05 Gemtexter - One Bash script to rule it all](./2021-06-05-gemtexter-one-bash-script-to-rule-it-all.md) -[2022-08-27 Gemtexter 1.1.0 - Let's Gemtext again (You are currently reading this)](./2022-08-27-gemtexter-1.1.0-lets-gemtext-again.md) -[2023-03-25 Gemtexter 2.0.0 - Let's Gemtext again²](./2023-03-25-gemtexter-2.0.0-lets-gemtext-again-2.md) -[2023-07-21 Gemtexter 2.1.0 - Let's Gemtext again³](./2023-07-21-gemtexter-2.1.0-lets-gemtext-again-3.md) [2024-10-02 Gemtexter 3.0.0 - Let's Gemtext again⁴](./2024-10-02-gemtexter-3.0.0-lets-gemtext-again-4.md) +[2023-07-21 Gemtexter 2.1.0 - Let's Gemtext again³](./2023-07-21-gemtexter-2.1.0-lets-gemtext-again-3.md) +[2023-03-25 Gemtexter 2.0.0 - Let's Gemtext again²](./2023-03-25-gemtexter-2.0.0-lets-gemtext-again-2.md) +[2022-08-27 Gemtexter 1.1.0 - Let's Gemtext again (You are currently reading this)](./2022-08-27-gemtexter-1.1.0-lets-gemtext-again.md) +[2021-06-05 Gemtexter - One Bash script to rule it all](./2021-06-05-gemtexter-one-bash-script-to-rule-it-all.md) +[2021-04-24 Welcome to the Geminispace](./2021-04-24-welcome-to-the-geminispace.md) [Back to the main site](../) diff --git a/gemfeed/2022-10-30-installing-dtail-on-openbsd.md b/gemfeed/2022-10-30-installing-dtail-on-openbsd.md index 232e7bb4..2ca8141b 100644 --- a/gemfeed/2022-10-30-installing-dtail-on-openbsd.md +++ b/gemfeed/2022-10-30-installing-dtail-on-openbsd.md @@ -357,9 +357,9 @@ E-Mail your comments to `paul@nospam.buetow.org` :-) Other related posts are: -[2021-04-22 DTail - The distributed log tail program](./2021-04-22-dtail-the-distributed-log-tail-program.md) -[2022-03-06 The release of DTail 4.0.0](./2022-03-06-the-release-of-dtail-4.0.0.md) -[2022-10-30 Installing DTail on OpenBSD (You are currently reading this)](./2022-10-30-installing-dtail-on-openbsd.md) [2023-09-25 DTail usage examples](./2023-09-25-dtail-usage-examples.md) +[2022-10-30 Installing DTail on OpenBSD (You are currently reading this)](./2022-10-30-installing-dtail-on-openbsd.md) +[2022-03-06 The release of DTail 4.0.0](./2022-03-06-the-release-of-dtail-4.0.0.md) +[2021-04-22 DTail - The distributed log tail program](./2021-04-22-dtail-the-distributed-log-tail-program.md) [Back to the main site](../) diff --git a/gemfeed/2023-03-16-the-pragmatic-programmer-book-notes.md b/gemfeed/2023-03-16-the-pragmatic-programmer-book-notes.md index f43d1055..6c1fe784 100644 --- a/gemfeed/2023-03-16-the-pragmatic-programmer-book-notes.md +++ b/gemfeed/2023-03-16-the-pragmatic-programmer-book-notes.md @@ -80,13 +80,13 @@ E-Mail your comments to `paul@nospam.buetow.org` :-) Other book notes of mine are: -[2023-03-16 "The Pragmatic Programmer" book notes (You are currently reading this)](./2023-03-16-the-pragmatic-programmer-book-notes.md) -[2023-04-01 "Never split the difference" book notes](./2023-04-01-never-split-the-difference-book-notes.md) -[2023-05-06 "The Obstacle is the Way" book notes](./2023-05-06-the-obstacle-is-the-way-book-notes.md) -[2023-07-17 "Software Developmers Career Guide and Soft Skills" book notes](./2023-07-17-career-guide-and-soft-skills-book-notes.md) -[2023-11-11 "Mind Management" book notes](./2023-11-11-mind-management-book-notes.md) -[2024-05-01 "Slow Productivity" book notes](./2024-05-01-slow-productivity-book-notes.md) -[2024-07-07 "The Stoic Challenge" book notes](./2024-07-07-the-stoic-challenge-book-notes.md) [2024-10-24 "Staff Engineer" book notes](./2024-10-24-staff-engineer-book-notes.md) +[2024-07-07 "The Stoic Challenge" book notes](./2024-07-07-the-stoic-challenge-book-notes.md) +[2024-05-01 "Slow Productivity" book notes](./2024-05-01-slow-productivity-book-notes.md) +[2023-11-11 "Mind Management" book notes](./2023-11-11-mind-management-book-notes.md) +[2023-07-17 "Software Developmers Career Guide and Soft Skills" book notes](./2023-07-17-career-guide-and-soft-skills-book-notes.md) +[2023-05-06 "The Obstacle is the Way" book notes](./2023-05-06-the-obstacle-is-the-way-book-notes.md) +[2023-04-01 "Never split the difference" book notes](./2023-04-01-never-split-the-difference-book-notes.md) +[2023-03-16 "The Pragmatic Programmer" book notes (You are currently reading this)](./2023-03-16-the-pragmatic-programmer-book-notes.md) [Back to the main site](../) diff --git a/gemfeed/2023-03-25-gemtexter-2.0.0-lets-gemtext-again-2.md b/gemfeed/2023-03-25-gemtexter-2.0.0-lets-gemtext-again-2.md index 568d1262..ceeace01 100644 --- a/gemfeed/2023-03-25-gemtexter-2.0.0-lets-gemtext-again-2.md +++ b/gemfeed/2023-03-25-gemtexter-2.0.0-lets-gemtext-again-2.md @@ -150,11 +150,11 @@ E-Mail your comments to `paul@nospam.buetow.org` :-) Other related posts are: -[2021-04-24 Welcome to the Geminispace](./2021-04-24-welcome-to-the-geminispace.md) -[2021-06-05 Gemtexter - One Bash script to rule it all](./2021-06-05-gemtexter-one-bash-script-to-rule-it-all.md) -[2022-08-27 Gemtexter 1.1.0 - Let's Gemtext again](./2022-08-27-gemtexter-1.1.0-lets-gemtext-again.md) -[2023-03-25 Gemtexter 2.0.0 - Let's Gemtext again² (You are currently reading this)](./2023-03-25-gemtexter-2.0.0-lets-gemtext-again-2.md) -[2023-07-21 Gemtexter 2.1.0 - Let's Gemtext again³](./2023-07-21-gemtexter-2.1.0-lets-gemtext-again-3.md) [2024-10-02 Gemtexter 3.0.0 - Let's Gemtext again⁴](./2024-10-02-gemtexter-3.0.0-lets-gemtext-again-4.md) +[2023-07-21 Gemtexter 2.1.0 - Let's Gemtext again³](./2023-07-21-gemtexter-2.1.0-lets-gemtext-again-3.md) +[2023-03-25 Gemtexter 2.0.0 - Let's Gemtext again² (You are currently reading this)](./2023-03-25-gemtexter-2.0.0-lets-gemtext-again-2.md) +[2022-08-27 Gemtexter 1.1.0 - Let's Gemtext again](./2022-08-27-gemtexter-1.1.0-lets-gemtext-again.md) +[2021-06-05 Gemtexter - One Bash script to rule it all](./2021-06-05-gemtexter-one-bash-script-to-rule-it-all.md) +[2021-04-24 Welcome to the Geminispace](./2021-04-24-welcome-to-the-geminispace.md) [Back to the main site](../) diff --git a/gemfeed/2023-04-01-never-split-the-difference-book-notes.md b/gemfeed/2023-04-01-never-split-the-difference-book-notes.md index 9500ae38..12ba5708 100644 --- a/gemfeed/2023-04-01-never-split-the-difference-book-notes.md +++ b/gemfeed/2023-04-01-never-split-the-difference-book-notes.md @@ -139,13 +139,13 @@ E-Mail your comments to `paul@nospam.buetow.org` :-) Other book notes of mine are: -[2023-03-16 "The Pragmatic Programmer" book notes](./2023-03-16-the-pragmatic-programmer-book-notes.md) -[2023-04-01 "Never split the difference" book notes (You are currently reading this)](./2023-04-01-never-split-the-difference-book-notes.md) -[2023-05-06 "The Obstacle is the Way" book notes](./2023-05-06-the-obstacle-is-the-way-book-notes.md) -[2023-07-17 "Software Developmers Career Guide and Soft Skills" book notes](./2023-07-17-career-guide-and-soft-skills-book-notes.md) -[2023-11-11 "Mind Management" book notes](./2023-11-11-mind-management-book-notes.md) -[2024-05-01 "Slow Productivity" book notes](./2024-05-01-slow-productivity-book-notes.md) -[2024-07-07 "The Stoic Challenge" book notes](./2024-07-07-the-stoic-challenge-book-notes.md) [2024-10-24 "Staff Engineer" book notes](./2024-10-24-staff-engineer-book-notes.md) +[2024-07-07 "The Stoic Challenge" book notes](./2024-07-07-the-stoic-challenge-book-notes.md) +[2024-05-01 "Slow Productivity" book notes](./2024-05-01-slow-productivity-book-notes.md) +[2023-11-11 "Mind Management" book notes](./2023-11-11-mind-management-book-notes.md) +[2023-07-17 "Software Developmers Career Guide and Soft Skills" book notes](./2023-07-17-career-guide-and-soft-skills-book-notes.md) +[2023-05-06 "The Obstacle is the Way" book notes](./2023-05-06-the-obstacle-is-the-way-book-notes.md) +[2023-04-01 "Never split the difference" book notes (You are currently reading this)](./2023-04-01-never-split-the-difference-book-notes.md) +[2023-03-16 "The Pragmatic Programmer" book notes](./2023-03-16-the-pragmatic-programmer-book-notes.md) [Back to the main site](../) diff --git a/gemfeed/2023-05-01-unveiling-guprecords:-uptime-records-with-raku.md b/gemfeed/2023-05-01-unveiling-guprecords:-uptime-records-with-raku.md index c1136931..4fb6d039 100644 --- a/gemfeed/2023-05-01-unveiling-guprecords:-uptime-records-with-raku.md +++ b/gemfeed/2023-05-01-unveiling-guprecords:-uptime-records-with-raku.md @@ -159,10 +159,10 @@ E-Mail your comments to hi@foo.zone :-) Other related posts are: -[2008-06-26 Perl Poetry](./2008-06-26-perl-poetry.md) -[2011-05-07 Perl Daemon (Service Framework)](./2011-05-07-perl-daemon-service-framework.md) -[2022-05-27 Perl is still a great choice](./2022-05-27-perl-is-still-a-great-choice.md) -[2022-06-15 Sweating the small stuff - Tiny projects of mine](./2022-06-15-sweating-the-small-stuff.md) [2023-05-01 Unveiling `guprecords.raku`: Global Uptime Records with Raku (You are currently reading this)](./2023-05-01-unveiling-guprecords:-uptime-records-with-raku.md) +[2022-06-15 Sweating the small stuff - Tiny projects of mine](./2022-06-15-sweating-the-small-stuff.md) +[2022-05-27 Perl is still a great choice](./2022-05-27-perl-is-still-a-great-choice.md) +[2011-05-07 Perl Daemon (Service Framework)](./2011-05-07-perl-daemon-service-framework.md) +[2008-06-26 Perl Poetry](./2008-06-26-perl-poetry.md) [Back to the main site](../) diff --git a/gemfeed/2023-05-06-the-obstacle-is-the-way-book-notes.md b/gemfeed/2023-05-06-the-obstacle-is-the-way-book-notes.md index 1256673d..39e8fbd6 100644 --- a/gemfeed/2023-05-06-the-obstacle-is-the-way-book-notes.md +++ b/gemfeed/2023-05-06-the-obstacle-is-the-way-book-notes.md @@ -100,13 +100,13 @@ E-Mail your comments to `paul@nospam.buetow.org` :-) Other book notes of mine are: -[2023-03-16 "The Pragmatic Programmer" book notes](./2023-03-16-the-pragmatic-programmer-book-notes.md) -[2023-04-01 "Never split the difference" book notes](./2023-04-01-never-split-the-difference-book-notes.md) -[2023-05-06 "The Obstacle is the Way" book notes (You are currently reading this)](./2023-05-06-the-obstacle-is-the-way-book-notes.md) -[2023-07-17 "Software Developmers Career Guide and Soft Skills" book notes](./2023-07-17-career-guide-and-soft-skills-book-notes.md) -[2023-11-11 "Mind Management" book notes](./2023-11-11-mind-management-book-notes.md) -[2024-05-01 "Slow Productivity" book notes](./2024-05-01-slow-productivity-book-notes.md) -[2024-07-07 "The Stoic Challenge" book notes](./2024-07-07-the-stoic-challenge-book-notes.md) [2024-10-24 "Staff Engineer" book notes](./2024-10-24-staff-engineer-book-notes.md) +[2024-07-07 "The Stoic Challenge" book notes](./2024-07-07-the-stoic-challenge-book-notes.md) +[2024-05-01 "Slow Productivity" book notes](./2024-05-01-slow-productivity-book-notes.md) +[2023-11-11 "Mind Management" book notes](./2023-11-11-mind-management-book-notes.md) +[2023-07-17 "Software Developmers Career Guide and Soft Skills" book notes](./2023-07-17-career-guide-and-soft-skills-book-notes.md) +[2023-05-06 "The Obstacle is the Way" book notes (You are currently reading this)](./2023-05-06-the-obstacle-is-the-way-book-notes.md) +[2023-04-01 "Never split the difference" book notes](./2023-04-01-never-split-the-difference-book-notes.md) +[2023-03-16 "The Pragmatic Programmer" book notes](./2023-03-16-the-pragmatic-programmer-book-notes.md) [Back to the main site](../) diff --git a/gemfeed/2023-06-01-kiss-server-monitoring-with-gogios.md b/gemfeed/2023-06-01-kiss-server-monitoring-with-gogios.md index 9da6dceb..3ebc3eae 100644 --- a/gemfeed/2023-06-01-kiss-server-monitoring-with-gogios.md +++ b/gemfeed/2023-06-01-kiss-server-monitoring-with-gogios.md @@ -255,9 +255,9 @@ E-Mail your comments to `paul@nospam.buetow.org` :-) Other KISS-related posts are: -[2021-09-12 Keep it simple and stupid](./2021-09-12-keep-it-simple-and-stupid.md) -[2023-06-01 KISS server monitoring with Gogios (You are currently reading this)](./2023-06-01-kiss-server-monitoring-with-gogios.md) -[2023-10-29 KISS static web photo albums with `photoalbum.sh`](./2023-10-29-kiss-static-web-photo-albums-with-photoalbum.sh.md) [2024-04-01 KISS high-availability with OpenBSD](./2024-04-01-KISS-high-availability-with-OpenBSD.md) +[2023-10-29 KISS static web photo albums with `photoalbum.sh`](./2023-10-29-kiss-static-web-photo-albums-with-photoalbum.sh.md) +[2023-06-01 KISS server monitoring with Gogios (You are currently reading this)](./2023-06-01-kiss-server-monitoring-with-gogios.md) +[2021-09-12 Keep it simple and stupid](./2021-09-12-keep-it-simple-and-stupid.md) [Back to the main site](../) diff --git a/gemfeed/2023-07-17-career-guide-and-soft-skills-book-notes.md b/gemfeed/2023-07-17-career-guide-and-soft-skills-book-notes.md index 8c5e6500..a14b6c22 100644 --- a/gemfeed/2023-07-17-career-guide-and-soft-skills-book-notes.md +++ b/gemfeed/2023-07-17-career-guide-and-soft-skills-book-notes.md @@ -308,13 +308,13 @@ E-Mail your comments to `paul@nospam.buetow.org` :-) Other book notes of mine are: -[2023-03-16 "The Pragmatic Programmer" book notes](./2023-03-16-the-pragmatic-programmer-book-notes.md) -[2023-04-01 "Never split the difference" book notes](./2023-04-01-never-split-the-difference-book-notes.md) -[2023-05-06 "The Obstacle is the Way" book notes](./2023-05-06-the-obstacle-is-the-way-book-notes.md) -[2023-07-17 "Software Developmers Career Guide and Soft Skills" book notes (You are currently reading this)](./2023-07-17-career-guide-and-soft-skills-book-notes.md) -[2023-11-11 "Mind Management" book notes](./2023-11-11-mind-management-book-notes.md) -[2024-05-01 "Slow Productivity" book notes](./2024-05-01-slow-productivity-book-notes.md) -[2024-07-07 "The Stoic Challenge" book notes](./2024-07-07-the-stoic-challenge-book-notes.md) [2024-10-24 "Staff Engineer" book notes](./2024-10-24-staff-engineer-book-notes.md) +[2024-07-07 "The Stoic Challenge" book notes](./2024-07-07-the-stoic-challenge-book-notes.md) +[2024-05-01 "Slow Productivity" book notes](./2024-05-01-slow-productivity-book-notes.md) +[2023-11-11 "Mind Management" book notes](./2023-11-11-mind-management-book-notes.md) +[2023-07-17 "Software Developmers Career Guide and Soft Skills" book notes (You are currently reading this)](./2023-07-17-career-guide-and-soft-skills-book-notes.md) +[2023-05-06 "The Obstacle is the Way" book notes](./2023-05-06-the-obstacle-is-the-way-book-notes.md) +[2023-04-01 "Never split the difference" book notes](./2023-04-01-never-split-the-difference-book-notes.md) +[2023-03-16 "The Pragmatic Programmer" book notes](./2023-03-16-the-pragmatic-programmer-book-notes.md) [Back to the main site](../) diff --git a/gemfeed/2023-07-21-gemtexter-2.1.0-lets-gemtext-again-3.md b/gemfeed/2023-07-21-gemtexter-2.1.0-lets-gemtext-again-3.md index fcb68332..a7c8bfae 100644 --- a/gemfeed/2023-07-21-gemtexter-2.1.0-lets-gemtext-again-3.md +++ b/gemfeed/2023-07-21-gemtexter-2.1.0-lets-gemtext-again-3.md @@ -106,11 +106,11 @@ E-Mail your comments to `paul@nospam.buetow.org` :-) Other related posts are: -[2021-04-24 Welcome to the Geminispace](./2021-04-24-welcome-to-the-geminispace.md) -[2021-06-05 Gemtexter - One Bash script to rule it all](./2021-06-05-gemtexter-one-bash-script-to-rule-it-all.md) -[2022-08-27 Gemtexter 1.1.0 - Let's Gemtext again](./2022-08-27-gemtexter-1.1.0-lets-gemtext-again.md) -[2023-03-25 Gemtexter 2.0.0 - Let's Gemtext again²](./2023-03-25-gemtexter-2.0.0-lets-gemtext-again-2.md) -[2023-07-21 Gemtexter 2.1.0 - Let's Gemtext again³ (You are currently reading this)](./2023-07-21-gemtexter-2.1.0-lets-gemtext-again-3.md) [2024-10-02 Gemtexter 3.0.0 - Let's Gemtext again⁴](./2024-10-02-gemtexter-3.0.0-lets-gemtext-again-4.md) +[2023-07-21 Gemtexter 2.1.0 - Let's Gemtext again³ (You are currently reading this)](./2023-07-21-gemtexter-2.1.0-lets-gemtext-again-3.md) +[2023-03-25 Gemtexter 2.0.0 - Let's Gemtext again²](./2023-03-25-gemtexter-2.0.0-lets-gemtext-again-2.md) +[2022-08-27 Gemtexter 1.1.0 - Let's Gemtext again](./2022-08-27-gemtexter-1.1.0-lets-gemtext-again.md) +[2021-06-05 Gemtexter - One Bash script to rule it all](./2021-06-05-gemtexter-one-bash-script-to-rule-it-all.md) +[2021-04-24 Welcome to the Geminispace](./2021-04-24-welcome-to-the-geminispace.md) [Back to the main site](../) diff --git a/gemfeed/2023-08-18-site-reliability-engineering-part-1.md b/gemfeed/2023-08-18-site-reliability-engineering-part-1.md index 5c61f9ac..1adfc337 100644 --- a/gemfeed/2023-08-18-site-reliability-engineering-part-1.md +++ b/gemfeed/2023-08-18-site-reliability-engineering-part-1.md @@ -4,10 +4,10 @@ Being a Site Reliability Engineer (SRE) is like stepping into a lively, ever-evolving universe. The world of SRE mixes together different tech, a unique culture, and a whole lot of determination. It’s one of the toughest but most exciting jobs out there. There's zero chance of getting bored because there's always a fresh challenge to tackle and new technology to play around with. It's not just about the tech side of things either; it's heavily rooted in communication, collaboration, and teamwork. As someone currently working as an SRE, I’m here to break it all down for you in this blog series. Let's dive into what SRE is really all about! -[2023-08-18 Site Reliability Engineering - Part 1: SRE and Organizational Culture (You are currently reading this)](./2023-08-18-site-reliability-engineering-part-1.md) -[2023-11-19 Site Reliability Engineering - Part 2: Operational Balance](./2023-11-19-site-reliability-engineering-part-2.md) -[2024-01-09 Site Reliability Engineering - Part 3: On-Call Culture](./2024-01-09-site-reliability-engineering-part-3.md) [2024-09-07 Site Reliability Engineering - Part 4: Onboarding for On-Call Engineers](./2024-09-07-site-reliability-engineering-part-4.md) +[2024-01-09 Site Reliability Engineering - Part 3: On-Call Culture](./2024-01-09-site-reliability-engineering-part-3.md) +[2023-11-19 Site Reliability Engineering - Part 2: Operational Balance](./2023-11-19-site-reliability-engineering-part-2.md) +[2023-08-18 Site Reliability Engineering - Part 1: SRE and Organizational Culture (You are currently reading this)](./2023-08-18-site-reliability-engineering-part-1.md) ``` ▓▓▓▓░░ diff --git a/gemfeed/2023-09-25-dtail-usage-examples.md b/gemfeed/2023-09-25-dtail-usage-examples.md index 595afb36..8df87a93 100644 --- a/gemfeed/2023-09-25-dtail-usage-examples.md +++ b/gemfeed/2023-09-25-dtail-usage-examples.md @@ -248,10 +248,10 @@ E-Mail your comments to `paul@nospam.buetow.org` :-) Other related posts are: -[2021-04-22 DTail - The distributed log tail program](./2021-04-22-dtail-the-distributed-log-tail-program.md) -[2022-03-06 The release of DTail 4.0.0](./2022-03-06-the-release-of-dtail-4.0.0.md) -[2022-10-30 Installing DTail on OpenBSD](./2022-10-30-installing-dtail-on-openbsd.md) [2023-09-25 DTail usage examples (You are currently reading this)](./2023-09-25-dtail-usage-examples.md) +[2022-10-30 Installing DTail on OpenBSD](./2022-10-30-installing-dtail-on-openbsd.md) +[2022-03-06 The release of DTail 4.0.0](./2022-03-06-the-release-of-dtail-4.0.0.md) +[2021-04-22 DTail - The distributed log tail program](./2021-04-22-dtail-the-distributed-log-tail-program.md) I hope you find the tools presented in this post useful! diff --git a/gemfeed/2023-10-29-kiss-static-web-photo-albums-with-photoalbum.sh.md b/gemfeed/2023-10-29-kiss-static-web-photo-albums-with-photoalbum.sh.md index dd8c0167..2121886c 100644 --- a/gemfeed/2023-10-29-kiss-static-web-photo-albums-with-photoalbum.sh.md +++ b/gemfeed/2023-10-29-kiss-static-web-photo-albums-with-photoalbum.sh.md @@ -272,14 +272,14 @@ E-Mail your comments to `paul@nospam.buetow.org` :-) Other Bash and KISS-related posts are: -[2021-05-16 Personal Bash coding style guide](./2021-05-16-personal-bash-coding-style-guide.md) -[2021-06-05 Gemtexter - One Bash script to rule it all](./2021-06-05-gemtexter-one-bash-script-to-rule-it-all.md) -[2021-09-12 Keep it simple and stupid](./2021-09-12-keep-it-simple-and-stupid.md) -[2021-11-29 Bash Golf Part 1](./2021-11-29-bash-golf-part-1.md) -[2022-01-01 Bash Golf Part 2](./2022-01-01-bash-golf-part-2.md) -[2023-06-01 KISS server monitoring with Gogios](./2023-06-01-kiss-server-monitoring-with-gogios.md) -[2023-10-29 KISS static web photo albums with `photoalbum.sh` (You are currently reading this)](./2023-10-29-kiss-static-web-photo-albums-with-photoalbum.sh.md) -[2023-12-10 Bash Golf Part 3](./2023-12-10-bash-golf-part-3.md) [2024-04-01 KISS high-availability with OpenBSD](./2024-04-01-KISS-high-availability-with-OpenBSD.md) +[2023-12-10 Bash Golf Part 3](./2023-12-10-bash-golf-part-3.md) +[2023-10-29 KISS static web photo albums with `photoalbum.sh` (You are currently reading this)](./2023-10-29-kiss-static-web-photo-albums-with-photoalbum.sh.md) +[2023-06-01 KISS server monitoring with Gogios](./2023-06-01-kiss-server-monitoring-with-gogios.md) +[2022-01-01 Bash Golf Part 2](./2022-01-01-bash-golf-part-2.md) +[2021-11-29 Bash Golf Part 1](./2021-11-29-bash-golf-part-1.md) +[2021-09-12 Keep it simple and stupid](./2021-09-12-keep-it-simple-and-stupid.md) +[2021-06-05 Gemtexter - One Bash script to rule it all](./2021-06-05-gemtexter-one-bash-script-to-rule-it-all.md) +[2021-05-16 Personal Bash coding style guide](./2021-05-16-personal-bash-coding-style-guide.md) [Back to the main site](../) diff --git a/gemfeed/2023-11-11-mind-management-book-notes.md b/gemfeed/2023-11-11-mind-management-book-notes.md index 96a2c6e5..2cefef51 100644 --- a/gemfeed/2023-11-11-mind-management-book-notes.md +++ b/gemfeed/2023-11-11-mind-management-book-notes.md @@ -110,13 +110,13 @@ E-Mail your comments to `paul@nospam.buetow.org` :-) Other book notes of mine are: -[2023-03-16 "The Pragmatic Programmer" book notes](./2023-03-16-the-pragmatic-programmer-book-notes.md) -[2023-04-01 "Never split the difference" book notes](./2023-04-01-never-split-the-difference-book-notes.md) -[2023-05-06 "The Obstacle is the Way" book notes](./2023-05-06-the-obstacle-is-the-way-book-notes.md) -[2023-07-17 "Software Developmers Career Guide and Soft Skills" book notes](./2023-07-17-career-guide-and-soft-skills-book-notes.md) -[2023-11-11 "Mind Management" book notes (You are currently reading this)](./2023-11-11-mind-management-book-notes.md) -[2024-05-01 "Slow Productivity" book notes](./2024-05-01-slow-productivity-book-notes.md) -[2024-07-07 "The Stoic Challenge" book notes](./2024-07-07-the-stoic-challenge-book-notes.md) [2024-10-24 "Staff Engineer" book notes](./2024-10-24-staff-engineer-book-notes.md) +[2024-07-07 "The Stoic Challenge" book notes](./2024-07-07-the-stoic-challenge-book-notes.md) +[2024-05-01 "Slow Productivity" book notes](./2024-05-01-slow-productivity-book-notes.md) +[2023-11-11 "Mind Management" book notes (You are currently reading this)](./2023-11-11-mind-management-book-notes.md) +[2023-07-17 "Software Developmers Career Guide and Soft Skills" book notes](./2023-07-17-career-guide-and-soft-skills-book-notes.md) +[2023-05-06 "The Obstacle is the Way" book notes](./2023-05-06-the-obstacle-is-the-way-book-notes.md) +[2023-04-01 "Never split the difference" book notes](./2023-04-01-never-split-the-difference-book-notes.md) +[2023-03-16 "The Pragmatic Programmer" book notes](./2023-03-16-the-pragmatic-programmer-book-notes.md) [Back to the main site](../) diff --git a/gemfeed/2023-11-19-site-reliability-engineering-part-2.md b/gemfeed/2023-11-19-site-reliability-engineering-part-2.md index 29749257..3220e499 100644 --- a/gemfeed/2023-11-19-site-reliability-engineering-part-2.md +++ b/gemfeed/2023-11-19-site-reliability-engineering-part-2.md @@ -4,10 +4,10 @@ This is the second part of my Site Reliability Engineering (SRE) series. I am currently employed as a Site Reliability Engineer and will try to share what SRE is about in this blog series. -[2023-08-18 Site Reliability Engineering - Part 1: SRE and Organizational Culture](./2023-08-18-site-reliability-engineering-part-1.md) -[2023-11-19 Site Reliability Engineering - Part 2: Operational Balance (You are currently reading this)](./2023-11-19-site-reliability-engineering-part-2.md) -[2024-01-09 Site Reliability Engineering - Part 3: On-Call Culture](./2024-01-09-site-reliability-engineering-part-3.md) [2024-09-07 Site Reliability Engineering - Part 4: Onboarding for On-Call Engineers](./2024-09-07-site-reliability-engineering-part-4.md) +[2024-01-09 Site Reliability Engineering - Part 3: On-Call Culture](./2024-01-09-site-reliability-engineering-part-3.md) +[2023-11-19 Site Reliability Engineering - Part 2: Operational Balance (You are currently reading this)](./2023-11-19-site-reliability-engineering-part-2.md) +[2023-08-18 Site Reliability Engineering - Part 1: SRE and Organizational Culture](./2023-08-18-site-reliability-engineering-part-1.md) ``` ⠀⠀⠀⠀⠀⠀⠀⠀⠀⠀⠀⠀⢀⣠⣾⣷⣄⡀⠀⠀⠀⠀⠀⠀⠀⠀⠀⠀⠀⠀ diff --git a/gemfeed/2023-12-10-bash-golf-part-3.md b/gemfeed/2023-12-10-bash-golf-part-3.md index f315e387..99716dd7 100644 --- a/gemfeed/2023-12-10-bash-golf-part-3.md +++ b/gemfeed/2023-12-10-bash-golf-part-3.md @@ -4,9 +4,9 @@ This is the third blog post about my Bash Golf series. This series is random Bash tips, tricks, and weirdnesses I have encountered over time. -[2021-11-29 Bash Golf Part 1](./2021-11-29-bash-golf-part-1.md) -[2022-01-01 Bash Golf Part 2](./2022-01-01-bash-golf-part-2.md) [2023-12-10 Bash Golf Part 3 (You are currently reading this)](./2023-12-10-bash-golf-part-3.md) +[2022-01-01 Bash Golf Part 2](./2022-01-01-bash-golf-part-2.md) +[2021-11-29 Bash Golf Part 1](./2021-11-29-bash-golf-part-1.md) ``` @@ -371,10 +371,10 @@ E-Mail your comments to `paul@nospam.buetow.org` :-) Other related posts are: -[2021-05-16 Personal Bash coding style guide](./2021-05-16-personal-bash-coding-style-guide.md) -[2021-06-05 Gemtexter - One Bash script to rule it all](./2021-06-05-gemtexter-one-bash-script-to-rule-it-all.md) -[2021-11-29 Bash Golf Part 1](./2021-11-29-bash-golf-part-1.md) -[2022-01-01 Bash Golf Part 2](./2022-01-01-bash-golf-part-2.md) [2023-12-10 Bash Golf Part 3 (You are currently reading this)](./2023-12-10-bash-golf-part-3.md) +[2022-01-01 Bash Golf Part 2](./2022-01-01-bash-golf-part-2.md) +[2021-11-29 Bash Golf Part 1](./2021-11-29-bash-golf-part-1.md) +[2021-06-05 Gemtexter - One Bash script to rule it all](./2021-06-05-gemtexter-one-bash-script-to-rule-it-all.md) +[2021-05-16 Personal Bash coding style guide](./2021-05-16-personal-bash-coding-style-guide.md) [Back to the main site](../) diff --git a/gemfeed/2024-01-09-site-reliability-engineering-part-3.md b/gemfeed/2024-01-09-site-reliability-engineering-part-3.md index 15b9a170..6627fa62 100644 --- a/gemfeed/2024-01-09-site-reliability-engineering-part-3.md +++ b/gemfeed/2024-01-09-site-reliability-engineering-part-3.md @@ -4,10 +4,10 @@ Welcome to Part 3 of my Site Reliability Engineering (SRE) series. I'm currently working as a Site Reliability Engineer, and I’m here to share what SRE is all about in this blog series. -[2023-08-18 Site Reliability Engineering - Part 1: SRE and Organizational Culture](./2023-08-18-site-reliability-engineering-part-1.md) -[2023-11-19 Site Reliability Engineering - Part 2: Operational Balance](./2023-11-19-site-reliability-engineering-part-2.md) -[2024-01-09 Site Reliability Engineering - Part 3: On-Call Culture (You are currently reading this)](./2024-01-09-site-reliability-engineering-part-3.md) [2024-09-07 Site Reliability Engineering - Part 4: Onboarding for On-Call Engineers](./2024-09-07-site-reliability-engineering-part-4.md) +[2024-01-09 Site Reliability Engineering - Part 3: On-Call Culture (You are currently reading this)](./2024-01-09-site-reliability-engineering-part-3.md) +[2023-11-19 Site Reliability Engineering - Part 2: Operational Balance](./2023-11-19-site-reliability-engineering-part-2.md) +[2023-08-18 Site Reliability Engineering - Part 1: SRE and Organizational Culture](./2023-08-18-site-reliability-engineering-part-1.md) ``` ..--""""----.. diff --git a/gemfeed/2024-01-13-one-reason-why-i-love-openbsd.md b/gemfeed/2024-01-13-one-reason-why-i-love-openbsd.md index 92598532..531c4581 100644 --- a/gemfeed/2024-01-13-one-reason-why-i-love-openbsd.md +++ b/gemfeed/2024-01-13-one-reason-why-i-love-openbsd.md @@ -51,13 +51,13 @@ E-Mail your comments to `paul@nospam.buetow.org` :-) Other *BSD related posts are: -[2016-04-09 Jails and ZFS with Puppet on FreeBSD](./2016-04-09-jails-and-zfs-on-freebsd-with-puppet.md) -[2022-07-30 Let's Encrypt with OpenBSD and Rex](./2022-07-30-lets-encrypt-with-openbsd-and-rex.md) -[2022-10-30 Installing DTail on OpenBSD](./2022-10-30-installing-dtail-on-openbsd.md) -[2024-01-13 One reason why I love OpenBSD (You are currently reading this)](./2024-01-13-one-reason-why-i-love-openbsd.md) -[2024-04-01 KISS high-availability with OpenBSD](./2024-04-01-KISS-high-availability-with-OpenBSD.md) -[2024-11-17 f3s: Kubernetes with FreeBSD - Part 1: Setting the stage](./2024-11-17-f3s-kubernetes-with-freebsd-part-1.md) -[2024-12-03 f3s: Kubernetes with FreeBSD - Part 2: Hardware and base installation](./2024-12-03-f3s-kubernetes-with-freebsd-part-2.md) [2025-02-01 f3s: Kubernetes with FreeBSD - Part 3: Protecting from power cuts](./2025-02-01-f3s-kubernetes-with-freebsd-part-3.md) +[2024-12-03 f3s: Kubernetes with FreeBSD - Part 2: Hardware and base installation](./2024-12-03-f3s-kubernetes-with-freebsd-part-2.md) +[2024-11-17 f3s: Kubernetes with FreeBSD - Part 1: Setting the stage](./2024-11-17-f3s-kubernetes-with-freebsd-part-1.md) +[2024-04-01 KISS high-availability with OpenBSD](./2024-04-01-KISS-high-availability-with-OpenBSD.md) +[2024-01-13 One reason why I love OpenBSD (You are currently reading this)](./2024-01-13-one-reason-why-i-love-openbsd.md) +[2022-10-30 Installing DTail on OpenBSD](./2022-10-30-installing-dtail-on-openbsd.md) +[2022-07-30 Let's Encrypt with OpenBSD and Rex](./2022-07-30-lets-encrypt-with-openbsd-and-rex.md) +[2016-04-09 Jails and ZFS with Puppet on FreeBSD](./2016-04-09-jails-and-zfs-on-freebsd-with-puppet.md) [Back to the main site](../) diff --git a/gemfeed/2024-04-01-KISS-high-availability-with-OpenBSD.md b/gemfeed/2024-04-01-KISS-high-availability-with-OpenBSD.md index 66e17f82..4a53071f 100644 --- a/gemfeed/2024-04-01-KISS-high-availability-with-OpenBSD.md +++ b/gemfeed/2024-04-01-KISS-high-availability-with-OpenBSD.md @@ -300,15 +300,15 @@ E-Mail your comments to `paul@nospam.buetow.org` :-) Other *BSD and KISS related posts are: -[2016-04-09 Jails and ZFS with Puppet on FreeBSD](./2016-04-09-jails-and-zfs-on-freebsd-with-puppet.md) -[2022-07-30 Let's Encrypt with OpenBSD and Rex](./2022-07-30-lets-encrypt-with-openbsd-and-rex.md) -[2022-10-30 Installing DTail on OpenBSD](./2022-10-30-installing-dtail-on-openbsd.md) -[2023-06-01 KISS server monitoring with Gogios](./2023-06-01-kiss-server-monitoring-with-gogios.md) -[2023-10-29 KISS static web photo albums with `photoalbum.sh`](./2023-10-29-kiss-static-web-photo-albums-with-photoalbum.sh.md) -[2024-01-13 One reason why I love OpenBSD](./2024-01-13-one-reason-why-i-love-openbsd.md) -[2024-04-01 KISS high-availability with OpenBSD (You are currently reading this)](./2024-04-01-KISS-high-availability-with-OpenBSD.md) -[2024-11-17 f3s: Kubernetes with FreeBSD - Part 1: Setting the stage](./2024-11-17-f3s-kubernetes-with-freebsd-part-1.md) -[2024-12-03 f3s: Kubernetes with FreeBSD - Part 2: Hardware and base installation](./2024-12-03-f3s-kubernetes-with-freebsd-part-2.md) [2025-02-01 f3s: Kubernetes with FreeBSD - Part 3: Protecting from power cuts](./2025-02-01-f3s-kubernetes-with-freebsd-part-3.md) +[2024-12-03 f3s: Kubernetes with FreeBSD - Part 2: Hardware and base installation](./2024-12-03-f3s-kubernetes-with-freebsd-part-2.md) +[2024-11-17 f3s: Kubernetes with FreeBSD - Part 1: Setting the stage](./2024-11-17-f3s-kubernetes-with-freebsd-part-1.md) +[2024-04-01 KISS high-availability with OpenBSD (You are currently reading this)](./2024-04-01-KISS-high-availability-with-OpenBSD.md) +[2024-01-13 One reason why I love OpenBSD](./2024-01-13-one-reason-why-i-love-openbsd.md) +[2023-10-29 KISS static web photo albums with `photoalbum.sh`](./2023-10-29-kiss-static-web-photo-albums-with-photoalbum.sh.md) +[2023-06-01 KISS server monitoring with Gogios](./2023-06-01-kiss-server-monitoring-with-gogios.md) +[2022-10-30 Installing DTail on OpenBSD](./2022-10-30-installing-dtail-on-openbsd.md) +[2022-07-30 Let's Encrypt with OpenBSD and Rex](./2022-07-30-lets-encrypt-with-openbsd-and-rex.md) +[2016-04-09 Jails and ZFS with Puppet on FreeBSD](./2016-04-09-jails-and-zfs-on-freebsd-with-puppet.md) [Back to the main site](../) diff --git a/gemfeed/2024-05-01-slow-productivity-book-notes.md b/gemfeed/2024-05-01-slow-productivity-book-notes.md index 6fde73fa..00349dd1 100644 --- a/gemfeed/2024-05-01-slow-productivity-book-notes.md +++ b/gemfeed/2024-05-01-slow-productivity-book-notes.md @@ -138,13 +138,13 @@ E-Mail your comments to `paul@nospam.buetow.org` :-) Other book notes of mine are: -[2023-03-16 "The Pragmatic Programmer" book notes](./2023-03-16-the-pragmatic-programmer-book-notes.md) -[2023-04-01 "Never split the difference" book notes](./2023-04-01-never-split-the-difference-book-notes.md) -[2023-05-06 "The Obstacle is the Way" book notes](./2023-05-06-the-obstacle-is-the-way-book-notes.md) -[2023-07-17 "Software Developmers Career Guide and Soft Skills" book notes](./2023-07-17-career-guide-and-soft-skills-book-notes.md) -[2023-11-11 "Mind Management" book notes](./2023-11-11-mind-management-book-notes.md) -[2024-05-01 "Slow Productivity" book notes (You are currently reading this)](./2024-05-01-slow-productivity-book-notes.md) -[2024-07-07 "The Stoic Challenge" book notes](./2024-07-07-the-stoic-challenge-book-notes.md) [2024-10-24 "Staff Engineer" book notes](./2024-10-24-staff-engineer-book-notes.md) +[2024-07-07 "The Stoic Challenge" book notes](./2024-07-07-the-stoic-challenge-book-notes.md) +[2024-05-01 "Slow Productivity" book notes (You are currently reading this)](./2024-05-01-slow-productivity-book-notes.md) +[2023-11-11 "Mind Management" book notes](./2023-11-11-mind-management-book-notes.md) +[2023-07-17 "Software Developmers Career Guide and Soft Skills" book notes](./2023-07-17-career-guide-and-soft-skills-book-notes.md) +[2023-05-06 "The Obstacle is the Way" book notes](./2023-05-06-the-obstacle-is-the-way-book-notes.md) +[2023-04-01 "Never split the difference" book notes](./2023-04-01-never-split-the-difference-book-notes.md) +[2023-03-16 "The Pragmatic Programmer" book notes](./2023-03-16-the-pragmatic-programmer-book-notes.md) [Back to the main site](../) diff --git a/gemfeed/2024-07-07-the-stoic-challenge-book-notes.md b/gemfeed/2024-07-07-the-stoic-challenge-book-notes.md index 395ad2e8..0e3b0ed4 100644 --- a/gemfeed/2024-07-07-the-stoic-challenge-book-notes.md +++ b/gemfeed/2024-07-07-the-stoic-challenge-book-notes.md @@ -57,13 +57,13 @@ E-Mail your comments to `paul@nospam.buetow.org` :-) Other book notes of mine are: -[2023-03-16 "The Pragmatic Programmer" book notes](./2023-03-16-the-pragmatic-programmer-book-notes.md) -[2023-04-01 "Never split the difference" book notes](./2023-04-01-never-split-the-difference-book-notes.md) -[2023-05-06 "The Obstacle is the Way" book notes](./2023-05-06-the-obstacle-is-the-way-book-notes.md) -[2023-07-17 "Software Developmers Career Guide and Soft Skills" book notes](./2023-07-17-career-guide-and-soft-skills-book-notes.md) -[2023-11-11 "Mind Management" book notes](./2023-11-11-mind-management-book-notes.md) -[2024-05-01 "Slow Productivity" book notes](./2024-05-01-slow-productivity-book-notes.md) -[2024-07-07 "The Stoic Challenge" book notes (You are currently reading this)](./2024-07-07-the-stoic-challenge-book-notes.md) [2024-10-24 "Staff Engineer" book notes](./2024-10-24-staff-engineer-book-notes.md) +[2024-07-07 "The Stoic Challenge" book notes (You are currently reading this)](./2024-07-07-the-stoic-challenge-book-notes.md) +[2024-05-01 "Slow Productivity" book notes](./2024-05-01-slow-productivity-book-notes.md) +[2023-11-11 "Mind Management" book notes](./2023-11-11-mind-management-book-notes.md) +[2023-07-17 "Software Developmers Career Guide and Soft Skills" book notes](./2023-07-17-career-guide-and-soft-skills-book-notes.md) +[2023-05-06 "The Obstacle is the Way" book notes](./2023-05-06-the-obstacle-is-the-way-book-notes.md) +[2023-04-01 "Never split the difference" book notes](./2023-04-01-never-split-the-difference-book-notes.md) +[2023-03-16 "The Pragmatic Programmer" book notes](./2023-03-16-the-pragmatic-programmer-book-notes.md) [Back to the main site](../) diff --git a/gemfeed/2024-09-07-site-reliability-engineering-part-4.md b/gemfeed/2024-09-07-site-reliability-engineering-part-4.md index 4af52caf..2b5e8b2f 100644 --- a/gemfeed/2024-09-07-site-reliability-engineering-part-4.md +++ b/gemfeed/2024-09-07-site-reliability-engineering-part-4.md @@ -4,10 +4,10 @@ Welcome to Part 4 of my Site Reliability Engineering (SRE) series. I'm currently working as a Site Reliability Engineer, and I’m here to share what SRE is all about in this blog series. -[2023-08-18 Site Reliability Engineering - Part 1: SRE and Organizational Culture](./2023-08-18-site-reliability-engineering-part-1.md) -[2023-11-19 Site Reliability Engineering - Part 2: Operational Balance](./2023-11-19-site-reliability-engineering-part-2.md) -[2024-01-09 Site Reliability Engineering - Part 3: On-Call Culture](./2024-01-09-site-reliability-engineering-part-3.md) [2024-09-07 Site Reliability Engineering - Part 4: Onboarding for On-Call Engineers (You are currently reading this)](./2024-09-07-site-reliability-engineering-part-4.md) +[2024-01-09 Site Reliability Engineering - Part 3: On-Call Culture](./2024-01-09-site-reliability-engineering-part-3.md) +[2023-11-19 Site Reliability Engineering - Part 2: Operational Balance](./2023-11-19-site-reliability-engineering-part-2.md) +[2023-08-18 Site Reliability Engineering - Part 1: SRE and Organizational Culture](./2023-08-18-site-reliability-engineering-part-1.md) ``` __..._ _...__ diff --git a/gemfeed/2024-10-02-gemtexter-3.0.0-lets-gemtext-again-4.md b/gemfeed/2024-10-02-gemtexter-3.0.0-lets-gemtext-again-4.md index a4a8554e..322fb989 100644 --- a/gemfeed/2024-10-02-gemtexter-3.0.0-lets-gemtext-again-4.md +++ b/gemfeed/2024-10-02-gemtexter-3.0.0-lets-gemtext-again-4.md @@ -76,11 +76,11 @@ E-Mail your comments to `paul@nospam.buetow.org` :-) Other related posts are: -[2021-04-24 Welcome to the Geminispace](./2021-04-24-welcome-to-the-geminispace.md) -[2021-06-05 Gemtexter - One Bash script to rule it all](./2021-06-05-gemtexter-one-bash-script-to-rule-it-all.md) -[2022-08-27 Gemtexter 1.1.0 - Let's Gemtext again](./2022-08-27-gemtexter-1.1.0-lets-gemtext-again.md) -[2023-03-25 Gemtexter 2.0.0 - Let's Gemtext again²](./2023-03-25-gemtexter-2.0.0-lets-gemtext-again-2.md) -[2023-07-21 Gemtexter 2.1.0 - Let's Gemtext again³](./2023-07-21-gemtexter-2.1.0-lets-gemtext-again-3.md) [2024-10-02 Gemtexter 3.0.0 - Let's Gemtext again⁴ (You are currently reading this)](./2024-10-02-gemtexter-3.0.0-lets-gemtext-again-4.md) +[2023-07-21 Gemtexter 2.1.0 - Let's Gemtext again³](./2023-07-21-gemtexter-2.1.0-lets-gemtext-again-3.md) +[2023-03-25 Gemtexter 2.0.0 - Let's Gemtext again²](./2023-03-25-gemtexter-2.0.0-lets-gemtext-again-2.md) +[2022-08-27 Gemtexter 1.1.0 - Let's Gemtext again](./2022-08-27-gemtexter-1.1.0-lets-gemtext-again.md) +[2021-06-05 Gemtexter - One Bash script to rule it all](./2021-06-05-gemtexter-one-bash-script-to-rule-it-all.md) +[2021-04-24 Welcome to the Geminispace](./2021-04-24-welcome-to-the-geminispace.md) [Back to the main site](../) diff --git a/gemfeed/2024-10-24-staff-engineer-book-notes.md b/gemfeed/2024-10-24-staff-engineer-book-notes.md index 4bc901b9..fe2961ca 100644 --- a/gemfeed/2024-10-24-staff-engineer-book-notes.md +++ b/gemfeed/2024-10-24-staff-engineer-book-notes.md @@ -121,13 +121,13 @@ E-Mail your comments to `paul@nospam.buetow.org` :-) Other book notes of mine are: -[2023-03-16 "The Pragmatic Programmer" book notes](./2023-03-16-the-pragmatic-programmer-book-notes.md) -[2023-04-01 "Never split the difference" book notes](./2023-04-01-never-split-the-difference-book-notes.md) -[2023-05-06 "The Obstacle is the Way" book notes](./2023-05-06-the-obstacle-is-the-way-book-notes.md) -[2023-07-17 "Software Developmers Career Guide and Soft Skills" book notes](./2023-07-17-career-guide-and-soft-skills-book-notes.md) -[2023-11-11 "Mind Management" book notes](./2023-11-11-mind-management-book-notes.md) -[2024-05-01 "Slow Productivity" book notes](./2024-05-01-slow-productivity-book-notes.md) -[2024-07-07 "The Stoic Challenge" book notes](./2024-07-07-the-stoic-challenge-book-notes.md) [2024-10-24 "Staff Engineer" book notes (You are currently reading this)](./2024-10-24-staff-engineer-book-notes.md) +[2024-07-07 "The Stoic Challenge" book notes](./2024-07-07-the-stoic-challenge-book-notes.md) +[2024-05-01 "Slow Productivity" book notes](./2024-05-01-slow-productivity-book-notes.md) +[2023-11-11 "Mind Management" book notes](./2023-11-11-mind-management-book-notes.md) +[2023-07-17 "Software Developmers Career Guide and Soft Skills" book notes](./2023-07-17-career-guide-and-soft-skills-book-notes.md) +[2023-05-06 "The Obstacle is the Way" book notes](./2023-05-06-the-obstacle-is-the-way-book-notes.md) +[2023-04-01 "Never split the difference" book notes](./2023-04-01-never-split-the-difference-book-notes.md) +[2023-03-16 "The Pragmatic Programmer" book notes](./2023-03-16-the-pragmatic-programmer-book-notes.md) [Back to the main site](../) diff --git a/gemfeed/2024-11-17-f3s-kubernetes-with-freebsd-part-1.md b/gemfeed/2024-11-17-f3s-kubernetes-with-freebsd-part-1.md index 230a77d0..6cd7c6a3 100644 --- a/gemfeed/2024-11-17-f3s-kubernetes-with-freebsd-part-1.md +++ b/gemfeed/2024-11-17-f3s-kubernetes-with-freebsd-part-1.md @@ -8,9 +8,9 @@ I will post a new entry every month or so (there are too many other side project These are all the posts so far: -[2024-11-17 f3s: Kubernetes with FreeBSD - Part 1: Setting the stage (You are currently reading this)](./2024-11-17-f3s-kubernetes-with-freebsd-part-1.md) -[2024-12-03 f3s: Kubernetes with FreeBSD - Part 2: Hardware and base installation](./2024-12-03-f3s-kubernetes-with-freebsd-part-2.md) [2025-02-01 f3s: Kubernetes with FreeBSD - Part 3: Protecting from power cuts](./2025-02-01-f3s-kubernetes-with-freebsd-part-3.md) +[2024-12-03 f3s: Kubernetes with FreeBSD - Part 2: Hardware and base installation](./2024-12-03-f3s-kubernetes-with-freebsd-part-2.md) +[2024-11-17 f3s: Kubernetes with FreeBSD - Part 1: Setting the stage (You are currently reading this)](./2024-11-17-f3s-kubernetes-with-freebsd-part-1.md) [![f3s logo](./f3s-kubernetes-with-freebsd-part-1/f3slogo.png "f3s logo")](./f3s-kubernetes-with-freebsd-part-1/f3slogo.png) @@ -159,14 +159,14 @@ Read the next post of this series: Other *BSD-related posts: -[2016-04-09 Jails and ZFS with Puppet on FreeBSD](./2016-04-09-jails-and-zfs-on-freebsd-with-puppet.md) -[2022-07-30 Let's Encrypt with OpenBSD and Rex](./2022-07-30-lets-encrypt-with-openbsd-and-rex.md) -[2022-10-30 Installing DTail on OpenBSD](./2022-10-30-installing-dtail-on-openbsd.md) -[2024-01-13 One reason why I love OpenBSD](./2024-01-13-one-reason-why-i-love-openbsd.md) -[2024-04-01 KISS high-availability with OpenBSD](./2024-04-01-KISS-high-availability-with-OpenBSD.md) -[2024-11-17 f3s: Kubernetes with FreeBSD - Part 1: Setting the stage (You are currently reading this)](./2024-11-17-f3s-kubernetes-with-freebsd-part-1.md) -[2024-12-03 f3s: Kubernetes with FreeBSD - Part 2: Hardware and base installation](./2024-12-03-f3s-kubernetes-with-freebsd-part-2.md) [2025-02-01 f3s: Kubernetes with FreeBSD - Part 3: Protecting from power cuts](./2025-02-01-f3s-kubernetes-with-freebsd-part-3.md) +[2024-12-03 f3s: Kubernetes with FreeBSD - Part 2: Hardware and base installation](./2024-12-03-f3s-kubernetes-with-freebsd-part-2.md) +[2024-11-17 f3s: Kubernetes with FreeBSD - Part 1: Setting the stage (You are currently reading this)](./2024-11-17-f3s-kubernetes-with-freebsd-part-1.md) +[2024-04-01 KISS high-availability with OpenBSD](./2024-04-01-KISS-high-availability-with-OpenBSD.md) +[2024-01-13 One reason why I love OpenBSD](./2024-01-13-one-reason-why-i-love-openbsd.md) +[2022-10-30 Installing DTail on OpenBSD](./2022-10-30-installing-dtail-on-openbsd.md) +[2022-07-30 Let's Encrypt with OpenBSD and Rex](./2022-07-30-lets-encrypt-with-openbsd-and-rex.md) +[2016-04-09 Jails and ZFS with Puppet on FreeBSD](./2016-04-09-jails-and-zfs-on-freebsd-with-puppet.md) E-Mail your comments to `paul@nospam.buetow.org` :-) diff --git a/gemfeed/2024-12-03-f3s-kubernetes-with-freebsd-part-2.md b/gemfeed/2024-12-03-f3s-kubernetes-with-freebsd-part-2.md index 161f4a1a..5417cbdc 100644 --- a/gemfeed/2024-12-03-f3s-kubernetes-with-freebsd-part-2.md +++ b/gemfeed/2024-12-03-f3s-kubernetes-with-freebsd-part-2.md @@ -8,9 +8,9 @@ We set the stage last time; this time, we will set up the hardware for this proj These are all the posts so far: -[2024-11-17 f3s: Kubernetes with FreeBSD - Part 1: Setting the stage](./2024-11-17-f3s-kubernetes-with-freebsd-part-1.md) -[2024-12-03 f3s: Kubernetes with FreeBSD - Part 2: Hardware and base installation (You are currently reading this)](./2024-12-03-f3s-kubernetes-with-freebsd-part-2.md) [2025-02-01 f3s: Kubernetes with FreeBSD - Part 3: Protecting from power cuts](./2025-02-01-f3s-kubernetes-with-freebsd-part-3.md) +[2024-12-03 f3s: Kubernetes with FreeBSD - Part 2: Hardware and base installation (You are currently reading this)](./2024-12-03-f3s-kubernetes-with-freebsd-part-2.md) +[2024-11-17 f3s: Kubernetes with FreeBSD - Part 1: Setting the stage](./2024-11-17-f3s-kubernetes-with-freebsd-part-1.md) [![f3s logo](./f3s-kubernetes-with-freebsd-part-1/f3slogo.png "f3s logo")](./f3s-kubernetes-with-freebsd-part-1/f3slogo.png) @@ -298,14 +298,14 @@ Read the next post of this series: Other *BSD-related posts: -[2016-04-09 Jails and ZFS with Puppet on FreeBSD](./2016-04-09-jails-and-zfs-on-freebsd-with-puppet.md) -[2022-07-30 Let's Encrypt with OpenBSD and Rex](./2022-07-30-lets-encrypt-with-openbsd-and-rex.md) -[2022-10-30 Installing DTail on OpenBSD](./2022-10-30-installing-dtail-on-openbsd.md) -[2024-01-13 One reason why I love OpenBSD](./2024-01-13-one-reason-why-i-love-openbsd.md) -[2024-04-01 KISS high-availability with OpenBSD](./2024-04-01-KISS-high-availability-with-OpenBSD.md) -[2024-11-17 f3s: Kubernetes with FreeBSD - Part 1: Setting the stage](./2024-11-17-f3s-kubernetes-with-freebsd-part-1.md) -[2024-12-03 f3s: Kubernetes with FreeBSD - Part 2: Hardware and base installation (You are currently reading this)](./2024-12-03-f3s-kubernetes-with-freebsd-part-2.md) [2025-02-01 f3s: Kubernetes with FreeBSD - Part 3: Protecting from power cuts](./2025-02-01-f3s-kubernetes-with-freebsd-part-3.md) +[2024-12-03 f3s: Kubernetes with FreeBSD - Part 2: Hardware and base installation (You are currently reading this)](./2024-12-03-f3s-kubernetes-with-freebsd-part-2.md) +[2024-11-17 f3s: Kubernetes with FreeBSD - Part 1: Setting the stage](./2024-11-17-f3s-kubernetes-with-freebsd-part-1.md) +[2024-04-01 KISS high-availability with OpenBSD](./2024-04-01-KISS-high-availability-with-OpenBSD.md) +[2024-01-13 One reason why I love OpenBSD](./2024-01-13-one-reason-why-i-love-openbsd.md) +[2022-10-30 Installing DTail on OpenBSD](./2022-10-30-installing-dtail-on-openbsd.md) +[2022-07-30 Let's Encrypt with OpenBSD and Rex](./2022-07-30-lets-encrypt-with-openbsd-and-rex.md) +[2016-04-09 Jails and ZFS with Puppet on FreeBSD](./2016-04-09-jails-and-zfs-on-freebsd-with-puppet.md) E-Mail your comments to `paul@nospam.buetow.org` :-) diff --git a/gemfeed/2025-02-01-f3s-kubernetes-with-freebsd-part-3.md b/gemfeed/2025-02-01-f3s-kubernetes-with-freebsd-part-3.md index a464f44f..df9826f5 100644 --- a/gemfeed/2025-02-01-f3s-kubernetes-with-freebsd-part-3.md +++ b/gemfeed/2025-02-01-f3s-kubernetes-with-freebsd-part-3.md @@ -4,9 +4,9 @@ This is the third blog post about my f3s series for my self-hosting demands in my home lab. f3s? The "f" stands for FreeBSD, and the "3s" stands for k3s, the Kubernetes distribution we will use on FreeBSD-based physical machines. -[2024-11-17 f3s: Kubernetes with FreeBSD - Part 1: Setting the stage](./2024-11-17-f3s-kubernetes-with-freebsd-part-1.md) -[2024-12-03 f3s: Kubernetes with FreeBSD - Part 2: Hardware and base installation](./2024-12-03-f3s-kubernetes-with-freebsd-part-2.md) [2025-02-01 f3s: Kubernetes with FreeBSD - Part 3: Protecting from power cuts (You are currently reading this)](./2025-02-01-f3s-kubernetes-with-freebsd-part-3.md) +[2024-12-03 f3s: Kubernetes with FreeBSD - Part 2: Hardware and base installation](./2024-12-03-f3s-kubernetes-with-freebsd-part-2.md) +[2024-11-17 f3s: Kubernetes with FreeBSD - Part 1: Setting the stage](./2024-11-17-f3s-kubernetes-with-freebsd-part-1.md) [![f3s logo](./f3s-kubernetes-with-freebsd-part-1/f3slogo.png "f3s logo")](./f3s-kubernetes-with-freebsd-part-1/f3slogo.png) @@ -352,14 +352,14 @@ All good :-) See you in the next post of this series! Other BSD related posts are: -[2016-04-09 Jails and ZFS with Puppet on FreeBSD](./2016-04-09-jails-and-zfs-on-freebsd-with-puppet.md) -[2022-07-30 Let's Encrypt with OpenBSD and Rex](./2022-07-30-lets-encrypt-with-openbsd-and-rex.md) -[2022-10-30 Installing DTail on OpenBSD](./2022-10-30-installing-dtail-on-openbsd.md) -[2024-01-13 One reason why I love OpenBSD](./2024-01-13-one-reason-why-i-love-openbsd.md) -[2024-04-01 KISS high-availability with OpenBSD](./2024-04-01-KISS-high-availability-with-OpenBSD.md) -[2024-11-17 f3s: Kubernetes with FreeBSD - Part 1: Setting the stage](./2024-11-17-f3s-kubernetes-with-freebsd-part-1.md) -[2024-12-03 f3s: Kubernetes with FreeBSD - Part 2: Hardware and base installation](./2024-12-03-f3s-kubernetes-with-freebsd-part-2.md) [2025-02-01 f3s: Kubernetes with FreeBSD - Part 3: Protecting from power cuts (You are currently reading this)](./2025-02-01-f3s-kubernetes-with-freebsd-part-3.md) +[2024-12-03 f3s: Kubernetes with FreeBSD - Part 2: Hardware and base installation](./2024-12-03-f3s-kubernetes-with-freebsd-part-2.md) +[2024-11-17 f3s: Kubernetes with FreeBSD - Part 1: Setting the stage](./2024-11-17-f3s-kubernetes-with-freebsd-part-1.md) +[2024-04-01 KISS high-availability with OpenBSD](./2024-04-01-KISS-high-availability-with-OpenBSD.md) +[2024-01-13 One reason why I love OpenBSD](./2024-01-13-one-reason-why-i-love-openbsd.md) +[2022-10-30 Installing DTail on OpenBSD](./2022-10-30-installing-dtail-on-openbsd.md) +[2022-07-30 Let's Encrypt with OpenBSD and Rex](./2022-07-30-lets-encrypt-with-openbsd-and-rex.md) +[2016-04-09 Jails and ZFS with Puppet on FreeBSD](./2016-04-09-jails-and-zfs-on-freebsd-with-puppet.md) E-Mail your comments to `paul@nospam.buetow.org` :-) diff --git a/gemfeed/DRAFT-f3s-kubernetes-with-freebsd-part-4.md b/gemfeed/DRAFT-f3s-kubernetes-with-freebsd-part-4.md index 4fc1bc63..fdec9071 100644 --- a/gemfeed/DRAFT-f3s-kubernetes-with-freebsd-part-4.md +++ b/gemfeed/DRAFT-f3s-kubernetes-with-freebsd-part-4.md @@ -2,9 +2,9 @@ This is the thourth blog post about my f3s series for my self-hosting demands in my home lab. f3s? The "f" stands for FreeBSD, and the "3s" stands for k3s, the Kubernetes distribution we will use on FreeBSD-based physical machines. -[2024-11-17 f3s: Kubernetes with FreeBSD - Part 1: Setting the stage](./2024-11-17-f3s-kubernetes-with-freebsd-part-1.md) -[2024-12-03 f3s: Kubernetes with FreeBSD - Part 2: Hardware and base installation](./2024-12-03-f3s-kubernetes-with-freebsd-part-2.md) [2025-02-01 f3s: Kubernetes with FreeBSD - Part 3: Protecting from power cuts](./2025-02-01-f3s-kubernetes-with-freebsd-part-3.md) +[2024-12-03 f3s: Kubernetes with FreeBSD - Part 2: Hardware and base installation](./2024-12-03-f3s-kubernetes-with-freebsd-part-2.md) +[2024-11-17 f3s: Kubernetes with FreeBSD - Part 1: Setting the stage](./2024-11-17-f3s-kubernetes-with-freebsd-part-1.md) [![f3s logo](./f3s-kubernetes-with-frhyveeebsd-part-1/f3slogo.png "f3s logo")](./f3s-kubernetes-with-frhyveeebsd-part-1/f3slogo.png) @@ -265,14 +265,14 @@ CPU STRESS TESTER VM VS NOT VM Other *BSD-related posts: -[2016-04-09 Jails and ZFS with Puppet on FreeBSD](./2016-04-09-jails-and-zfs-on-freebsd-with-puppet.md) -[2022-07-30 Let's Encrypt with OpenBSD and Rex](./2022-07-30-lets-encrypt-with-openbsd-and-rex.md) -[2022-10-30 Installing DTail on OpenBSD](./2022-10-30-installing-dtail-on-openbsd.md) -[2024-01-13 One reason why I love OpenBSD](./2024-01-13-one-reason-why-i-love-openbsd.md) -[2024-04-01 KISS high-availability with OpenBSD](./2024-04-01-KISS-high-availability-with-OpenBSD.md) -[2024-11-17 f3s: Kubernetes with FreeBSD - Part 1: Setting the stage](./2024-11-17-f3s-kubernetes-with-freebsd-part-1.md) -[2024-12-03 f3s: Kubernetes with FreeBSD - Part 2: Hardware and base installation](./2024-12-03-f3s-kubernetes-with-freebsd-part-2.md) [2025-02-01 f3s: Kubernetes with FreeBSD - Part 3: Protecting from power cuts](./2025-02-01-f3s-kubernetes-with-freebsd-part-3.md) +[2024-12-03 f3s: Kubernetes with FreeBSD - Part 2: Hardware and base installation](./2024-12-03-f3s-kubernetes-with-freebsd-part-2.md) +[2024-11-17 f3s: Kubernetes with FreeBSD - Part 1: Setting the stage](./2024-11-17-f3s-kubernetes-with-freebsd-part-1.md) +[2024-04-01 KISS high-availability with OpenBSD](./2024-04-01-KISS-high-availability-with-OpenBSD.md) +[2024-01-13 One reason why I love OpenBSD](./2024-01-13-one-reason-why-i-love-openbsd.md) +[2022-10-30 Installing DTail on OpenBSD](./2022-10-30-installing-dtail-on-openbsd.md) +[2022-07-30 Let's Encrypt with OpenBSD and Rex](./2022-07-30-lets-encrypt-with-openbsd-and-rex.md) +[2016-04-09 Jails and ZFS with Puppet on FreeBSD](./2016-04-09-jails-and-zfs-on-freebsd-with-puppet.md) E-Mail your comments to `paul@nospam.buetow.org` :-) -- cgit v1.2.3 From f0900c46294c105f093076f210311a851093d943 Mon Sep 17 00:00:00 2001 From: Paul Buetow Date: Sun, 2 Feb 2025 10:54:25 +0200 Subject: Update content for md --- gemfeed/2021-11-29-bash-golf-part-1.md | 4 ++-- gemfeed/2022-01-01-bash-golf-part-2.md | 4 ++-- ...1-unveiling-guprecords:-uptime-records-with-raku.md | 8 ++++---- .../2023-08-18-site-reliability-engineering-part-1.md | 6 +++--- gemfeed/2023-09-25-dtail-usage-examples.md | 6 +++--- ...-kiss-static-web-photo-albums-with-photoalbum.sh.md | 16 ++++++++-------- gemfeed/2023-11-11-mind-management-book-notes.md | 14 +++++++------- .../2023-11-19-site-reliability-engineering-part-2.md | 6 +++--- gemfeed/2023-12-10-bash-golf-part-3.md | 12 ++++++------ .../2024-01-09-site-reliability-engineering-part-3.md | 6 +++--- gemfeed/2024-01-13-one-reason-why-i-love-openbsd.md | 14 +++++++------- .../2024-04-01-KISS-high-availability-with-OpenBSD.md | 18 +++++++++--------- gemfeed/2024-05-01-slow-productivity-book-notes.md | 14 +++++++------- gemfeed/2024-07-07-the-stoic-challenge-book-notes.md | 14 +++++++------- .../2024-09-07-site-reliability-engineering-part-4.md | 6 +++--- .../2024-10-02-gemtexter-3.0.0-lets-gemtext-again-4.md | 10 +++++----- gemfeed/2024-10-24-staff-engineer-book-notes.md | 14 +++++++------- .../2024-11-17-f3s-kubernetes-with-freebsd-part-1.md | 18 +++++++++--------- .../2024-12-03-f3s-kubernetes-with-freebsd-part-2.md | 18 +++++++++--------- .../2025-02-01-f3s-kubernetes-with-freebsd-part-3.md | 18 +++++++++--------- gemfeed/DRAFT-f3s-kubernetes-with-freebsd-part-4.md | 18 +++++++++--------- 21 files changed, 122 insertions(+), 122 deletions(-) (limited to 'gemfeed') diff --git a/gemfeed/2021-11-29-bash-golf-part-1.md b/gemfeed/2021-11-29-bash-golf-part-1.md index b7959f14..bc9ec420 100644 --- a/gemfeed/2021-11-29-bash-golf-part-1.md +++ b/gemfeed/2021-11-29-bash-golf-part-1.md @@ -4,9 +4,9 @@ This is the first blog post about my Bash Golf series. This series is about random Bash tips, tricks and weirdnesses I came across. It's a collection of smaller articles I wrote in an older (in German language) blog, which I translated and refreshed with some new content. -[2023-12-10 Bash Golf Part 3](./2023-12-10-bash-golf-part-3.md) -[2022-01-01 Bash Golf Part 2](./2022-01-01-bash-golf-part-2.md) [2021-11-29 Bash Golf Part 1 (You are currently reading this)](./2021-11-29-bash-golf-part-1.md) +[2022-01-01 Bash Golf Part 2](./2022-01-01-bash-golf-part-2.md) +[2023-12-10 Bash Golf Part 3](./2023-12-10-bash-golf-part-3.md) ``` diff --git a/gemfeed/2022-01-01-bash-golf-part-2.md b/gemfeed/2022-01-01-bash-golf-part-2.md index 1f028f18..84238b32 100644 --- a/gemfeed/2022-01-01-bash-golf-part-2.md +++ b/gemfeed/2022-01-01-bash-golf-part-2.md @@ -4,9 +4,9 @@ This is the second blog post about my Bash Golf series. This series is random Bash tips, tricks and weirdnesses I came across. It's a collection of smaller articles I wrote in an older (in German language) blog, which I translated and refreshed with some new content. -[2023-12-10 Bash Golf Part 3](./2023-12-10-bash-golf-part-3.md) -[2022-01-01 Bash Golf Part 2 (You are currently reading this)](./2022-01-01-bash-golf-part-2.md) [2021-11-29 Bash Golf Part 1](./2021-11-29-bash-golf-part-1.md) +[2022-01-01 Bash Golf Part 2 (You are currently reading this)](./2022-01-01-bash-golf-part-2.md) +[2023-12-10 Bash Golf Part 3](./2023-12-10-bash-golf-part-3.md) ``` diff --git a/gemfeed/2023-05-01-unveiling-guprecords:-uptime-records-with-raku.md b/gemfeed/2023-05-01-unveiling-guprecords:-uptime-records-with-raku.md index 4fb6d039..c1136931 100644 --- a/gemfeed/2023-05-01-unveiling-guprecords:-uptime-records-with-raku.md +++ b/gemfeed/2023-05-01-unveiling-guprecords:-uptime-records-with-raku.md @@ -159,10 +159,10 @@ E-Mail your comments to hi@foo.zone :-) Other related posts are: -[2023-05-01 Unveiling `guprecords.raku`: Global Uptime Records with Raku (You are currently reading this)](./2023-05-01-unveiling-guprecords:-uptime-records-with-raku.md) -[2022-06-15 Sweating the small stuff - Tiny projects of mine](./2022-06-15-sweating-the-small-stuff.md) -[2022-05-27 Perl is still a great choice](./2022-05-27-perl-is-still-a-great-choice.md) -[2011-05-07 Perl Daemon (Service Framework)](./2011-05-07-perl-daemon-service-framework.md) [2008-06-26 Perl Poetry](./2008-06-26-perl-poetry.md) +[2011-05-07 Perl Daemon (Service Framework)](./2011-05-07-perl-daemon-service-framework.md) +[2022-05-27 Perl is still a great choice](./2022-05-27-perl-is-still-a-great-choice.md) +[2022-06-15 Sweating the small stuff - Tiny projects of mine](./2022-06-15-sweating-the-small-stuff.md) +[2023-05-01 Unveiling `guprecords.raku`: Global Uptime Records with Raku (You are currently reading this)](./2023-05-01-unveiling-guprecords:-uptime-records-with-raku.md) [Back to the main site](../) diff --git a/gemfeed/2023-08-18-site-reliability-engineering-part-1.md b/gemfeed/2023-08-18-site-reliability-engineering-part-1.md index 1adfc337..5c61f9ac 100644 --- a/gemfeed/2023-08-18-site-reliability-engineering-part-1.md +++ b/gemfeed/2023-08-18-site-reliability-engineering-part-1.md @@ -4,10 +4,10 @@ Being a Site Reliability Engineer (SRE) is like stepping into a lively, ever-evolving universe. The world of SRE mixes together different tech, a unique culture, and a whole lot of determination. It’s one of the toughest but most exciting jobs out there. There's zero chance of getting bored because there's always a fresh challenge to tackle and new technology to play around with. It's not just about the tech side of things either; it's heavily rooted in communication, collaboration, and teamwork. As someone currently working as an SRE, I’m here to break it all down for you in this blog series. Let's dive into what SRE is really all about! -[2024-09-07 Site Reliability Engineering - Part 4: Onboarding for On-Call Engineers](./2024-09-07-site-reliability-engineering-part-4.md) -[2024-01-09 Site Reliability Engineering - Part 3: On-Call Culture](./2024-01-09-site-reliability-engineering-part-3.md) -[2023-11-19 Site Reliability Engineering - Part 2: Operational Balance](./2023-11-19-site-reliability-engineering-part-2.md) [2023-08-18 Site Reliability Engineering - Part 1: SRE and Organizational Culture (You are currently reading this)](./2023-08-18-site-reliability-engineering-part-1.md) +[2023-11-19 Site Reliability Engineering - Part 2: Operational Balance](./2023-11-19-site-reliability-engineering-part-2.md) +[2024-01-09 Site Reliability Engineering - Part 3: On-Call Culture](./2024-01-09-site-reliability-engineering-part-3.md) +[2024-09-07 Site Reliability Engineering - Part 4: Onboarding for On-Call Engineers](./2024-09-07-site-reliability-engineering-part-4.md) ``` ▓▓▓▓░░ diff --git a/gemfeed/2023-09-25-dtail-usage-examples.md b/gemfeed/2023-09-25-dtail-usage-examples.md index 8df87a93..595afb36 100644 --- a/gemfeed/2023-09-25-dtail-usage-examples.md +++ b/gemfeed/2023-09-25-dtail-usage-examples.md @@ -248,10 +248,10 @@ E-Mail your comments to `paul@nospam.buetow.org` :-) Other related posts are: -[2023-09-25 DTail usage examples (You are currently reading this)](./2023-09-25-dtail-usage-examples.md) -[2022-10-30 Installing DTail on OpenBSD](./2022-10-30-installing-dtail-on-openbsd.md) -[2022-03-06 The release of DTail 4.0.0](./2022-03-06-the-release-of-dtail-4.0.0.md) [2021-04-22 DTail - The distributed log tail program](./2021-04-22-dtail-the-distributed-log-tail-program.md) +[2022-03-06 The release of DTail 4.0.0](./2022-03-06-the-release-of-dtail-4.0.0.md) +[2022-10-30 Installing DTail on OpenBSD](./2022-10-30-installing-dtail-on-openbsd.md) +[2023-09-25 DTail usage examples (You are currently reading this)](./2023-09-25-dtail-usage-examples.md) I hope you find the tools presented in this post useful! diff --git a/gemfeed/2023-10-29-kiss-static-web-photo-albums-with-photoalbum.sh.md b/gemfeed/2023-10-29-kiss-static-web-photo-albums-with-photoalbum.sh.md index 2121886c..dd8c0167 100644 --- a/gemfeed/2023-10-29-kiss-static-web-photo-albums-with-photoalbum.sh.md +++ b/gemfeed/2023-10-29-kiss-static-web-photo-albums-with-photoalbum.sh.md @@ -272,14 +272,14 @@ E-Mail your comments to `paul@nospam.buetow.org` :-) Other Bash and KISS-related posts are: -[2024-04-01 KISS high-availability with OpenBSD](./2024-04-01-KISS-high-availability-with-OpenBSD.md) -[2023-12-10 Bash Golf Part 3](./2023-12-10-bash-golf-part-3.md) -[2023-10-29 KISS static web photo albums with `photoalbum.sh` (You are currently reading this)](./2023-10-29-kiss-static-web-photo-albums-with-photoalbum.sh.md) -[2023-06-01 KISS server monitoring with Gogios](./2023-06-01-kiss-server-monitoring-with-gogios.md) -[2022-01-01 Bash Golf Part 2](./2022-01-01-bash-golf-part-2.md) -[2021-11-29 Bash Golf Part 1](./2021-11-29-bash-golf-part-1.md) -[2021-09-12 Keep it simple and stupid](./2021-09-12-keep-it-simple-and-stupid.md) -[2021-06-05 Gemtexter - One Bash script to rule it all](./2021-06-05-gemtexter-one-bash-script-to-rule-it-all.md) [2021-05-16 Personal Bash coding style guide](./2021-05-16-personal-bash-coding-style-guide.md) +[2021-06-05 Gemtexter - One Bash script to rule it all](./2021-06-05-gemtexter-one-bash-script-to-rule-it-all.md) +[2021-09-12 Keep it simple and stupid](./2021-09-12-keep-it-simple-and-stupid.md) +[2021-11-29 Bash Golf Part 1](./2021-11-29-bash-golf-part-1.md) +[2022-01-01 Bash Golf Part 2](./2022-01-01-bash-golf-part-2.md) +[2023-06-01 KISS server monitoring with Gogios](./2023-06-01-kiss-server-monitoring-with-gogios.md) +[2023-10-29 KISS static web photo albums with `photoalbum.sh` (You are currently reading this)](./2023-10-29-kiss-static-web-photo-albums-with-photoalbum.sh.md) +[2023-12-10 Bash Golf Part 3](./2023-12-10-bash-golf-part-3.md) +[2024-04-01 KISS high-availability with OpenBSD](./2024-04-01-KISS-high-availability-with-OpenBSD.md) [Back to the main site](../) diff --git a/gemfeed/2023-11-11-mind-management-book-notes.md b/gemfeed/2023-11-11-mind-management-book-notes.md index 2cefef51..96a2c6e5 100644 --- a/gemfeed/2023-11-11-mind-management-book-notes.md +++ b/gemfeed/2023-11-11-mind-management-book-notes.md @@ -110,13 +110,13 @@ E-Mail your comments to `paul@nospam.buetow.org` :-) Other book notes of mine are: -[2024-10-24 "Staff Engineer" book notes](./2024-10-24-staff-engineer-book-notes.md) -[2024-07-07 "The Stoic Challenge" book notes](./2024-07-07-the-stoic-challenge-book-notes.md) -[2024-05-01 "Slow Productivity" book notes](./2024-05-01-slow-productivity-book-notes.md) -[2023-11-11 "Mind Management" book notes (You are currently reading this)](./2023-11-11-mind-management-book-notes.md) -[2023-07-17 "Software Developmers Career Guide and Soft Skills" book notes](./2023-07-17-career-guide-and-soft-skills-book-notes.md) -[2023-05-06 "The Obstacle is the Way" book notes](./2023-05-06-the-obstacle-is-the-way-book-notes.md) -[2023-04-01 "Never split the difference" book notes](./2023-04-01-never-split-the-difference-book-notes.md) [2023-03-16 "The Pragmatic Programmer" book notes](./2023-03-16-the-pragmatic-programmer-book-notes.md) +[2023-04-01 "Never split the difference" book notes](./2023-04-01-never-split-the-difference-book-notes.md) +[2023-05-06 "The Obstacle is the Way" book notes](./2023-05-06-the-obstacle-is-the-way-book-notes.md) +[2023-07-17 "Software Developmers Career Guide and Soft Skills" book notes](./2023-07-17-career-guide-and-soft-skills-book-notes.md) +[2023-11-11 "Mind Management" book notes (You are currently reading this)](./2023-11-11-mind-management-book-notes.md) +[2024-05-01 "Slow Productivity" book notes](./2024-05-01-slow-productivity-book-notes.md) +[2024-07-07 "The Stoic Challenge" book notes](./2024-07-07-the-stoic-challenge-book-notes.md) +[2024-10-24 "Staff Engineer" book notes](./2024-10-24-staff-engineer-book-notes.md) [Back to the main site](../) diff --git a/gemfeed/2023-11-19-site-reliability-engineering-part-2.md b/gemfeed/2023-11-19-site-reliability-engineering-part-2.md index 3220e499..29749257 100644 --- a/gemfeed/2023-11-19-site-reliability-engineering-part-2.md +++ b/gemfeed/2023-11-19-site-reliability-engineering-part-2.md @@ -4,10 +4,10 @@ This is the second part of my Site Reliability Engineering (SRE) series. I am currently employed as a Site Reliability Engineer and will try to share what SRE is about in this blog series. -[2024-09-07 Site Reliability Engineering - Part 4: Onboarding for On-Call Engineers](./2024-09-07-site-reliability-engineering-part-4.md) -[2024-01-09 Site Reliability Engineering - Part 3: On-Call Culture](./2024-01-09-site-reliability-engineering-part-3.md) -[2023-11-19 Site Reliability Engineering - Part 2: Operational Balance (You are currently reading this)](./2023-11-19-site-reliability-engineering-part-2.md) [2023-08-18 Site Reliability Engineering - Part 1: SRE and Organizational Culture](./2023-08-18-site-reliability-engineering-part-1.md) +[2023-11-19 Site Reliability Engineering - Part 2: Operational Balance (You are currently reading this)](./2023-11-19-site-reliability-engineering-part-2.md) +[2024-01-09 Site Reliability Engineering - Part 3: On-Call Culture](./2024-01-09-site-reliability-engineering-part-3.md) +[2024-09-07 Site Reliability Engineering - Part 4: Onboarding for On-Call Engineers](./2024-09-07-site-reliability-engineering-part-4.md) ``` ⠀⠀⠀⠀⠀⠀⠀⠀⠀⠀⠀⠀⢀⣠⣾⣷⣄⡀⠀⠀⠀⠀⠀⠀⠀⠀⠀⠀⠀⠀ diff --git a/gemfeed/2023-12-10-bash-golf-part-3.md b/gemfeed/2023-12-10-bash-golf-part-3.md index 99716dd7..f315e387 100644 --- a/gemfeed/2023-12-10-bash-golf-part-3.md +++ b/gemfeed/2023-12-10-bash-golf-part-3.md @@ -4,9 +4,9 @@ This is the third blog post about my Bash Golf series. This series is random Bash tips, tricks, and weirdnesses I have encountered over time. -[2023-12-10 Bash Golf Part 3 (You are currently reading this)](./2023-12-10-bash-golf-part-3.md) -[2022-01-01 Bash Golf Part 2](./2022-01-01-bash-golf-part-2.md) [2021-11-29 Bash Golf Part 1](./2021-11-29-bash-golf-part-1.md) +[2022-01-01 Bash Golf Part 2](./2022-01-01-bash-golf-part-2.md) +[2023-12-10 Bash Golf Part 3 (You are currently reading this)](./2023-12-10-bash-golf-part-3.md) ``` @@ -371,10 +371,10 @@ E-Mail your comments to `paul@nospam.buetow.org` :-) Other related posts are: -[2023-12-10 Bash Golf Part 3 (You are currently reading this)](./2023-12-10-bash-golf-part-3.md) -[2022-01-01 Bash Golf Part 2](./2022-01-01-bash-golf-part-2.md) -[2021-11-29 Bash Golf Part 1](./2021-11-29-bash-golf-part-1.md) -[2021-06-05 Gemtexter - One Bash script to rule it all](./2021-06-05-gemtexter-one-bash-script-to-rule-it-all.md) [2021-05-16 Personal Bash coding style guide](./2021-05-16-personal-bash-coding-style-guide.md) +[2021-06-05 Gemtexter - One Bash script to rule it all](./2021-06-05-gemtexter-one-bash-script-to-rule-it-all.md) +[2021-11-29 Bash Golf Part 1](./2021-11-29-bash-golf-part-1.md) +[2022-01-01 Bash Golf Part 2](./2022-01-01-bash-golf-part-2.md) +[2023-12-10 Bash Golf Part 3 (You are currently reading this)](./2023-12-10-bash-golf-part-3.md) [Back to the main site](../) diff --git a/gemfeed/2024-01-09-site-reliability-engineering-part-3.md b/gemfeed/2024-01-09-site-reliability-engineering-part-3.md index 6627fa62..15b9a170 100644 --- a/gemfeed/2024-01-09-site-reliability-engineering-part-3.md +++ b/gemfeed/2024-01-09-site-reliability-engineering-part-3.md @@ -4,10 +4,10 @@ Welcome to Part 3 of my Site Reliability Engineering (SRE) series. I'm currently working as a Site Reliability Engineer, and I’m here to share what SRE is all about in this blog series. -[2024-09-07 Site Reliability Engineering - Part 4: Onboarding for On-Call Engineers](./2024-09-07-site-reliability-engineering-part-4.md) -[2024-01-09 Site Reliability Engineering - Part 3: On-Call Culture (You are currently reading this)](./2024-01-09-site-reliability-engineering-part-3.md) -[2023-11-19 Site Reliability Engineering - Part 2: Operational Balance](./2023-11-19-site-reliability-engineering-part-2.md) [2023-08-18 Site Reliability Engineering - Part 1: SRE and Organizational Culture](./2023-08-18-site-reliability-engineering-part-1.md) +[2023-11-19 Site Reliability Engineering - Part 2: Operational Balance](./2023-11-19-site-reliability-engineering-part-2.md) +[2024-01-09 Site Reliability Engineering - Part 3: On-Call Culture (You are currently reading this)](./2024-01-09-site-reliability-engineering-part-3.md) +[2024-09-07 Site Reliability Engineering - Part 4: Onboarding for On-Call Engineers](./2024-09-07-site-reliability-engineering-part-4.md) ``` ..--""""----.. diff --git a/gemfeed/2024-01-13-one-reason-why-i-love-openbsd.md b/gemfeed/2024-01-13-one-reason-why-i-love-openbsd.md index 531c4581..92598532 100644 --- a/gemfeed/2024-01-13-one-reason-why-i-love-openbsd.md +++ b/gemfeed/2024-01-13-one-reason-why-i-love-openbsd.md @@ -51,13 +51,13 @@ E-Mail your comments to `paul@nospam.buetow.org` :-) Other *BSD related posts are: -[2025-02-01 f3s: Kubernetes with FreeBSD - Part 3: Protecting from power cuts](./2025-02-01-f3s-kubernetes-with-freebsd-part-3.md) -[2024-12-03 f3s: Kubernetes with FreeBSD - Part 2: Hardware and base installation](./2024-12-03-f3s-kubernetes-with-freebsd-part-2.md) -[2024-11-17 f3s: Kubernetes with FreeBSD - Part 1: Setting the stage](./2024-11-17-f3s-kubernetes-with-freebsd-part-1.md) -[2024-04-01 KISS high-availability with OpenBSD](./2024-04-01-KISS-high-availability-with-OpenBSD.md) -[2024-01-13 One reason why I love OpenBSD (You are currently reading this)](./2024-01-13-one-reason-why-i-love-openbsd.md) -[2022-10-30 Installing DTail on OpenBSD](./2022-10-30-installing-dtail-on-openbsd.md) -[2022-07-30 Let's Encrypt with OpenBSD and Rex](./2022-07-30-lets-encrypt-with-openbsd-and-rex.md) [2016-04-09 Jails and ZFS with Puppet on FreeBSD](./2016-04-09-jails-and-zfs-on-freebsd-with-puppet.md) +[2022-07-30 Let's Encrypt with OpenBSD and Rex](./2022-07-30-lets-encrypt-with-openbsd-and-rex.md) +[2022-10-30 Installing DTail on OpenBSD](./2022-10-30-installing-dtail-on-openbsd.md) +[2024-01-13 One reason why I love OpenBSD (You are currently reading this)](./2024-01-13-one-reason-why-i-love-openbsd.md) +[2024-04-01 KISS high-availability with OpenBSD](./2024-04-01-KISS-high-availability-with-OpenBSD.md) +[2024-11-17 f3s: Kubernetes with FreeBSD - Part 1: Setting the stage](./2024-11-17-f3s-kubernetes-with-freebsd-part-1.md) +[2024-12-03 f3s: Kubernetes with FreeBSD - Part 2: Hardware and base installation](./2024-12-03-f3s-kubernetes-with-freebsd-part-2.md) +[2025-02-01 f3s: Kubernetes with FreeBSD - Part 3: Protecting from power cuts](./2025-02-01-f3s-kubernetes-with-freebsd-part-3.md) [Back to the main site](../) diff --git a/gemfeed/2024-04-01-KISS-high-availability-with-OpenBSD.md b/gemfeed/2024-04-01-KISS-high-availability-with-OpenBSD.md index 4a53071f..66e17f82 100644 --- a/gemfeed/2024-04-01-KISS-high-availability-with-OpenBSD.md +++ b/gemfeed/2024-04-01-KISS-high-availability-with-OpenBSD.md @@ -300,15 +300,15 @@ E-Mail your comments to `paul@nospam.buetow.org` :-) Other *BSD and KISS related posts are: -[2025-02-01 f3s: Kubernetes with FreeBSD - Part 3: Protecting from power cuts](./2025-02-01-f3s-kubernetes-with-freebsd-part-3.md) -[2024-12-03 f3s: Kubernetes with FreeBSD - Part 2: Hardware and base installation](./2024-12-03-f3s-kubernetes-with-freebsd-part-2.md) -[2024-11-17 f3s: Kubernetes with FreeBSD - Part 1: Setting the stage](./2024-11-17-f3s-kubernetes-with-freebsd-part-1.md) -[2024-04-01 KISS high-availability with OpenBSD (You are currently reading this)](./2024-04-01-KISS-high-availability-with-OpenBSD.md) -[2024-01-13 One reason why I love OpenBSD](./2024-01-13-one-reason-why-i-love-openbsd.md) -[2023-10-29 KISS static web photo albums with `photoalbum.sh`](./2023-10-29-kiss-static-web-photo-albums-with-photoalbum.sh.md) -[2023-06-01 KISS server monitoring with Gogios](./2023-06-01-kiss-server-monitoring-with-gogios.md) -[2022-10-30 Installing DTail on OpenBSD](./2022-10-30-installing-dtail-on-openbsd.md) -[2022-07-30 Let's Encrypt with OpenBSD and Rex](./2022-07-30-lets-encrypt-with-openbsd-and-rex.md) [2016-04-09 Jails and ZFS with Puppet on FreeBSD](./2016-04-09-jails-and-zfs-on-freebsd-with-puppet.md) +[2022-07-30 Let's Encrypt with OpenBSD and Rex](./2022-07-30-lets-encrypt-with-openbsd-and-rex.md) +[2022-10-30 Installing DTail on OpenBSD](./2022-10-30-installing-dtail-on-openbsd.md) +[2023-06-01 KISS server monitoring with Gogios](./2023-06-01-kiss-server-monitoring-with-gogios.md) +[2023-10-29 KISS static web photo albums with `photoalbum.sh`](./2023-10-29-kiss-static-web-photo-albums-with-photoalbum.sh.md) +[2024-01-13 One reason why I love OpenBSD](./2024-01-13-one-reason-why-i-love-openbsd.md) +[2024-04-01 KISS high-availability with OpenBSD (You are currently reading this)](./2024-04-01-KISS-high-availability-with-OpenBSD.md) +[2024-11-17 f3s: Kubernetes with FreeBSD - Part 1: Setting the stage](./2024-11-17-f3s-kubernetes-with-freebsd-part-1.md) +[2024-12-03 f3s: Kubernetes with FreeBSD - Part 2: Hardware and base installation](./2024-12-03-f3s-kubernetes-with-freebsd-part-2.md) +[2025-02-01 f3s: Kubernetes with FreeBSD - Part 3: Protecting from power cuts](./2025-02-01-f3s-kubernetes-with-freebsd-part-3.md) [Back to the main site](../) diff --git a/gemfeed/2024-05-01-slow-productivity-book-notes.md b/gemfeed/2024-05-01-slow-productivity-book-notes.md index 00349dd1..6fde73fa 100644 --- a/gemfeed/2024-05-01-slow-productivity-book-notes.md +++ b/gemfeed/2024-05-01-slow-productivity-book-notes.md @@ -138,13 +138,13 @@ E-Mail your comments to `paul@nospam.buetow.org` :-) Other book notes of mine are: -[2024-10-24 "Staff Engineer" book notes](./2024-10-24-staff-engineer-book-notes.md) -[2024-07-07 "The Stoic Challenge" book notes](./2024-07-07-the-stoic-challenge-book-notes.md) -[2024-05-01 "Slow Productivity" book notes (You are currently reading this)](./2024-05-01-slow-productivity-book-notes.md) -[2023-11-11 "Mind Management" book notes](./2023-11-11-mind-management-book-notes.md) -[2023-07-17 "Software Developmers Career Guide and Soft Skills" book notes](./2023-07-17-career-guide-and-soft-skills-book-notes.md) -[2023-05-06 "The Obstacle is the Way" book notes](./2023-05-06-the-obstacle-is-the-way-book-notes.md) -[2023-04-01 "Never split the difference" book notes](./2023-04-01-never-split-the-difference-book-notes.md) [2023-03-16 "The Pragmatic Programmer" book notes](./2023-03-16-the-pragmatic-programmer-book-notes.md) +[2023-04-01 "Never split the difference" book notes](./2023-04-01-never-split-the-difference-book-notes.md) +[2023-05-06 "The Obstacle is the Way" book notes](./2023-05-06-the-obstacle-is-the-way-book-notes.md) +[2023-07-17 "Software Developmers Career Guide and Soft Skills" book notes](./2023-07-17-career-guide-and-soft-skills-book-notes.md) +[2023-11-11 "Mind Management" book notes](./2023-11-11-mind-management-book-notes.md) +[2024-05-01 "Slow Productivity" book notes (You are currently reading this)](./2024-05-01-slow-productivity-book-notes.md) +[2024-07-07 "The Stoic Challenge" book notes](./2024-07-07-the-stoic-challenge-book-notes.md) +[2024-10-24 "Staff Engineer" book notes](./2024-10-24-staff-engineer-book-notes.md) [Back to the main site](../) diff --git a/gemfeed/2024-07-07-the-stoic-challenge-book-notes.md b/gemfeed/2024-07-07-the-stoic-challenge-book-notes.md index 0e3b0ed4..395ad2e8 100644 --- a/gemfeed/2024-07-07-the-stoic-challenge-book-notes.md +++ b/gemfeed/2024-07-07-the-stoic-challenge-book-notes.md @@ -57,13 +57,13 @@ E-Mail your comments to `paul@nospam.buetow.org` :-) Other book notes of mine are: -[2024-10-24 "Staff Engineer" book notes](./2024-10-24-staff-engineer-book-notes.md) -[2024-07-07 "The Stoic Challenge" book notes (You are currently reading this)](./2024-07-07-the-stoic-challenge-book-notes.md) -[2024-05-01 "Slow Productivity" book notes](./2024-05-01-slow-productivity-book-notes.md) -[2023-11-11 "Mind Management" book notes](./2023-11-11-mind-management-book-notes.md) -[2023-07-17 "Software Developmers Career Guide and Soft Skills" book notes](./2023-07-17-career-guide-and-soft-skills-book-notes.md) -[2023-05-06 "The Obstacle is the Way" book notes](./2023-05-06-the-obstacle-is-the-way-book-notes.md) -[2023-04-01 "Never split the difference" book notes](./2023-04-01-never-split-the-difference-book-notes.md) [2023-03-16 "The Pragmatic Programmer" book notes](./2023-03-16-the-pragmatic-programmer-book-notes.md) +[2023-04-01 "Never split the difference" book notes](./2023-04-01-never-split-the-difference-book-notes.md) +[2023-05-06 "The Obstacle is the Way" book notes](./2023-05-06-the-obstacle-is-the-way-book-notes.md) +[2023-07-17 "Software Developmers Career Guide and Soft Skills" book notes](./2023-07-17-career-guide-and-soft-skills-book-notes.md) +[2023-11-11 "Mind Management" book notes](./2023-11-11-mind-management-book-notes.md) +[2024-05-01 "Slow Productivity" book notes](./2024-05-01-slow-productivity-book-notes.md) +[2024-07-07 "The Stoic Challenge" book notes (You are currently reading this)](./2024-07-07-the-stoic-challenge-book-notes.md) +[2024-10-24 "Staff Engineer" book notes](./2024-10-24-staff-engineer-book-notes.md) [Back to the main site](../) diff --git a/gemfeed/2024-09-07-site-reliability-engineering-part-4.md b/gemfeed/2024-09-07-site-reliability-engineering-part-4.md index 2b5e8b2f..4af52caf 100644 --- a/gemfeed/2024-09-07-site-reliability-engineering-part-4.md +++ b/gemfeed/2024-09-07-site-reliability-engineering-part-4.md @@ -4,10 +4,10 @@ Welcome to Part 4 of my Site Reliability Engineering (SRE) series. I'm currently working as a Site Reliability Engineer, and I’m here to share what SRE is all about in this blog series. -[2024-09-07 Site Reliability Engineering - Part 4: Onboarding for On-Call Engineers (You are currently reading this)](./2024-09-07-site-reliability-engineering-part-4.md) -[2024-01-09 Site Reliability Engineering - Part 3: On-Call Culture](./2024-01-09-site-reliability-engineering-part-3.md) -[2023-11-19 Site Reliability Engineering - Part 2: Operational Balance](./2023-11-19-site-reliability-engineering-part-2.md) [2023-08-18 Site Reliability Engineering - Part 1: SRE and Organizational Culture](./2023-08-18-site-reliability-engineering-part-1.md) +[2023-11-19 Site Reliability Engineering - Part 2: Operational Balance](./2023-11-19-site-reliability-engineering-part-2.md) +[2024-01-09 Site Reliability Engineering - Part 3: On-Call Culture](./2024-01-09-site-reliability-engineering-part-3.md) +[2024-09-07 Site Reliability Engineering - Part 4: Onboarding for On-Call Engineers (You are currently reading this)](./2024-09-07-site-reliability-engineering-part-4.md) ``` __..._ _...__ diff --git a/gemfeed/2024-10-02-gemtexter-3.0.0-lets-gemtext-again-4.md b/gemfeed/2024-10-02-gemtexter-3.0.0-lets-gemtext-again-4.md index 322fb989..a4a8554e 100644 --- a/gemfeed/2024-10-02-gemtexter-3.0.0-lets-gemtext-again-4.md +++ b/gemfeed/2024-10-02-gemtexter-3.0.0-lets-gemtext-again-4.md @@ -76,11 +76,11 @@ E-Mail your comments to `paul@nospam.buetow.org` :-) Other related posts are: -[2024-10-02 Gemtexter 3.0.0 - Let's Gemtext again⁴ (You are currently reading this)](./2024-10-02-gemtexter-3.0.0-lets-gemtext-again-4.md) -[2023-07-21 Gemtexter 2.1.0 - Let's Gemtext again³](./2023-07-21-gemtexter-2.1.0-lets-gemtext-again-3.md) -[2023-03-25 Gemtexter 2.0.0 - Let's Gemtext again²](./2023-03-25-gemtexter-2.0.0-lets-gemtext-again-2.md) -[2022-08-27 Gemtexter 1.1.0 - Let's Gemtext again](./2022-08-27-gemtexter-1.1.0-lets-gemtext-again.md) -[2021-06-05 Gemtexter - One Bash script to rule it all](./2021-06-05-gemtexter-one-bash-script-to-rule-it-all.md) [2021-04-24 Welcome to the Geminispace](./2021-04-24-welcome-to-the-geminispace.md) +[2021-06-05 Gemtexter - One Bash script to rule it all](./2021-06-05-gemtexter-one-bash-script-to-rule-it-all.md) +[2022-08-27 Gemtexter 1.1.0 - Let's Gemtext again](./2022-08-27-gemtexter-1.1.0-lets-gemtext-again.md) +[2023-03-25 Gemtexter 2.0.0 - Let's Gemtext again²](./2023-03-25-gemtexter-2.0.0-lets-gemtext-again-2.md) +[2023-07-21 Gemtexter 2.1.0 - Let's Gemtext again³](./2023-07-21-gemtexter-2.1.0-lets-gemtext-again-3.md) +[2024-10-02 Gemtexter 3.0.0 - Let's Gemtext again⁴ (You are currently reading this)](./2024-10-02-gemtexter-3.0.0-lets-gemtext-again-4.md) [Back to the main site](../) diff --git a/gemfeed/2024-10-24-staff-engineer-book-notes.md b/gemfeed/2024-10-24-staff-engineer-book-notes.md index fe2961ca..4bc901b9 100644 --- a/gemfeed/2024-10-24-staff-engineer-book-notes.md +++ b/gemfeed/2024-10-24-staff-engineer-book-notes.md @@ -121,13 +121,13 @@ E-Mail your comments to `paul@nospam.buetow.org` :-) Other book notes of mine are: -[2024-10-24 "Staff Engineer" book notes (You are currently reading this)](./2024-10-24-staff-engineer-book-notes.md) -[2024-07-07 "The Stoic Challenge" book notes](./2024-07-07-the-stoic-challenge-book-notes.md) -[2024-05-01 "Slow Productivity" book notes](./2024-05-01-slow-productivity-book-notes.md) -[2023-11-11 "Mind Management" book notes](./2023-11-11-mind-management-book-notes.md) -[2023-07-17 "Software Developmers Career Guide and Soft Skills" book notes](./2023-07-17-career-guide-and-soft-skills-book-notes.md) -[2023-05-06 "The Obstacle is the Way" book notes](./2023-05-06-the-obstacle-is-the-way-book-notes.md) -[2023-04-01 "Never split the difference" book notes](./2023-04-01-never-split-the-difference-book-notes.md) [2023-03-16 "The Pragmatic Programmer" book notes](./2023-03-16-the-pragmatic-programmer-book-notes.md) +[2023-04-01 "Never split the difference" book notes](./2023-04-01-never-split-the-difference-book-notes.md) +[2023-05-06 "The Obstacle is the Way" book notes](./2023-05-06-the-obstacle-is-the-way-book-notes.md) +[2023-07-17 "Software Developmers Career Guide and Soft Skills" book notes](./2023-07-17-career-guide-and-soft-skills-book-notes.md) +[2023-11-11 "Mind Management" book notes](./2023-11-11-mind-management-book-notes.md) +[2024-05-01 "Slow Productivity" book notes](./2024-05-01-slow-productivity-book-notes.md) +[2024-07-07 "The Stoic Challenge" book notes](./2024-07-07-the-stoic-challenge-book-notes.md) +[2024-10-24 "Staff Engineer" book notes (You are currently reading this)](./2024-10-24-staff-engineer-book-notes.md) [Back to the main site](../) diff --git a/gemfeed/2024-11-17-f3s-kubernetes-with-freebsd-part-1.md b/gemfeed/2024-11-17-f3s-kubernetes-with-freebsd-part-1.md index 6cd7c6a3..230a77d0 100644 --- a/gemfeed/2024-11-17-f3s-kubernetes-with-freebsd-part-1.md +++ b/gemfeed/2024-11-17-f3s-kubernetes-with-freebsd-part-1.md @@ -8,9 +8,9 @@ I will post a new entry every month or so (there are too many other side project These are all the posts so far: -[2025-02-01 f3s: Kubernetes with FreeBSD - Part 3: Protecting from power cuts](./2025-02-01-f3s-kubernetes-with-freebsd-part-3.md) -[2024-12-03 f3s: Kubernetes with FreeBSD - Part 2: Hardware and base installation](./2024-12-03-f3s-kubernetes-with-freebsd-part-2.md) [2024-11-17 f3s: Kubernetes with FreeBSD - Part 1: Setting the stage (You are currently reading this)](./2024-11-17-f3s-kubernetes-with-freebsd-part-1.md) +[2024-12-03 f3s: Kubernetes with FreeBSD - Part 2: Hardware and base installation](./2024-12-03-f3s-kubernetes-with-freebsd-part-2.md) +[2025-02-01 f3s: Kubernetes with FreeBSD - Part 3: Protecting from power cuts](./2025-02-01-f3s-kubernetes-with-freebsd-part-3.md) [![f3s logo](./f3s-kubernetes-with-freebsd-part-1/f3slogo.png "f3s logo")](./f3s-kubernetes-with-freebsd-part-1/f3slogo.png) @@ -159,14 +159,14 @@ Read the next post of this series: Other *BSD-related posts: -[2025-02-01 f3s: Kubernetes with FreeBSD - Part 3: Protecting from power cuts](./2025-02-01-f3s-kubernetes-with-freebsd-part-3.md) -[2024-12-03 f3s: Kubernetes with FreeBSD - Part 2: Hardware and base installation](./2024-12-03-f3s-kubernetes-with-freebsd-part-2.md) -[2024-11-17 f3s: Kubernetes with FreeBSD - Part 1: Setting the stage (You are currently reading this)](./2024-11-17-f3s-kubernetes-with-freebsd-part-1.md) -[2024-04-01 KISS high-availability with OpenBSD](./2024-04-01-KISS-high-availability-with-OpenBSD.md) -[2024-01-13 One reason why I love OpenBSD](./2024-01-13-one-reason-why-i-love-openbsd.md) -[2022-10-30 Installing DTail on OpenBSD](./2022-10-30-installing-dtail-on-openbsd.md) -[2022-07-30 Let's Encrypt with OpenBSD and Rex](./2022-07-30-lets-encrypt-with-openbsd-and-rex.md) [2016-04-09 Jails and ZFS with Puppet on FreeBSD](./2016-04-09-jails-and-zfs-on-freebsd-with-puppet.md) +[2022-07-30 Let's Encrypt with OpenBSD and Rex](./2022-07-30-lets-encrypt-with-openbsd-and-rex.md) +[2022-10-30 Installing DTail on OpenBSD](./2022-10-30-installing-dtail-on-openbsd.md) +[2024-01-13 One reason why I love OpenBSD](./2024-01-13-one-reason-why-i-love-openbsd.md) +[2024-04-01 KISS high-availability with OpenBSD](./2024-04-01-KISS-high-availability-with-OpenBSD.md) +[2024-11-17 f3s: Kubernetes with FreeBSD - Part 1: Setting the stage (You are currently reading this)](./2024-11-17-f3s-kubernetes-with-freebsd-part-1.md) +[2024-12-03 f3s: Kubernetes with FreeBSD - Part 2: Hardware and base installation](./2024-12-03-f3s-kubernetes-with-freebsd-part-2.md) +[2025-02-01 f3s: Kubernetes with FreeBSD - Part 3: Protecting from power cuts](./2025-02-01-f3s-kubernetes-with-freebsd-part-3.md) E-Mail your comments to `paul@nospam.buetow.org` :-) diff --git a/gemfeed/2024-12-03-f3s-kubernetes-with-freebsd-part-2.md b/gemfeed/2024-12-03-f3s-kubernetes-with-freebsd-part-2.md index 5417cbdc..161f4a1a 100644 --- a/gemfeed/2024-12-03-f3s-kubernetes-with-freebsd-part-2.md +++ b/gemfeed/2024-12-03-f3s-kubernetes-with-freebsd-part-2.md @@ -8,9 +8,9 @@ We set the stage last time; this time, we will set up the hardware for this proj These are all the posts so far: -[2025-02-01 f3s: Kubernetes with FreeBSD - Part 3: Protecting from power cuts](./2025-02-01-f3s-kubernetes-with-freebsd-part-3.md) -[2024-12-03 f3s: Kubernetes with FreeBSD - Part 2: Hardware and base installation (You are currently reading this)](./2024-12-03-f3s-kubernetes-with-freebsd-part-2.md) [2024-11-17 f3s: Kubernetes with FreeBSD - Part 1: Setting the stage](./2024-11-17-f3s-kubernetes-with-freebsd-part-1.md) +[2024-12-03 f3s: Kubernetes with FreeBSD - Part 2: Hardware and base installation (You are currently reading this)](./2024-12-03-f3s-kubernetes-with-freebsd-part-2.md) +[2025-02-01 f3s: Kubernetes with FreeBSD - Part 3: Protecting from power cuts](./2025-02-01-f3s-kubernetes-with-freebsd-part-3.md) [![f3s logo](./f3s-kubernetes-with-freebsd-part-1/f3slogo.png "f3s logo")](./f3s-kubernetes-with-freebsd-part-1/f3slogo.png) @@ -298,14 +298,14 @@ Read the next post of this series: Other *BSD-related posts: -[2025-02-01 f3s: Kubernetes with FreeBSD - Part 3: Protecting from power cuts](./2025-02-01-f3s-kubernetes-with-freebsd-part-3.md) -[2024-12-03 f3s: Kubernetes with FreeBSD - Part 2: Hardware and base installation (You are currently reading this)](./2024-12-03-f3s-kubernetes-with-freebsd-part-2.md) -[2024-11-17 f3s: Kubernetes with FreeBSD - Part 1: Setting the stage](./2024-11-17-f3s-kubernetes-with-freebsd-part-1.md) -[2024-04-01 KISS high-availability with OpenBSD](./2024-04-01-KISS-high-availability-with-OpenBSD.md) -[2024-01-13 One reason why I love OpenBSD](./2024-01-13-one-reason-why-i-love-openbsd.md) -[2022-10-30 Installing DTail on OpenBSD](./2022-10-30-installing-dtail-on-openbsd.md) -[2022-07-30 Let's Encrypt with OpenBSD and Rex](./2022-07-30-lets-encrypt-with-openbsd-and-rex.md) [2016-04-09 Jails and ZFS with Puppet on FreeBSD](./2016-04-09-jails-and-zfs-on-freebsd-with-puppet.md) +[2022-07-30 Let's Encrypt with OpenBSD and Rex](./2022-07-30-lets-encrypt-with-openbsd-and-rex.md) +[2022-10-30 Installing DTail on OpenBSD](./2022-10-30-installing-dtail-on-openbsd.md) +[2024-01-13 One reason why I love OpenBSD](./2024-01-13-one-reason-why-i-love-openbsd.md) +[2024-04-01 KISS high-availability with OpenBSD](./2024-04-01-KISS-high-availability-with-OpenBSD.md) +[2024-11-17 f3s: Kubernetes with FreeBSD - Part 1: Setting the stage](./2024-11-17-f3s-kubernetes-with-freebsd-part-1.md) +[2024-12-03 f3s: Kubernetes with FreeBSD - Part 2: Hardware and base installation (You are currently reading this)](./2024-12-03-f3s-kubernetes-with-freebsd-part-2.md) +[2025-02-01 f3s: Kubernetes with FreeBSD - Part 3: Protecting from power cuts](./2025-02-01-f3s-kubernetes-with-freebsd-part-3.md) E-Mail your comments to `paul@nospam.buetow.org` :-) diff --git a/gemfeed/2025-02-01-f3s-kubernetes-with-freebsd-part-3.md b/gemfeed/2025-02-01-f3s-kubernetes-with-freebsd-part-3.md index df9826f5..a464f44f 100644 --- a/gemfeed/2025-02-01-f3s-kubernetes-with-freebsd-part-3.md +++ b/gemfeed/2025-02-01-f3s-kubernetes-with-freebsd-part-3.md @@ -4,9 +4,9 @@ This is the third blog post about my f3s series for my self-hosting demands in my home lab. f3s? The "f" stands for FreeBSD, and the "3s" stands for k3s, the Kubernetes distribution we will use on FreeBSD-based physical machines. -[2025-02-01 f3s: Kubernetes with FreeBSD - Part 3: Protecting from power cuts (You are currently reading this)](./2025-02-01-f3s-kubernetes-with-freebsd-part-3.md) -[2024-12-03 f3s: Kubernetes with FreeBSD - Part 2: Hardware and base installation](./2024-12-03-f3s-kubernetes-with-freebsd-part-2.md) [2024-11-17 f3s: Kubernetes with FreeBSD - Part 1: Setting the stage](./2024-11-17-f3s-kubernetes-with-freebsd-part-1.md) +[2024-12-03 f3s: Kubernetes with FreeBSD - Part 2: Hardware and base installation](./2024-12-03-f3s-kubernetes-with-freebsd-part-2.md) +[2025-02-01 f3s: Kubernetes with FreeBSD - Part 3: Protecting from power cuts (You are currently reading this)](./2025-02-01-f3s-kubernetes-with-freebsd-part-3.md) [![f3s logo](./f3s-kubernetes-with-freebsd-part-1/f3slogo.png "f3s logo")](./f3s-kubernetes-with-freebsd-part-1/f3slogo.png) @@ -352,14 +352,14 @@ All good :-) See you in the next post of this series! Other BSD related posts are: -[2025-02-01 f3s: Kubernetes with FreeBSD - Part 3: Protecting from power cuts (You are currently reading this)](./2025-02-01-f3s-kubernetes-with-freebsd-part-3.md) -[2024-12-03 f3s: Kubernetes with FreeBSD - Part 2: Hardware and base installation](./2024-12-03-f3s-kubernetes-with-freebsd-part-2.md) -[2024-11-17 f3s: Kubernetes with FreeBSD - Part 1: Setting the stage](./2024-11-17-f3s-kubernetes-with-freebsd-part-1.md) -[2024-04-01 KISS high-availability with OpenBSD](./2024-04-01-KISS-high-availability-with-OpenBSD.md) -[2024-01-13 One reason why I love OpenBSD](./2024-01-13-one-reason-why-i-love-openbsd.md) -[2022-10-30 Installing DTail on OpenBSD](./2022-10-30-installing-dtail-on-openbsd.md) -[2022-07-30 Let's Encrypt with OpenBSD and Rex](./2022-07-30-lets-encrypt-with-openbsd-and-rex.md) [2016-04-09 Jails and ZFS with Puppet on FreeBSD](./2016-04-09-jails-and-zfs-on-freebsd-with-puppet.md) +[2022-07-30 Let's Encrypt with OpenBSD and Rex](./2022-07-30-lets-encrypt-with-openbsd-and-rex.md) +[2022-10-30 Installing DTail on OpenBSD](./2022-10-30-installing-dtail-on-openbsd.md) +[2024-01-13 One reason why I love OpenBSD](./2024-01-13-one-reason-why-i-love-openbsd.md) +[2024-04-01 KISS high-availability with OpenBSD](./2024-04-01-KISS-high-availability-with-OpenBSD.md) +[2024-11-17 f3s: Kubernetes with FreeBSD - Part 1: Setting the stage](./2024-11-17-f3s-kubernetes-with-freebsd-part-1.md) +[2024-12-03 f3s: Kubernetes with FreeBSD - Part 2: Hardware and base installation](./2024-12-03-f3s-kubernetes-with-freebsd-part-2.md) +[2025-02-01 f3s: Kubernetes with FreeBSD - Part 3: Protecting from power cuts (You are currently reading this)](./2025-02-01-f3s-kubernetes-with-freebsd-part-3.md) E-Mail your comments to `paul@nospam.buetow.org` :-) diff --git a/gemfeed/DRAFT-f3s-kubernetes-with-freebsd-part-4.md b/gemfeed/DRAFT-f3s-kubernetes-with-freebsd-part-4.md index fdec9071..4fc1bc63 100644 --- a/gemfeed/DRAFT-f3s-kubernetes-with-freebsd-part-4.md +++ b/gemfeed/DRAFT-f3s-kubernetes-with-freebsd-part-4.md @@ -2,9 +2,9 @@ This is the thourth blog post about my f3s series for my self-hosting demands in my home lab. f3s? The "f" stands for FreeBSD, and the "3s" stands for k3s, the Kubernetes distribution we will use on FreeBSD-based physical machines. -[2025-02-01 f3s: Kubernetes with FreeBSD - Part 3: Protecting from power cuts](./2025-02-01-f3s-kubernetes-with-freebsd-part-3.md) -[2024-12-03 f3s: Kubernetes with FreeBSD - Part 2: Hardware and base installation](./2024-12-03-f3s-kubernetes-with-freebsd-part-2.md) [2024-11-17 f3s: Kubernetes with FreeBSD - Part 1: Setting the stage](./2024-11-17-f3s-kubernetes-with-freebsd-part-1.md) +[2024-12-03 f3s: Kubernetes with FreeBSD - Part 2: Hardware and base installation](./2024-12-03-f3s-kubernetes-with-freebsd-part-2.md) +[2025-02-01 f3s: Kubernetes with FreeBSD - Part 3: Protecting from power cuts](./2025-02-01-f3s-kubernetes-with-freebsd-part-3.md) [![f3s logo](./f3s-kubernetes-with-frhyveeebsd-part-1/f3slogo.png "f3s logo")](./f3s-kubernetes-with-frhyveeebsd-part-1/f3slogo.png) @@ -265,14 +265,14 @@ CPU STRESS TESTER VM VS NOT VM Other *BSD-related posts: -[2025-02-01 f3s: Kubernetes with FreeBSD - Part 3: Protecting from power cuts](./2025-02-01-f3s-kubernetes-with-freebsd-part-3.md) -[2024-12-03 f3s: Kubernetes with FreeBSD - Part 2: Hardware and base installation](./2024-12-03-f3s-kubernetes-with-freebsd-part-2.md) -[2024-11-17 f3s: Kubernetes with FreeBSD - Part 1: Setting the stage](./2024-11-17-f3s-kubernetes-with-freebsd-part-1.md) -[2024-04-01 KISS high-availability with OpenBSD](./2024-04-01-KISS-high-availability-with-OpenBSD.md) -[2024-01-13 One reason why I love OpenBSD](./2024-01-13-one-reason-why-i-love-openbsd.md) -[2022-10-30 Installing DTail on OpenBSD](./2022-10-30-installing-dtail-on-openbsd.md) -[2022-07-30 Let's Encrypt with OpenBSD and Rex](./2022-07-30-lets-encrypt-with-openbsd-and-rex.md) [2016-04-09 Jails and ZFS with Puppet on FreeBSD](./2016-04-09-jails-and-zfs-on-freebsd-with-puppet.md) +[2022-07-30 Let's Encrypt with OpenBSD and Rex](./2022-07-30-lets-encrypt-with-openbsd-and-rex.md) +[2022-10-30 Installing DTail on OpenBSD](./2022-10-30-installing-dtail-on-openbsd.md) +[2024-01-13 One reason why I love OpenBSD](./2024-01-13-one-reason-why-i-love-openbsd.md) +[2024-04-01 KISS high-availability with OpenBSD](./2024-04-01-KISS-high-availability-with-OpenBSD.md) +[2024-11-17 f3s: Kubernetes with FreeBSD - Part 1: Setting the stage](./2024-11-17-f3s-kubernetes-with-freebsd-part-1.md) +[2024-12-03 f3s: Kubernetes with FreeBSD - Part 2: Hardware and base installation](./2024-12-03-f3s-kubernetes-with-freebsd-part-2.md) +[2025-02-01 f3s: Kubernetes with FreeBSD - Part 3: Protecting from power cuts](./2025-02-01-f3s-kubernetes-with-freebsd-part-3.md) E-Mail your comments to `paul@nospam.buetow.org` :-) -- cgit v1.2.3 From 8f20084f8aa24b19d94e1d81b8bc585a86ac568b Mon Sep 17 00:00:00 2001 From: Paul Buetow Date: Sun, 2 Feb 2025 10:59:21 +0200 Subject: Update content for md --- .../2023-03-25-gemtexter-2.0.0-lets-gemtext-again-2.md | 2 +- ...1-unveiling-guprecords:-uptime-records-with-raku.md | 8 ++++---- gemfeed/2023-09-25-dtail-usage-examples.md | 6 +++--- ...-kiss-static-web-photo-albums-with-photoalbum.sh.md | 16 ++++++++-------- gemfeed/2023-11-11-mind-management-book-notes.md | 14 +++++++------- gemfeed/2023-12-10-bash-golf-part-3.md | 8 ++++---- gemfeed/2024-01-13-one-reason-why-i-love-openbsd.md | 14 +++++++------- .../2024-04-01-KISS-high-availability-with-OpenBSD.md | 18 +++++++++--------- gemfeed/2024-05-01-slow-productivity-book-notes.md | 14 +++++++------- gemfeed/2024-07-07-the-stoic-challenge-book-notes.md | 14 +++++++------- .../2024-10-02-gemtexter-3.0.0-lets-gemtext-again-4.md | 10 +++++----- gemfeed/2024-10-24-staff-engineer-book-notes.md | 14 +++++++------- .../2024-11-17-f3s-kubernetes-with-freebsd-part-1.md | 18 +++++++++--------- .../2024-12-03-f3s-kubernetes-with-freebsd-part-2.md | 18 +++++++++--------- .../2025-02-01-f3s-kubernetes-with-freebsd-part-3.md | 14 +++++++------- gemfeed/DRAFT-f3s-kubernetes-with-freebsd-part-4.md | 14 +++++++------- 16 files changed, 101 insertions(+), 101 deletions(-) (limited to 'gemfeed') diff --git a/gemfeed/2023-03-25-gemtexter-2.0.0-lets-gemtext-again-2.md b/gemfeed/2023-03-25-gemtexter-2.0.0-lets-gemtext-again-2.md index ceeace01..1fb0f838 100644 --- a/gemfeed/2023-03-25-gemtexter-2.0.0-lets-gemtext-again-2.md +++ b/gemfeed/2023-03-25-gemtexter-2.0.0-lets-gemtext-again-2.md @@ -81,7 +81,7 @@ Another thing you can do is insert an index with links to similar blog posts. E. ``` See more entries about DTail and Golang: -<< template::inline::index dtail golang +<< template::inline::rindex dtail golang Blablabla... ``` diff --git a/gemfeed/2023-05-01-unveiling-guprecords:-uptime-records-with-raku.md b/gemfeed/2023-05-01-unveiling-guprecords:-uptime-records-with-raku.md index c1136931..4fb6d039 100644 --- a/gemfeed/2023-05-01-unveiling-guprecords:-uptime-records-with-raku.md +++ b/gemfeed/2023-05-01-unveiling-guprecords:-uptime-records-with-raku.md @@ -159,10 +159,10 @@ E-Mail your comments to hi@foo.zone :-) Other related posts are: -[2008-06-26 Perl Poetry](./2008-06-26-perl-poetry.md) -[2011-05-07 Perl Daemon (Service Framework)](./2011-05-07-perl-daemon-service-framework.md) -[2022-05-27 Perl is still a great choice](./2022-05-27-perl-is-still-a-great-choice.md) -[2022-06-15 Sweating the small stuff - Tiny projects of mine](./2022-06-15-sweating-the-small-stuff.md) [2023-05-01 Unveiling `guprecords.raku`: Global Uptime Records with Raku (You are currently reading this)](./2023-05-01-unveiling-guprecords:-uptime-records-with-raku.md) +[2022-06-15 Sweating the small stuff - Tiny projects of mine](./2022-06-15-sweating-the-small-stuff.md) +[2022-05-27 Perl is still a great choice](./2022-05-27-perl-is-still-a-great-choice.md) +[2011-05-07 Perl Daemon (Service Framework)](./2011-05-07-perl-daemon-service-framework.md) +[2008-06-26 Perl Poetry](./2008-06-26-perl-poetry.md) [Back to the main site](../) diff --git a/gemfeed/2023-09-25-dtail-usage-examples.md b/gemfeed/2023-09-25-dtail-usage-examples.md index 595afb36..8df87a93 100644 --- a/gemfeed/2023-09-25-dtail-usage-examples.md +++ b/gemfeed/2023-09-25-dtail-usage-examples.md @@ -248,10 +248,10 @@ E-Mail your comments to `paul@nospam.buetow.org` :-) Other related posts are: -[2021-04-22 DTail - The distributed log tail program](./2021-04-22-dtail-the-distributed-log-tail-program.md) -[2022-03-06 The release of DTail 4.0.0](./2022-03-06-the-release-of-dtail-4.0.0.md) -[2022-10-30 Installing DTail on OpenBSD](./2022-10-30-installing-dtail-on-openbsd.md) [2023-09-25 DTail usage examples (You are currently reading this)](./2023-09-25-dtail-usage-examples.md) +[2022-10-30 Installing DTail on OpenBSD](./2022-10-30-installing-dtail-on-openbsd.md) +[2022-03-06 The release of DTail 4.0.0](./2022-03-06-the-release-of-dtail-4.0.0.md) +[2021-04-22 DTail - The distributed log tail program](./2021-04-22-dtail-the-distributed-log-tail-program.md) I hope you find the tools presented in this post useful! diff --git a/gemfeed/2023-10-29-kiss-static-web-photo-albums-with-photoalbum.sh.md b/gemfeed/2023-10-29-kiss-static-web-photo-albums-with-photoalbum.sh.md index dd8c0167..2121886c 100644 --- a/gemfeed/2023-10-29-kiss-static-web-photo-albums-with-photoalbum.sh.md +++ b/gemfeed/2023-10-29-kiss-static-web-photo-albums-with-photoalbum.sh.md @@ -272,14 +272,14 @@ E-Mail your comments to `paul@nospam.buetow.org` :-) Other Bash and KISS-related posts are: -[2021-05-16 Personal Bash coding style guide](./2021-05-16-personal-bash-coding-style-guide.md) -[2021-06-05 Gemtexter - One Bash script to rule it all](./2021-06-05-gemtexter-one-bash-script-to-rule-it-all.md) -[2021-09-12 Keep it simple and stupid](./2021-09-12-keep-it-simple-and-stupid.md) -[2021-11-29 Bash Golf Part 1](./2021-11-29-bash-golf-part-1.md) -[2022-01-01 Bash Golf Part 2](./2022-01-01-bash-golf-part-2.md) -[2023-06-01 KISS server monitoring with Gogios](./2023-06-01-kiss-server-monitoring-with-gogios.md) -[2023-10-29 KISS static web photo albums with `photoalbum.sh` (You are currently reading this)](./2023-10-29-kiss-static-web-photo-albums-with-photoalbum.sh.md) -[2023-12-10 Bash Golf Part 3](./2023-12-10-bash-golf-part-3.md) [2024-04-01 KISS high-availability with OpenBSD](./2024-04-01-KISS-high-availability-with-OpenBSD.md) +[2023-12-10 Bash Golf Part 3](./2023-12-10-bash-golf-part-3.md) +[2023-10-29 KISS static web photo albums with `photoalbum.sh` (You are currently reading this)](./2023-10-29-kiss-static-web-photo-albums-with-photoalbum.sh.md) +[2023-06-01 KISS server monitoring with Gogios](./2023-06-01-kiss-server-monitoring-with-gogios.md) +[2022-01-01 Bash Golf Part 2](./2022-01-01-bash-golf-part-2.md) +[2021-11-29 Bash Golf Part 1](./2021-11-29-bash-golf-part-1.md) +[2021-09-12 Keep it simple and stupid](./2021-09-12-keep-it-simple-and-stupid.md) +[2021-06-05 Gemtexter - One Bash script to rule it all](./2021-06-05-gemtexter-one-bash-script-to-rule-it-all.md) +[2021-05-16 Personal Bash coding style guide](./2021-05-16-personal-bash-coding-style-guide.md) [Back to the main site](../) diff --git a/gemfeed/2023-11-11-mind-management-book-notes.md b/gemfeed/2023-11-11-mind-management-book-notes.md index 96a2c6e5..2cefef51 100644 --- a/gemfeed/2023-11-11-mind-management-book-notes.md +++ b/gemfeed/2023-11-11-mind-management-book-notes.md @@ -110,13 +110,13 @@ E-Mail your comments to `paul@nospam.buetow.org` :-) Other book notes of mine are: -[2023-03-16 "The Pragmatic Programmer" book notes](./2023-03-16-the-pragmatic-programmer-book-notes.md) -[2023-04-01 "Never split the difference" book notes](./2023-04-01-never-split-the-difference-book-notes.md) -[2023-05-06 "The Obstacle is the Way" book notes](./2023-05-06-the-obstacle-is-the-way-book-notes.md) -[2023-07-17 "Software Developmers Career Guide and Soft Skills" book notes](./2023-07-17-career-guide-and-soft-skills-book-notes.md) -[2023-11-11 "Mind Management" book notes (You are currently reading this)](./2023-11-11-mind-management-book-notes.md) -[2024-05-01 "Slow Productivity" book notes](./2024-05-01-slow-productivity-book-notes.md) -[2024-07-07 "The Stoic Challenge" book notes](./2024-07-07-the-stoic-challenge-book-notes.md) [2024-10-24 "Staff Engineer" book notes](./2024-10-24-staff-engineer-book-notes.md) +[2024-07-07 "The Stoic Challenge" book notes](./2024-07-07-the-stoic-challenge-book-notes.md) +[2024-05-01 "Slow Productivity" book notes](./2024-05-01-slow-productivity-book-notes.md) +[2023-11-11 "Mind Management" book notes (You are currently reading this)](./2023-11-11-mind-management-book-notes.md) +[2023-07-17 "Software Developmers Career Guide and Soft Skills" book notes](./2023-07-17-career-guide-and-soft-skills-book-notes.md) +[2023-05-06 "The Obstacle is the Way" book notes](./2023-05-06-the-obstacle-is-the-way-book-notes.md) +[2023-04-01 "Never split the difference" book notes](./2023-04-01-never-split-the-difference-book-notes.md) +[2023-03-16 "The Pragmatic Programmer" book notes](./2023-03-16-the-pragmatic-programmer-book-notes.md) [Back to the main site](../) diff --git a/gemfeed/2023-12-10-bash-golf-part-3.md b/gemfeed/2023-12-10-bash-golf-part-3.md index f315e387..8c6e5e01 100644 --- a/gemfeed/2023-12-10-bash-golf-part-3.md +++ b/gemfeed/2023-12-10-bash-golf-part-3.md @@ -371,10 +371,10 @@ E-Mail your comments to `paul@nospam.buetow.org` :-) Other related posts are: -[2021-05-16 Personal Bash coding style guide](./2021-05-16-personal-bash-coding-style-guide.md) -[2021-06-05 Gemtexter - One Bash script to rule it all](./2021-06-05-gemtexter-one-bash-script-to-rule-it-all.md) -[2021-11-29 Bash Golf Part 1](./2021-11-29-bash-golf-part-1.md) -[2022-01-01 Bash Golf Part 2](./2022-01-01-bash-golf-part-2.md) [2023-12-10 Bash Golf Part 3 (You are currently reading this)](./2023-12-10-bash-golf-part-3.md) +[2022-01-01 Bash Golf Part 2](./2022-01-01-bash-golf-part-2.md) +[2021-11-29 Bash Golf Part 1](./2021-11-29-bash-golf-part-1.md) +[2021-06-05 Gemtexter - One Bash script to rule it all](./2021-06-05-gemtexter-one-bash-script-to-rule-it-all.md) +[2021-05-16 Personal Bash coding style guide](./2021-05-16-personal-bash-coding-style-guide.md) [Back to the main site](../) diff --git a/gemfeed/2024-01-13-one-reason-why-i-love-openbsd.md b/gemfeed/2024-01-13-one-reason-why-i-love-openbsd.md index 92598532..531c4581 100644 --- a/gemfeed/2024-01-13-one-reason-why-i-love-openbsd.md +++ b/gemfeed/2024-01-13-one-reason-why-i-love-openbsd.md @@ -51,13 +51,13 @@ E-Mail your comments to `paul@nospam.buetow.org` :-) Other *BSD related posts are: -[2016-04-09 Jails and ZFS with Puppet on FreeBSD](./2016-04-09-jails-and-zfs-on-freebsd-with-puppet.md) -[2022-07-30 Let's Encrypt with OpenBSD and Rex](./2022-07-30-lets-encrypt-with-openbsd-and-rex.md) -[2022-10-30 Installing DTail on OpenBSD](./2022-10-30-installing-dtail-on-openbsd.md) -[2024-01-13 One reason why I love OpenBSD (You are currently reading this)](./2024-01-13-one-reason-why-i-love-openbsd.md) -[2024-04-01 KISS high-availability with OpenBSD](./2024-04-01-KISS-high-availability-with-OpenBSD.md) -[2024-11-17 f3s: Kubernetes with FreeBSD - Part 1: Setting the stage](./2024-11-17-f3s-kubernetes-with-freebsd-part-1.md) -[2024-12-03 f3s: Kubernetes with FreeBSD - Part 2: Hardware and base installation](./2024-12-03-f3s-kubernetes-with-freebsd-part-2.md) [2025-02-01 f3s: Kubernetes with FreeBSD - Part 3: Protecting from power cuts](./2025-02-01-f3s-kubernetes-with-freebsd-part-3.md) +[2024-12-03 f3s: Kubernetes with FreeBSD - Part 2: Hardware and base installation](./2024-12-03-f3s-kubernetes-with-freebsd-part-2.md) +[2024-11-17 f3s: Kubernetes with FreeBSD - Part 1: Setting the stage](./2024-11-17-f3s-kubernetes-with-freebsd-part-1.md) +[2024-04-01 KISS high-availability with OpenBSD](./2024-04-01-KISS-high-availability-with-OpenBSD.md) +[2024-01-13 One reason why I love OpenBSD (You are currently reading this)](./2024-01-13-one-reason-why-i-love-openbsd.md) +[2022-10-30 Installing DTail on OpenBSD](./2022-10-30-installing-dtail-on-openbsd.md) +[2022-07-30 Let's Encrypt with OpenBSD and Rex](./2022-07-30-lets-encrypt-with-openbsd-and-rex.md) +[2016-04-09 Jails and ZFS with Puppet on FreeBSD](./2016-04-09-jails-and-zfs-on-freebsd-with-puppet.md) [Back to the main site](../) diff --git a/gemfeed/2024-04-01-KISS-high-availability-with-OpenBSD.md b/gemfeed/2024-04-01-KISS-high-availability-with-OpenBSD.md index 66e17f82..4a53071f 100644 --- a/gemfeed/2024-04-01-KISS-high-availability-with-OpenBSD.md +++ b/gemfeed/2024-04-01-KISS-high-availability-with-OpenBSD.md @@ -300,15 +300,15 @@ E-Mail your comments to `paul@nospam.buetow.org` :-) Other *BSD and KISS related posts are: -[2016-04-09 Jails and ZFS with Puppet on FreeBSD](./2016-04-09-jails-and-zfs-on-freebsd-with-puppet.md) -[2022-07-30 Let's Encrypt with OpenBSD and Rex](./2022-07-30-lets-encrypt-with-openbsd-and-rex.md) -[2022-10-30 Installing DTail on OpenBSD](./2022-10-30-installing-dtail-on-openbsd.md) -[2023-06-01 KISS server monitoring with Gogios](./2023-06-01-kiss-server-monitoring-with-gogios.md) -[2023-10-29 KISS static web photo albums with `photoalbum.sh`](./2023-10-29-kiss-static-web-photo-albums-with-photoalbum.sh.md) -[2024-01-13 One reason why I love OpenBSD](./2024-01-13-one-reason-why-i-love-openbsd.md) -[2024-04-01 KISS high-availability with OpenBSD (You are currently reading this)](./2024-04-01-KISS-high-availability-with-OpenBSD.md) -[2024-11-17 f3s: Kubernetes with FreeBSD - Part 1: Setting the stage](./2024-11-17-f3s-kubernetes-with-freebsd-part-1.md) -[2024-12-03 f3s: Kubernetes with FreeBSD - Part 2: Hardware and base installation](./2024-12-03-f3s-kubernetes-with-freebsd-part-2.md) [2025-02-01 f3s: Kubernetes with FreeBSD - Part 3: Protecting from power cuts](./2025-02-01-f3s-kubernetes-with-freebsd-part-3.md) +[2024-12-03 f3s: Kubernetes with FreeBSD - Part 2: Hardware and base installation](./2024-12-03-f3s-kubernetes-with-freebsd-part-2.md) +[2024-11-17 f3s: Kubernetes with FreeBSD - Part 1: Setting the stage](./2024-11-17-f3s-kubernetes-with-freebsd-part-1.md) +[2024-04-01 KISS high-availability with OpenBSD (You are currently reading this)](./2024-04-01-KISS-high-availability-with-OpenBSD.md) +[2024-01-13 One reason why I love OpenBSD](./2024-01-13-one-reason-why-i-love-openbsd.md) +[2023-10-29 KISS static web photo albums with `photoalbum.sh`](./2023-10-29-kiss-static-web-photo-albums-with-photoalbum.sh.md) +[2023-06-01 KISS server monitoring with Gogios](./2023-06-01-kiss-server-monitoring-with-gogios.md) +[2022-10-30 Installing DTail on OpenBSD](./2022-10-30-installing-dtail-on-openbsd.md) +[2022-07-30 Let's Encrypt with OpenBSD and Rex](./2022-07-30-lets-encrypt-with-openbsd-and-rex.md) +[2016-04-09 Jails and ZFS with Puppet on FreeBSD](./2016-04-09-jails-and-zfs-on-freebsd-with-puppet.md) [Back to the main site](../) diff --git a/gemfeed/2024-05-01-slow-productivity-book-notes.md b/gemfeed/2024-05-01-slow-productivity-book-notes.md index 6fde73fa..00349dd1 100644 --- a/gemfeed/2024-05-01-slow-productivity-book-notes.md +++ b/gemfeed/2024-05-01-slow-productivity-book-notes.md @@ -138,13 +138,13 @@ E-Mail your comments to `paul@nospam.buetow.org` :-) Other book notes of mine are: -[2023-03-16 "The Pragmatic Programmer" book notes](./2023-03-16-the-pragmatic-programmer-book-notes.md) -[2023-04-01 "Never split the difference" book notes](./2023-04-01-never-split-the-difference-book-notes.md) -[2023-05-06 "The Obstacle is the Way" book notes](./2023-05-06-the-obstacle-is-the-way-book-notes.md) -[2023-07-17 "Software Developmers Career Guide and Soft Skills" book notes](./2023-07-17-career-guide-and-soft-skills-book-notes.md) -[2023-11-11 "Mind Management" book notes](./2023-11-11-mind-management-book-notes.md) -[2024-05-01 "Slow Productivity" book notes (You are currently reading this)](./2024-05-01-slow-productivity-book-notes.md) -[2024-07-07 "The Stoic Challenge" book notes](./2024-07-07-the-stoic-challenge-book-notes.md) [2024-10-24 "Staff Engineer" book notes](./2024-10-24-staff-engineer-book-notes.md) +[2024-07-07 "The Stoic Challenge" book notes](./2024-07-07-the-stoic-challenge-book-notes.md) +[2024-05-01 "Slow Productivity" book notes (You are currently reading this)](./2024-05-01-slow-productivity-book-notes.md) +[2023-11-11 "Mind Management" book notes](./2023-11-11-mind-management-book-notes.md) +[2023-07-17 "Software Developmers Career Guide and Soft Skills" book notes](./2023-07-17-career-guide-and-soft-skills-book-notes.md) +[2023-05-06 "The Obstacle is the Way" book notes](./2023-05-06-the-obstacle-is-the-way-book-notes.md) +[2023-04-01 "Never split the difference" book notes](./2023-04-01-never-split-the-difference-book-notes.md) +[2023-03-16 "The Pragmatic Programmer" book notes](./2023-03-16-the-pragmatic-programmer-book-notes.md) [Back to the main site](../) diff --git a/gemfeed/2024-07-07-the-stoic-challenge-book-notes.md b/gemfeed/2024-07-07-the-stoic-challenge-book-notes.md index 395ad2e8..0e3b0ed4 100644 --- a/gemfeed/2024-07-07-the-stoic-challenge-book-notes.md +++ b/gemfeed/2024-07-07-the-stoic-challenge-book-notes.md @@ -57,13 +57,13 @@ E-Mail your comments to `paul@nospam.buetow.org` :-) Other book notes of mine are: -[2023-03-16 "The Pragmatic Programmer" book notes](./2023-03-16-the-pragmatic-programmer-book-notes.md) -[2023-04-01 "Never split the difference" book notes](./2023-04-01-never-split-the-difference-book-notes.md) -[2023-05-06 "The Obstacle is the Way" book notes](./2023-05-06-the-obstacle-is-the-way-book-notes.md) -[2023-07-17 "Software Developmers Career Guide and Soft Skills" book notes](./2023-07-17-career-guide-and-soft-skills-book-notes.md) -[2023-11-11 "Mind Management" book notes](./2023-11-11-mind-management-book-notes.md) -[2024-05-01 "Slow Productivity" book notes](./2024-05-01-slow-productivity-book-notes.md) -[2024-07-07 "The Stoic Challenge" book notes (You are currently reading this)](./2024-07-07-the-stoic-challenge-book-notes.md) [2024-10-24 "Staff Engineer" book notes](./2024-10-24-staff-engineer-book-notes.md) +[2024-07-07 "The Stoic Challenge" book notes (You are currently reading this)](./2024-07-07-the-stoic-challenge-book-notes.md) +[2024-05-01 "Slow Productivity" book notes](./2024-05-01-slow-productivity-book-notes.md) +[2023-11-11 "Mind Management" book notes](./2023-11-11-mind-management-book-notes.md) +[2023-07-17 "Software Developmers Career Guide and Soft Skills" book notes](./2023-07-17-career-guide-and-soft-skills-book-notes.md) +[2023-05-06 "The Obstacle is the Way" book notes](./2023-05-06-the-obstacle-is-the-way-book-notes.md) +[2023-04-01 "Never split the difference" book notes](./2023-04-01-never-split-the-difference-book-notes.md) +[2023-03-16 "The Pragmatic Programmer" book notes](./2023-03-16-the-pragmatic-programmer-book-notes.md) [Back to the main site](../) diff --git a/gemfeed/2024-10-02-gemtexter-3.0.0-lets-gemtext-again-4.md b/gemfeed/2024-10-02-gemtexter-3.0.0-lets-gemtext-again-4.md index a4a8554e..322fb989 100644 --- a/gemfeed/2024-10-02-gemtexter-3.0.0-lets-gemtext-again-4.md +++ b/gemfeed/2024-10-02-gemtexter-3.0.0-lets-gemtext-again-4.md @@ -76,11 +76,11 @@ E-Mail your comments to `paul@nospam.buetow.org` :-) Other related posts are: -[2021-04-24 Welcome to the Geminispace](./2021-04-24-welcome-to-the-geminispace.md) -[2021-06-05 Gemtexter - One Bash script to rule it all](./2021-06-05-gemtexter-one-bash-script-to-rule-it-all.md) -[2022-08-27 Gemtexter 1.1.0 - Let's Gemtext again](./2022-08-27-gemtexter-1.1.0-lets-gemtext-again.md) -[2023-03-25 Gemtexter 2.0.0 - Let's Gemtext again²](./2023-03-25-gemtexter-2.0.0-lets-gemtext-again-2.md) -[2023-07-21 Gemtexter 2.1.0 - Let's Gemtext again³](./2023-07-21-gemtexter-2.1.0-lets-gemtext-again-3.md) [2024-10-02 Gemtexter 3.0.0 - Let's Gemtext again⁴ (You are currently reading this)](./2024-10-02-gemtexter-3.0.0-lets-gemtext-again-4.md) +[2023-07-21 Gemtexter 2.1.0 - Let's Gemtext again³](./2023-07-21-gemtexter-2.1.0-lets-gemtext-again-3.md) +[2023-03-25 Gemtexter 2.0.0 - Let's Gemtext again²](./2023-03-25-gemtexter-2.0.0-lets-gemtext-again-2.md) +[2022-08-27 Gemtexter 1.1.0 - Let's Gemtext again](./2022-08-27-gemtexter-1.1.0-lets-gemtext-again.md) +[2021-06-05 Gemtexter - One Bash script to rule it all](./2021-06-05-gemtexter-one-bash-script-to-rule-it-all.md) +[2021-04-24 Welcome to the Geminispace](./2021-04-24-welcome-to-the-geminispace.md) [Back to the main site](../) diff --git a/gemfeed/2024-10-24-staff-engineer-book-notes.md b/gemfeed/2024-10-24-staff-engineer-book-notes.md index 4bc901b9..fe2961ca 100644 --- a/gemfeed/2024-10-24-staff-engineer-book-notes.md +++ b/gemfeed/2024-10-24-staff-engineer-book-notes.md @@ -121,13 +121,13 @@ E-Mail your comments to `paul@nospam.buetow.org` :-) Other book notes of mine are: -[2023-03-16 "The Pragmatic Programmer" book notes](./2023-03-16-the-pragmatic-programmer-book-notes.md) -[2023-04-01 "Never split the difference" book notes](./2023-04-01-never-split-the-difference-book-notes.md) -[2023-05-06 "The Obstacle is the Way" book notes](./2023-05-06-the-obstacle-is-the-way-book-notes.md) -[2023-07-17 "Software Developmers Career Guide and Soft Skills" book notes](./2023-07-17-career-guide-and-soft-skills-book-notes.md) -[2023-11-11 "Mind Management" book notes](./2023-11-11-mind-management-book-notes.md) -[2024-05-01 "Slow Productivity" book notes](./2024-05-01-slow-productivity-book-notes.md) -[2024-07-07 "The Stoic Challenge" book notes](./2024-07-07-the-stoic-challenge-book-notes.md) [2024-10-24 "Staff Engineer" book notes (You are currently reading this)](./2024-10-24-staff-engineer-book-notes.md) +[2024-07-07 "The Stoic Challenge" book notes](./2024-07-07-the-stoic-challenge-book-notes.md) +[2024-05-01 "Slow Productivity" book notes](./2024-05-01-slow-productivity-book-notes.md) +[2023-11-11 "Mind Management" book notes](./2023-11-11-mind-management-book-notes.md) +[2023-07-17 "Software Developmers Career Guide and Soft Skills" book notes](./2023-07-17-career-guide-and-soft-skills-book-notes.md) +[2023-05-06 "The Obstacle is the Way" book notes](./2023-05-06-the-obstacle-is-the-way-book-notes.md) +[2023-04-01 "Never split the difference" book notes](./2023-04-01-never-split-the-difference-book-notes.md) +[2023-03-16 "The Pragmatic Programmer" book notes](./2023-03-16-the-pragmatic-programmer-book-notes.md) [Back to the main site](../) diff --git a/gemfeed/2024-11-17-f3s-kubernetes-with-freebsd-part-1.md b/gemfeed/2024-11-17-f3s-kubernetes-with-freebsd-part-1.md index 230a77d0..6cd7c6a3 100644 --- a/gemfeed/2024-11-17-f3s-kubernetes-with-freebsd-part-1.md +++ b/gemfeed/2024-11-17-f3s-kubernetes-with-freebsd-part-1.md @@ -8,9 +8,9 @@ I will post a new entry every month or so (there are too many other side project These are all the posts so far: -[2024-11-17 f3s: Kubernetes with FreeBSD - Part 1: Setting the stage (You are currently reading this)](./2024-11-17-f3s-kubernetes-with-freebsd-part-1.md) -[2024-12-03 f3s: Kubernetes with FreeBSD - Part 2: Hardware and base installation](./2024-12-03-f3s-kubernetes-with-freebsd-part-2.md) [2025-02-01 f3s: Kubernetes with FreeBSD - Part 3: Protecting from power cuts](./2025-02-01-f3s-kubernetes-with-freebsd-part-3.md) +[2024-12-03 f3s: Kubernetes with FreeBSD - Part 2: Hardware and base installation](./2024-12-03-f3s-kubernetes-with-freebsd-part-2.md) +[2024-11-17 f3s: Kubernetes with FreeBSD - Part 1: Setting the stage (You are currently reading this)](./2024-11-17-f3s-kubernetes-with-freebsd-part-1.md) [![f3s logo](./f3s-kubernetes-with-freebsd-part-1/f3slogo.png "f3s logo")](./f3s-kubernetes-with-freebsd-part-1/f3slogo.png) @@ -159,14 +159,14 @@ Read the next post of this series: Other *BSD-related posts: -[2016-04-09 Jails and ZFS with Puppet on FreeBSD](./2016-04-09-jails-and-zfs-on-freebsd-with-puppet.md) -[2022-07-30 Let's Encrypt with OpenBSD and Rex](./2022-07-30-lets-encrypt-with-openbsd-and-rex.md) -[2022-10-30 Installing DTail on OpenBSD](./2022-10-30-installing-dtail-on-openbsd.md) -[2024-01-13 One reason why I love OpenBSD](./2024-01-13-one-reason-why-i-love-openbsd.md) -[2024-04-01 KISS high-availability with OpenBSD](./2024-04-01-KISS-high-availability-with-OpenBSD.md) -[2024-11-17 f3s: Kubernetes with FreeBSD - Part 1: Setting the stage (You are currently reading this)](./2024-11-17-f3s-kubernetes-with-freebsd-part-1.md) -[2024-12-03 f3s: Kubernetes with FreeBSD - Part 2: Hardware and base installation](./2024-12-03-f3s-kubernetes-with-freebsd-part-2.md) [2025-02-01 f3s: Kubernetes with FreeBSD - Part 3: Protecting from power cuts](./2025-02-01-f3s-kubernetes-with-freebsd-part-3.md) +[2024-12-03 f3s: Kubernetes with FreeBSD - Part 2: Hardware and base installation](./2024-12-03-f3s-kubernetes-with-freebsd-part-2.md) +[2024-11-17 f3s: Kubernetes with FreeBSD - Part 1: Setting the stage (You are currently reading this)](./2024-11-17-f3s-kubernetes-with-freebsd-part-1.md) +[2024-04-01 KISS high-availability with OpenBSD](./2024-04-01-KISS-high-availability-with-OpenBSD.md) +[2024-01-13 One reason why I love OpenBSD](./2024-01-13-one-reason-why-i-love-openbsd.md) +[2022-10-30 Installing DTail on OpenBSD](./2022-10-30-installing-dtail-on-openbsd.md) +[2022-07-30 Let's Encrypt with OpenBSD and Rex](./2022-07-30-lets-encrypt-with-openbsd-and-rex.md) +[2016-04-09 Jails and ZFS with Puppet on FreeBSD](./2016-04-09-jails-and-zfs-on-freebsd-with-puppet.md) E-Mail your comments to `paul@nospam.buetow.org` :-) diff --git a/gemfeed/2024-12-03-f3s-kubernetes-with-freebsd-part-2.md b/gemfeed/2024-12-03-f3s-kubernetes-with-freebsd-part-2.md index 161f4a1a..5417cbdc 100644 --- a/gemfeed/2024-12-03-f3s-kubernetes-with-freebsd-part-2.md +++ b/gemfeed/2024-12-03-f3s-kubernetes-with-freebsd-part-2.md @@ -8,9 +8,9 @@ We set the stage last time; this time, we will set up the hardware for this proj These are all the posts so far: -[2024-11-17 f3s: Kubernetes with FreeBSD - Part 1: Setting the stage](./2024-11-17-f3s-kubernetes-with-freebsd-part-1.md) -[2024-12-03 f3s: Kubernetes with FreeBSD - Part 2: Hardware and base installation (You are currently reading this)](./2024-12-03-f3s-kubernetes-with-freebsd-part-2.md) [2025-02-01 f3s: Kubernetes with FreeBSD - Part 3: Protecting from power cuts](./2025-02-01-f3s-kubernetes-with-freebsd-part-3.md) +[2024-12-03 f3s: Kubernetes with FreeBSD - Part 2: Hardware and base installation (You are currently reading this)](./2024-12-03-f3s-kubernetes-with-freebsd-part-2.md) +[2024-11-17 f3s: Kubernetes with FreeBSD - Part 1: Setting the stage](./2024-11-17-f3s-kubernetes-with-freebsd-part-1.md) [![f3s logo](./f3s-kubernetes-with-freebsd-part-1/f3slogo.png "f3s logo")](./f3s-kubernetes-with-freebsd-part-1/f3slogo.png) @@ -298,14 +298,14 @@ Read the next post of this series: Other *BSD-related posts: -[2016-04-09 Jails and ZFS with Puppet on FreeBSD](./2016-04-09-jails-and-zfs-on-freebsd-with-puppet.md) -[2022-07-30 Let's Encrypt with OpenBSD and Rex](./2022-07-30-lets-encrypt-with-openbsd-and-rex.md) -[2022-10-30 Installing DTail on OpenBSD](./2022-10-30-installing-dtail-on-openbsd.md) -[2024-01-13 One reason why I love OpenBSD](./2024-01-13-one-reason-why-i-love-openbsd.md) -[2024-04-01 KISS high-availability with OpenBSD](./2024-04-01-KISS-high-availability-with-OpenBSD.md) -[2024-11-17 f3s: Kubernetes with FreeBSD - Part 1: Setting the stage](./2024-11-17-f3s-kubernetes-with-freebsd-part-1.md) -[2024-12-03 f3s: Kubernetes with FreeBSD - Part 2: Hardware and base installation (You are currently reading this)](./2024-12-03-f3s-kubernetes-with-freebsd-part-2.md) [2025-02-01 f3s: Kubernetes with FreeBSD - Part 3: Protecting from power cuts](./2025-02-01-f3s-kubernetes-with-freebsd-part-3.md) +[2024-12-03 f3s: Kubernetes with FreeBSD - Part 2: Hardware and base installation (You are currently reading this)](./2024-12-03-f3s-kubernetes-with-freebsd-part-2.md) +[2024-11-17 f3s: Kubernetes with FreeBSD - Part 1: Setting the stage](./2024-11-17-f3s-kubernetes-with-freebsd-part-1.md) +[2024-04-01 KISS high-availability with OpenBSD](./2024-04-01-KISS-high-availability-with-OpenBSD.md) +[2024-01-13 One reason why I love OpenBSD](./2024-01-13-one-reason-why-i-love-openbsd.md) +[2022-10-30 Installing DTail on OpenBSD](./2022-10-30-installing-dtail-on-openbsd.md) +[2022-07-30 Let's Encrypt with OpenBSD and Rex](./2022-07-30-lets-encrypt-with-openbsd-and-rex.md) +[2016-04-09 Jails and ZFS with Puppet on FreeBSD](./2016-04-09-jails-and-zfs-on-freebsd-with-puppet.md) E-Mail your comments to `paul@nospam.buetow.org` :-) diff --git a/gemfeed/2025-02-01-f3s-kubernetes-with-freebsd-part-3.md b/gemfeed/2025-02-01-f3s-kubernetes-with-freebsd-part-3.md index a464f44f..b129dc50 100644 --- a/gemfeed/2025-02-01-f3s-kubernetes-with-freebsd-part-3.md +++ b/gemfeed/2025-02-01-f3s-kubernetes-with-freebsd-part-3.md @@ -352,14 +352,14 @@ All good :-) See you in the next post of this series! Other BSD related posts are: -[2016-04-09 Jails and ZFS with Puppet on FreeBSD](./2016-04-09-jails-and-zfs-on-freebsd-with-puppet.md) -[2022-07-30 Let's Encrypt with OpenBSD and Rex](./2022-07-30-lets-encrypt-with-openbsd-and-rex.md) -[2022-10-30 Installing DTail on OpenBSD](./2022-10-30-installing-dtail-on-openbsd.md) -[2024-01-13 One reason why I love OpenBSD](./2024-01-13-one-reason-why-i-love-openbsd.md) -[2024-04-01 KISS high-availability with OpenBSD](./2024-04-01-KISS-high-availability-with-OpenBSD.md) -[2024-11-17 f3s: Kubernetes with FreeBSD - Part 1: Setting the stage](./2024-11-17-f3s-kubernetes-with-freebsd-part-1.md) -[2024-12-03 f3s: Kubernetes with FreeBSD - Part 2: Hardware and base installation](./2024-12-03-f3s-kubernetes-with-freebsd-part-2.md) [2025-02-01 f3s: Kubernetes with FreeBSD - Part 3: Protecting from power cuts (You are currently reading this)](./2025-02-01-f3s-kubernetes-with-freebsd-part-3.md) +[2024-12-03 f3s: Kubernetes with FreeBSD - Part 2: Hardware and base installation](./2024-12-03-f3s-kubernetes-with-freebsd-part-2.md) +[2024-11-17 f3s: Kubernetes with FreeBSD - Part 1: Setting the stage](./2024-11-17-f3s-kubernetes-with-freebsd-part-1.md) +[2024-04-01 KISS high-availability with OpenBSD](./2024-04-01-KISS-high-availability-with-OpenBSD.md) +[2024-01-13 One reason why I love OpenBSD](./2024-01-13-one-reason-why-i-love-openbsd.md) +[2022-10-30 Installing DTail on OpenBSD](./2022-10-30-installing-dtail-on-openbsd.md) +[2022-07-30 Let's Encrypt with OpenBSD and Rex](./2022-07-30-lets-encrypt-with-openbsd-and-rex.md) +[2016-04-09 Jails and ZFS with Puppet on FreeBSD](./2016-04-09-jails-and-zfs-on-freebsd-with-puppet.md) E-Mail your comments to `paul@nospam.buetow.org` :-) diff --git a/gemfeed/DRAFT-f3s-kubernetes-with-freebsd-part-4.md b/gemfeed/DRAFT-f3s-kubernetes-with-freebsd-part-4.md index 4fc1bc63..67371b5d 100644 --- a/gemfeed/DRAFT-f3s-kubernetes-with-freebsd-part-4.md +++ b/gemfeed/DRAFT-f3s-kubernetes-with-freebsd-part-4.md @@ -265,14 +265,14 @@ CPU STRESS TESTER VM VS NOT VM Other *BSD-related posts: -[2016-04-09 Jails and ZFS with Puppet on FreeBSD](./2016-04-09-jails-and-zfs-on-freebsd-with-puppet.md) -[2022-07-30 Let's Encrypt with OpenBSD and Rex](./2022-07-30-lets-encrypt-with-openbsd-and-rex.md) -[2022-10-30 Installing DTail on OpenBSD](./2022-10-30-installing-dtail-on-openbsd.md) -[2024-01-13 One reason why I love OpenBSD](./2024-01-13-one-reason-why-i-love-openbsd.md) -[2024-04-01 KISS high-availability with OpenBSD](./2024-04-01-KISS-high-availability-with-OpenBSD.md) -[2024-11-17 f3s: Kubernetes with FreeBSD - Part 1: Setting the stage](./2024-11-17-f3s-kubernetes-with-freebsd-part-1.md) -[2024-12-03 f3s: Kubernetes with FreeBSD - Part 2: Hardware and base installation](./2024-12-03-f3s-kubernetes-with-freebsd-part-2.md) [2025-02-01 f3s: Kubernetes with FreeBSD - Part 3: Protecting from power cuts](./2025-02-01-f3s-kubernetes-with-freebsd-part-3.md) +[2024-12-03 f3s: Kubernetes with FreeBSD - Part 2: Hardware and base installation](./2024-12-03-f3s-kubernetes-with-freebsd-part-2.md) +[2024-11-17 f3s: Kubernetes with FreeBSD - Part 1: Setting the stage](./2024-11-17-f3s-kubernetes-with-freebsd-part-1.md) +[2024-04-01 KISS high-availability with OpenBSD](./2024-04-01-KISS-high-availability-with-OpenBSD.md) +[2024-01-13 One reason why I love OpenBSD](./2024-01-13-one-reason-why-i-love-openbsd.md) +[2022-10-30 Installing DTail on OpenBSD](./2022-10-30-installing-dtail-on-openbsd.md) +[2022-07-30 Let's Encrypt with OpenBSD and Rex](./2022-07-30-lets-encrypt-with-openbsd-and-rex.md) +[2016-04-09 Jails and ZFS with Puppet on FreeBSD](./2016-04-09-jails-and-zfs-on-freebsd-with-puppet.md) E-Mail your comments to `paul@nospam.buetow.org` :-) -- cgit v1.2.3 From 30e7bf7e59b13e8348403a4cba3684cdbd1410cc Mon Sep 17 00:00:00 2001 From: Paul Buetow Date: Sat, 8 Feb 2025 11:07:21 +0200 Subject: Update content for md --- gemfeed/2024-07-05-random-weird-things.md | 7 +- gemfeed/2025-02-08-random-weird-things-ii.md | 251 ++++++++++++++++++++++++ gemfeed/index.md | 3 +- gemfeed/random-weird-things-ii/css-conway.png | Bin 0 -> 150862 bytes gemfeed/random-weird-things-ii/go-font-code.png | Bin 0 -> 88459 bytes gemfeed/random-weird-things-ii/sqlite-gem.png | Bin 0 -> 121177 bytes 6 files changed, 258 insertions(+), 3 deletions(-) create mode 100644 gemfeed/2025-02-08-random-weird-things-ii.md create mode 100644 gemfeed/random-weird-things-ii/css-conway.png create mode 100644 gemfeed/random-weird-things-ii/go-font-code.png create mode 100644 gemfeed/random-weird-things-ii/sqlite-gem.png (limited to 'gemfeed') diff --git a/gemfeed/2024-07-05-random-weird-things.md b/gemfeed/2024-07-05-random-weird-things.md index f8866ba7..08d9f5b0 100644 --- a/gemfeed/2024-07-05-random-weird-things.md +++ b/gemfeed/2024-07-05-random-weird-things.md @@ -1,9 +1,12 @@ -# Random Weird Things +# Random Weird Things - Part Ⅰ > Published at 2024-07-05T10:59:59+03:00 Every so often, I come across random, weird, and unexpected things on the internet. I thought it would be neat to share them here from time to time. As a start, here are ten of them. +[2024-07-05 Random Weird Things - Part Ⅰ (You are currently reading this)](./2024-07-05-random-weird-things.md) +[2025-02-08 Random Weird Things - Part Ⅱ](./2025-02-08-random-weird-things-ii.md) + ``` /\_/\ WHOA!! ( o.o ) @@ -15,7 +18,7 @@ WHOA!! ( o.o ) ## Table of Contents -* [⇢ Random Weird Things](#random-weird-things) +* [⇢ Random Weird Things - Part Ⅰ](#random-weird-things---part-) * [⇢ ⇢ 1. `bad.horse` traceroute](#1-badhorse-traceroute) * [⇢ ⇢ 2. ASCII cinema](#2-ascii-cinema) * [⇢ ⇢ 3. Netflix's Hello World application](#3-netflix-s-hello-world-application) diff --git a/gemfeed/2025-02-08-random-weird-things-ii.md b/gemfeed/2025-02-08-random-weird-things-ii.md new file mode 100644 index 00000000..3bd8973b --- /dev/null +++ b/gemfeed/2025-02-08-random-weird-things-ii.md @@ -0,0 +1,251 @@ +# Random Weird Things - Part Ⅱ + +> Published at 2025-02-08T11:06:16+02:00 + +Every so often, I come across random, weird, and unexpected things on the internet. I thought it would be neat to share them here from time to time. This is the second run. + +[2024-07-05 Random Weird Things - Part Ⅰ](./2024-07-05-random-weird-things.md) +[2025-02-08 Random Weird Things - Part Ⅱ (You are currently reading this)](./2025-02-08-random-weird-things-ii.md) + +``` +/\_/\ /\_/\ +( o.o ) WHOA!! ( o.o ) +> ^ < > ^ < +/ \ MOEEW! / \ +/______\ /______\ +``` + +## Table of Contents + +* [⇢ Random Weird Things - Part Ⅱ](#random-weird-things---part-) +* [⇢ ⇢ Go Programming](#go-programming) +* [⇢ ⇢ ⇢ 11. Official Go font](#11-official-go-font) +* [⇢ ⇢ ⇢ 12. Go functions can have methods](#12-go-functions-can-have-methods) +* [⇢ ⇢ macOS](#macos) +* [⇢ ⇢ ⇢ 13. ß and ss are treated the same](#13--and-ss-are-treated-the-same) +* [⇢ ⇢ ⇢ 14. Colon as file path separator](#14-colon-as-file-path-separator) +* [⇢ ⇢ 15. Polyglots - programs written in multiple languages](#15-polyglots---programs-written-in-multiple-languages) +* [⇢ ⇢ 16. Languages, where indices start at 1](#16-languages-where-indices-start-at-1) +* [⇢ ⇢ 17. Perl Poetry](#17-perl-poetry) +* [⇢ ⇢ 18. CSS3 is turing complete](#18-css3-is-turing-complete) +* [⇢ ⇢ 19. The SQLite codebase is a gem](#19-the-sqlite-codebase-is-a-gem) +* [⇢ ⇢ 20. The biggest shell programs ](#20-the-biggest-shell-programs-) + +## Go Programming + +### 11. Official Go font + +The Go programming language has an official font called "Go Font." It was created to complement the aesthetic of the Go language, ensuring clear and legible rendering of code. The font includes a monospace version for code and a proportional version for general text, supporting consistent look and readability in Go-related materials and development environments. + +Check out some Go code displayed using the Go font: + +[![Go font code](./random-weird-things-ii/go-font-code.png "Go font code")](./random-weird-things-ii/go-font-code.png) + +[https://go.dev/blog/go-fonts](https://go.dev/blog/go-fonts) + +The design emphasizes simplicity and readability, reflecting Go's philosophy of clarity and efficiency. + +I found it interesting and/or weird, as Go is a programming language. Why should it bother having its own font? I have never seen another open-source project like Go do this. But I also like it. Maybe I will use it in the future for this blog :-) + +### 12. Go functions can have methods + +Functions on struct types? Well, know. Functions on types like `int` and `string`? It's also known of, but a bit lesser. Functions on function types? That sounds a bit funky, but it's possible, too! For demonstration, have a look at this snippet: + +```go +package main + +import "log" + +type fun func() string + +func (f fun) Bar() string { + return "Bar" +} + +func main() { + var f fun = func() string { + return "Foo" + } + log.Println("Example 1: ", f()) + log.Println("Example 2: ", f.Bar()) + log.Println("Example 3: ", fun(f.Bar).Bar()) + log.Println("Example 4: ", fun(fun(f.Bar).Bar).Bar()) +} +``` + +It runs just fine: + +```sh +❯ go run main.go +2025/02/07 22:56:14 Example 1: Foo +2025/02/07 22:56:14 Example 2: Bar +2025/02/07 22:56:14 Example 3: Bar +2025/02/07 22:56:14 Example 4: Bar +``` + +## macOS + +For personal computing, I don't use Apple, but I have to use it for work. + +### 13. ß and ss are treated the same + +Know German? In German, the letter "sarp s" is written as ß. ß is treated the same as ss on macOS. + +On a case-insensitive file system like macOS, not only are uppercase and lowercase letters treated the same, but non-Latin characters like the German "ß" are also considered equivalent to their Latin counterparts (in this case, "ss"). + +So, even though "Maß" and "Mass" are not strictly equivalent, the macOS file system still treats them as the same filename due to its handling of Unicode characters. This can sometimes lead to unexpected behaviour. Check this out: + +```sh +❯ touch Maß +❯ ls -l +-rw-r--r--@ 1 paul wheel 0 Feb 7 23:02 Maß +❯ touch Mass +❯ ls -l +-rw-r--r--@ 1 paul wheel 0 Feb 7 23:02 Maß +❯ rm Mass +❯ ls -l + +❯ touch Mass +❯ ls -ltr +-rw-r--r--@ 1 paul wheel 0 Feb 7 23:02 Mass +❯ rm Maß +❯ ls -l + +``` + +### 14. Colon as file path separator + +MacOS can use the colon as a file path separator on its ADFS (file system). A typical ADFS file pathname on a hard disc might be: + +``` +ADFS::4.$.Documents.Techwriter.Myfile +``` + +I can't reproduce this on my (work) Mac, though, as it now uses the APFS file system. In essence, ADFS is an older file system, while APFS is a contemporary file system optimized for Apple's modern devices. + +[https://social.jvns.ca/@b0rk/113041293527832730](https://social.jvns.ca/@b0rk/113041293527832730) + +## 15. Polyglots - programs written in multiple languages + +A coding polyglot is a program or script written so that it can be executed in multiple programming languages without modification. This is typically achieved by leveraging syntax overlaps or crafting valid and meaningful code in each targeted language. Polyglot programs are often created as a challenge or for demonstration purposes to showcase language similarities or clever coding techniques. + +Check out my very own polyglot: + +[The `fibonatti.pl.c` Polyglot](./2014-03-24-the-fibonacci.pl.c-polyglot.md) + +## 16. Languages, where indices start at 1 + +Array indices start at 1 instead of 0 in some programming languages, known as one-based indexing. This can be controversial because zero-based indexing is more common in popular languages like C, C++, Java, and Python. One-based indexing can lead to off-by-one errors when developers switch between languages with different indexing schemes. + +Languages with One-Based Indexing: + +* Fortran +* MATLAB +* Lua +* R (for vectors and lists) +* Smalltalk +* Julia (by default, although zero-based indexing is also possible) + +`foo.lua` example: + +```lua +arr = {10, 20, 30, 40, 50} +print(arr[1]) -- Accessing the first element +```` + +```sh +❯ lua foo.lua +10 +``` + +One-based indexing is more natural for human-readable, mathematical, and theoretical contexts, where counting traditionally starts from one. + +## 17. Perl Poetry + +Perl Poetry is a playful and creative practice within the programming community where Perl code is written as a poem. These poems are crafted to be syntactically valid Perl code and make sense as poetic text, often with whimsical or humorous intent. This showcases Perl's flexibility and expressiveness, as well as the creativity of its programmers. + +See this Poetry of my own; the Perl interpreter does not yield any syntax error parsing that. But also, the Peom doesn't do anything useful then executed: + +```perl +# (C) 2006 by Paul C. Buetow + +Christmas:{time;#!!! + +Children: do tell $wishes; + +Santa: for $each (@children) { +BEGIN { read $each, $their, wishes and study them; use Memoize#ing + +} use constant gift, 'wrapping'; +package Gifts; pack $each, gift and bless $each and goto deliver +or do import if not local $available,!!! HO, HO, HO; + +redo Santa, pipe $gifts, to_childs; +redo Santa and do return if last one, is, delivered; + +deliver: gift and require diagnostics if our $gifts ,not break; +do{ use NEXT; time; tied $gifts} if broken and dump the, broken, ones; +The_children: sleep and wait for (each %gift) and try { to => untie $gifts }; + +redo Santa, pipe $gifts, to_childs; +redo Santa and do return if last one, is, delivered; + +The_christmas_tree: formline s/ /childrens/, $gifts; +alarm and warn if not exists $Christmas{ tree}, @t, $ENV{HOME}; +write <100wpm average`)](./2024-08-05-typing-127.1-words-per-minute.md) [2024-07-07 - 'The Stoic Challenge' book notes](./2024-07-07-the-stoic-challenge-book-notes.md) -[2024-07-05 - Random Weird Things](./2024-07-05-random-weird-things.md) +[2024-07-05 - Random Weird Things - Part Ⅰ](./2024-07-05-random-weird-things.md) [2024-06-23 - Terminal multiplexing with `tmux`](./2024-06-23-terminal-multiplexing-with-tmux.md) [2024-05-03 - Projects I currently don't have time for](./2024-05-03-projects-i-currently-dont-have-time-for.md) [2024-05-01 - 'Slow Productivity' book notes](./2024-05-01-slow-productivity-book-notes.md) diff --git a/gemfeed/random-weird-things-ii/css-conway.png b/gemfeed/random-weird-things-ii/css-conway.png new file mode 100644 index 00000000..c29d1d8b Binary files /dev/null and b/gemfeed/random-weird-things-ii/css-conway.png differ diff --git a/gemfeed/random-weird-things-ii/go-font-code.png b/gemfeed/random-weird-things-ii/go-font-code.png new file mode 100644 index 00000000..630cccfe Binary files /dev/null and b/gemfeed/random-weird-things-ii/go-font-code.png differ diff --git a/gemfeed/random-weird-things-ii/sqlite-gem.png b/gemfeed/random-weird-things-ii/sqlite-gem.png new file mode 100644 index 00000000..f3c3ceb6 Binary files /dev/null and b/gemfeed/random-weird-things-ii/sqlite-gem.png differ -- cgit v1.2.3 From 6c4b170afe6cee2c9dbd2cc117b597b8fd544590 Mon Sep 17 00:00:00 2001 From: Paul Buetow Date: Sat, 8 Feb 2025 11:12:36 +0200 Subject: Update content for md --- gemfeed/2025-02-08-random-weird-things-ii.md | 54 ++++++++++++++-------------- 1 file changed, 27 insertions(+), 27 deletions(-) (limited to 'gemfeed') diff --git a/gemfeed/2025-02-08-random-weird-things-ii.md b/gemfeed/2025-02-08-random-weird-things-ii.md index 3bd8973b..00d7100e 100644 --- a/gemfeed/2025-02-08-random-weird-things-ii.md +++ b/gemfeed/2025-02-08-random-weird-things-ii.md @@ -18,22 +18,32 @@ Every so often, I come across random, weird, and unexpected things on the intern ## Table of Contents * [⇢ Random Weird Things - Part Ⅱ](#random-weird-things---part-) +* [⇢ ⇢ 11. The SQLite codebase is a gem](#11-the-sqlite-codebase-is-a-gem) * [⇢ ⇢ Go Programming](#go-programming) -* [⇢ ⇢ ⇢ 11. Official Go font](#11-official-go-font) -* [⇢ ⇢ ⇢ 12. Go functions can have methods](#12-go-functions-can-have-methods) +* [⇢ ⇢ ⇢ 12. Official Go font](#12-official-go-font) +* [⇢ ⇢ ⇢ 13. Go functions can have methods](#13-go-functions-can-have-methods) * [⇢ ⇢ macOS](#macos) -* [⇢ ⇢ ⇢ 13. ß and ss are treated the same](#13--and-ss-are-treated-the-same) -* [⇢ ⇢ ⇢ 14. Colon as file path separator](#14-colon-as-file-path-separator) -* [⇢ ⇢ 15. Polyglots - programs written in multiple languages](#15-polyglots---programs-written-in-multiple-languages) -* [⇢ ⇢ 16. Languages, where indices start at 1](#16-languages-where-indices-start-at-1) -* [⇢ ⇢ 17. Perl Poetry](#17-perl-poetry) -* [⇢ ⇢ 18. CSS3 is turing complete](#18-css3-is-turing-complete) -* [⇢ ⇢ 19. The SQLite codebase is a gem](#19-the-sqlite-codebase-is-a-gem) +* [⇢ ⇢ ⇢ 14. ß and ss are treated the same](#14--and-ss-are-treated-the-same) +* [⇢ ⇢ ⇢ 15. Colon as file path separator](#15-colon-as-file-path-separator) +* [⇢ ⇢ 16. Polyglots - programs written in multiple languages](#16-polyglots---programs-written-in-multiple-languages) +* [⇢ ⇢ 17. Languages, where indices start at 1](#17-languages-where-indices-start-at-1) +* [⇢ ⇢ 18. Perl Poetry](#18-perl-poetry) +* [⇢ ⇢ 19. CSS3 is turing complete](#19-css3-is-turing-complete) * [⇢ ⇢ 20. The biggest shell programs ](#20-the-biggest-shell-programs-) +## 11. The SQLite codebase is a gem + +Check this out: + +[![SQLite Gem](./random-weird-things-ii/sqlite-gem.png "SQLite Gem")](./random-weird-things-ii/sqlite-gem.png) + +Source: + +[https://wetdry.world/@memes/112717700557038278](https://wetdry.world/@memes/112717700557038278) + ## Go Programming -### 11. Official Go font +### 12. Official Go font The Go programming language has an official font called "Go Font." It was created to complement the aesthetic of the Go language, ensuring clear and legible rendering of code. The font includes a monospace version for code and a proportional version for general text, supporting consistent look and readability in Go-related materials and development environments. @@ -47,7 +57,7 @@ The design emphasizes simplicity and readability, reflecting Go's philosophy of I found it interesting and/or weird, as Go is a programming language. Why should it bother having its own font? I have never seen another open-source project like Go do this. But I also like it. Maybe I will use it in the future for this blog :-) -### 12. Go functions can have methods +### 13. Go functions can have methods Functions on struct types? Well, know. Functions on types like `int` and `string`? It's also known of, but a bit lesser. Functions on function types? That sounds a bit funky, but it's possible, too! For demonstration, have a look at this snippet: @@ -87,7 +97,7 @@ It runs just fine: For personal computing, I don't use Apple, but I have to use it for work. -### 13. ß and ss are treated the same +### 14. ß and ss are treated the same Know German? In German, the letter "sarp s" is written as ß. ß is treated the same as ss on macOS. @@ -113,7 +123,7 @@ So, even though "Maß" and "Mass" are not strictly equivalent, the macOS file sy ``` -### 14. Colon as file path separator +### 15. Colon as file path separator MacOS can use the colon as a file path separator on its ADFS (file system). A typical ADFS file pathname on a hard disc might be: @@ -125,7 +135,7 @@ I can't reproduce this on my (work) Mac, though, as it now uses the APFS file sy [https://social.jvns.ca/@b0rk/113041293527832730](https://social.jvns.ca/@b0rk/113041293527832730) -## 15. Polyglots - programs written in multiple languages +## 16. Polyglots - programs written in multiple languages A coding polyglot is a program or script written so that it can be executed in multiple programming languages without modification. This is typically achieved by leveraging syntax overlaps or crafting valid and meaningful code in each targeted language. Polyglot programs are often created as a challenge or for demonstration purposes to showcase language similarities or clever coding techniques. @@ -133,7 +143,7 @@ Check out my very own polyglot: [The `fibonatti.pl.c` Polyglot](./2014-03-24-the-fibonacci.pl.c-polyglot.md) -## 16. Languages, where indices start at 1 +## 17. Languages, where indices start at 1 Array indices start at 1 instead of 0 in some programming languages, known as one-based indexing. This can be controversial because zero-based indexing is more common in popular languages like C, C++, Java, and Python. One-based indexing can lead to off-by-one errors when developers switch between languages with different indexing schemes. @@ -160,7 +170,7 @@ print(arr[1]) -- Accessing the first element One-based indexing is more natural for human-readable, mathematical, and theoretical contexts, where counting traditionally starts from one. -## 17. Perl Poetry +## 18. Perl Poetry Perl Poetry is a playful and creative practice within the programming community where Perl code is written as a poem. These poems are crafted to be syntactically valid Perl code and make sense as poetic text, often with whimsical or humorous intent. This showcases Perl's flexibility and expressiveness, as well as the creativity of its programmers. @@ -210,7 +220,7 @@ This is perl, v5.8.8 built for i386-freebsd-64int [More Perl Poetry of mine](./2008-06-26-perl-poetry.md) -## 18. CSS3 is turing complete +## 19. CSS3 is turing complete CSS3 is Turing complete because it can simulate a Turing machine using only CSS animations and styles without any JavaScript or external logic. This is achieved by using keyframe animations to change the styles of HTML elements in a way that encodes computation, performing calculations and state transitions. @@ -226,16 +236,6 @@ Check out this 100% CSS implementation of the Conways Game of Life: Conway's Game of Life is Turing complete because it can simulate a universal Turing machine, meaning it can perform any computation that a computer can, given the right initial conditions and sufficient time and space. Suppose a language can implement Conway's Game of Life. In that case, it demonstrates the language's ability to handle complex state transitions and computations. It has the necessary constructs (like iteration, conditionals, and data manipulation) to simulate any algorithm, thus confirming its Turing completeness. -## 19. The SQLite codebase is a gem - -Check this out: - -[![SQLite Gem](./random-weird-things-ii/sqlite-gem.png "SQLite Gem")](./random-weird-things-ii/sqlite-gem.png) - -Source: - -[https://wetdry.world/@memes/112717700557038278](https://wetdry.world/@memes/112717700557038278) - ## 20. The biggest shell programs One would think that shell scripts are only suitable for small tasks. Well, I must be wrong, as there are huge shell programs out there (up to 87k LOC) which aren't auto-generated but hand-written! -- cgit v1.2.3 From de8e48beffe62be50e5ad247aecca8e2d9787e34 Mon Sep 17 00:00:00 2001 From: Paul Buetow Date: Sat, 8 Feb 2025 23:21:32 +0200 Subject: Update content for md --- gemfeed/2024-07-05-random-weird-things.md | 70 +++++++++++++++++++------------ 1 file changed, 43 insertions(+), 27 deletions(-) (limited to 'gemfeed') diff --git a/gemfeed/2024-07-05-random-weird-things.md b/gemfeed/2024-07-05-random-weird-things.md index 08d9f5b0..9e4161a0 100644 --- a/gemfeed/2024-07-05-random-weird-things.md +++ b/gemfeed/2024-07-05-random-weird-things.md @@ -35,39 +35,55 @@ WHOA!! ( o.o ) Run traceroute to get the poem (or song). +> Update: A reader hinted that by specifying `-n 60`, there will be even more output! + ```bash -% traceroute bad.horse -traceroute to bad.horse (162.252.205.157), 30 hops max, 60 byte packets - 1 dsldevice.lan (192.168.1.1) 5.712 ms 5.800 ms 6.466 ms - 2 87-243-116-2.ip.btc-net.bg (87.243.116.2) 8.017 ms 7.506 ms 8.432 ms - 3 * * * +❯ traceroute -m 60 bad.horse +traceroute to bad.horse (162.252.205.157), 60 hops max, 60 byte packets + 1 _gateway (192.168.1.1) 5.237 ms 5.264 ms 6.009 ms + 2 77-85-0-2.ip.btc-net.bg (77.85.0.2) 8.753 ms 7.112 ms 8.336 ms + 3 212-39-69-103.ip.btc-net.bg (212.39.69.103) 9.434 ms 9.268 ms 9.986 ms 4 * * * - 5 xe-1-2-0.mpr1.fra4.de.above.net (80.81.194.26) 39.952 ms 40.155 ms 40.139 ms - 6 ae12.cs1.fra6.de.eth.zayo.com (64.125.26.172) 128.014 ms * * + 5 xe-1-2-0.mpr1.fra4.de.above.net (80.81.194.26) 39.812 ms 39.030 ms 39.772 ms + 6 * ae12.cs1.fra6.de.eth.zayo.com (64.125.26.172) 123.576 ms * 7 * * * 8 * * * - 9 ae10.cs1.lhr15.uk.eth.zayo.com (64.125.29.17) 120.625 ms 121.117 ms 121.050 ms -10 * * * + 9 ae10.cr1.lhr15.uk.eth.zayo.com (64.125.29.17) 119.097 ms 119.478 ms 120.767 ms +10 ae2.cr1.lhr11.uk.zip.zayo.com (64.125.24.140) 120.398 ms 121.147 ms 120.948 ms 11 * * * -12 * * * -13 ae5.mpr1.tor3.ca.zip.zayo.com (64.125.23.118) 192.605 ms 205.741 ms 203.607 ms -14 64.124.217.237.IDIA-265104-ZYO.zip.zayo.com (64.124.217.237) 204.673 ms 134.674 ms 131.442 ms +12 ae25.mpr1.yyz1.ca.zip.zayo.com (64.125.23.117) 145.072 ms * 181.773 ms +13 ae5.mpr1.tor3.ca.zip.zayo.com (64.125.23.118) 168.239 ms 168.158 ms 168.137 ms +14 64.124.217.237.IDIA-265104-ZYO.zip.zayo.com (64.124.217.237) 168.026 ms 167.999 ms 165.451 ms 15 * * * -16 67.223.96.90 (67.223.96.90) 128.245 ms 127.844 ms 127.843 ms -17 bad.horse (162.252.205.130) 128.194 ms 122.854 ms 121.786 ms -18 bad.horse (162.252.205.131) 128.831 ms 128.341 ms 186.559 ms -19 bad.horse (162.252.205.132) 185.716 ms 180.121 ms 180.042 ms -20 bad.horse (162.252.205.133) 203.170 ms 203.076 ms 203.168 ms -21 he.rides.across.the.nation (162.252.205.134) 203.115 ms 141.830 ms 141.799 ms -22 the.thoroughbred.of.sin (162.252.205.135) 147.965 ms 148.230 ms 170.478 ms -23 he.got.the.application (162.252.205.136) 165.161 ms 164.939 ms 159.085 ms -24 that.you.just.sent.in (162.252.205.137) 162.310 ms 158.569 ms 158.896 ms -25 it.needs.evaluation (162.252.205.138) 162.927 ms 163.046 ms 163.085 ms -26 so.let.the.games.begin (162.252.205.139) 233.363 ms 233.545 ms 233.317 ms -27 a.heinous.crime (162.252.205.140) 237.745 ms 233.614 ms 233.740 ms -28 a.show.of.force (162.252.205.141) 237.974 ms 176.085 ms 175.927 ms -29 a.murder.would.be.nice.of.course (162.252.205.142) 181.838 ms 181.858 ms 182.059 ms -30 bad.horse (162.252.205.143) 187.731 ms 187.416 ms 187.532 ms +16 t00.toroc1.on.ca.sn11.net (162.252.204.2) 131.598 ms 131.308 ms 131.482 ms +17 bad.horse (162.252.205.130) 131.430 ms 145.914 ms 130.514 ms +18 bad.horse (162.252.205.131) 136.634 ms 145.295 ms 135.631 ms +19 bad.horse (162.252.205.132) 139.158 ms 148.363 ms 138.934 ms +20 bad.horse (162.252.205.133) 145.395 ms 148.054 ms 147.140 ms +21 he.rides.across.the.nation (162.252.205.134) 149.687 ms 147.731 ms 150.135 ms +22 the.thoroughbred.of.sin (162.252.205.135) 156.644 ms 155.155 ms 156.447 ms +23 he.got.the.application (162.252.205.136) 161.187 ms 162.318 ms 162.674 ms +24 that.you.just.sent.in (162.252.205.137) 166.763 ms 166.675 ms 164.243 ms +25 it.needs.evaluation (162.252.205.138) 172.073 ms 171.919 ms 171.390 ms +26 so.let.the.games.begin (162.252.205.139) 175.386 ms 174.180 ms 175.965 ms +27 a.heinous.crime (162.252.205.140) 180.857 ms 180.766 ms 180.192 ms +28 a.show.of.force (162.252.205.141) 187.942 ms 186.669 ms 186.986 ms +29 a.murder.would.be.nice.of.course (162.252.205.142) 191.349 ms 191.939 ms 190.740 ms +30 bad.horse (162.252.205.143) 195.425 ms 195.716 ms 196.186 ms +31 bad.horse (162.252.205.144) 199.238 ms 200.620 ms 200.318 ms +32 bad.horse (162.252.205.145) 207.554 ms 206.729 ms 205.201 ms +33 he-s.bad (162.252.205.146) 211.087 ms 211.649 ms 211.712 ms +34 the.evil.league.of.evil (162.252.205.147) 212.657 ms 216.777 ms 216.589 ms +35 is.watching.so.beware (162.252.205.148) 220.911 ms 220.326 ms 221.961 ms +36 the.grade.that.you.receive (162.252.205.149) 225.384 ms 225.696 ms 225.640 ms +37 will.be.your.last.we.swear (162.252.205.150) 232.312 ms 230.989 ms 230.919 ms +38 so.make.the.bad.horse.gleeful (162.252.205.151) 235.761 ms 235.291 ms 235.585 ms +39 or.he-ll.make.you.his.mare (162.252.205.152) 241.350 ms 239.407 ms 238.394 ms +40 o_o (162.252.205.153) 246.154 ms 247.650 ms 247.110 ms +41 you-re.saddled.up (162.252.205.154) 250.925 ms 250.401 ms 250.619 ms +42 there-s.no.recourse (162.252.205.155) 256.071 ms 251.154 ms 255.340 ms +43 it-s.hi-ho.silver (162.252.205.156) 260.152 ms 261.775 ms 261.544 ms +44 signed.bad.horse (162.252.205.157) 262.430 ms 261.410 ms 261.365 ms ``` ## 2. ASCII cinema -- cgit v1.2.3 From d5c8bc23cec177ab0b29354a11cfea6d7ef9d7fa Mon Sep 17 00:00:00 2001 From: Paul Buetow Date: Wed, 12 Feb 2025 22:32:18 +0200 Subject: Update content for md --- gemfeed/2024-07-05-random-weird-things.md | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) (limited to 'gemfeed') diff --git a/gemfeed/2024-07-05-random-weird-things.md b/gemfeed/2024-07-05-random-weird-things.md index 9e4161a0..77eac814 100644 --- a/gemfeed/2024-07-05-random-weird-things.md +++ b/gemfeed/2024-07-05-random-weird-things.md @@ -1,6 +1,6 @@ # Random Weird Things - Part Ⅰ -> Published at 2024-07-05T10:59:59+03:00 +> Published at 2024-07-05T10:59:59+03:00; Updated at 2025-02-08 Every so often, I come across random, weird, and unexpected things on the internet. I thought it would be neat to share them here from time to time. As a start, here are ten of them. -- cgit v1.2.3 From 779895496e17944aa189d70e24fbc65cb8e5599a Mon Sep 17 00:00:00 2001 From: Paul Buetow Date: Thu, 13 Feb 2025 10:13:42 +0200 Subject: Update content for md --- ...25-01-01-posts-from-october-to-december-2024.md | 86 ++++++++++++---------- 1 file changed, 47 insertions(+), 39 deletions(-) (limited to 'gemfeed') diff --git a/gemfeed/2025-01-01-posts-from-october-to-december-2024.md b/gemfeed/2025-01-01-posts-from-october-to-december-2024.md index ba9ae92d..1ee46de0 100644 --- a/gemfeed/2025-01-01-posts-from-october-to-december-2024.md +++ b/gemfeed/2025-01-01-posts-from-october-to-december-2024.md @@ -35,6 +35,7 @@ These are from Mastodon and LinkedIn. Have a look at my about page for my social * [⇢ ⇢ ⇢ So, `#Haskell` is better suited for general ...](#so-haskell-is-better-suited-for-general-) * [⇢ ⇢ ⇢ At first, functional options add a bit of ...](#at-first-functional-options-add-a-bit-of-) * [⇢ ⇢ ⇢ Revamping my home lab a little bit. `#freebsd` ...](#revamping-my-home-lab-a-little-bit-freebsd-) +* [⇢ ⇢ ⇢ Revamping my home lab a little bit. `#freebsd` ...](#revamping-my-home-lab-a-little-bit-freebsd-) * [⇢ ⇢ ⇢ Wondering to which `#web` `#browser` I should ...](#wondering-to-which-web-browser-i-should-) * [⇢ ⇢ ⇢ eks-node-viewer is a nifty tool, showing the ...](#eks-node-viewer-is-a-nifty-tool-showing-the-) * [⇢ ⇢ ⇢ Have put more Photos on - On my static photo ...](#have-put-more-photos-on---on-my-static-photo-) @@ -70,43 +71,43 @@ These are from Mastodon and LinkedIn. Have a look at my about page for my social First on-call experience in a startup. Doesn't sound a lot of fun! But the lessons were learned! `#sre` -[ntietz.com/bl...irst-on-call/](https://ntietz.com/blog/lessons-from-my-first-on-call/) +[ntietz.com/blog/lessons-from-my-first-on-call/](https://ntietz.com/blog/lessons-from-my-first-on-call/) ### Reviewing your own PR or MR before asking ... Reviewing your own PR or MR before asking others to review it makes a lot of sense. Have seen so many silly mistakes which would have been avoided. Saving time for the real reviewer. -[www.jvt.me/po...-code-review/](https://www.jvt.me/posts/2019/01/12/self-code-review/) +[www.jvt.me/posts/2019/01/12/self-code-review/](https://www.jvt.me/posts/2019/01/12/self-code-review/) ### Fun with defer in `#golang`, I did't know, that ... Fun with defer in `#golang`, I did't know, that a defer object can either be heap or stack allocated. And there are some rules for inlining, too. -[victoriametri.../defer-in-go/](https://victoriametrics.com/blog/defer-in-go/) +[victoriametrics.com/blog/defer-in-go/](https://victoriametrics.com/blog/defer-in-go/) ### I have been in incidents. Understandably, ... I have been in incidents. Understandably, everyone wants the issue to be resolved as quickly and others want to know how long TTR will be. IMHO, providing no estimates at all is no solution either. So maybe give a rough estimate but clearly communicate that the estimate is rough and that X, Y, and Z can interfere, meaning there is a chance it will take longer to resolve the incident. Just my thought. What's yours? -[firehydrant.c...on-estimates/](https://firehydrant.com/blog/hot-take-dont-provide-incident-resolution-estimates/) +[firehydrant.com/blog/hot-take-dont-provide-incident-resolution-estimates/](https://firehydrant.com/blog/hot-take-dont-provide-incident-resolution-estimates/) ### Little tips using strings in `#golang` and I ... Little tips using strings in `#golang` and I personally think one must look more into the std lib (not just for strings, also for slices, maps,...), there are tons of useful helper functions. -[www.calhoun.i...trings-in-go/](https://www.calhoun.io/6-tips-for-using-strings-in-go/) +[www.calhoun.io/6-tips-for-using-strings-in-go/](https://www.calhoun.io/6-tips-for-using-strings-in-go/) ### Reading this post about `#rust` (especially the ... Reading this post about `#rust` (especially the first part), I think I made a good choice in deciding to dive into `#golang` instead. There was a point where I wanted to learn a new programming language, and Rust was on my list of choices. I think the Go project does a much better job of deciding what goes into the language and how. What are your thoughts? -[josephg.com/b...writing-rust/](https://josephg.com/blog/rewriting-rust/) +[josephg.com/blog/rewriting-rust/](https://josephg.com/blog/rewriting-rust/) ### The opposite of `#ChaosMonkey` ... ... The opposite of `#ChaosMonkey` ... automatically repairing and healing services helping to reduce manual toil work. Runbooks and scripts are only the first step, followed by a fully blown service written in Go. Could be useful, but IMHO why not rather address the root causes of the manual toil work? `#sre` -[blog.cloudfla...t-cloudflare/](https://blog.cloudflare.com/nl-nl/improving-platform-resilience-at-cloudflare/) +[blog.cloudflare.com/nl-nl/improving-platform-resilience-at-cloudflare/](https://blog.cloudflare.com/nl-nl/improving-platform-resilience-at-cloudflare/) ## November 2024 @@ -114,8 +115,8 @@ The opposite of `#ChaosMonkey` ... automatically repairing and healing services I just became a Silver Patreon for OSnews. What is OSnews? It is an independent news site about IT. It is slightly independent and, at times, alternative. I have enjoyed it since my early student days. This one and other projects I financially support are listed here: -[foo.zone/gemf...i-support.gmi (Gemini)](gemini://foo.zone/gemfeed/2024-09-07-projects-i-support.gmi) -[foo.zone/gemf...-support.html](https://foo.zone/gemfeed/2024-09-07-projects-i-support.html) +[foo.zone/gemfeed/2024-09-07-projects-i-support.gmi (Gemini)](gemini://foo.zone/gemfeed/2024-09-07-projects-i-support.gmi) +[foo.zone/gemfeed/2024-09-07-projects-i-support.html](https://foo.zone/gemfeed/2024-09-07-projects-i-support.html) ### Until now, I wasn't aware, that Go is under a ... @@ -127,8 +128,8 @@ Until now, I wasn't aware, that Go is under a BSD-style license (3-clause as it These are some book notes from "Staff Engineer" – there is some really good insight into what is expected from a Staff Engineer and beyond in the industry. I wish I had read the book earlier. -[foo.zone/gemf...ook-notes.gmi (Gemini)](gemini://foo.zone/gemfeed/2024-10-24-staff-engineer-book-notes.gmi) -[foo.zone/gemf...ok-notes.html](https://foo.zone/gemfeed/2024-10-24-staff-engineer-book-notes.html) +[foo.zone/gemfeed/2024-10-24-staff-engineer-book-notes.gmi (Gemini)](gemini://foo.zone/gemfeed/2024-10-24-staff-engineer-book-notes.gmi) +[foo.zone/gemfeed/2024-10-24-staff-engineer-book-notes.html](https://foo.zone/gemfeed/2024-10-24-staff-engineer-book-notes.html) ### Looking at `#Kubernetes`, it's pretty much ... @@ -138,21 +139,21 @@ Looking at `#Kubernetes`, it's pretty much following the Unix way of doing thing There has been an outage at the upstream network provider for OpenBSD.Amsterdam (hoster, I am using). This was the first real-world test for my KISS HA setup, and it worked flawlessly! All my sites and services failed over automatically to my other `#OpenBSD` VM! -[foo.zone/gemf...h-OpenBSD.gmi (Gemini)](gemini://foo.zone/gemfeed/2024-04-01-KISS-high-availability-with-OpenBSD.gmi) -[foo.zone/gemf...-OpenBSD.html](https://foo.zone/gemfeed/2024-04-01-KISS-high-availability-with-OpenBSD.html) +[foo.zone/gemfeed/2024-04-01-KISS-high-availability-with-OpenBSD.gmi (Gemini)](gemini://foo.zone/gemfeed/2024-04-01-KISS-high-availability-with-OpenBSD.gmi) +[foo.zone/gemfeed/2024-04-01-KISS-high-availability-with-OpenBSD.html](https://foo.zone/gemfeed/2024-04-01-KISS-high-availability-with-OpenBSD.html) [openbsd.amsterdam/](https://openbsd.amsterdam/) ### One of the more confusing parts in Go, nil ... One of the more confusing parts in Go, nil values vs nil errors: `#golang` -[unexpected-go...l-errors.html](https://unexpected-go.com/nil-errors-that-are-non-nil-errors.html) +[unexpected-go.com/nil-errors-that-are-non-nil-errors.html](https://unexpected-go.com/nil-errors-that-are-non-nil-errors.html) ### Agreeably, writing down with Diagrams helps you ... Agreeably, writing down with Diagrams helps you to think things more through. And keeps others on the same page. Only worth for projects from a certain size, IMHO. -[ntietz.com/bl...-design-docs/](https://ntietz.com/blog/reasons-to-write-design-docs/) +[ntietz.com/blog/reasons-to-write-design-docs/](https://ntietz.com/blog/reasons-to-write-design-docs/) ### I like the idea of types in Ruby. Raku is ... @@ -170,26 +171,33 @@ So, `#Haskell` is better suited for general purpose than `#Rust`? I thought depl At first, functional options add a bit of boilerplate, but they turn out to be quite neat, especially when you have very long parameter lists that need to be made neat and tidy. `#golang` -[www.calhoun.i...aining-in-go/](https://www.calhoun.io/using-functional-options-instead-of-method-chaining-in-go/) +[www.calhoun.io/using-functional-options-instead-of-method-chaining-in-go/](https://www.calhoun.io/using-functional-options-instead-of-method-chaining-in-go/) + +### Revamping my home lab a little bit. `#freebsd` ... + +Revamping my home lab a little bit. `#freebsd` `#bhyve` `#rocky` `#linux` `#vm` `#k3s` `#kuberbetes` `#wireguard` `#zfs` `#nfs` `#ha` `#relayd` `#k8s` `#selfhosting` `#self`-hosting `#homelab` `#home`-lab + +[foo.zone/gemfeed/2024-11-17-f3s-kubernetes-with-freebsd-part-1.gmi (Gemini)](gemini://foo.zone/gemfeed/2024-11-17-f3s-kubernetes-with-freebsd-part-1.gmi) +[foo.zone/gemfeed/2024-11-17-f3s-kubernetes-with-freebsd-part-1.html](https://foo.zone/gemfeed/2024-11-17-f3s-kubernetes-with-freebsd-part-1.html) ### Revamping my home lab a little bit. `#freebsd` ... Revamping my home lab a little bit. `#freebsd` `#bhyve` `#rocky` `#linux` `#vm` `#k3s` `#kubernetes` `#wireguard` `#zfs` `#nfs` `#ha` `#relayd` `#k8s` `#selfhosting` `#homelab` -[foo.zone/gemf...sd-part-1.gmi (Gemini)](gemini://foo.zone/gemfeed/2024-11-17-f3s-kubernetes-with-freebsd-part-1.gmi) -[foo.zone/gemf...d-part-1.html](https://foo.zone/gemfeed/2024-11-17-f3s-kubernetes-with-freebsd-part-1.html) +[foo.zone/gemfeed/2024-11-17-f3s-kubernetes-with-freebsd-part-1.gmi (Gemini)](gemini://foo.zone/gemfeed/2024-11-17-f3s-kubernetes-with-freebsd-part-1.gmi) +[foo.zone/gemfeed/2024-11-17-f3s-kubernetes-with-freebsd-part-1.html](https://foo.zone/gemfeed/2024-11-17-f3s-kubernetes-with-freebsd-part-1.html) ### Wondering to which `#web` `#browser` I should ... Wondering to which `#web` `#browser` I should switch now personally ... -[www.osnews.co...acy-and-more/](https://www.osnews.com/story/141100/mozilla-foundation-lays-off-30-of-its-employees-ends-advocacy-for-open-web-privacy-and-more/) +[www.osnews.com/story/141100/mozilla-fo...dvocacy-for-open-web-privacy-and-more/](https://www.osnews.com/story/141100/mozilla-foundation-lays-off-30-of-its-employees-ends-advocacy-for-open-web-privacy-and-more/) ### eks-node-viewer is a nifty tool, showing the ... eks-node-viewer is a nifty tool, showing the compute nodes currently in use in the `#EKS` cluster. especially useful when dynamically allocating nodes with `#karpenter` or auto scaling groups. -[github.com/aw...s-node-viewer](https://github.com/awslabs/eks-node-viewer) +[github.com/awslabs/eks-node-viewer](https://github.com/awslabs/eks-node-viewer) ### Have put more Photos on - On my static photo ... @@ -201,13 +209,13 @@ Have put more Photos on - On my static photo sites - Generated with a `#bash` sc In Go, passing pointers are not automatically faster than values. Pointers often force the memory to be allocated on the heap, adding GC overhad. With values, Go can determine whether to put the memory on the stack instead. But with large structs/objects (how you want to call them) or if you want to modify state, then pointers are the semantic to use. `#golang` -[blog.boot.dev...-than-values/](https://blog.boot.dev/golang/pointers-faster-than-values/) +[blog.boot.dev/golang/pointers-faster-than-values/](https://blog.boot.dev/golang/pointers-faster-than-values/) ### Myself being part of an on-call rotations over ... Myself being part of an on-call rotations over my whole professional life, just have learned this lesson "Tell people who are new to on-call: Just have fun" :-) This is a neat blog post to read: -[ntietz.com/bl...ew-to-oncall/](https://ntietz.com/blog/what-i-tell-people-new-to-oncall/) +[ntietz.com/blog/what-i-tell-people-new-to-oncall/](https://ntietz.com/blog/what-i-tell-people-new-to-oncall/) ### Feels good to code in my old love `#Perl` again ... @@ -225,20 +233,20 @@ This is an interactive summary of the Go release, with a lot of examples utilisi Thats unexpected, you cant remove a NaN key from a map without clearing it! `#golang` -[unexpected-go...aring-it.html](https://unexpected-go.com/you-cant-remove-a-nan-key-from-a-map-without-clearing-it.html) +[unexpected-go.com/you-cant-remove-a-nan-key-from-a-map-without-clearing-it.html](https://unexpected-go.com/you-cant-remove-a-nan-key-from-a-map-without-clearing-it.html) ### My second blog post about revamping my home lab ... My second blog post about revamping my home lab a little bit just hit the net. `#FreeBSD` `#ZFS` `#n100` `#k8s` `#k3s` `#kubernetes` -[foo.zone/gemf...sd-part-2.gmi (Gemini)](gemini://foo.zone/gemfeed/2024-12-03-f3s-kubernetes-with-freebsd-part-2.gmi) -[foo.zone/gemf...d-part-2.html](https://foo.zone/gemfeed/2024-12-03-f3s-kubernetes-with-freebsd-part-2.html) +[foo.zone/gemfeed/2024-12-03-f3s-kubernetes-with-freebsd-part-2.gmi (Gemini)](gemini://foo.zone/gemfeed/2024-12-03-f3s-kubernetes-with-freebsd-part-2.gmi) +[foo.zone/gemfeed/2024-12-03-f3s-kubernetes-with-freebsd-part-2.html](https://foo.zone/gemfeed/2024-12-03-f3s-kubernetes-with-freebsd-part-2.html) ### Very insightful article about tech hiring in ... Very insightful article about tech hiring in the age of LLMs. As an interviewer, I have experienced some of the scrnarios already first hand... -[newsletter.pr...s-tech-hiring](https://newsletter.pragmaticengineer.com/p/how-genai-changes-tech-hiring) +[newsletter.pragmaticengineer.com/p/how-genai-changes-tech-hiring](https://newsletter.pragmaticengineer.com/p/how-genai-changes-tech-hiring) ### for `#bpf` `#ebpf` performance debugging, have ... @@ -250,7 +258,7 @@ for `#bpf` `#ebpf` performance debugging, have a look at bpftop from Netflix. A 89 things he/she knows about Git commits is a neat list of `#Git` wisdoms -[www.jvt.me/po...know-commits/](https://www.jvt.me/posts/2024/07/12/things-know-commits/) +[www.jvt.me/posts/2024/07/12/things-know-commits/](https://www.jvt.me/posts/2024/07/12/things-know-commits/) ### I found that working on multiple side projects ... @@ -260,51 +268,51 @@ I found that working on multiple side projects concurrently is better than conce Agreed? Agreed. Besides `#Ruby`, I would also add `#RakuLang` and `#Perl` @Perl to the list of languages that are great for shell scripts - "Making Easy Things Easy and Hard Things Possible" -[lucasoshiro.g...-shellscript/](https://lucasoshiro.github.io/posts-en/2024-06-17-ruby-shellscript/) +[lucasoshiro.github.io/posts-en/2024-06-17-ruby-shellscript/](https://lucasoshiro.github.io/posts-en/2024-06-17-ruby-shellscript/) ### Plan9 assembly format in Go, but wait, it's not ... Plan9 assembly format in Go, but wait, it's not the Operating System Plan9! `#golang` `#rabbithole` -[www.osnews.co...ulations-450/](https://www.osnews.com/story/140941/go-plan9-memo-speeding-up-calculations-450/) +[www.osnews.com/story/140941/go-plan9-memo-speeding-up-calculations-450/](https://www.osnews.com/story/140941/go-plan9-memo-speeding-up-calculations-450/) ### This is a neat blog post about the Helix text ... This is a neat blog post about the Helix text editor, to which I personally switched around a year ago (from NeoVim). I should blog about my experience as well. To summarize: I am using it together with the terminal multiplexer `#tmux`. It doesn't bother me that Helix is purely terminal-based and therefore everything has to be in the same font. `#HelixEditor` -[jonathan-frer.../posts/helix/](https://jonathan-frere.com/posts/helix/) +[jonathan-frere.com/posts/helix/](https://jonathan-frere.com/posts/helix/) ### This blog post is basically a rant against ... This blog post is basically a rant against DataDog... Personally, I don't have much experience with DataDog (actually, I have never used it), but one reason to work with logs at my day job (with over 2,000 physical server machines) and to be cost-effective is by using dtail! `#dtail` `#logs` `#logmanagement` -[crys.site/blo...int-the-weel/](https://crys.site/blog/2024/reinventint-the-weel/) +[crys.site/blog/2024/reinventint-the-weel/](https://crys.site/blog/2024/reinventint-the-weel/) [dtail.dev](https://dtail.dev) ### Quick trick to get Helix themes selected ... Quick trick to get Helix themes selected randomly `#HelixEditor` -[foo.zone/gemf...ix-themes.gmi (Gemini)](gemini://foo.zone/gemfeed/2024-12-15-random-helix-themes.gmi) -[foo.zone/gemf...x-themes.html](https://foo.zone/gemfeed/2024-12-15-random-helix-themes.html) +[foo.zone/gemfeed/2024-12-15-random-helix-themes.gmi (Gemini)](gemini://foo.zone/gemfeed/2024-12-15-random-helix-themes.gmi) +[foo.zone/gemfeed/2024-12-15-random-helix-themes.html](https://foo.zone/gemfeed/2024-12-15-random-helix-themes.html) ### Example where complexity attacks you from ... Example where complexity attacks you from behind `#k8s` `#kubernetes` `#OpenAI` -[surfingcomple...ent-write-up/](https://surfingcomplexity.blog/2024/12/14/quick-takes-on-the-recent-openai-public-incident-write-up/) +[surfingcomplexity.blog/2024/12/14/quic...ecent-openai-public-incident-write-up/](https://surfingcomplexity.blog/2024/12/14/quick-takes-on-the-recent-openai-public-incident-write-up/) ### LLMs for Ops? Summaries of logs, probabilities ... LLMs for Ops? Summaries of logs, probabilities about correctness, auto-generating Ansible, some uses cases are there. Wouldn't trust it fully, though. -[youtu.be/Woda...0egrfl5izCSQI](https://youtu.be/WodaffxVq-E?si=noY0egrfl5izCSQI) +[youtu.be/WodaffxVq-E?si=noY0egrfl5izCSQI](https://youtu.be/WodaffxVq-E?si=noY0egrfl5izCSQI) ### Excellent article about your dream Product ... Excellent article about your dream Product Manager: Why every software team needs a product manager to thrive via @wallabagapp -[testdouble.co...ware-delivery](https://testdouble.com/insights/why-product-managers-accelerate-improve-software-delivery) +[testdouble.com/insights/why-product-ma...s-accelerate-improve-software-delivery](https://testdouble.com/insights/why-product-managers-accelerate-improve-software-delivery) ### I just finished reading all chapters of CPU ... @@ -316,17 +324,17 @@ I just finished reading all chapters of CPU land: ... not claiming to remember e Indeed, useful to know this stuff! `#sre` -[biriukov.dev/...applications/](https://biriukov.dev/docs/resolver-dual-stack-application/0-sre-should-know-about-gnu-linux-resolvers-and-dual-stack-applications/) +[biriukov.dev/docs/resolver-dual-stack-...resolvers-and-dual-stack-applications/](https://biriukov.dev/docs/resolver-dual-stack-application/0-sre-should-know-about-gnu-linux-resolvers-and-dual-stack-applications/) ### It's the small things, which make Unix like ... It's the small things, which make Unix like systems, like GNU/Linux, interesting. Didn't know about this `#GNU` `#Tar` behaviour yet: -[xeiaso.net/no...pop-quiz-tar/](https://xeiaso.net/notes/2024/pop-quiz-tar/) +[xeiaso.net/notes/2024/pop-quiz-tar/](https://xeiaso.net/notes/2024/pop-quiz-tar/) ### My New Year's resolution is not to start any ... -My New Year's resolution is not to start any new non-fiction books (or only very few) but to re-read and listen to my favorites, which I read to reflect on and see things from different perspectives. Every time you re-read a book, you gain new insights.16350 +My New Year's resolution is not to start any new non-fiction books (or only very few) but to re-read and listen to my favorites, which I read to reflect on and see things from different perspectives. Every time you re-read a book, you gain new insights.17483 Other related posts: -- cgit v1.2.3 From 06c0bb8b81d2eb47342069cd479433950e821eaf Mon Sep 17 00:00:00 2001 From: Paul Buetow Date: Thu, 13 Feb 2025 10:14:40 +0200 Subject: Update content for md --- gemfeed/2025-01-01-posts-from-october-to-december-2024.md | 8 -------- 1 file changed, 8 deletions(-) (limited to 'gemfeed') diff --git a/gemfeed/2025-01-01-posts-from-october-to-december-2024.md b/gemfeed/2025-01-01-posts-from-october-to-december-2024.md index 1ee46de0..a28e3d67 100644 --- a/gemfeed/2025-01-01-posts-from-october-to-december-2024.md +++ b/gemfeed/2025-01-01-posts-from-october-to-december-2024.md @@ -35,7 +35,6 @@ These are from Mastodon and LinkedIn. Have a look at my about page for my social * [⇢ ⇢ ⇢ So, `#Haskell` is better suited for general ...](#so-haskell-is-better-suited-for-general-) * [⇢ ⇢ ⇢ At first, functional options add a bit of ...](#at-first-functional-options-add-a-bit-of-) * [⇢ ⇢ ⇢ Revamping my home lab a little bit. `#freebsd` ...](#revamping-my-home-lab-a-little-bit-freebsd-) -* [⇢ ⇢ ⇢ Revamping my home lab a little bit. `#freebsd` ...](#revamping-my-home-lab-a-little-bit-freebsd-) * [⇢ ⇢ ⇢ Wondering to which `#web` `#browser` I should ...](#wondering-to-which-web-browser-i-should-) * [⇢ ⇢ ⇢ eks-node-viewer is a nifty tool, showing the ...](#eks-node-viewer-is-a-nifty-tool-showing-the-) * [⇢ ⇢ ⇢ Have put more Photos on - On my static photo ...](#have-put-more-photos-on---on-my-static-photo-) @@ -175,13 +174,6 @@ At first, functional options add a bit of boilerplate, but they turn out to be q ### Revamping my home lab a little bit. `#freebsd` ... -Revamping my home lab a little bit. `#freebsd` `#bhyve` `#rocky` `#linux` `#vm` `#k3s` `#kuberbetes` `#wireguard` `#zfs` `#nfs` `#ha` `#relayd` `#k8s` `#selfhosting` `#self`-hosting `#homelab` `#home`-lab - -[foo.zone/gemfeed/2024-11-17-f3s-kubernetes-with-freebsd-part-1.gmi (Gemini)](gemini://foo.zone/gemfeed/2024-11-17-f3s-kubernetes-with-freebsd-part-1.gmi) -[foo.zone/gemfeed/2024-11-17-f3s-kubernetes-with-freebsd-part-1.html](https://foo.zone/gemfeed/2024-11-17-f3s-kubernetes-with-freebsd-part-1.html) - -### Revamping my home lab a little bit. `#freebsd` ... - Revamping my home lab a little bit. `#freebsd` `#bhyve` `#rocky` `#linux` `#vm` `#k3s` `#kubernetes` `#wireguard` `#zfs` `#nfs` `#ha` `#relayd` `#k8s` `#selfhosting` `#homelab` [foo.zone/gemfeed/2024-11-17-f3s-kubernetes-with-freebsd-part-1.gmi (Gemini)](gemini://foo.zone/gemfeed/2024-11-17-f3s-kubernetes-with-freebsd-part-1.gmi) -- cgit v1.2.3 From e3971ae885e26a6947ed3b6e3f4c7372a7d4328e Mon Sep 17 00:00:00 2001 From: Paul Buetow Date: Thu, 13 Feb 2025 10:21:52 +0200 Subject: Update content for md --- gemfeed/2025-01-01-posts-from-october-to-december-2024.md | 10 +++++----- 1 file changed, 5 insertions(+), 5 deletions(-) (limited to 'gemfeed') diff --git a/gemfeed/2025-01-01-posts-from-october-to-december-2024.md b/gemfeed/2025-01-01-posts-from-october-to-december-2024.md index a28e3d67..f8cbae83 100644 --- a/gemfeed/2025-01-01-posts-from-october-to-december-2024.md +++ b/gemfeed/2025-01-01-posts-from-october-to-december-2024.md @@ -183,7 +183,7 @@ Revamping my home lab a little bit. `#freebsd` `#bhyve` `#rocky` `#linux` `#vm` Wondering to which `#web` `#browser` I should switch now personally ... -[www.osnews.com/story/141100/mozilla-fo...dvocacy-for-open-web-privacy-and-more/](https://www.osnews.com/story/141100/mozilla-foundation-lays-off-30-of-its-employees-ends-advocacy-for-open-web-privacy-and-more/) +[www.osnews.com/story/141100/mozilla-fo..-..dvocacy-for-open-web-privacy-and-more/](https://www.osnews.com/story/141100/mozilla-foundation-lays-off-30-of-its-employees-ends-advocacy-for-open-web-privacy-and-more/) ### eks-node-viewer is a nifty tool, showing the ... @@ -292,7 +292,7 @@ Quick trick to get Helix themes selected randomly `#HelixEditor` Example where complexity attacks you from behind `#k8s` `#kubernetes` `#OpenAI` -[surfingcomplexity.blog/2024/12/14/quic...ecent-openai-public-incident-write-up/](https://surfingcomplexity.blog/2024/12/14/quick-takes-on-the-recent-openai-public-incident-write-up/) +[surfingcomplexity.blog/2024/12/14/quic..-..ecent-openai-public-incident-write-up/](https://surfingcomplexity.blog/2024/12/14/quick-takes-on-the-recent-openai-public-incident-write-up/) ### LLMs for Ops? Summaries of logs, probabilities ... @@ -304,7 +304,7 @@ LLMs for Ops? Summaries of logs, probabilities about correctness, auto-generatin Excellent article about your dream Product Manager: Why every software team needs a product manager to thrive via @wallabagapp -[testdouble.com/insights/why-product-ma...s-accelerate-improve-software-delivery](https://testdouble.com/insights/why-product-managers-accelerate-improve-software-delivery) +[testdouble.com/insights/why-product-ma..-..s-accelerate-improve-software-delivery](https://testdouble.com/insights/why-product-managers-accelerate-improve-software-delivery) ### I just finished reading all chapters of CPU ... @@ -316,7 +316,7 @@ I just finished reading all chapters of CPU land: ... not claiming to remember e Indeed, useful to know this stuff! `#sre` -[biriukov.dev/docs/resolver-dual-stack-...resolvers-and-dual-stack-applications/](https://biriukov.dev/docs/resolver-dual-stack-application/0-sre-should-know-about-gnu-linux-resolvers-and-dual-stack-applications/) +[biriukov.dev/docs/resolver-dual-stack-..-..resolvers-and-dual-stack-applications/](https://biriukov.dev/docs/resolver-dual-stack-application/0-sre-should-know-about-gnu-linux-resolvers-and-dual-stack-applications/) ### It's the small things, which make Unix like ... @@ -326,7 +326,7 @@ It's the small things, which make Unix like systems, like GNU/Linux, interesting ### My New Year's resolution is not to start any ... -My New Year's resolution is not to start any new non-fiction books (or only very few) but to re-read and listen to my favorites, which I read to reflect on and see things from different perspectives. Every time you re-read a book, you gain new insights.17483 +My New Year's resolution is not to start any new non-fiction books (or only very few) but to re-read and listen to my favorites, which I read to reflect on and see things from different perspectives. Every time you re-read a book, you gain new insights.17491 Other related posts: -- cgit v1.2.3 From e4ffe6a7fc83ce139d910dfefdec91d1f1b4ff09 Mon Sep 17 00:00:00 2001 From: Paul Buetow Date: Thu, 13 Feb 2025 21:24:14 +0200 Subject: Update content for md --- gemfeed/2009-02-13-sgi-onyx-3200.md | 66 ++++++++++++++++++++++++++++++++++++ gemfeed/index.md | 1 + gemfeed/sgi-onyx-3200/collage.webp | Bin 0 -> 63022 bytes gemfeed/sgi-onyx-3200/desk.webp | Bin 0 -> 254420 bytes 4 files changed, 67 insertions(+) create mode 100644 gemfeed/2009-02-13-sgi-onyx-3200.md create mode 100644 gemfeed/sgi-onyx-3200/collage.webp create mode 100644 gemfeed/sgi-onyx-3200/desk.webp (limited to 'gemfeed') diff --git a/gemfeed/2009-02-13-sgi-onyx-3200.md b/gemfeed/2009-02-13-sgi-onyx-3200.md new file mode 100644 index 00000000..1bc56794 --- /dev/null +++ b/gemfeed/2009-02-13-sgi-onyx-3200.md @@ -0,0 +1,66 @@ +# SGI Onyx 3200 + +> Published at 2025-02-13T21:17:16+02:00 + +For nostalgia, I've kept this output of the 'dmesg' around. It's from an SGI Onyx 3200 graphics supercomputer with the following specs: + +* 4 400 MHz IP35 MIPS CPUs +* 4GB of RAM + +[![./sgi-onyx-3200/desk.webp](./sgi-onyx-3200/desk.webp)](./sgi-onyx-3200/desk.webp) + +We used this monster when I was a student worker at the Fraunhofer Institute for Production Technology around the year 2006. It operated a walk-in 2-sided 3D cave (unfortunately, I don't have any pictures of that cave), where you could literally walk around with a set of VR glasses and see everything in 3D (that was when there wasn't any Oculus Quest yet). That was useful for running industrial simulations. + +``` +4 400 MHZ IP35 Processors +CPU: MIPS R12000 Processor Chip Revision: 3.5 +FPU: MIPS R12010 Floating Point Chip Revision: 3.5 +Main memory size: 4096 Mbytes +Instruction cache size: 32 Kbytes +Data cache size: 32 Kbytes +Secondary unified instruction/data cache size: 8 Mbytes +Integral SCSI controller 8: Version Fibre Channel QL2200A +Integral SCSI controller 6: Version QL12160, single ended +Integral SCSI controller 7: Version QL12160, low voltage differential +Integral SCSI controller 9: Version IEEE1394 SBP2 + IEEE1394 CDROM: node 1010031001a454 port 0 on SCSI controller 9 +Integral SCSI controller 0: Version Fibre Channel QL2200A + Disk drive: unit 1 on SpCSI controller 0 + Disk drive: unit 2 on SCSI controller 0 +Integral SCSI controller 5: Version IEEE1394 SBP2 + IEEE1394 CDROM: node 1010031001c080 port 0 on SCSI controller 5 +IOC3 serial port: tty3 +IOC3 serial port: tty4 +IOC3 serial port: tty10 +IOC3 serial port: tty11 +IOC3 serial port: tty12 +IOC3 serial port: tty5 +IOC3 serial port: tty6 +IOC3 serial port: tty7 +IOC3 serial port: tty8 +IOC3 serial port: tty9 +Graphics board: InfiniteReality3 +Graphics board: InfiniteReality3 +Gigabit Ethernet: eg0, module 001c04, pci_bus 2, pci_slot 2, firmware version 12.4.10 +Fast Ethernet: ef1, version 1, module 001c07, pci 4 +Integral Fast Ethernet: ef0, version 1, module 001c04, pci 4 +Iris Audio Processor: version RAD revision 13.0, number 1 +IOC3 external interrupts: 2 +IOC3 external interrupts: 1 +IEEE 1394 High performance serial bus controller 0: Type: OHCI, Version 0 0 +IEEE 1394 High performance serial bus controller 1: Type: OHCI, Version 0 0 +USB controller: type OHCI +USB Human Interface Device: device id 1 type keyboard +USB Human Interface Device: device id 1 type mouse +USB controller: type OHCI +USB Human Interface Device: device id 0 type keyboard +USB Human Interface Device: device id 0 type mouse +``` + +I was mainly working on drilling simulations on this machine. Sometimes I worked directly at one of the 2 terminal screens of the Onyx, or often I used a nearby Linux machine and forwarded the X11 windows to my local screen. + +[![./sgi-onyx-3200/collage.webp](./sgi-onyx-3200/collage.webp)](./sgi-onyx-3200/collage.webp) + +E-Mail your comments to `paul@nospam.buetow.org` :-) + +[Back to the main site](../) diff --git a/gemfeed/index.md b/gemfeed/index.md index 1319a0cc..81c3326c 100644 --- a/gemfeed/index.md +++ b/gemfeed/index.md @@ -75,5 +75,6 @@ [2010-05-09 - The Fype Programming Language](./2010-05-09-the-fype-programming-language.md) [2010-05-07 - Lazy Evaluation with Standard ML](./2010-05-07-lazy-evaluation-with-standarn-ml.md) [2010-04-09 - Standard ML and Haskell](./2010-04-09-standard-ml-and-haskell.md) +[2009-02-13 - SGI Onyx 3200](./2009-02-13-sgi-onyx-3200.md) [2008-12-29 - Using my Nokia N95 for fixing my MTA](./2008-12-29-using-my-nokia-n95-for-fixing-my-mta.md) [2008-06-26 - Perl Poetry](./2008-06-26-perl-poetry.md) diff --git a/gemfeed/sgi-onyx-3200/collage.webp b/gemfeed/sgi-onyx-3200/collage.webp new file mode 100644 index 00000000..e33ea1c8 Binary files /dev/null and b/gemfeed/sgi-onyx-3200/collage.webp differ diff --git a/gemfeed/sgi-onyx-3200/desk.webp b/gemfeed/sgi-onyx-3200/desk.webp new file mode 100644 index 00000000..d82681e5 Binary files /dev/null and b/gemfeed/sgi-onyx-3200/desk.webp differ -- cgit v1.2.3 From c28c7bcc351150911c49aabc551d2eef328b0b06 Mon Sep 17 00:00:00 2001 From: Paul Buetow Date: Sat, 15 Feb 2025 21:57:18 +0200 Subject: Update content for md --- gemfeed/2009-02-13-sgi-onyx-3200.md | 8 +++++--- gemfeed/sgi-onyx-3200/collage2.webp | Bin 0 -> 55770 bytes 2 files changed, 5 insertions(+), 3 deletions(-) create mode 100644 gemfeed/sgi-onyx-3200/collage2.webp (limited to 'gemfeed') diff --git a/gemfeed/2009-02-13-sgi-onyx-3200.md b/gemfeed/2009-02-13-sgi-onyx-3200.md index 1bc56794..dd523bcc 100644 --- a/gemfeed/2009-02-13-sgi-onyx-3200.md +++ b/gemfeed/2009-02-13-sgi-onyx-3200.md @@ -2,9 +2,9 @@ > Published at 2025-02-13T21:17:16+02:00 -For nostalgia, I've kept this output of the 'dmesg' around. It's from an SGI Onyx 3200 graphics supercomputer with the following specs: +For nostalgia, I've kept this output of the 'dmesg' around. It's from an SGI Onyx 3200 graphics supercomputer running IRIX with the following specs: -* 4 400 MHz IP35 MIPS CPUs +* 4 x 400 MHz IP35 MIPS CPUs * 4GB of RAM [![./sgi-onyx-3200/desk.webp](./sgi-onyx-3200/desk.webp)](./sgi-onyx-3200/desk.webp) @@ -57,9 +57,11 @@ USB Human Interface Device: device id 0 type keyboard USB Human Interface Device: device id 0 type mouse ``` +[![./sgi-onyx-3200/collage.webp](./sgi-onyx-3200/collage.webp)](./sgi-onyx-3200/collage.webp) + I was mainly working on drilling simulations on this machine. Sometimes I worked directly at one of the 2 terminal screens of the Onyx, or often I used a nearby Linux machine and forwarded the X11 windows to my local screen. -[![./sgi-onyx-3200/collage.webp](./sgi-onyx-3200/collage.webp)](./sgi-onyx-3200/collage.webp) +[![./sgi-onyx-3200/collage2.webp](./sgi-onyx-3200/collage2.webp)](./sgi-onyx-3200/collage2.webp) E-Mail your comments to `paul@nospam.buetow.org` :-) diff --git a/gemfeed/sgi-onyx-3200/collage2.webp b/gemfeed/sgi-onyx-3200/collage2.webp new file mode 100644 index 00000000..21ccbc44 Binary files /dev/null and b/gemfeed/sgi-onyx-3200/collage2.webp differ -- cgit v1.2.3