OUTCOMES
What this Prompt helps you deliver
- TabTin runs reliably on your server
- You receive deployment, backup, recovery, and upgrade instructions
BEFORE YOU START
Before you start
- You can sign in to a target server remotely
- You have chosen a domain and persistent data location
What AI should inspect first
AGENTS.mddocker-compose.deploy.ymldeploymentdocs/agent/setup.mdREADY TO RUN
Complete Prompt
Copy the complete Prompt with its execution and acceptance boundaries.
You are deploying TabTin on my server as a private product environment that can be maintained, backed up, and upgraded. Base the deployment on this repository and the actual server; do not paste in a generic Docker tutorial that ignores TabTin’s services.
Before you begin
Read AGENTS.md, docker-compose.deploy.yml, deployment, and docs/agent/setup.md. With read-only checks, establish the server OS, CPU, memory, disk, Docker version, exposed ports, DNS, and TLS readiness. Tell me which domain, secret, or object-storage values you need, but never print secrets in logs or the final report.
Work to complete
- Explain the deployment topology: ingress proxy, Web, API, database, cache, collaboration, and realtime services.
- Keep environment variables in the repository’s designated location and store generated passwords and keys securely.
- Configure persistent volumes, database initialization, static assets, uploads, health checks, and service restart policies.
- Configure the domain and HTTPS. If no domain is ready, provide an explicit temporary access path and the later switch point.
- Perform the deployment and resolve failures from logs. Do not delete existing server data or expose unnecessary public ports.
Verification
From both the server and the external entry point, verify the page, API health, realtime connection, sign-in, and one basic data write. Restart the services and prove the data survives. Inspect container state, resource use, and errors, then run the backup command and confirm it creates a recoverable artifact.
Final report
Provide the access address, service topology, data locations, backup and restore commands, upgrade procedure, certificate renewal path, and remaining security work. Never commit real secrets, and do not push repository changes without my permission.