Merge pull request #2 from hackmysql/path-revamp

Path revamp

Author: daniel-nichter

config.toml

@@ -15,6 +15,7 @@ copyright = "2024 Daniel Nichter"
 [taxonomies]
 tag = "tags"
 series = "series"
+path = "path"
 
 [markup.goldmark.renderer]
 unsafe = true

content/21-parameter-group-values-to-change-in-amazon-rds-for-mysql.md

@@ -6,6 +6,8 @@ comments: true
 aliases:
   - /post/21-parameter-group-values-to-change-in-amazon-rds-for-mysql/
 disqus_url: "https://hackmysql.com/post/21-parameter-group-values-to-change-in-amazon-rds-for-mysql/"
+params:
+  path: cloud
 ---
 
 [Amazon RDS for MySQL](https://aws.amazon.com/rds/mysql/) uses many default values for system variables, but it also sets a few "sys vars" with different values. As with any database, neither product (MySQL) nor provider (AWS) defaults can best suite all use cases. It's our responsibility to carefully review and set every important system variable. This is tedious and difficult, but I've done it for you.

content/about.md

@@ -1,6 +1,5 @@
 ---
 title: "About"
-menu: main
 summary: "Hack MySQL is the personal website of Daniel Nichter, author of the book Efficient MySQL Performance published by O'Reilly. His webiste explores MySQL, Go, and software design."
 ---
 

content/are-aurora-performance-claims-true.md

@@ -7,6 +7,8 @@ type: "page"
 lastMod: "2024-06-04T13:36:00-04:00"
 aliases:
   - /post/are-aurora-performance-claims-true/
+params:
+  path: cloud
 ---
 
 Amazon claims that Aurora has "Up to 5X the throughput of MySQL".

content/book-0.md

@@ -1,5 +1,4 @@
 ---
-type: "page"
 date: "2021-12-27T09:30:00-05:00"
 title: "Efficient MySQL Performance"
 subtitle: "Preface"

content/book-1.md

@@ -8,6 +8,8 @@ aliases:
   - /post/book-1/
 disqus_url: "https://hackmysql.com/post/book-1/"
 series: "Behind the Book"
+params:
+  path: qrt
 ---
 
 Editors and technical reviewers suggested that I cover how to configure MySQL query metrics in chapter 1 of [_Efficient MySQL Performance_](https://oreil.ly/efficient-mysql-performance), but I deferred because it was out of scope for the book, which focuses on engineers _using_ MySQL, not DBAs.

content/book-10.md

@@ -9,6 +9,8 @@ aliases:
   - /post/book-10/
 disqus_url: "https://hackmysql.com/post/book-10/"
 series: "Behind the Book"
+params:
+  path: cloud
 ---
 
 No, I don't think so.

content/book-2.md

@@ -9,6 +9,8 @@ aliases:
   - /post/book-2/
 disqus_url: "https://hackmysql.com/post/book-2/"
 series: "Behind the Book"
+params:
+  path: index
 ---
 
 As of MySQL 8.0.18, [`EXPLAIN ANALYZE`](https://dev.mysql.com/doc/refman/8.0/en/explain.html#explain-analyze) is an indispensable tool for understanding query execution because it breaks down the query execution stage of response time by measuring each step of the query execution plan.

content/book-3.md

@@ -9,6 +9,8 @@ aliases:
   - /post/book-3/
 disqus_url: "https://hackmysql.com/post/book-3/"
 series: "Behind the Book"
+params:
+  path: data
 ---
 
 Is MySQL performance about "more" or "less"? From the title, you can tell that I'm going to argue that it's about "less". Here's the punchline: zero is maximum performance. Let's see where this philosophical blog post leads us.

content/book-4.md

@@ -9,6 +9,8 @@ aliases:
   - /post/book-4/
 disqus_url: "https://hackmysql.com/post/book-4/"
 series: "Behind the Book"
+params:
+  path: data
 ---
 
 Access patterns intrigue me because it seems that everyone knows what they are and talks about them, but there's also very little written about them—in MySQL literature, at least.