Agent Deployment Prompt

Use this prompt with a terminal Agent that can inspect the project and run commands on the service machine. It follows the same security boundary as the recommended quick start.

The prompt is the execution entrypoint. It links to Moon-hosted technical backup and Token flows, so Agent documentation remains available when GitHub is unreachable.

Safe deployment prompt

Treat this prompt as the complete execution entrypoint for publishing the HTTP service in my current workspace as a public Printf HTTPS URL. Do not install or download an Agent Skill and do not clone the printf-client-releases repository. Read the Moon-hosted technical backup at https://moon.lprintf.com/docs/backup/printf-client-release/docs/getting-started.md, https://moon.lprintf.com/docs/backup/printf-client-release/docs/configuration.md, https://moon.lprintf.com/docs/backup/printf-client-release/docs/api/panel-api-experimental.md, https://moon.lprintf.com/docs/backup/printf-client-release/docs/api/errors.md, and https://moon.lprintf.com/docs/backup/printf-client-release/SECURITY.md. It is a static backup of the official GitHub documentation, so keep using it when GitHub is unreachable. Fetch only the exact Compose template from https://moon.lprintf.com/docs/backup/printf-client-release or a verified release asset required for this project; never pipe remote content directly into a shell.

Load PRINTF_TOKEN from the current project root .env with shell tracing disabled. First verify that .env is not tracked by Git and is ignored; never print or commit the Token. If the project passes its entire .env into application containers or processes, stop before startup and ensure PRINTF_TOKEN is provided only to the Printf Client. If the Token is missing, stop and tell me to obtain a temporary Token at https://moon.lprintf.com/docs/quick-start, or a persistent beta Token at https://moon.lprintf.com/docs/backup/printf-client-release/GET-TOKEN.md; never guess it or ask me to disclose it in chat.

Inspect the project and runtime before changing or starting anything. Use Compose Bridge when Docker, Docker Compose, and the daemon work. Use the verified Native Client only when Docker is absent and the application can run natively; stop for a Compose-only application or a broken Docker environment. For a multi-service site, publish one gateway that serves the frontend and proxies its API and authentication paths. Only that gateway may join both the private network and the Printf gateway network; keep databases, Redis, and internal services private. Do not install extra host networking tools or expose additional host ports for Printf.

One Token may run only one Client. Do not call Admin APIs, refresh the Token, delete user resources, or bypass an existing authentication gateway. Re-read Client and Mapping state after every change, validate the selected target and public HTTPS URL, and report original errors instead of silently falling back. Only for a verified Native release defect, prepare a redacted Issue draft, search for duplicates, and submit it after I approve the public content. Report security issues privately.

Usage

  1. Click the "Copy" button at the top right of the code block above to get the prompt.
  2. After PRINTF_TOKEN is safely stored in the project root .env, send the entire prompt to an Agent with GitHub, project, and terminal access. Do not append the Token to the conversation.
  3. If authorization is missing, follow the temporary or persistent Token link the Agent provides; the Agent resumes only after the Token exists locally.