.forgejo/workflows/unlighthouse.yml

@@ -7,7 +7,7 @@ on:
 jobs:
   unlighthouse:
     runs-on: docker
-    container: forgejo.neshweb.net/firq/unlighthouse-docker:latest
+    container: forgejo.neshweb.net/ci-docker-images/unlighthouse-docker:latest
     steps:
       - name: Checkout repository
         uses: https://code.forgejo.org/actions/checkout@v3 

Dockerfile

@@ -4,7 +4,7 @@ COPY . .
 RUN npm i
 RUN npm run build
 
-FROM forgejo.neshweb.net/firq/website-serve-docker:latest AS runtime
+FROM forgejo.neshweb.net/ci-docker-images/website-serve-docker:latest AS runtime
 
 COPY --from=build /app/dist /public
 COPY --from=build /app/serve.json /public/serve.json

package.json

@@ -1,7 +1,7 @@
 {
 	"name": "@firq/fgosite",
 	"type": "module",
-	"version": "0.1.12",
+	"version": "0.1.13",
 	"private": true,
 	"scripts": {
 		"dev": "astro dev",

src/pages/blog/deploying-this-round-2.md

@@ -2,7 +2,7 @@
 layout: ../../layouts/blogPost.astro
 title: 'Migrating to Forgejo'
 pubDate: 2023-12-23
-description: 'My small recollection of migrating this site + CI to Forgejo'
+description: 'My short recollection of migrating this site + CI to Forgejo'
 author: 'Firq'
 tags: ['astro', 'docker', 'forgejo']
 ---
@@ -58,7 +58,7 @@ COPY . .
 RUN npm i
 RUN npm run build
 
-FROM forgejo.neshweb.net/firq/website-serve-docker:latest AS runtime
+FROM forgejo.neshweb.net/ci-docker-images/website-serve-docker:latest AS runtime
 
 COPY --from=build /app/dist /public
 COPY --from=build /app/serve.json /public/serve.json
@@ -138,7 +138,7 @@ With this container, the CI step to actually run the tests became a lot easier:
 jobs:
   unlighthouse:
     runs-on: docker
-    container: forgejo.neshweb.net/firq/unlighthouse-docker:latest
+    container: forgejo.neshweb.net/ci-docker-images/unlighthouse-docker:latest
     steps:
       - name: Checkout repository
         uses: https://code.forgejo.org/actions/checkout@v3