Extensions are Postgres most loved feature. Augment your database functionality in every
imaginable way! And benefit from an ecosystem of hundreds of open source extensions.
StackGres supports dynamically loading extensions into your Postgres cluster's pods. StackGres supports
100+ extensions, with the list growing every day. No allow list, no small set of extensions
available. StackGres is the Postgres platform with the most extensions available. Search/browse them
below:
# 2️⃣ Add your key/value pairs echo "DB_PASSWORD=SuperSecret123!" >> .secrets
| Reason | What it solves | |--------|----------------| | | By keeping secrets out of source code you prevent them from being pushed to public repos. | | Centralized management | All secret values live in one place, making rotation and audit easier. | | Environment‑specific values | You can have separate secret files for development, staging, production, etc. | | Tooling support | Many libraries (dotenv, python‑decouple, etc.) can automatically load a hidden file. | .secrets
In your pipeline (e.g., GitHub Actions), you do not store the .secrets file in the repo. Instead, you store each secret as an encrypted . During the build, the pipeline reads the encrypted variables and dynamically creates a .secrets file inside the ephemeral container. | | Tooling support | Many libraries (dotenv,
# Secrets .secrets .secrets.*
Do you feel any extension is missing? Please create an issue and let
us know. If you are an extension creator/maintainer and would like to see your extension added,
please contact us on the #extensions channel in our Community Slack.