Deployment guides for AI-built apps, with practical notes on hosting, Git builds, databases, domains and keeping the next release repeatable.
Articles, shipping notes, and the thinking behind how aidrop.it works.
Every host runs three clocks: when it stops serving, when it deletes, and what a payment restores. The questions to ask, and a worksheet to keep the answers in.
Build arguments, ENV lines and copied files all stay in the image. Where each value belongs, the one exception, and two commands that prove a build is clean.
A container that is up is not a site that answers. What a health path is for, what it should fail on, and an outside check that settles a deploy.
A healthy process and a dead address: binding to localhost instead of 0.0.0.0, or ignoring PORT. Two one-line fixes, and how to reproduce it locally.
DNS propagation and certificate issuance are two different clocks. Why HTTPS fails after the record is correct, and the Cloudflare setting that deadlocks it.
Domain verification that resolves your DNS record fails for correctly configured domains behind a proxy. Prove that requests arrive instead.
A zone apex cannot hold a CNAME — it is a rule of DNS, not your provider. What CNAME flattening, ALIAS and ANAME actually do, and which to pick.
A deploy tool should say what is missing before it builds. Three verdicts instead of two, and why the output should be a list rather than a score.
A plan that counts containers rather than projects taxes building properly. Two limits, why they answer different questions, and why reserved is not used.
