change git domain

docker-stack.yml.template

@@ -7,7 +7,7 @@ networks:
 
 services:
   static:
-    image: git.pim.kunis.nl/pim/static:TAG
+    image: git.kun.is/pim/static:TAG
     networks:
       - traefik
     deploy:

jekyll/_config.yml

@@ -3,7 +3,7 @@ description: There can be only one
 lang: en-US
 timezone: Europe/Amsterdam
 image: assets/img/avatar.jpg
-repo: https://git.pim.kunis.nl/pim/pizzeria
+repo: https://git.kun.is/pim/static
 mode: light
 
 author:

jekyll/_includes/footer.html

@@ -2,7 +2,7 @@
   <a href="https://ci.kun.is/teams/main/pipelines/static" target="_blank" rel="nofollow noopener">
     <img src="https://ci.kun.is/api/v1/teams/main/pipelines/static/badge" alt="CI">
   </a>
-  <a class="footer_item" href="https://git.pim.kunis.nl/pim"><i class="fa-solid fa-code-branch"></i> Git</a>
+  <a class="footer_item" href="https://git.kun.is/pim"><i class="fa-solid fa-code-branch"></i> Git</a>
   <a class="footer_item" rel="me" href="https://social.pizzapim.nl/@pim"><i class="fab fa-mastodon"></i> Mastodon</a>
   <span class="footer_item">&copy; {{ site.time | date: "%Y" }}</span>
   <small class="footer_copyright">

jekyll/_posts/concourse-apprise-notifier/2023-06-14-concourse-apprise-notifier.md

@@ -7,7 +7,7 @@ categories: concourse apprise
 
 Recently, I deployed [Concourse CI](https://concourse-ci.org/) because I wanted to get my feet wet with a CI/CD pipeline.
 However, I had a practical use case lying around for a long time: automatically compiling my static website and deploying it to my docker Swarm.
-This took some time getting right, but the result works like a charm ([source code](https://git.pim.kunis.nl/pim/static)).
+This took some time getting right, but the result works like a charm ([source code](https://git.kun.is/pim/static)).
 
 It's comforting to know I don't have move a finger and my website is automatically deployed.
 However, I would still like to receive some indication of what's happening.
@@ -44,7 +44,7 @@ As Apprise notifications are basically fire-and-forget, we will only implement t
 
 # Writing the `out` script
 
-The whole script can be found [here](https://git.pim.kunis.nl/pim/concourse-apprise-notifier/src/branch/master/out), but I will explain the most important bits of it.
+The whole script can be found [here](https://git.kun.is/pim/concourse-apprise-notifier/src/branch/master/out), but I will explain the most important bits of it.
 Note that I only use Apprise's persistent storage solution, and not its stateless solution.
 
 Concourse provides us with the working directory, which we `cd` to:
@@ -125,7 +125,7 @@ echo "${timestamp}" >&3
 # Building the Container
 
 As said earlier, to actually use this script, we need to add it to a image.
-I won't be explaining this whole process, but the source can be found [here](https://git.pim.kunis.nl/pim/concourse-apprise-notifier/src/branch/master/pipeline.yml).
+I won't be explaining this whole process, but the source can be found [here](https://git.kun.is/pim/concourse-apprise-notifier/src/branch/master/pipeline.yml).
 The most important take-aways are these:
 - Use `concourse/oci-build-task` to build a image from a Dockerfile.
 - Use `registry-image` to push the image to an image registry.
@@ -133,14 +133,14 @@ The most important take-aways are these:
 # Using the Resource Type
 
 Using our newly created resource type is surprisingly simple.
-I use it for the blog you are reading right now and the pipeline definition can be found [here](https://git.pim.kunis.nl/pim/static/src/branch/main/pipeline.yml).
+I use it for the blog you are reading right now and the pipeline definition can be found [here](https://git.kun.is/pim/static/src/branch/main/pipeline.yml).
 Here we specify the resource type in a Concourse pipeline:
 ```yaml
 resource_types:
 - name: apprise
   type: registry-image
   source:
-    repository: git.pim.kunis.nl/pim/concourse-apprise-notifier
+    repository: git.kun.is/pim/concourse-apprise-notifier
     tag: "1.1.1"
 ```
 

jekyll/_posts/homebrew-ssh-ca/2023-05-23-homebrew-ssh-ca.md

@@ -181,4 +181,4 @@ There are ways to implement these, but for my home lab I did not deem this neces
 In a more professional environment, I would suggest using [Hashicorp's Vault](https://www.vaultproject.io/).
 
 This project did teach me about the limits and flexibility of Terraform, so all in all a success!
-All code can be found on the git repository [here](https://git.pim.kunis.nl/home/tf-modules/src/branch/master/debian).
+All code can be found on the git repository [here](https://git.kun.is/home/tf-modules/src/branch/master/debian).

labels

@@ -1,4 +1,4 @@
 org.opencontainers.image.authors=Pim Kunis
-org.opencontainers.image.source=https://git.pim.kunis.nl/pim/static
+org.opencontainers.image.source=https://git.kun.is/pim/static
-org.opencontainers.image.documentation=https://git.pim.kunis.nl/pim/static/src/branch/master/README.md
+org.opencontainers.image.documentation=https://git.kun.is/pim/static/src/branch/master/README.md
 org.opencontainers.image.description=My static website written in Jekyll.

pipeline.yml

@@ -3,19 +3,19 @@ resource_types:
 - name: apprise
   type: registry-image
   source:
-    repository: git.pim.kunis.nl/pim/concourse-apprise-notifier
+    repository: git.kun.is/pim/concourse-apprise-notifier
     tag: "1.1.1"
 
 resources:
 - name: site-repo
   type: git
   source:
-    uri: https://git.pim.kunis.nl/pim/static.git
+    uri: https://git.kun.is/pim/static.git
   icon: git
 - name: site-registry-image
   type: registry-image
   source:
-    repository: git.pim.kunis.nl/pim/static
+    repository: git.kun.is/pim/static
     username: pim
     password: ((api_key))
     tag: stable
@@ -31,7 +31,7 @@ resources:
   source:
     driver: git
     initial_version: "1.1.0"
-    uri: ssh://git@git.pim.kunis.nl:56287/pim/static.git
+    uri: ssh://git@git.kun.is:56287/pim/static.git
     branch: version
     file: version
     private_key: {{private_key}}