A Rollback Should Not Rebuild
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.
4 min read
Read
aidrop.it blog
Notes on keeping software worth changing.
Product updates, implementation details, and field notes on getting an app running, who may reach it, and the record the next change starts from.
Latest
From the team
Articles, shipping notes, and the thinking behind how aidrop.it works.
Code Should Enter a Host Through Git and Nowhere Else
An upload has no history; a platform that commits for you holds a write path a prompt can reach. Why code should reach a host by git push, with three checks.
4 min read
Read
Abuse Should Be Judged at the Address, Not at Signup
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.
4 min read
Read
Two Apps Share a Database. Who Changes the Schema?
Share a database between two applications with a named migration owner, clear table permissions and a release checklist that checks both apps still work.
3 min read
Read
Give Your Coding Agent Access to One Project
Scope a coding agent to one project, test the actions its credential permits, and verify revocation. A copyable checklist helps you review each connection.
3 min read
Read
Test Your Database Restore Before You Need It
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.
3 min read
Read
What Happens When You Stop Paying for Hosting
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.
4 min read
Read
Your Build Should Not Know Your Secrets
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.
5 min read
Read
Running Is Not the Same as Answering
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.
4 min read
Read