misaki-studio-backend is the Node.js, Express, and Postgres shell intended to run backend output for a project with a database/ folder.
Current public status: not ready for production use. The public repository's current README states that its SQL action engine is not built. The service can boot, migrate its shell tables, handle session scaffolding, and answer health/auth routes, but real action reads or writes throw instead of producing an incomplete or misleading result.
Do not connect a production application or real user data to this public version.
The frontend export describes Components, Pages, styles, assets, and client access to data. A project that requests backend output also needs a server shell that owns:
Postgres connection and migrations;
session creation, lookup, expiry, and sign-out;
password verification rules;
request validation and absolute row limits;
compiled views/actions and access enforcement;
HTTP routes for authentication, views, and actions.
The generated database tree describes the project. The shell enforces what that description is allowed to do.
The public repository requires Node.js 20 or newer and a Postgres database.
git clone https://github.com/Misaki-Studio/misaki-studio-backend.git
cd misaki-studio-backend
npm install
cp .env.example .env
Set DATABASE_URL in .env. The example also exposes PORT and SESSION_TTL_HOURS.
npm run dev
The documented default is http://localhost:4000. With no generated project database yet, /health is the meaningful smoke test. Passing that check does not prove project views or actions work.
An export target can carry both halves. For example:
REACT SRC PATH → <website-or-hosting-clone>/src
ASSET PATH → <website-or-hosting-clone>/public
NODEJS SRC PATH → <backend-clone>/src
Leaving NODEJS SRC PATH empty means no backend is generated. For a local-folder target, every configured directory must already exist.
The generated backend content lives under src/database/ and is overwritten on export. Shell code outside that generated boundary should remain owned by the backend repository.
Coverage: Partial MCP. Desktop required for local-folder export.
An agent can inspect whether a project has database files, configure the three export paths, run the whole-project export, and review the resulting generated tree. That does not make the incomplete public backend safe to deploy.
Inspect my project for database tables, views, actions, and auth dependencies. Inspect the backend boilerplate's current README and source. Report whether its public engine can execute every generated operation this project needs. Do not configure a path, export, migrate, connect to Postgres, or start the service.
After the public backend is completed and synchronized, a runtime verification must cover migrations, seed behavior, public/private views, parameter binding, sort/slice limits, every write kind, session/auth behavior, refusal cases, and parity with the editor evaluator before this page can be approved.
The public shell documents these route families:
GET /health
POST /auth/sign-in
POST /auth/sign-out
GET /views/:name
POST /actions/:name
Do not interpret route presence as feature readiness. The current public README explicitly says real action execution is unfinished.
The Cloudflare and Vercel static boilerplates do not host this backend. Their repositories describe database hosting as a future phase.