admin/metatron-open-seo
1
0
Fork 0
Code Issues Pull Requests Actions Packages Projects Releases Wiki Activity

vite.config.ts: actually read PORT/ALLOWED_HOST from env

Browse Source 
Both were documented self-host knobs (SELF_HOSTING_DOCKER.md, compose.yaml)
but hardcoded to port 3001 and seo.thedomainnest.com instead, so any second
instance on a different port/domain got either a port clash or Vite's
preview host-check ("Blocked request... not allowed"). Defaults preserve
exact current behavior for deployments that don't set these.

Co-Authored-By: Claude Sonnet 5 <noreply@anthropic.com>
This commit is contained in:
metatroncubeswdev 2026-10-17 19:49:21 -04:00
parent 324c9e064b
commit bed0504418
1 changed files with 8 additions and 2 deletions
Show Stats Download Patch File Download Diff File Expand all files Collapse all files

10
vite.config.ts
View File

@ -8,13 +8,19 @@ import { devtools } from "@tanstack/devtools-vite";
import { leanWorkerBundle } from "./vite-plugin-lean-worker-bundle";
export default defineConfig(() => {
const port = 3001;
// PORT/ALLOWED_HOST are documented self-host knobs (SELF_HOSTING_DOCKER.md,
// compose.yaml) but were never actually read here — every deployment was
// silently stuck on port 3001 and this one hardcoded domain, breaking any
// second instance on a different domain or port. Defaults keep existing
// deployments that don't set these working exactly as before.
const port = Number(process.env.PORT) || 3001;
const showDevtools = false;
const allowedHosts = [
"seo.thedomainnest.com",
];
process.env.ALLOWED_HOST,
].filter((host): host is string => Boolean(host));
return {
envPrefix: [