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.
Explore why aidrop assigns databases to Projects, how Services share them, and why deployments, schema changes, and data recovery have separate lifecycles.
A database keeps records, a cache holds replaceable copies, and a queue tracks work. Explore how PostgreSQL and two Valkey configurations serve these roles.
Application state has different lifetimes. Understand what belongs in the browser, process memory, or durable storage, and what survives an aidrop deployment.
Move an app from a VPS to aidrop.it with a tested data transfer, a planned domain cutover, and a rollback procedure that accounts for new database writes.
Deploy Django with PostgreSQL on aidrop.it: configure production settings, serve static files, run migrations, and verify data survives the next release.
Deploy a Next.js app on aidrop.it with standalone output, runtime secrets, and a cache strategy that works on a read-only filesystem. Verify two releases.
Deploy a Slack Bolt bot over HTTPS: configure secrets, build the service, set its Request URL, and verify a slash command with local development stopped.
Understand what makes a legacy monolith hard to change, assess one critical workflow, and choose a first improvement with clear evidence and recovery steps.
Compare legacy app rewrite services using evidence: scope, behaviour checks, data migration, cutover, recovery, and a handover your team can actually run.
