From 725868f83790cb04098af87f5f7264c7ef8e37a5 Mon Sep 17 00:00:00 2001
From: MaximEdogawa <leo@librem.one>
Date: Mon, 20 Apr 2026 10:52:02 +0200
Subject: [PATCH 1/2] update: enhance Vite configuration and deployment
 documentation

- Added 'penguinpool.space' to the allowed hosts in Vite config.
- Updated deployment README with instructions for fixing TLS certificate warnings for 'pengine.net'.
---
 deployment/README.md |  6 ++++++
 vite.config.ts       | 29 +++++++++++++++--------------
 2 files changed, 21 insertions(+), 14 deletions(-)

diff --git a/deployment/README.md b/deployment/README.md
index 6999f81..8e893cb 100644
--- a/deployment/README.md
+++ b/deployment/README.md
@@ -22,6 +22,12 @@ curl -fsS http://127.0.0.1:1422/ | head
 
 Configure **`PENGINE_SUBDOMAIN`** on the **Pengui** repo (Certbot + nginx vhost); see Pengui `deployment/README.md`.
 
+If the browser warns that the certificate is for **`penguinpool.space`** (or another hostname) when you open **`https://pengine.net`**, nginx is serving a **default TLS certificate** that does not list **`pengine.net`** in **Subject Alternative Name**. Fix it on the server:
+
+1. Confirm DNS **`A`/`AAAA`** for `pengine.net` points at this host.
+2. Obtain a certificate that **includes `pengine.net`** (e.g. Certbot: add `-d pengine.net` to the existing certificate request, or run a separate cert for `pengine.net` and point the `pengine.net` `server` block at those files).
+3. Reload nginx so the `server_name pengine.net` block uses that certificate (not the pool-only cert).
+
 ## Remove the container and pull a fresh image
 
 Use this after a new image tag is published, if the container is stuck, or you want to clear the cached local image.
diff --git a/vite.config.ts b/vite.config.ts
index f582596..97979a9 100644
--- a/vite.config.ts
+++ b/vite.config.ts
@@ -30,21 +30,21 @@ export default defineConfig(async () => {
         },
       },
     },
-  server: {
-    port: 1420,
-    strictPort: true,
-    host: host || false,
-    hmr: host
-      ? {
-          protocol: "ws",
-          host,
-          port: 1421,
-        }
-      : undefined,
-    watch: {
-      ignored: ["**/src-tauri/**"],
+    server: {
+      port: 1420,
+      strictPort: true,
+      host: host || false,
+      hmr: host
+        ? {
+            protocol: "ws",
+            host,
+            port: 1421,
+          }
+        : undefined,
+      watch: {
+        ignored: ["**/src-tauri/**"],
+      },
     },
-  },
     // Production build preview — not Vite’s default 4173 (avoids clashes e.g. with other Vite apps / tooling); adjacent to dev :1420.
     preview: {
       port: 1422,
@@ -52,6 +52,7 @@ export default defineConfig(async () => {
       // Required when nginx (or any reverse proxy) sends Host: pengine.net — Vite 7 blocks unknown hosts by default.
       allowedHosts: [
         "pengine.net",
+        "penguinpool.space",
         "localhost",
         "127.0.0.1",
         ...(process.env.VITE_PREVIEW_ALLOWED_HOSTS?.split(",")

From 071e225392204b038e1eb1036c57e97fc1968352 Mon Sep 17 00:00:00 2001
From: MaximEdogawa <leo@librem.one>
Date: Mon, 20 Apr 2026 11:50:03 +0200
Subject: [PATCH 2/2] update: remove 'penguinpool.space' from allowed hosts in
 Vite configuration

---
 vite.config.ts | 1 -
 1 file changed, 1 deletion(-)

diff --git a/vite.config.ts b/vite.config.ts
index 97979a9..17907ae 100644
--- a/vite.config.ts
+++ b/vite.config.ts
@@ -52,7 +52,6 @@ export default defineConfig(async () => {
       // Required when nginx (or any reverse proxy) sends Host: pengine.net — Vite 7 blocks unknown hosts by default.
       allowedHosts: [
         "pengine.net",
-        "penguinpool.space",
         "localhost",
         "127.0.0.1",
         ...(process.env.VITE_PREVIEW_ALLOWED_HOSTS?.split(",")