Thanks for your interest in improving postgresql-fdw! This project aims to be a clean, reusable, laptop-friendly PostgreSQL development setup. Contributions of all sizes are welcome.
- 🐛 Report a bug (use the issue templates)
- 💡 Propose a feature or a new optional service/extension
- 📖 Improve the docs (
docs/andREADME.md) - 🔧 Submit a fix or enhancement via a pull request
git clone https://github.com/programmerShinobi/postgresql-fdw.git
cd postgresql-fdw
make init # copies .env.example -> .env AND installs the git hooks
# edit .env: set a strong POSTGRES_PASSWORD
make build
make up
make extensions # sanity check
make initinstalls the pre-commit secret guard (scripts/git-hooks/). Please keep it enabled — it blocks accidental commits of credentials or internal IPs.
- Never commit secrets or internal infrastructure details. Real values go
in
.env/.env.source(gitignored); commit only*.exampletemplates. Runmake scan-secretsif unsure. - Keep the default lightweight. New services must be opt-in behind a Docker
Compose
profileand carrymem_limit+cpuscaps. Nothing new should run on a plainmake up. See docs/12-OPTIONAL-FEATURES.md. - Pin image versions (no
:latest) for reproducible builds. - Document it. A feature without a doc entry is incomplete.
- Match the surrounding style in configs, SQL, and Makefile targets.
-
docker compose configpasses (and with--profile ...if you touched a profile) -
make buildsucceeds;make up && make extensionsworks - No secrets/IPs added (
make scan-secretsclean) - Docs updated (
README.mdand/ordocs/) -
CHANGELOG.mdupdated under "Unreleased"
Use clear, imperative summaries (e.g. Add hypopg usage example). Conventional
Commit prefixes (feat:, fix:, docs:, chore:) are welcome but not required.
By participating you agree to uphold our Code of Conduct.