Deployment
Overview
How lab apps go from GitHub to the VPS
Summary
All lab apps follow one path:
git push → GitHub (superbonfire-lab) → webhook → Coolify → build → VPS → https://app-name.cp.superbonfire.techThe code lives in GitHub. The server runs what Coolify builds from GitHub. Do not edit files on the server by hand.
Use an AI agent
You can give these pages to your AI agent. Tell the agent to walk you through the setup step by step, and to stop and ask before it does anything destructive or needs a password or token.
Ground rules
- Never paste or commit secrets. Passwords, API tokens, database URLs, and
.envcontents do not go in code, Git, or chat. Put them in Coolify environment variables or in Vaultwarden. - Ask before destructive actions. Do not delete containers, volumes, databases, branches, or server files without confirmation.
mainis production. Work in feature branches. Merge tomainonly when the change is ready to go live.- No SSH. Server access is not granted for now. Use the Coolify dashboard for logs and status.
- Check before you change. Look at the current state before you change it. If an AI agent does the work, it shows you the result first.
- Follow the conventions. Use kebab-case names, Conventional Commits, one branch per feature, and a reviewed pull request. See Git workflow.
Key facts
| Item | Value |
|---|---|
| GitHub organisation | https://github.com/superbonfire-lab |
| Deployment platform | Coolify (self-hosted PaaS) |
| Coolify dashboard | https://cp.superbonfire.tech |
| VPS | Tencent Cloud, Singapore (ap-singapore) |
| VPS public IP | 43.128.88.92 |
| App domains | app-name.cp.superbonfire.tech |
| Password manager | https://pass.superbonfire.tech (Vaultwarden) |
| DNS | Cloudflare |
Contact
Syahman sets up the GitHub organisation, Coolify, Cloudflare, Vaultwarden, and server access.
Email: syahman@superbonfire.com.
If you are stuck after two attempts, stop. Send the exact error message and the command or screen that produced it.