Serve from custom domain openportal.cc at root

Build with default base / instead of the /openportal/ sub-path so
assets resolve at the custom domain root (was the source of the 404s).
Pin the domain with public/CNAME so it persists across Actions deploys,
and point README references at openportal.cc. Old project URLs keep
working via GitHub's automatic 301 redirect, so existing badges survive.

Author: andronedev

.github/workflows/deploy.yml

@@ -34,10 +34,8 @@ jobs:
 
       - run: pnpm lint
 
-      # Base path must match the repository name for project Pages sites.
+      # Served from the custom domain root (openportal.cc), so build with base "/".
       - run: pnpm build
-        env:
-          VITE_BASE: /${{ github.event.repository.name }}/
 
       # SPA fallback so deep links resolve to index.html.
       - run: cp dist/index.html dist/404.html

CLAUDE.md

@@ -64,4 +64,4 @@ Installable, offline app shell. The service worker (`public/sw.js`) is a **hand-
 
 ## Deploy
 
-`pnpm build` → static `dist/`. For a GitHub Pages **project** site, set `VITE_BASE=/<repo-name>/` (CI does this automatically) so asset paths resolve under the sub-path; CI also copies `index.html` → `404.html` for SPA deep-link fallback. For a custom domain / root deploy, the default base `/` is correct.
+`pnpm build` → static `dist/`. The site is served at the **custom domain `openportal.cc`** (root), so CI builds with the default base `/`; `public/CNAME` pins the domain across Actions deploys, and CI copies `index.html` → `404.html` for SPA deep-link fallback. GitHub Pages 301-redirects the old project URL `andronedev.github.io/openportal/*` to `openportal.cc/*` with the path preserved, so existing badge embeds keep working. To deploy a fork under a sub-path instead, set `VITE_BASE=/<repo-name>/`.

README.md

@@ -6,7 +6,7 @@ Your Meta Portal doesn't have to end up in a drawer. OpenPortal gives it a secon
 
 OpenPortal talks to your Portal over USB using [WebUSB](https://developer.mozilla.org/en-US/docs/Web/API/WebUSB_API) and [ya-webadb](https://github.com/yume-chan/ya-webadb) to speak the ADB protocol straight from a web page.
 
-**[Open the app](https://andronedev.github.io/openportal/)** in a Chromium-based browser, no install required.
+**[Open the app](https://openportal.cc/)** in a Chromium-based browser, no install required.
 
 <!-- Screenshot: drop an image at docs/screenshot.png and uncomment the line below -->
 <!-- ![OpenPortal](docs/screenshot.png) -->
@@ -72,14 +72,14 @@ Built an app that's in the catalog? Link straight to it from your own README or
 Paste this into your README and replace `YOUR.PACKAGE.NAME` with your app's Android package name (the same `packageName` as in its catalog entry):
 
 ```md
-[![Get it on OpenPortal](https://andronedev.github.io/openportal/openportal-badge.svg)](https://andronedev.github.io/openportal/apps/YOUR.PACKAGE.NAME)
+[![Get it on OpenPortal](https://openportal.cc/openportal-badge.svg)](https://openportal.cc/apps/YOUR.PACKAGE.NAME)
 ```
 
 For example, Portal Calendar (`com.portal.calendar`) renders as:
 
-[![Get it on OpenPortal](https://andronedev.github.io/openportal/openportal-badge.svg)](https://andronedev.github.io/openportal/apps/com.portal.calendar)
+[![Get it on OpenPortal](https://openportal.cc/openportal-badge.svg)](https://openportal.cc/apps/com.portal.calendar)
 
-Just want the plain link? It's `https://andronedev.github.io/openportal/apps/YOUR.PACKAGE.NAME` — you can also grab it straight from the app's detail dialog with the **Copy link** button.
+Just want the plain link? It's `https://openportal.cc/apps/YOUR.PACKAGE.NAME` — you can also grab it straight from the app's detail dialog with the **Copy link** button.
 
 ## Contributing
 

public/CNAME

@@ -0,0 +1 @@
+openportal.cc