DEV Community: Adelodun Peter

I Need a Postgres Instance. Now.

Adelodun Peter — Mon, 22 Dec 2025 10:26:18 +0000

I'm not trying to deploy to production.

I'm not setting up infra.

I just want to build something.

Yet somehow, getting a local database looks like this:

Install Docker
Learn Docker (enough to not break things)
Run Docker
Write a docker-compose.yml
Pull images
Expose ports
Pray nothing else is already using that port

All of this… just to get Postgres running locally.

That friction adds up. Especially when you're experimenting, prototyping, or switching projects often.

The Real Problem

The problem isn't Postgres.

The problem is that starting a database shouldn't feel like infrastructure work.

Databases are foundational tools. They should be:

Fast to start
Easy to stop
Disposable
Local-first

Instead, we've normalized spinning up containers, managing configs, and debugging environment issues before we even write our first query.

What If It Was Just One Command?

What if starting a database was as simple as:

instant-db start

No Docker.

No containers to manage.

No extra mental overhead.

Just… a database. Running. Ready.

That question is why I'm building Instant DB.

Introducing Instant DB

Instant DB is a single-command local database launcher.

Right now, it supports:

PostgreSQL
Redis

More engines are coming.

You run one command, and you immediately have a working database instance you can connect to from your app, your ORM, or your SQL client.

It's designed for:

Local development
Prototyping
Testing
Side projects
Hackathons
Anyone who just wants to move fast

Why Not Docker?

Docker is powerful — but it's also heavy.

For many developers, especially beginners or solo builders like me:

Docker adds cognitive load
Debugging containers becomes a distraction
The setup cost outweighs the benefit for local work

Instant DB isn't trying to replace Docker in production.

It's trying to remove friction during development.

The Goal

My goal with Instant DB is simple:

Databases should feel like tools, not projects.

You shouldn't need a tutorial to start a local database.

You shouldn't lose momentum before you even begin.

Still Early — But Moving Fast

Instant DB is still evolving.

Postgres and Redis are just the beginning.

The vision is a growing list of supported databases, all started the same way:

instant-db start

One command.

Instant database.

Zero drama.

Try It / Get Involved 🚀

👉 GitHub:

https://github.com/db-toolkit/instantdb

👉 Install instantly(Mac and Linux, Windows coming soon):

curl -sSL https://raw.githubusercontent.com/db-toolkit/instantdb/main/install.sh | bash

If this resonates with you — I'd love to hear your thoughts and feedback.

DB-Toolkit - Database Management Made Simple

Adelodun Peter — Sat, 13 Dec 2025 18:17:12 +0000

For a long time, I searched for a modern database tool that truly fit the way I work.

Not just something that connects to a database, but something that stays out of the way, and feels intuitive to use.

I wanted multiple databases open without mental clutter, a workflow that minimizes context switching, an editor that just makes sense, and a tool that feels like it belongs in 2025 — not 2012.

I couldn’t find it.

So I started building it.

That journey became DB Toolkit — a cross-platform desktop database management application built from frustration and real needs.

👉Check It Out

What started as “let me fix this small annoyance” turned into:

Multi-database support (PostgreSQL, MySQL, SQLite, MongoDB)
A schema explorer that actually helps you understand your data
A Monaco-powered query editor with history and multiple tabs Workspaces that let me isolate projects and think clearly
A data explorer that lets you edit, import/export, and preview data effortlessly

DB Toolkit is just getting started.
I’m still learning. Still improving.

🔗 DB Toolkit
Would love feedback from fellow developers

🚀 Stop Fighting Alembic — FastAPI & Flask Migrations Can Finally Be as Simple as Django.

Adelodun Peter — Mon, 17 Nov 2025 14:53:16 +0000

If you’ve ever tried setting up Alembic, you probably went through this cycle:

create a migrations folder
edit alembic.ini
modify env.py
manually import your models
configure database URLs
hope it works

And when it finally runs, you pray nothing breaks when you update your models again.

I hated this.
Every FastAPI / Flask / SQLAlchemy developer I know hates this.
So I built something to fix it.

Introducing Migrator — A Zero-Config Migration CLI for Python

Migrator brings Django-like migrations to FastAPI and Flask.

No configuration.
No boilerplate.
No Alembic headaches.

Just migrations that work.

❌ Before Migrator: Alembic Setup Pain

Traditional Alembic workflow:
alembic init migrations

edit alembic.ini
edit env.py
import models, configure engine
hope it works

If you've done it, you know how fragile this is.

✅ After Migrator: Pure Simplicity

migrator init migrator makemigrations "initial" migrator migrate

That’s it. No configs. No patches. No manual imports. It just works.

🔍 How Migrator Works

✔️ Finds your models automatically
✔️ Detects your database engine
✔️ Builds migration environment
✔️ Wires Alembic automatically
✔️ Runs safe schema diffs

This means you keep the power of Alembic, without any of the setup.

🎉 Why Migrator Rocks

Zero configuration
Auto-discovery of models & metadata
Framework-agnostic (FastAPI, Flask, Django, SQLAlchemy)
Django-like workflow
Production-ready (powered by Alembic)

🧪 Quick Start

Install:

curl -sSL https://raw.githubusercontent.com/Adelodunpeter25/migrator/main/install.sh | bash

Initialize:

migrator init

Create first migration:

migrator makemigrations "initial"

Apply:

migrator migrate

Done.

💬 Final Thoughts

Python needed a migration tool like this.

FastAPI and Flask are amazing frameworks — but Alembic setup has always been a huge barrier for beginners and even experienced devs.

Migrator removes the friction so you can focus on building, not fighting config files.

If you want migrations that work like Django, without switching ecosystems, give Migrator a try.

GitHub • PyPI • Docs

I would love feedback, suggestions, and contributors, this is just the beginning.

Happy coding!