# This service runs on Turn Zero Cloud The service in this folder is hosted on Turn Zero Cloud. It started from the platform's `notes-app` template: a Node.js service with a web page, sign-in for its users, and each user's own rows in the platform's database. This file describes the template the service started from: keep it current as the service changes. ## Where you build - The page: `client/`, plain HTML, CSS, and script, which the platform serves at the application's address. - The routes: `src/server.mjs`. The service started with routes under `/api/` that each read the signed-in user, and keep, list, and delete that user's own rows. - The tables: `migrations/`, one file for each change, applied in order at each start. ## Where the rules are Turn Zero Cloud serves its rules to a coding tool through the MCP server `turnzero`, one connection to the products your account holds. The rules change with the platform, so none is repeated here. - Where the server is not connected, set up Turn Zero Cloud first: https://turnzero.ai/cloud/getting-started/set-up/ - Before you change or deploy this service, read the server's `deploy` skill, and before you change its sign-in, the server's `add-sign-in` skill. ## What you run here - The tests: `npm test`, in this folder. - A local run and a deploy: the `deploy` skill gives each step and the line to run, in this order: `tzcloud_submit_manifest`, the local run, `tzcloud_deploy_command`. - Sign-in on a local run: start it with `--sign-in` and the application's own hostname, then open the address its port line names; the command sends the sign-in routes to that hostname. Without `--sign-in`, the page a local run serves has no sign-in routes, sign-in is on the deployed application's own address, and a local run's API routes take a session as a Bearer.