add link checker

.github/workflows/links.yml

@@ -0,0 +1,38 @@
+name: Link Checker
+
+on:
+  pull_request:
+  schedule:
+    - cron: '0 2 * * *'
+
+jobs:
+  linkChecker:
+    runs-on: ubuntu-latest
+    steps:
+      - uses: actions/checkout@v4
+
+      - name: Setup Hugo
+        if: github.event_name == 'pull_request'
+        uses: peaceiris/actions-hugo@v3
+        with:
+          hugo-version: '0.131.0'
+
+      - name: Build
+        if: github.event_name == 'pull_request'
+        run: hugo --minify
+
+      - name: Serve
+        if: github.event_name == 'pull_request'
+        run: python3 -m http.server 8080 --directory public &
+
+      - name: Check Links (PR)
+        if: github.event_name == 'pull_request'
+        uses: lycheeverse/lychee-action@v2
+        with:
+          args: --config lychee.toml --base-url 'http://localhost:8080' --verbose --no-progress './public/**/*.html'
+
+      - name: Check Links (Scheduled)
+        if: github.event_name == 'schedule'
+        uses: lycheeverse/lychee-action@v2
+        with:
+          args: --config lychee.toml --base-url 'https://cedardb.com' --verbose --no-progress './content/**/*.md'

README.md

@@ -1,6 +1,6 @@
 # CedarDB Documentation
 
