Introduction to Cake20 Core

What is a Cake20 Core?

Cake20 Core is a full-stack website platform for creating and operating small websites. You can use Cake20 View, Cake20 UI, Tailwind CSS, API, Prisma and schedule tasks without having to install the framework on each website.

Administrators can edit sources, test, start, and check logs from one screen. Each website has its own independent folder, PostgreSQL database, and Bun process.

Cake20.js

Cake20.js is the official website programming model that brings together the Cake20 View screen system and Cake20 Runtime build, server and execution capabilities.

The official Cake20.js site presents its core ideas and examples for screens, state, APIs and data in one place.

Rule-driven development

• The file path in app/pages becomes the webpage URL.
• The file name of server/api determines the HTTP method and URL.
• Create a website-specific DB Client using the *.db.ts model of server/db.
• Website common functions and types are automatically imported from shared.
• HTTP, date and DB connections use Cake20 Runtime built-in functions.
• Since build and node_modules are managed by Cake20, you do not need to modify them directly.

Public guidance and search

Cake20 Web's privacy policy and terms of service can be viewed without logging in. You can check them in /privacy and /terms respectively.

The search engine includes public introductions, templates, subscription plans, development documents and laws. Only the www canonical URL of the page points to sitemap.xml. Log in, manage, Inspection, API and MCP routes are searched in robots.txt and response headers. Excluded.

A simpler Cake20 backend

The website backend uses Cake20 file-based APIs and server modules. It is based on method. Cake20 Runtime repeats setup and operation on top of it. By adding user-friendly rules that reduce code, even small websites can use the backend. It allows you to complete the infrastructure without assembling it yourself.

This is not simply a reduced backend, but rather allows website users to Common functions and operations to safely develop, inspect, and deploy with less code This is an upgrade that incorporates safety devices.

• The method and URL are determined only by the file name of the server/api, and the return value is automatically This will be an HTTP response.
• DB, authentication/session, queue, reservation task, WebSocket, file, email and payment Use as a basic runtime function without installation/connection code.
• DB models are written with TypeScript objects and z methods instead of complex creation settings. Prisma Client creation and connection is managed by Cake20.
• Input verification, test samples, website-specific permissions, and operation/inspection data isolation are the same. Its inclusion in the rules provides both simplicity and operational safety.
• Inspection and production builds select runtime modules used in the server source. Record in release. The execution process includes recorded DB, authentication, queue, Only Task, Mail, Excel and real-time communication modules are loaded.

Current Runtime Scope

• The website UI is client-rendered Vite SPA and does not provide SSR or prerender.
• Optional runtime modules are automatically determined in release builds and are not used. Modules, connections and workers do not start in the website process.
• Editor UI Preview is displayed as a separate sandbox Vite development server and HMR.
• Process coordination is based on a single manager host, and multi-host load balancing is configured in an external infrastructure.
• Custom Domain is created by Cloudflare for SaaS when the user connects the DNS. Manage TLS certificates.
• Login and Role access use package.json auth, exceptional Route Hooks use app/middleware, Jobs and Tasks use server/tasks, HTTP Hooks use server/hooks, and WebSocket and SSE use suffixes in server/routes.
• Toss, Stripe and PayPal single payments are processed with the Runtime payment function. Regular payments and billing keys are not currently included in the common interface.