Website Management and Repair

Website List

• Websites owned by the current account, favorited websites, and the rest Displayed in website order.
• The same priority will show recently created websites first.
• In the administrator list, emails from your own site are colored in blue, and emails from other users are displayed in blue. Favorite site emails are identified with a fluorescent orange marker.

Resource Monitoring

Administrators and subscribers can use the top Monitoring menu to inspect every website they may access, including runtime state, visitors in the last 10 minutes, files, DB, Redis, memory, and CPU usage.

• Displays total/execution/error/limit exceeded summary, recent users and accumulated storage space.
• DB usage includes data, indexes, TOAST of public user tables, and Materialized View·Sequences only are summed. PostgreSQL default capacity and Excludes Cake20 internal schema and has a minimum value of 0.
• RAM and Swap usage is within the site systemd scope, including Bun and sandbox. Calculate the total separately. Swap the same amount as the plan RAM only when necessary. A larger memory plan is recommended for continuous swap use.
• Search by name, ID, domain, and owner, and filter out execution status and caution items.
• IP and browser combination that sent HTTP/HTTPS requests in the last 10 minutes It is anonymized and counted as a unique visitor to each website.
• The running website also displays uptime, cumulative requests, API, Task, Queue and WebSocket status.
• In the Database submenu of the Website Settings drop-down menu, you can view the information about the currently operating website. Open Database, Cache Memory, and Storage each in a new tab. Owners and administrators can use PostgreSQL and Redis regardless of the website running status. You may modify or delete operational data, including user files.
• The editor and management screen show the same shared DB and Redis data. In-memory Redis in local data mode is not available from the management screen.
• Even if there are many websites, we use limited concurrent collection and 15-second snapshots to avoid overloading all at once.
• The manager can check the server CPU, RAM, SSD, and NET usage, remaining resources, and after starting the manager. Check the minimum and maximum at the top. Only system information is updated every 3 seconds, Total Site Visitors uses the existing 15-second measurement.

Go to ZIP Source

• ZIP export and import only moves the editable source of your website.
• DB data, Secret, uploaded files, tsconfig.json, Does not include server/db/migrations and build artifacts.
• It includes visible source files such as package.json and app/index.html. Environment-specific and generated files are prepared by the engine.
• The file name is in the format YYYYMMDD-HHmmss-{Website ID}.zip. Use the timezone from package.json.
• version.json in the ZIP root contains the ZIP format, the exported Runtime, and finally the full Record the inspection runtime and export time.
• Import package.json, app, public, and server as sources, and version.json After checking compatibility, we will not copy it to your website files.
• The top level of the ZIP is the source structure, or the same source within one top level folder. If there is a structure, get it. ZIPs that contain multiple top-level folders or a mixture of both structures It won't be imported.
• A ZIP created on a Runtime that does not have version.json or is older or newer than the current one, ZIPs that do not have a fully inspected version will be imported after verification.
• package.json remains the imported source of public settings and dependencies.
• The DB schema of the imported website is newly created in server/db/*.db.ts.
• If you need DB data, use the backup and restore function separately from ZIP.

External state monitoring

The operator must check the authenticated status URL on the Manager and other devices every minute. You can configure it. To detect even when the entire Manager device is stopped: It must be run on a separate host.

• Manager DB·Redis connection, check the target website response and disk space.
• If the most recent regular recovery training has failed or is longer than the set maximum period, it is judged as abnormal.
• Next run of full browser E2E scheduled in admin settings and latest results If it fails, the external condition is also judged as abnormal.
• Send a failure notification once when the number of consecutive failures is exceeded and send a recovery notification when normalization occurs.
• It supports Slack, Discord, and general JSON webhooks, and tokens and webhook addresses are not disclosed.

Integrated activity record

View activity records and logs in the Activity History pop-up in the Website Settings drop-down menu. Switch tabs. Activity records include editor, data, settings, and management screens. Traces of access through MCP are displayed in the most recent order, including success, time, and request. It shows the route, HTTP status and processing time together.

• Save it as YYYYMMDD-HHmmss.log in the logs folder for each website and save it as YYYYMMDD-HHmmss.log. If the file size in the settings is exceeded, a new log file is created.
• In the log view tab, you can check log files by date, size, and scheduled deletion date. Download the original log using the save icon.
• DB/Redis changes record the operator, target, task type, primary key/column/key, and number of processes.
• Logs that have exceeded the retention period are automatically deleted, and the latest files currently being recorded remain.
• The MCP change tool provides secure information such as tool name, file path, table, and processing number. Only target information is additionally logged, and failed requests are left for diagnostic purposes.
• The MCP URL's access key is masked as /mcp/[token], and the request body and authentication information are not recorded.
• Git stores source changes and start times, and activity records complement usage traces that do not remain in Git, such as views, failures, settings, and MCP.

Website deletion and recovery

In Stopped websites, select Delete website and enter 1 to 4 once. Enter the confirmation number to permanently delete the website folder and its shared PostgreSQL database.

• If you turn on site deletion protection in Advanced Settings, you will see a protection icon in the list and Blocks all delete menus, server deletion requests, and automatic deletion.
• If the editor is active in another window, it will instruct you to close the window without deleting it.
• If there is no active editor, the file will be deleted after terminating all file testing, preview, and operation/review processes.
• Deletion removes the web-{12 digits} folder, including build/debug and build/release.
• Deletion drops the website's single web-{12 digits} database.
• Only websites for which both the source ZIP and production DB dump were created in the midnight automatic backup. Site recovery in the account menu displays for the most recent month.
• For recovery, use the latest ZIP and dump and keep the same limit on the number of website creations. Apply. If the latest file restoration fails, the previous backup is automatically restored. Please retry. Websites created that day and deleted before the first midnight backup cannot be recovered.
• One month after deletion, external backup files and recovery list are completely deleted.
• If an error occurs during deletion, it will be left in the hidden path and retried in the next cleanup cycle.
• Matters subject to policy violations, legal retention obligations, or security incident investigations may be retained longer through a separate process while access is blocked.

Security Incident Response

• If there are signs of an attack, first stop the website and check the time and path in the activity history and execution log.
• We reissue secrets and AI coding addresses that may be exposed, and strengthen authentication and request restrictions.
• If necessary, secure ZIP, Git source history, and DB backup and restore to a safe version.
• Blocking based on the website usage policy can be lifted after removing vulnerabilities and malicious content and confirming measures to prevent recurrence.