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.
Deploying from an agent session is fast. Give the loop three reasons to stop, name the fixes it may never make, and paste a deploy-loop block into instructions.
Every host is a contract: writable paths, disk, port, replicas, egress. Read it before your agent picks a stack, with a worksheet you can fill in for any host.
A fresh agent session reads the repository, not the running app. Six facts to read from the host first, and a block to paste into your agent instructions.
Rebuilding an old commit is a new artefact. Keep every built image by commit, start it by name, and write migrations so an old version runs on a new schema.
An upload has no history; a commit keeps author, revision and diff. Why code should reach a host through Git, from a shell or a chat, with three checks.
Signup checks measure the person, not the app. Judge abuse when an address opens to the internet, stop first, delete last, and grade any host with a worksheet.
Share a database between two applications with a named migration owner, clear table permissions and a release checklist that checks both apps still work.
Scope a coding agent to one project, test the actions its credential permits, and verify revocation. A copyable checklist helps you review each connection.
Test your database export in an isolated restore drill. Check records, uploaded files and recovery time, then keep a worksheet the next maintainer can use.
