Prepare the machine
Resized mohtasham-hermes to 8 vCPU / 32 GB RAM and 200 GB disk. The public IP was reserved so DNS stays stable across VM restarts.
← All plans
Implementation recap · 13 Jul 2026
Coolify hosting foundation
How mohtasham-hermes became a repeatable Coolify hosting lane: GitHub source in, HTTPS demo link out. Future prototypes ship at <project>.demo.mohtasham.dev without hand-managed ports, proxy files, or per-project DNS work.
Project
MohtashamMurshid/visual-plans ↗
Branch
main
Author
Mohtasham
Model
Fable 5
Deployed via
Coolify
8vCPU · e2-standard-8
32 GBRAM capacity
200 GBPersistent disk
∞Wildcard demos
Build sequence.
In the order it mattered
Install Coolify
Installed Coolify 4.1.2 on the VM, isolated Docker networks to 172.30.0.0/16, and secured its environment file. Coolify now owns the deployment lifecycle.
Establish routing
Vercel DNS now sends deploy.mohtasham.dev and the *.demo.mohtasham.dev wildcard to the VM. The root portfolio stays untouched on Vercel.
Resolve platform conflicts
Moved cAdvisor from host port 8080 to 8081 so Coolify's proxy can own 80, 443, and 8080. Opened the real-time ports Coolify requires.
Ship each demo
Create or connect a GitHub repo, deploy it through Coolify, assign a readable wildcard subdomain, then verify public HTTPS before sharing the link.
How a demo moves.
The repeatable operating model
Guardrails.
Fast for prototypes, tidy enough to keep
Keep it simple
- GitHub is the source of truth.
- Coolify handles build logs, env vars, and redeploys.
- Only 80/443 are used for public applications.
Do not break the platform
- Leave mohtasham.dev and www on Vercel.
- Never take port 8080 away from the Coolify proxy.
- Keep monitoring exporters private to the monitoring VM.
Approval to proceed.
Next test
Ready for the first real deploy
This page is the first end-to-end test. The next test is deploying a real visual plan or prototype from GitHub to a named *.demo.mohtasham.dev URL.