serfaandClaude Opus 5
1808ad4cba
The showcase was a Barcelona market: Catalan names, +34 numbers, euro rates and "Carrer Example 12" on every job. Presented to a Mexican client, all of that reads as somebody else's product. City comes from NEXT_PUBLIC_CITY_* as before, now Ciudad de México at 19.4326/-99.1332, with MAPBOX_COUNTRY=mx. The seed's fallbacks were Barcelona literals, so an unset env quietly seeded a different city than the app rendered — they now agree. Two db tests pinned the Barcelona centre as a hardcoded constant, which is why the deck returned zero cards on the first run here: every pro was a continent outside the radius. They read the same env as the seed now, so the trap cannot recur. Money: formatCents defaults to USD/en-US, and the nine hardcoded euro signs across the card, search rows, quote strip and forms are dollars. The rate NUMBERS are unchanged and still read high for CDMX — that is a pricing decision, not a currency one, and is left alone deliberately. Seed people are Mexican, addressed on real Roma/Condesa streets rotated by index rather than one placeholder repeated. Phones moved to +52 55, which moves the demo login to +525500000000 / 000000. Also in here, from the same session: - Sending a job now confirms. The mutation always succeeded; the sheet just closed with no receipt, which from the customer's side is indistinguishable from a dead button. Dismissing that receipt resolves as 'sent', so the card does not return to the deck. - Media moves to DigitalOcean Spaces, with the public origin derived from bucket and region instead of a second env var to keep in sync. - Managed-Postgres TLS: DATABASE_CA_CERT takes a path or inline PEM. - The client-facing project panel beside the running app. - Two profiles removed and four renamed to match their photos. Co-Authored-By: Claude Opus 5 (1M context) <noreply@anthropic.com>
48 lines
1.9 KiB
TypeScript
48 lines
1.9 KiB
TypeScript
import { config as loadEnv } from 'dotenv';
|
|
import { withSentryConfig } from '@sentry/nextjs';
|
|
import type { NextConfig } from 'next';
|
|
|
|
// The monorepo keeps one .env at the root; Next only looks in the app directory.
|
|
loadEnv({ path: '../../.env' });
|
|
|
|
const config: NextConfig = {
|
|
reactStrictMode: true,
|
|
// The workspace packages ship TypeScript source, not build output.
|
|
transpilePackages: ['@linkdr/api', '@linkdr/db', '@linkdr/shared', '@linkdr/storage'],
|
|
images: {
|
|
remotePatterns: [
|
|
// Seed data only — real pros upload to R2. The deck renders a plain <img>,
|
|
// so these matter only where next/image is used.
|
|
{ protocol: 'https', hostname: 'i.pravatar.cc' },
|
|
{ protocol: 'https', hostname: 'picsum.photos' },
|
|
{ protocol: 'https', hostname: '**.r2.dev' },
|
|
],
|
|
},
|
|
// postgres-js opens raw sockets; it must not be bundled into the server chunk.
|
|
serverExternalPackages: ['postgres'],
|
|
};
|
|
|
|
/**
|
|
* Bugsink speaks the Sentry protocol, so the Sentry build plugin applies — but
|
|
* only the parts that make sense for a self-hosted error tracker.
|
|
*
|
|
* Source maps are uploaded so a minified production stack is readable, and then
|
|
* deleted from the build output so they are not served publicly. Everything
|
|
* tracing-related stays off: Bugsink does not ingest it.
|
|
*/
|
|
export default withSentryConfig(config, {
|
|
// Bugsink has no organisation/project slugs in the Sentry sense; the DSN
|
|
// carries the project. These are only used by the upload step, which is
|
|
// skipped entirely without an auth token.
|
|
silent: true,
|
|
disableLogger: true,
|
|
sourcemaps: {
|
|
deleteSourcemapsAfterUpload: true,
|
|
},
|
|
// Do NOT route events through a Next rewrite: the tunnel exists to dodge ad
|
|
// blockers against sentry.io, and this DSN is our own host already.
|
|
tunnelRoute: undefined,
|
|
// The SDK's automatic Vercel Cron instrumentation has nothing to talk to here.
|
|
automaticVercelMonitors: false,
|
|
});
|