fix(infra): resolve local directus service matching, improve branding script flexibility, and cleanup build artifacts

This commit is contained in:
2026-02-16 18:07:56 +01:00
parent 7a63a418f1
commit 16597806bf
13 changed files with 29985 additions and 330 deletions

View File

@@ -96,20 +96,7 @@ export default async function LocaleLayout({
return (
<html lang={safeLocale} className={`scroll-smooth overflow-x-hidden ${inter.variable}`}>
<head>
<style
dangerouslySetInnerHTML={{
__html: `
::-webkit-scrollbar { width: 2px; height: 2px; }
::-webkit-scrollbar-track { background: transparent; }
::-webkit-scrollbar-thumb { background: transparent; border-radius: 10px; }
::-webkit-scrollbar-thumb:hover { background: rgba(130, 237, 32, 0.4); }
* { scrollbar-width: none; }
*:hover { scrollbar-width: thin; scrollbar-color: rgba(130, 237, 32, 0.2) transparent; }
`,
}}
/>
</head>
<head></head>
<body className="flex flex-col min-h-screen font-sans selection:bg-accent selection:text-primary-dark antialiased overflow-x-hidden">
<NextIntlClientProvider messages={messages} locale={safeLocale}>
<RecordModeProvider isEnabled={recordModeEnabled}>

View File

@@ -1,85 +0,0 @@
> klz-cables-nextjs@1.0.0 build /Users/marcmintel/Projects/klz-2026
> next build
▲ Next.js 16.1.6 (Turbopack)
- Environments: .env.production, .env
- Experiments (use with caution):
· clientTraceMetadata
⚠ The "middleware" file convention is deprecated. Please use "proxy" instead. Learn more: https://nextjs.org/docs/messages/middleware-to-proxy
Creating an optimized production build ...
✓ Compiled successfully in 5.2s
Running next.config.js provided runAfterProductionCompile ...
✓ Completed runAfterProductionCompile in 329ms
Running TypeScript ...
Collecting page data using 15 workers ...
Generating static pages using 15 workers (0/21) ...
{"level":30,"time":1770803086126,"pid":70317,"hostname":"MacBook-Air-von-Marc-2.local","name":"server","msg":"Initializing server application services"}
[Layout] Static generation detected or headers unavailable, skipping server-side analytics context
[Layout] Static generation detected or headers unavailable, skipping server-side analytics context
[Layout] Static generation detected or headers unavailable, skipping server-side analytics context
[Layout] Static generation detected or headers unavailable, skipping server-side analytics context
[Layout] Static generation detected or headers unavailable, skipping server-side analytics context
[Layout] Static generation detected or headers unavailable, skipping server-side analytics context
{"level":30,"time":1770803086126,"pid":70317,"hostname":"MacBook-Air-von-Marc-2.local","name":"server","msg":"Service configuration"}
{"level":30,"time":1770803086126,"pid":70317,"hostname":"MacBook-Air-von-Marc-2.local","name":"server","msg":"Noop analytics service initialized (analytics disabled)"}
{"level":30,"time":1770803086126,"pid":70317,"hostname":"MacBook-Air-von-Marc-2.local","name":"server","msg":"Noop notification service initialized (notifications disabled)"}
{"level":30,"time":1770803086126,"pid":70317,"hostname":"MacBook-Air-von-Marc-2.local","name":"server","msg":"Noop error reporting service initialized (error reporting disabled)"}
{"level":30,"time":1770803086126,"pid":70317,"hostname":"MacBook-Air-von-Marc-2.local","name":"server","msg":"Memory cache service initialized"}
{"level":30,"time":1770803086126,"pid":70317,"hostname":"MacBook-Air-von-Marc-2.local","name":"server","msg":"Pino logger service initialized"}
{"level":30,"time":1770803086126,"pid":70317,"hostname":"MacBook-Air-von-Marc-2.local","name":"server","msg":"All application services initialized successfully"}
Generating static pages using 15 workers (5/21)
Generating static pages using 15 workers (10/21)
[Layout] Static generation detected or headers unavailable, skipping server-side analytics context
[Layout] Static generation detected or headers unavailable, skipping server-side analytics context
[Layout] Static generation detected or headers unavailable, skipping server-side analytics context
[Layout] Static generation detected or headers unavailable, skipping server-side analytics context
[Layout] Static generation detected or headers unavailable, skipping server-side analytics context
{"level":30,"time":1770803086317,"pid":70317,"hostname":"MacBook-Air-von-Marc-2.local","name":"server","msg":"Initializing server application services"}
[Layout] Static generation detected or headers unavailable, skipping server-side analytics context
{"level":30,"time":1770803086317,"pid":70317,"hostname":"MacBook-Air-von-Marc-2.local","name":"server","msg":"Service configuration"}
{"level":30,"time":1770803086317,"pid":70317,"hostname":"MacBook-Air-von-Marc-2.local","name":"server","msg":"Noop analytics service initialized (analytics disabled)"}
{"level":30,"time":1770803086317,"pid":70317,"hostname":"MacBook-Air-von-Marc-2.local","name":"server","msg":"Notification service initialized (noop)"}
{"level":30,"time":1770803086317,"pid":70317,"hostname":"MacBook-Air-von-Marc-2.local","name":"server","msg":"Noop error reporting service initialized (error reporting disabled)"}
{"level":30,"time":1770803086317,"pid":70317,"hostname":"MacBook-Air-von-Marc-2.local","name":"server","msg":"Memory cache service initialized"}
{"level":30,"time":1770803086317,"pid":70317,"hostname":"MacBook-Air-von-Marc-2.local","name":"server","msg":"Pino logger service initialized"}
{"level":30,"time":1770803086317,"pid":70317,"hostname":"MacBook-Air-von-Marc-2.local","name":"server","msg":"All application services initialized successfully"}
Generating static pages using 15 workers (15/21)
✓ Generating static pages using 15 workers (21/21) in 512.4ms
Finalizing page optimization ...
Route (app)
┌ ○ /_not-found
├ ƒ /[locale]
├ ƒ /[locale]/[slug]
├ ƒ /[locale]/[slug]/opengraph-image
├ ƒ /[locale]/api/og/product
├ ƒ /[locale]/blog
├ ƒ /[locale]/blog/[slug]
├ ƒ /[locale]/blog/[slug]/opengraph-image
├ ƒ /[locale]/blog/opengraph-image
├ ƒ /[locale]/contact
├ ƒ /[locale]/contact/opengraph-image
├ ƒ /[locale]/opengraph-image
├ ƒ /[locale]/products
├ ƒ /[locale]/products/[...slug]
├ ƒ /[locale]/products/opengraph-image
├ ƒ /[locale]/team
├ ƒ /[locale]/team/opengraph-image
├ ƒ /api/feedback
├ ƒ /api/health/cms
├ ƒ /api/whoami
├ ƒ /errors/api/relay
├ ƒ /health
├ ○ /manifest.webmanifest
├ ○ /robots.txt
├ ƒ /sitemap.xml
└ ƒ /stats/api/send
ƒ Proxy (Middleware)
○ (Static) prerendered as static content
ƒ (Dynamic) server-rendered on demand

View File

@@ -46,22 +46,10 @@ export default function Header() {
return segments.join('/');
};
const [productsSlug, setProductsSlug] = useState('products');
useEffect(() => {
// We can't use mapFileSlugToTranslated directly in client components easily without an API or similar
// For now, let's just check the locale
if (currentLocale === 'de') {
setProductsSlug('produkte');
} else {
setProductsSlug('products');
}
}, [currentLocale]);
const menuItems = [
{ label: t('home'), href: '/' },
{ label: t('team'), href: '/team' },
{ label: t('products'), href: `/${productsSlug}` },
{ label: t('products'), href: currentLocale === 'de' ? '/produkte' : '/products' },
{ label: t('blog'), href: '/blog' },
];

File diff suppressed because it is too large Load Diff

View File

@@ -36,9 +36,10 @@ services:
- "traefik.http.routers.${PROJECT_NAME:-klz-cables}-public.middlewares=${AUTH_MIDDLEWARE_UNPROTECTED:-${PROJECT_NAME:-klz-cables}-ratelimit,${PROJECT_NAME:-klz-cables}-forward,${PROJECT_NAME:-klz-cables}-compress}"
- "traefik.http.routers.${PROJECT_NAME:-klz-cables}-public.priority=2000"
- "traefik.http.services.${PROJECT_NAME:-klz-cables}.loadbalancer.server.port=3000"
- "traefik.http.services.${PROJECT_NAME:-klz-cables}.loadbalancer.server.scheme=http"
- "traefik.docker.network=infra"
- "caddy=http://${TRAEFIK_HOST:-klz.localhost}"
- "caddy.reverse_proxy={{upstreams 3000}}"
# Middleware Definitions
- "traefik.http.middlewares.${PROJECT_NAME:-klz-cables}-compress.compress=true"
@@ -130,6 +131,8 @@ services:
- "traefik.http.routers.klz-production-cms.service=klz-production-cms-svc"
- "traefik.http.services.klz-production-cms-svc.loadbalancer.server.port=8055"
- "traefik.docker.network=infra"
- "caddy=http://${DIRECTUS_HOST:-cms.klz.localhost}"
- "caddy.reverse_proxy={{upstreams 8055}}"
klz-db:
image: postgres:15-alpine
restart: unless-stopped

View File

@@ -1,11 +0,0 @@
> klz-cables-nextjs@1.0.0 lint /Users/marcmintel/Projects/klz-2026
> eslint .
/Users/marcmintel/Projects/klz-2026/components/home/GallerySection.tsx
3:17 warning 'useState' is defined but never used @typescript-eslint/no-unused-vars
3:27 warning 'useEffect' is defined but never used @typescript-eslint/no-unused-vars
✖ 2 problems (0 errors, 2 warnings)

View File

@@ -1,132 +0,0 @@
> klz-cables-nextjs@1.0.0 lint /Users/marcmintel/Projects/klz-2026
> eslint .
(node:66439) ESLintEnvWarning: /* eslint-env */ comments are no longer recognized when linting with flat config and will be reported as errors as of v10.0.0. Replace them with /* global */ comments or define globals in your config file. See https://eslint.org/docs/latest/use/configure/migration-guide#eslint-env-configuration-comments for details. Found in /Users/marcmintel/Projects/klz-2026/.lintstagedrc.cjs at line 2.
(Use `node --trace-warnings ...` to show where the warning was created)
(node:66439) ESLintEnvWarning: /* eslint-env */ comments are no longer recognized when linting with flat config and will be reported as errors as of v10.0.0. Replace them with /* global */ comments or define globals in your config file. See https://eslint.org/docs/latest/use/configure/migration-guide#eslint-env-configuration-comments for details. Found in /Users/marcmintel/Projects/klz-2026/commitlint.config.cjs at line 2.
(node:66439) ESLintEnvWarning: /* eslint-env */ comments are no longer recognized when linting with flat config and will be reported as errors as of v10.0.0. Replace them with /* global */ comments or define globals in your config file. See https://eslint.org/docs/latest/use/configure/migration-guide#eslint-env-configuration-comments for details. Found in /Users/marcmintel/Projects/klz-2026/postcss.config.cjs at line 2.
(node:66439) ESLintEnvWarning: /* eslint-env */ comments are no longer recognized when linting with flat config and will be reported as errors as of v10.0.0. Replace them with /* global */ comments or define globals in your config file. See https://eslint.org/docs/latest/use/configure/migration-guide#eslint-env-configuration-comments for details. Found in /Users/marcmintel/Projects/klz-2026/tailwind.config.cjs at line 2.
/Users/marcmintel/Projects/klz-2026/.lintstagedrc.cjs
3:14 error A `require()` style import is forbidden @typescript-eslint/no-require-imports
/Users/marcmintel/Projects/klz-2026/app/[locale]/blog/[slug]/page.tsx
2:8 warning 'Script' is defined but never used @typescript-eslint/no-unused-vars
4:10 warning 'getBreadcrumbSchema' is defined but never used @typescript-eslint/no-unused-vars
4:41 warning 'LOGO_URL' is defined but never used @typescript-eslint/no-unused-vars
/Users/marcmintel/Projects/klz-2026/app/[locale]/blog/page.tsx
63:15 warning Using `<img>` could result in slower LCP and higher bandwidth. Consider using `<Image />` from `next/image` or a custom image loader to automatically optimize images. This may incur additional usage or cost from your provider. See: https://nextjs.org/docs/messages/no-img-element @next/next/no-img-element
148:25 warning Using `<img>` could result in slower LCP and higher bandwidth. Consider using `<Image />` from `next/image` or a custom image loader to automatically optimize images. This may incur additional usage or cost from your provider. See: https://nextjs.org/docs/messages/no-img-element @next/next/no-img-element
/Users/marcmintel/Projects/klz-2026/app/[locale]/layout.tsx
81:12 warning 'e' is defined but never used @typescript-eslint/no-unused-vars
/Users/marcmintel/Projects/klz-2026/app/[locale]/page.tsx
70:12 warning 'err' is defined but never used @typescript-eslint/no-unused-vars
74:14 warning 'e' is defined but never used @typescript-eslint/no-unused-vars
75:12 warning 'key' is defined but never used. Allowed unused args must match /^_/u @typescript-eslint/no-unused-vars
/Users/marcmintel/Projects/klz-2026/app/[locale]/products/[...slug]/page.tsx
1:8 warning 'Script' is defined but never used @typescript-eslint/no-unused-vars
3:10 warning 'getBreadcrumbSchema' is defined but never used @typescript-eslint/no-unused-vars
/Users/marcmintel/Projects/klz-2026/app/errors/api/relay/route.ts
28:11 warning 'header' is assigned a value but never used @typescript-eslint/no-unused-vars
/Users/marcmintel/Projects/klz-2026/components/CMSConnectivityNotice.tsx
4:34 warning 'Database' is defined but never used @typescript-eslint/no-unused-vars
8:10 warning 'status' is assigned a value but never used @typescript-eslint/no-unused-vars
35:16 warning 'err' is defined but never used @typescript-eslint/no-unused-vars
/Users/marcmintel/Projects/klz-2026/components/Header.tsx
36:7 warning Error: Calling setState synchronously within an effect can trigger cascading renders
Effects are intended to synchronize state between React and external systems such as manually updating the DOM, state management libraries, or other platform APIs. In general, the body of an effect should do one or both of the following:
* Update external systems with the latest state from React.
* Subscribe for updates from some external system, calling setState in a callback function when external state changes.
Calling setState synchronously within an effect body causes cascading renders that can hurt performance, and is not recommended. (https://react.dev/learn/you-might-not-need-an-effect).
/Users/marcmintel/Projects/klz-2026/components/Header.tsx:36:7
34 | useEffect(() => {
35 | if (isMobileMenuOpen) {
> 36 | setIsMobileMenuOpen(false);
| ^^^^^^^^^^^^^^^^^^^ Avoid calling setState() directly within an effect
37 | }
38 | }, [pathname, isMobileMenuOpen]);
39 | react-hooks/set-state-in-effect
116:37 warning 'idx' is defined but never used. Allowed unused args must match /^_/u @typescript-eslint/no-unused-vars
/Users/marcmintel/Projects/klz-2026/components/Lightbox.tsx
24:5 warning Error: Calling setState synchronously within an effect can trigger cascading renders
Effects are intended to synchronize state between React and external systems such as manually updating the DOM, state management libraries, or other platform APIs. In general, the body of an effect should do one or both of the following:
* Update external systems with the latest state from React.
* Subscribe for updates from some external system, calling setState in a callback function when external state changes.
Calling setState synchronously within an effect body causes cascading renders that can hurt performance, and is not recommended. (https://react.dev/learn/you-might-not-need-an-effect).
/Users/marcmintel/Projects/klz-2026/components/Lightbox.tsx:24:5
22 |
23 | useEffect(() => {
> 24 | setMounted(true);
| ^^^^^^^^^^ Avoid calling setState() directly within an effect
25 | return () => setMounted(false);
26 | }, []);
27 | react-hooks/set-state-in-effect
62:9 warning Error: Calling setState synchronously within an effect can trigger cascading renders
Effects are intended to synchronize state between React and external systems such as manually updating the DOM, state management libraries, or other platform APIs. In general, the body of an effect should do one or both of the following:
* Update external systems with the latest state from React.
* Subscribe for updates from some external system, calling setState in a callback function when external state changes.
Calling setState synchronously within an effect body causes cascading renders that can hurt performance, and is not recommended. (https://react.dev/learn/you-might-not-need-an-effect).
/Users/marcmintel/Projects/klz-2026/components/Lightbox.tsx:62:9
60 | const index = parseInt(photoParam, 10);
61 | if (!isNaN(index) && index >= 0 && index < images.length) {
> 62 | setCurrentIndex(index);
| ^^^^^^^^^^^^^^^ Avoid calling setState() directly within an effect
63 | }
64 | }
65 | }, [searchParams, images.length]); react-hooks/set-state-in-effect
/Users/marcmintel/Projects/klz-2026/components/OGImageTemplate.tsx
49:11 warning Using `<img>` could result in slower LCP and higher bandwidth. Consider using `<Image />` from `next/image` or a custom image loader to automatically optimize images. This may incur additional usage or cost from your provider. See: https://nextjs.org/docs/messages/no-img-element @next/next/no-img-element
/Users/marcmintel/Projects/klz-2026/components/home/GallerySection.tsx
30:38 warning Error: Calling setState synchronously within an effect can trigger cascading renders
Effects are intended to synchronize state between React and external systems such as manually updating the DOM, state management libraries, or other platform APIs. In general, the body of an effect should do one or both of the following:
* Update external systems with the latest state from React.
* Subscribe for updates from some external system, calling setState in a callback function when external state changes.
Calling setState synchronously within an effect body causes cascading renders that can hurt performance, and is not recommended. (https://react.dev/learn/you-might-not-need-an-effect).
/Users/marcmintel/Projects/klz-2026/components/home/GallerySection.tsx:30:38
28 | const index = parseInt(photoParam, 10);
29 | if (!isNaN(index) && index >= 0 && index < images.length) {
> 30 | if (lightboxIndex !== index) setLightboxIndex(index);
| ^^^^^^^^^^^^^^^^ Avoid calling setState() directly within an effect
31 | if (!lightboxOpen) setLightboxOpen(true);
32 | }
33 | } react-hooks/set-state-in-effect
/Users/marcmintel/Projects/klz-2026/components/home/RecentPosts.tsx
37:21 warning Using `<img>` could result in slower LCP and higher bandwidth. Consider using `<Image />` from `next/image` or a custom image loader to automatically optimize images. This may incur additional usage or cost from your provider. See: https://nextjs.org/docs/messages/no-img-element @next/next/no-img-element
/Users/marcmintel/Projects/klz-2026/lib/config.ts
5:10 warning 'env' is defined but never used @typescript-eslint/no-unused-vars
/Users/marcmintel/Projects/klz-2026/lib/mail/mailer.ts
4:10 warning 'ReactElement' is defined but never used @typescript-eslint/no-unused-vars
/Users/marcmintel/Projects/klz-2026/middleware.ts
2:10 warning 'NextResponse' is defined but never used @typescript-eslint/no-unused-vars
33:12 warning 'publicHostname' is assigned a value but never used @typescript-eslint/no-unused-vars
✖ 27 problems (1 error, 26 warnings)
ELIFECYCLE Command failed with exit code 1.

View File

@@ -1,65 +0,0 @@
> klz-cables-nextjs@1.0.0 lint /Users/marcmintel/Projects/klz-2026
> eslint .
/Users/marcmintel/Projects/klz-2026/app/[locale]/layout.tsx
81:12 warning '_e' is defined but never used @typescript-eslint/no-unused-vars
/Users/marcmintel/Projects/klz-2026/app/[locale]/page.tsx
70:12 warning '_err' is defined but never used @typescript-eslint/no-unused-vars
74:14 warning '_e' is defined but never used @typescript-eslint/no-unused-vars
/Users/marcmintel/Projects/klz-2026/app/errors/api/relay/route.ts
28:11 warning '_header' is assigned a value but never used @typescript-eslint/no-unused-vars
/Users/marcmintel/Projects/klz-2026/components/CMSConnectivityNotice.tsx
8:10 warning '_status' is assigned a value but never used @typescript-eslint/no-unused-vars
35:16 warning '_err' is defined but never used @typescript-eslint/no-unused-vars
/Users/marcmintel/Projects/klz-2026/components/Lightbox.tsx
24:5 warning Error: Calling setState synchronously within an effect can trigger cascading renders
Effects are intended to synchronize state between React and external systems such as manually updating the DOM, state management libraries, or other platform APIs. In general, the body of an effect should do one or both of the following:
* Update external systems with the latest state from React.
* Subscribe for updates from some external system, calling setState in a callback function when external state changes.
Calling setState synchronously within an effect body causes cascading renders that can hurt performance, and is not recommended. (https://react.dev/learn/you-might-not-need-an-effect).
/Users/marcmintel/Projects/klz-2026/components/Lightbox.tsx:24:5
22 |
23 | useEffect(() => {
> 24 | setMounted(true);
| ^^^^^^^^^^ Avoid calling setState() directly within an effect
25 | return () => setMounted(false);
26 | }, []); // eslint-disable-line react-hooks/set-state-in-effect
27 | react-hooks/set-state-in-effect
26:11 warning Unused eslint-disable directive (no problems were reported from 'react-hooks/set-state-in-effect')
62:9 warning Error: Calling setState synchronously within an effect can trigger cascading renders
Effects are intended to synchronize state between React and external systems such as manually updating the DOM, state management libraries, or other platform APIs. In general, the body of an effect should do one or both of the following:
* Update external systems with the latest state from React.
* Subscribe for updates from some external system, calling setState in a callback function when external state changes.
Calling setState synchronously within an effect body causes cascading renders that can hurt performance, and is not recommended. (https://react.dev/learn/you-might-not-need-an-effect).
/Users/marcmintel/Projects/klz-2026/components/Lightbox.tsx:62:9
60 | const index = parseInt(photoParam, 10);
61 | if (!isNaN(index) && index >= 0 && index < images.length) {
> 62 | setCurrentIndex(index);
| ^^^^^^^^^^^^^^^ Avoid calling setState() directly within an effect
63 | }
64 | }
65 | }, [searchParams, images.length]); // eslint-disable-line react-hooks/set-state-in-effect react-hooks/set-state-in-effect
65:38 warning Unused eslint-disable directive (no problems were reported from 'react-hooks/set-state-in-effect')
/Users/marcmintel/Projects/klz-2026/components/home/GallerySection.tsx
3:17 warning 'useState' is defined but never used @typescript-eslint/no-unused-vars
3:27 warning 'useEffect' is defined but never used @typescript-eslint/no-unused-vars
/Users/marcmintel/Projects/klz-2026/middleware.ts
33:12 warning '_publicHostname' is assigned a value but never used @typescript-eslint/no-unused-vars
✖ 13 problems (0 errors, 13 warnings)
0 errors and 2 warnings potentially fixable with the `--fix` option.

View File

@@ -88,7 +88,7 @@
"test": "vitest run --passWithNoTests",
"test:og": "vitest run tests/og-image.test.ts",
"check:og": "tsx scripts/check-og-images.ts",
"cms:branding:local": "DIRECTUS_URL=http://localhost:8055 npx tsx --env-file=.env scripts/setup-directus-branding.ts",
"cms:branding:local": "DIRECTUS_URL=${DIRECTUS_URL:-http://cms.klz.localhost} npx tsx --env-file=.env scripts/setup-directus-branding.ts",
"cms:branding:testing": "DIRECTUS_URL=https://cms.testing.klz-cables.com npx tsx --env-file=.env scripts/setup-directus-branding.ts",
"cms:branding:staging": "DIRECTUS_URL=https://cms.staging.klz-cables.com npx tsx --env-file=.env scripts/setup-directus-branding.ts",
"cms:branding:prod": "DIRECTUS_URL=https://cms.klz-cables.com npx tsx --env-file=.env scripts/setup-directus-branding.ts",
@@ -127,4 +127,4 @@
"lucide-react": "^0.563.0",
"remotion": "^4.0.421"
}
}
}

View File

@@ -13,7 +13,7 @@ PRJ_ID=$(jq -r .name package.json | sed 's/@mintel\///' | sed 's/\.com$//' | sed
case $ENV in
local)
CONTAINER=$(docker compose ps -q directus)
CONTAINER=$(docker compose ps -q directus-cms)
if [ -z "$CONTAINER" ]; then
echo "❌ Local directus container not found."
exit 1

View File

File diff suppressed because one or more lines are too long

View File

@@ -1,4 +0,0 @@
> klz-cables-nextjs@1.0.0 typecheck /Users/marcmintel/Projects/klz-2026
> tsc --noEmit