Martin Dvorak
3f52ab47c2
- Production now runs from ~/freezmo-prod/current (release symlink) as a standalone server on :3207; releases are exported by scripts/deploy.sh, built and e2e-verified on a temp port, switched atomically, health- checked via the new /api/healthz (commit + build time) and rolled back automatically on failure. Last 5 releases kept; scripts/rollback.sh for manual rollback. Shared env + data live in ~/freezmo-prod/shared/ and are symlinked into every release (existing sync/push data migrated and verified identical). - Dev runs from ~/freezmo via freezmo-dev.service: next dev on :3217 (LAN only), its own build folder (.next-dev via NEXT_DIST_DIR), its own data (~/freezmo/.freezmo-dev), DEV badge, dev favicon/theme colour, "Freezmo Dev" PWA identity and never the production service worker. - /api/healthz + the Settings Details version row (short commit + build time). output: standalone in next.config (next start still works). - AGENTS.md documents the workflow rules: only dev updates during a task, temporary dirs/ports for test builds, and deploy-at-the-end as the only production path. README gains an Environments and deploy section. - Fix found by the rehearsal: lib/dev-mode.ts must not be a client module (a server component importing a constant from a "use client" module gets a truthy proxy, which baked dev metadata into production builds). - SW -> freezmo-v34.
37 lines
1.2 KiB
TypeScript
37 lines
1.2 KiB
TypeScript
import type { NextConfig } from "next";
|
|
|
|
/**
|
|
* Freezmo is meant to be opened from a phone on the same network, so the dev
|
|
* server should accept dev-asset requests coming from private hostnames.
|
|
* Production builds are not affected by this option.
|
|
*
|
|
* Add your own hostname here if Next still warns about a cross-origin request.
|
|
*/
|
|
const nextConfig: NextConfig = {
|
|
/**
|
|
* Dev and production never share a build folder: the dev service runs with
|
|
* NEXT_DIST_DIR=.next-dev (see deploy/freezmo-dev.service), while a manual
|
|
* `npm run build` keeps producing .next for the test suites. A production
|
|
* build can therefore never clobber the running dev server, and the other
|
|
* way around.
|
|
*/
|
|
distDir: process.env.NEXT_DIST_DIR || ".next",
|
|
/**
|
|
* Releases ship as self-contained standalone output: scripts/deploy.sh
|
|
* copies public/ and .next/static next to `.next/standalone/server.js` and
|
|
* runs that. `next start` keeps working too, so the existing workflows and
|
|
* the e2e suites are unaffected.
|
|
*/
|
|
output: "standalone",
|
|
allowedDevOrigins: [
|
|
"127.0.0.1",
|
|
"localhost",
|
|
"*.local",
|
|
"**.local",
|
|
"192.168.*.*",
|
|
"10.*.*.*",
|
|
"*.ts.net", // Tailscale
|
|
],
|
|
};
|
|
|
|
export default nextConfig;
|