set codeberg as primary remote forge

5 files changed, 25 insertions, 23 deletions

diff --git a/README.org b/README.org
index 01f4856..4c95409 100644
--- a/README.org
+++ b/README.org
@@ -1,4 +1,6 @@
-* tdback.net
+#+TITLE: tdback.net
+#+AUTHOR: Tyler Dunneback
+#+OPTIONS: toc:nil
 Source code for my personal website/blog.
 
 Build the site:
diff --git a/content/about/index.md b/content/about/index.md
index 13e75f6..52c3deb 100644
--- a/content/about/index.md
+++ b/content/about/index.md
@@ -14,7 +14,7 @@ I enjoy systems administration, infrastructure, and programming. I currently
 work as a systems administrator and IT specialist.
 
 You can find my current and past projects on my [personal git
-server](https://git.tdback.net) or [GitHub](https://github.com/tdback).
+server](https://gffit.tdback.net) or [Codeberg](https://codeberg.org/tdback).
 The source code for this website is also publicly
 [available](https://git.tdback.net/website).
 
diff --git a/content/posts/switching-to-hugo-one/index.md b/content/posts/switching-to-hugo-one/index.md
index 53b89c5..a93d18d 100644
--- a/content/posts/switching-to-hugo-one/index.md
+++ b/content/posts/switching-to-hugo-one/index.md
@@ -21,14 +21,15 @@ point your browser to https://tdback.net, things will look noticeably
 different.
 
 Some may recall that my old website employed the use of the
-[TiddlyWiki](https://tiddlywiki.com), a wonderful piece of software that allows
-you to create a non-linear notebook for organizing and sharing complex
-information. The downside to using a TiddlyWiki as my primary blogging platform
-was the need to do almost everything in the browser. As someone who spends a
-majority of their time editing text inside [neovim](https://neovim.io), I found
-myself sorely missing my beloved [vim motions](https://vim.rtorr.com/) and the
-ability to quickly move around my system using tools such as `tmux` or `fzf`.
-In short: I missed my terminal.
+[TiddlyWiki](https://tiddlywiki.com), a wonderful piece of software
+that allows you to create a non-linear notebook for organizing and
+sharing complex information. The downside to using a TiddlyWiki as my
+primary blogging platform was the need to do almost everything in the
+browser. As someone who spends a majority of their time editing text
+inside [neovim](https://neovim.io), I found myself sorely missing my
+beloved [vim motions](https://vim.rtorr.com/) and the ability to
+quickly move around my system using tools such as `tmux` or `fzf`. In
+short: I missed my terminal.
 
 When researching static site generators, I stumbled across the ever so popular
 [Hugo](https://gohugo.io). I immediately found it quite compelling: writing an
@@ -38,13 +39,7 @@ also comes with a built-in RSS feed generator, meaning that I didn't have to
 [write one myself](https://old.tdback.net/#Hacking%20on%20RSS) (although I
 quite enjoyed doing so).
 
-While I've traditionally thrown my site's index.html file onto GitHub Pages
-and/or Codeberg Pages, as a hobbyist self-hoster I'd be doing an injustice by
-not hosting the server on my own hardware. While I would encourage others to
-take advantage of free static site hosting services such as
-[GitHub Pages](https://pages.github.com/), I've found that I quite enjoy the
-responsibilities, challenges, and learning opportunities associated with
-self-hosting.
+While I've traditionally thrown my site's index.html file onto Codeberg Pages, as a hobbyist self-hoster I'd be doing an injustice by not hosting the server on my own hardware. While I would encourage others to take advantage of free static site hosting services such as [Codeberg Pages](https://codeberg.page/), I've found that I quite enjoy the responsibilities, challenges, and learning opportunities associated with self-hosting.
 
 ## Closing Thoughts
 So far my experience with Hugo has been great! After just a few hours I had a
diff --git a/content/posts/switching-to-hugo-two/index.md b/content/posts/switching-to-hugo-two/index.md
index 22f7d56..f7a68bb 100644
--- a/content/posts/switching-to-hugo-two/index.md
+++ b/content/posts/switching-to-hugo-two/index.md
@@ -26,7 +26,7 @@ same, regardless of the server it's running on. This alleviates the headache of
 dependency management and reduces setup times down to just
 `nixos-rebuild switch`, should I have the need to move my website to different
 hardware. The [nix flake for my system
-configurations](https://github.com/tdback/nix-config) is tracked in a remote
+configurations](https://git.tdback.net/nix-config) is tracked in a remote
 repository with `git`, making configuration changes a single `git pull` away.
 
 The following module defined in `modules/services/proxy/default.nix` enables
@@ -34,14 +34,20 @@ the caddy service using the `caddy` package found in
 [nixpkgs](https://search.nixos.org/packages?channel=24.11&query=caddy),
 and opens up both TCP ports 80 and 443 to accept inbound HTTP/S traffic.
 ```nix
-{ pkgs, ... }:
+{
+  pkgs,
+  ...
+}:
 {
   services.caddy = {
     enable = true;
     package = pkgs.caddy;
   };
 
-  networking.firewall.allowTCPPorts = [ 80 443 ];
+  networking.firewall.allowTCPPorts = [
+    80
+    443
+  ];
 }
 ```
 
@@ -53,7 +59,6 @@ server. I've also enabled both gzip and zstd support for compressing web server
 responses.
 
 ```nix
-{ ... }:
 {
   services.caddy.virtualHosts = {
     "tdback.net".extraConfig = ''
diff --git a/hugo.toml b/hugo.toml
index 2e8cd61..9938d9f 100644
--- a/hugo.toml
+++ b/hugo.toml
@@ -22,8 +22,8 @@ defaultContentLanguage = 'en-us'
     name = 'tdback.net'
     display = 'standalone'
   [[params.socialIcons]]
-    name = 'github'
-    url = 'https://github.com/tdback'
+    name = 'gitea'
+    url = 'https://codeberg.org/tdback'
   [[params.socialIcons]]
     name = 'mastodon'
     url = 'https://social.tdback.net/@tdback'