<?xml version="1.0" encoding="utf-8" standalone="yes"?><rss version="2.0" xmlns:atom="http://www.w3.org/2005/Atom"><channel><title>Postgresql Docker Compose on Econumo</title><link>https://econumo.com/tags/postgresql-docker-compose/</link><description>Recent content in Postgresql Docker Compose on Econumo</description><generator>Hugo</generator><language>en</language><lastBuildDate>Wed, 22 Apr 2026 08:16:07 +0000</lastBuildDate><atom:link href="https://econumo.com/tags/postgresql-docker-compose/index.xml" rel="self" type="application/rss+xml"/><item><title>Mastering PostgreSQL Docker Compose for Dev &amp; Prod</title><link>https://econumo.com/posts/postgresql-docker-compose/</link><pubDate>Wed, 22 Apr 2026 08:16:07 +0000</pubDate><guid>https://econumo.com/posts/postgresql-docker-compose/</guid><description>You’re probably in one of two places right now.
Either you need PostgreSQL running locally in the next few minutes so you can build features instead of wrestling with package managers, or you’re self-hosting an app and realizing that the cheerful one-file examples on the internet skip the parts that protect your data.
That gap matters. A disposable dev database and a production database may both start from postgres in a Compose file, but they don’t deserve the same defaults.</description></item></channel></rss>