2c27fc65d0
The Docker-based CI/CD approach is the industry standard but requires: - Proper container registry (GHCR, Docker Hub) with HTTPS - Or complex local registry setup with containerd HTTP configuration The init container approach works reliably for now. To enable auto-deploy: 1. Flux detects git changes in 30s (via webhook) 2. Kustomization applies new config 3. Manually run: kubectl rollout restart deployment/storefront -n manoonoils For true auto-deploy, consider: - Setting up GHCR with proper auth - Using GitHub Actions to build/push images - Using Flux ImageUpdateAutomation Or simpler: A post-deploy webhook that triggers rollout restart.
This is a Next.js project bootstrapped with create-next-app.
Getting Started
First, run the development server:
npm run dev
# or
yarn dev
# or
pnpm dev
# or
bun dev
Open http://localhost:3000 with your browser to see the result.
You can start editing the page by modifying app/page.tsx. The page auto-updates as you edit the file.
This project uses next/font to automatically optimize and load Geist, a new font family for Vercel.
Learn More
To learn more about Next.js, take a look at the following resources:
- Next.js Documentation - learn about Next.js features and API.
- Learn Next.js - an interactive Next.js tutorial.
You can check out the Next.js GitHub repository - your feedback and contributions are welcome!
Deploy on Vercel
The easiest way to deploy your Next.js app is to use the Vercel Platform from the creators of Next.js.
Check out our Next.js deployment documentation for more details.
CI/CD Test
// Flux auto-deploy test - Sat Mar 7 10:55:48 AM EET 2026 // Auto-deploy test: 2026-03-07T09:02:49Z