Wenfeng Font Library App Platform Launches and Auto-Deployment Configuration Completed

Windfonts
1

WindFonts App Platform Deployment Completed

The WindFonts font CDN management platform has been successfully deployed to production. Site URL: app.windfonts.com

Technical Architecture

  • Frontend Framework: Next.js 16 (App Router, standalone mode)
  • UI: React 19 + Tailwind CSS 4 + shadcn/ui
  • Database: SQLite 3 + Drizzle ORM
  • Authentication: NextAuth.js 5
  • Font Storage: Alibaba Cloud OSS (Guangzhou region)
  • Containerization: Podman container deployment

Platform Features

  • Font CDN distribution with on-demand subsetting support
  • Font resource management (categorization, brand, tags, license types)
  • OSS font synchronization and batch management
  • Admin dashboard (font publishing/unpublishing, analytics & statistics)
  • CSS API—embed fonts with a single line of code

Automated Deployment

A Forgejo Webhook-triggered automated deployment pipeline is now configured:

  1. Developer pushes code to the main branch
  2. Forgejo triggers a webhook to notify the production server
  3. The server automatically pulls the latest code, builds a new container image, and replaces the running container
  4. Automatic health checks verify service availability, followed by cleanup of obsolete images

The entire process is fully automated—“push-to-deploy”—with full traceability of deployment logs.

Issues Resolved During Deployment

  • Container Network Connectivity: Adjusted firewall policies and DNS configurations to ensure network reachability during both container build and runtime
  • Database Initialization: Resolved compatibility issues with Drizzle ORM migration files
  • Dependency Synchronization: Fixed build failures caused by inconsistencies between lock files and dependency versions

Operations documentation has been archived; future iterations will be deployed automatically via Git pushes.

2

Progress Update

Login Page 404 Issue Resolved

Investigation confirmed this was a brief interruption during deployment rebuild—not a routing configuration issue. The /login route functions correctly inside the container (HTTP 200), and the nginx reverse-proxy configuration (location /) forwards all paths to port 4000 without omission.

Current status:

  • https://app.windfonts.com/login → HTTP 200 ✓
  • https://app.windfonts.com/ → HTTP 200 ✓

Webhook-Based Automatic Deployment Verified

A full deployment pipeline was successfully triggered by simulating a Forgejo webhook, confirming end-to-end functionality:

  1. Webhook Reception → Python receiver validates HMAC-SHA256 signature, matching repository Windfonts/fonts-vault and branch refs/heads/main.
  2. Build → git pull → podman build (Next.js 16 with Turbopack).
  3. Swap → Stop old container → Start new container → Health check passes within 15 seconds.
  4. Cleanup → Automatic podman image prune.

Deployment logs confirm: [ok] deploy success, health check passed.

Additionally, Forgejo git push credentials have been configured on the cravatar-prod server, enabling direct code pushes from the server going forward.

3

Login Functionality Fixed

Issue 1: Admin Dashboard Login Failure — Environment Variables Not Injected

The podman run command in the deployment script was missing the --env-file parameter, causing authentication-related environment variables (e.g., admin credentials, NextAuth secret) to be omitted from the container. As a result, the container used only the default values hardcoded in the Dockerfile, preventing the authentication module from functioning correctly.

Fix: Added the --env-file parameter to the deployment script. After rebuilding the container, login verification at the API layer succeeded.

Issue 2: Browser-Side Server Action Error

During login, the browser console displayed UnrecognizedActionError: Server Action was not found, and the POST request returned HTTP 404.

Root Cause: A bug exists in Next.js 16’s Turbopack standalone build — the node and edge fields in server-reference-manifest.json are empty objects, preventing Server Actions from being registered. We attempted building with --webpack, which generated a correct manifest, but runtime native modules were missing.

Final Resolution: Upstream has migrated the login logic from Server Actions to the NextAuth credentials provider, routing authentication through the API route (/api/auth/callback/credentials). This fully bypasses Turbopack’s Server Action registration issue. After rebuilding and redeploying, login functionality was restored.
A hard browser refresh confirmed successful login, and session cookies were correctly issued.

Additional Fix: Forgejo Git Service Timeout

During deployment, git pull timed out. Investigation revealed memory bloat in the Forgejo instance (exceeding 12 GB RAM / 5000+ threads), causing all HTTP requests to take over 3 seconds to respond. This was caused by high-frequency polling from Action Runners combined with aggressive crawler activity targeting large mirror repositories. Restarting the Forgejo container resolved the issue (memory usage dropped to ~140 MB), and git operations resumed normally.

Current Status

  • Login functionality at https://app.windfonts.com/login is working ✓
  • Automated deployment pipeline is operating normally ✓
  • Forgejo Git service has been restored ✓

Pending Follow-ups

  • Upgrade Forgejo from v11.0.3 → v11.0.10 (to address the root cause of memory leaks)
  • Integrate full-site Cloudflare acceleration