wip

.gitea/workflows/build.yml

@@ -15,13 +15,13 @@ jobs:
         uses: docker/setup-qemu-action@v3
       - name: dockerx setup
         uses: docker/setup-buildx-action@v1
-      - name: Cache Docker layers
-        uses: actions/cache@v2
-        with:
-          path: /tmp/.buildx-cache
-          key: ${{ runner.os }}-buildx-${{ github.sha }}
-          restore-keys: |
-            ${{ runner.os }}-buildx-
+      # - name: Cache Docker layers
+      #   uses: actions/cache@v2
+      #   with:
+      #     path: /tmp/.buildx-cache
+      #     key: ${{ runner.os }}-buildx-${{ github.sha }}
+      #     restore-keys: |
+      #       ${{ runner.os }}-buildx-
       - name: login
         uses: docker/login-action@v3
         with:

content/posts/how-to-blog.md

@@ -172,3 +172,6 @@ This was the most difficult thing to do. We are _almost_ there.
 With a docker image readily available, we can automatically deploy the blog when we push it!
 
 I personally am a big fan of the simplicity of [portainer](https://www.portainer.io/), as it scales really well when doing perosnal server stuff.
+
+## P.S.
+You may notice that the build script on the real