-This repository contains the code for the [CedarDB documentation](https://cedardb.com/docs).
+This repository contains the code for the [CedarDB documentation](https://cedardb.com/docs/).
 The documentation is built by the static-site-generator [Hugo](https://gohugo.io/) and uses the [Hextra](https://imfing.github.io/hextra/docs/guide/) theme.
 
 Clone repository:

content/clients/javascript/_index.md

@@ -71,7 +71,7 @@ for (const row of result.rows) {
 ### Bulk loading
 
 For large imports, use `COPY FROM STDIN` via the
-[pg-copy-streams](https://github.com/brianc/pg-copy-streams) package:
+[pg-copy-streams](https://github.com/brianc/node-pg-copy-streams) package:
 
 ```shell
 npm install pg-copy-streams

content/clients/tools/dbeaver.md

@@ -51,7 +51,7 @@ the [official docs](https://dbeaver.com/docs/dbeaver/Create-Connection/).
 
 This is a brief overview of the features you can use with DBeaver.
 For more in-depth information, use
-[DBeaver's getting started guide](https://dbeaver.com/docs/dbeaver/Basic-operations-with-DBeaver/).
+[DBeaver's getting started guide](https://github.com/dbeaver/dbeaver/wiki/Basic-operations).
 
 ### Schema
 

content/community_edition.md

@@ -38,7 +38,7 @@ The **CedarDB Community Edition**
 It is **the right choice** for everything from solo projects to small-scale production workloads. No strings attached!
 
 {{% callout type="info" %}}
-Looking for advanced features or enterprise support? Check out the **Enterprise Edition** or visit our [pricing page](https://cedardb.com/pricing).
+Looking for advanced features or enterprise support? Check out the **Enterprise Edition** or visit our [pricing page](https://cedardb.com/pricing/).
 {{% /callout %}}
 
 |                              | Community Edition                                                                                                 | Enterprise Edition        |

content/example_datasets/job.md

@@ -16,7 +16,7 @@ assume uniform data distribution and instead has to rely on collected samples an
 
 The dataset comprises a total of 21 tables extracted from IMDB, containing information about the movie industry, such
 as movies, studios, actors, and their connections, such as roles of actors in movies.
-The full schema with information on all tables is available as an SQL file [schema.sql](https://www.cedardb.com/data/job/schema.sql).
+The full schema with information on all tables is available as an SQL file [schema.sql](https://cedardb.com/data/job/schema.sql).
 E.g., the `cast_info` table, which comprises the most rows by far, can be created as:
 
 ```sql
@@ -50,7 +50,7 @@ The compressed tarball is about 1.2 GB to download, which decompresses to a
 
 ### Import the schema to CedarDB
 
-To create the full schema inside CedarDB, download the [schema.sql](https://www.cedardb.com/data/job/schema.sql) file and load it, either on a new connection using:
+To create the full schema inside CedarDB, download the [schema.sql](https://cedardb.com/data/job/schema.sql) file and load it, either on a new connection using:
 
 ```shell
 psql -h localhost -U {{username}} < your/path/schema.sql
@@ -78,7 +78,7 @@ Some strings in the IMDB dataset contain the separator `,`, so you have to use t
 more performant `TEXT` when importing the data.
 {{< /callout >}}
 
-For convenience, we provide an SQL file will all necessary copy commands [load.sql](https://www.cedardb.com/data/job/load.sql).
+For convenience, we provide an SQL file will all necessary copy commands [load.sql](https://cedardb.com/data/job/load.sql).
 Please note that you need to modify the include paths from `your/path` to the correct location relative to the CedarDB
 server.
 

content/example_datasets/nasdaq.md

@@ -81,7 +81,7 @@ $ hexdump -C -n 100 01302020.NASDAQ_ITCH50
 00000064
 ```
 
-We have written a [Python parser](https://github.com/cedardb/examples/blob/main/nasdaq/parser.py) to transform this into human-readable CSV files.
+We have written a [Python parser](https://github.com/cedardb/examples/blob/main/nasdaq/parser/parser.py) to transform this into human-readable CSV files.
 It is automatically invoked by the `prepare.sh` script.
 
 {{< callout type="info" >}}

content/references/datatypes/boolean.md

@@ -52,7 +52,7 @@ To opt-out of this behavior you can use `x is null`, which never returns `null`.
 The syntax to compare two values and consider `nulls` equal is somewhat verbose: `x is not distinct from y`.
 
 However, while most functions return `null` for any `null` input, for boolean logic, e.g., in `and`, a single `false`
-can determine the whole expressions [[1](http://databasearchitects.blogspot.com/2017/02/reasoning-in-presence-of-nulls.html), [2](https://doi.org/10.1109/ICDE.2018.00214)].
+can determine the whole expressions [[1](https://databasearchitects.blogspot.com/2017/02/reasoning-in-presence-of-nulls.html), [2](https://doi.org/10.1109/ICDE.2018.00214)].
 This results in more subtle ternary truth tables for booleans:
 
 ```sql

data/releasenotes.json

@@ -1527,11 +1527,11 @@
 		"notes": [
 			{
 				"type": "feat",
-				"note": "Added support for <a href=\"https://cedardb.com/docs/references/sqlreference/functions/text/#regexp_count\"><tt>regexp_count</tt> and <tt>regexp_instr</tt></a>."
+				"note": "Added support for <a href=\"https://cedardb.com/docs/references/functions/text/#regexp_count\"><tt>regexp_count</tt> and <tt>regexp_instr</tt></a>."
 			},
 			{
 				"type": "feat",
-				"note": "Added support for <a href=\"https://cedardb.com/docs/references/sqlreference/functions/text/#string_to_table\"><tt>string_to_table</tt></a>."
+				"note": "Added support for <a href=\"https://cedardb.com/docs/references/functions/text/#string_to_table\"><tt>string_to_table</tt></a>."
 			},
 			{
 				"type": "feat",
@@ -2334,7 +2334,7 @@
 			},
 			{
 				"type": "feat",
-				"note": "Output of <tt>explain</tt> is now flatter, allowing you to more easily read query plans of complex queries. For a full overview and instructions on how to get back the old behavior, please refer to <a href=https://cedardb.com/docs/references/sqlreference/statements/explain>our docs</a>."
+				"note": "Output of <tt>explain</tt> is now flatter, allowing you to more easily read query plans of complex queries. For a full overview and instructions on how to get back the old behavior, please refer to <a href=https://cedardb.com/docs/references/utility/explain/>our docs</a>."
 			},
 			{
 				"type": "feat",
@@ -2496,7 +2496,7 @@
 		"notes": [
 			{
 				"type": "feat",
-				"note": "We have added support for explain statements after different query optimization steps. For example, <tt>explain (step Unnesting) select * from foo, bar where foo.a = bar.b</tt> shows the query tree after the 'Unnesting' optimization step but before the 'Predicate Pushdown' step. For the syntax and available steps, please refer to <a href=https://cedardb.com/docs/references/sqlreference/statements/explain/#step>our docs</a>."
+				"note": "We have added support for explain statements after different query optimization steps. For example, <tt>explain (step Unnesting) select * from foo, bar where foo.a = bar.b</tt> shows the query tree after the 'Unnesting' optimization step but before the 'Predicate Pushdown' step. For the syntax and available steps, please refer to <a href=https://cedardb.com/docs/references/utility/explain/#step>our docs</a>."
 			},
 			{
 				"type": "perf",

hugo.yaml

@@ -37,7 +37,7 @@ menu:
       url: https://cedardb.com/
       weight: 1
     - name: Blog
-      url: https://cedardb.com/blog
+      url: https://cedardb.com/blog/
       weight: 2
     - name: Search
       weight: 3

i18n/en.yaml

@@ -1,2 +1,2 @@
-copyright: "© CedarDB | [Imprint](https://cedardb.com/imprint)"
+copyright: "© CedarDB | [Imprint](https://cedardb.com/imprint/)"
 poweredBy: ""

layouts/partials/footer.html

@@ -11,9 +11,9 @@
     <div class="cedar-footer__links">
       <div>
         <h2>Company</h2>
-        <a href="https://cedardb.com/pricing">Pricing</a>
+        <a href="https://cedardb.com/pricing/">Pricing</a>
         <a href="https://cedardb.com/about/">About Us</a>
-        <a href="https://cedardb.com/blog">Blog</a>
+        <a href="https://cedardb.com/blog/">Blog</a>
       </div>
       <div>
         <h2>Developers</h2>
@@ -36,7 +36,7 @@ <h2>Install</h2>
     <div class="cedar-footer__meta-links">
       <a href="https://github.com/cedardb" target="_blank" rel="noreferrer">GitHub</a>
       <a href="https://cedardb.com/privacy-policy/" target="_blank" rel="noreferrer">Privacy</a>
-      <a href="https://cedardb.com/imprint" target="_blank" rel="noreferrer">Imprint</a>
+      <a href="https://cedardb.com/imprint/" target="_blank" rel="noreferrer">Imprint</a>
     </div>
   </div>
 </footer>

lychee.toml

@@ -0,0 +1,17 @@
+timeout = 30
+max_retries = 3
+max_concurrency = 32
+
+# Accept rate-limited responses as non-failures
+ accept = [200, 202, 204, 206, 429]
+
+# When links are available using HTTPS, treat HTTP links as errors.
+require_https = true
+
+exclude = [
+  # Local addresses
+  "https?://localhost",
+  "file://",
+  "https://bonsai.cedardb.com/slack",
+  "https://www.bka.de",
+]