Infisical {shmolf}
Stack
The open-source secret management platform: Sync secrets/configs across your team/infrastructure and prevent secret leaks.
Configuration
TypeComposelinuxPORT=8078ENCRYPTION_KEY=c6606cd2daad581c4de96531427aae0dAUTH_SECRET=5lrMXKKWCVocS/uerPsl7V+TX/aaUaI7iDkgl3tSmLE=POSTGRES_PASSWORD=postgres_passwordPOSTGRES_USER=infisicalPOSTGRES_DB=infisicalDB_CONNECTION_URI=postgres://${POSTGRES_USER}:${POSTGRES_PASSWORD}@db:5432/${POSTGRES_DB}SITE_URL=http://localhost:8078REDIS_URL=redis://redis:6379SMTP_HOST=SMTP_PORT=SMTP_NAME=SMTP_USERNAME=SMTP_PASSWORD=CLIENT_ID_HEROKU=CLIENT_SECRET_HEROKU=CLIENT_ID_VERCEL=CLIENT_SECRET_VERCEL=CLIENT_SLUG_VERCEL=CLIENT_ID_NETLIFY=CLIENT_SECRET_NETLIFY=CLIENT_ID_GITHUB=CLIENT_SECRET_GITHUB=CLIENT_ID_GITLAB=CLIENT_SECRET_GITLAB=CLIENT_ID_BITBUCKET=CLIENT_SECRET_BITBUCKET=SENTRY_DSN=CLIENT_ID_GOOGLE_LOGIN=CLIENT_SECRET_GOOGLE_LOGIN=CLIENT_ID_GITHUB_LOGIN=CLIENT_SECRET_GITHUB_LOGIN=CLIENT_ID_GITLAB_LOGIN=CLIENT_SECRET_GITLAB_LOGIN=CAPTCHA_SECRET=NEXT_PUBLIC_CAPTCHA_SITE_KEY=PLAIN_API_KEY=PLAIN_WISH_LABEL_IDS=unless-stoppedNotes
Services
db-migration
Configuration
Imageinfisical/infisical:latest-postgresnpm run migration:latestDB_CONNECTION_URI=Image details
backend
Configuration
Imageinfisical/infisical:latest-postgres${PORT}:8080NODE_ENV=productionDB_CONNECTION_URI=ENCRYPTION_KEY=AUTH_SECRET=SITE_URL=REDIS_URL=SMTP_HOST=SMTP_PORT=SMTP_NAME=SMTP_USERNAME=SMTP_PASSWORD=CLIENT_ID_HEROKU=CLIENT_SECRET_HEROKU=CLIENT_ID_VERCEL=CLIENT_SECRET_VERCEL=CLIENT_SLUG_VERCEL=CLIENT_ID_NETLIFY=CLIENT_SECRET_NETLIFY=CLIENT_ID_GITHUB=CLIENT_SECRET_GITHUB=CLIENT_ID_GITLAB=CLIENT_SECRET_GITLAB=CLIENT_ID_BITBUCKET=SENTRY_DSN=CLIENT_ID_GOOGLE_LOGIN=CLIENT_SECRET_GOOGLE_LOGIN=CLIENT_ID_GITHUB_LOGIN=CLIENT_SECRET_GITHUB_LOGIN=CLIENT_ID_GITLAB_LOGIN=CLIENT_SECRET_GITLAB_LOGIN=CAPTCHA_SECRET=NEXT_PUBLIC_CAPTCHA_SITE_KEY=PLAIN_API_KEY=PLAIN_WISH_LABEL_IDS=unless-stoppedImage details
redis
Configuration
Imageredis6379:6379/data : redis_dataALLOW_EMPTY_PASSWORD=yesImage details
db
Configuration
Imagepostgres:14-alpine/var/lib/postgresql/data : pg_dataPOSTGRES_PASSWORD=POSTGRES_USER=POSTGRES_DB=alwaysImage details
Standalone Install
Select an install method, to see config/commands for deploying Infisical {shmolf}
Install on Portainer
Import all app templates into your Portainer instance, for easy 1-click deploys
- Ensure both Docker and Portainer are installed, and up-to-date
- Log into your Portainer web UI
- Under Settings → App Templates, paste the below URL
- Head to Home → App Templates, and the list of apps will show up
- Select Infisical {shmolf}, fill in any config options, and hit Deploy
Template Import URL
https://raw.githubusercontent.com/Lissy93/portainer-templates/main/templates.json
Show Me
Original stackfile
The compose file this template deploys, straight from its repo:
services:
db-migration:
container_name: infisical-db-migration
depends_on:
db:
condition: service_healthy
image: infisical/infisical:latest-postgres
environment:
- DB_CONNECTION_URI
command: npm run migration:latest
pull_policy: always
networks:
- infisical
backend:
container_name: infisical-backend
restart: unless-stopped
depends_on:
db:
condition: service_healthy
redis:
condition: service_started
db-migration:
condition: service_completed_successfully
image: infisical/infisical:latest-postgres
pull_policy: always
ports:
- ${PORT}:8080
environment:
- NODE_ENV=production
- DB_CONNECTION_URI
- ENCRYPTION_KEY
- AUTH_SECRET
- SITE_URL
- REDIS_URL
- SMTP_HOST
- SMTP_PORT
- SMTP_NAME
- SMTP_USERNAME
- SMTP_PASSWORD
- CLIENT_ID_HEROKU
- CLIENT_SECRET_HEROKU
- CLIENT_ID_VERCEL
- CLIENT_SECRET_VERCEL
- CLIENT_SLUG_VERCEL
- CLIENT_ID_NETLIFY
- CLIENT_SECRET_NETLIFY
- CLIENT_ID_GITHUB
- CLIENT_SECRET_GITHUB
- CLIENT_ID_GITLAB
- CLIENT_SECRET_GITLAB
- CLIENT_ID_BITBUCKET
- SENTRY_DSN
- CLIENT_ID_GOOGLE_LOGIN
- CLIENT_SECRET_GOOGLE_LOGIN
- CLIENT_ID_GITHUB_LOGIN
- CLIENT_SECRET_GITHUB_LOGIN
- CLIENT_ID_GITLAB_LOGIN
- CLIENT_SECRET_GITLAB_LOGIN
- CAPTCHA_SECRET
- NEXT_PUBLIC_CAPTCHA_SITE_KEY
- PLAIN_API_KEY
- PLAIN_WISH_LABEL_IDS
networks:
- infisical
redis:
image: redis
container_name: infisical-dev-redis
environment:
- ALLOW_EMPTY_PASSWORD=yes
ports:
- 6379:6379
networks:
- infisical
volumes:
- redis_data:/data
db:
container_name: infisical-db
image: postgres:14-alpine
restart: always
environment:
- POSTGRES_PASSWORD
- POSTGRES_USER
- POSTGRES_DB
volumes:
- pg_data:/var/lib/postgresql/data
networks:
- infisical
healthcheck:
test: "pg_isready --username=${POSTGRES_USER} && psql --username=${POSTGRES_USER} --list"
interval: 5s
timeout: 10s
retries: 10
volumes:
pg_data:
driver: local
redis_data:
driver: local
networks:
infisical:
Or deploy it directly from the source:
git clone https://github.com/shmolf/portainer-templates
cd portainer-templates
docker compose -f stacks/infisical/compose.yml up -dMore install options in our documentation.
Container Documentation
db-migration Documentation
This version of Infisical combines all the essential components into a single image
backend Documentation
This version of Infisical combines all the essential components into a single image
redis Documentation
Redis is the world’s fastest data platform for caching, vector search, and NoSQL databases.
db Documentation
The PostgreSQL object-relational database system provides reliability and data integrity.
Serve Infisical {shmolf} on your own domain behind Caddy, Nginx or Traefik. Fill in your domain and copy the result. It's a starting point, some apps need their own base URL or extra headers set too.
Proxying infisical-shmolf.example.com to http://redis:6379
Add this to your Caddyfile
infisical-shmolf.example.com {
reverse_proxy http://redis:6379
}Check the logs first
Nine times out of ten the logs tell you exactly what went wrong.
- In Portainer, go to Containers, click the container, then Logs. Or run
docker logs <container> - Exit codes help too:
137means killed, usually out of memory.126or127means the command inside the image is broken.
Port already in use
If deployment fails with "Bind for 0.0.0.0:6379 failed: port is already allocated", something else on your server is using that port.
- Find what's using it:
sudo ss -tlnp | grep :6379 - Stop the other service, or pick a different host port. In
6379:6379only the left number is yours to change, the right one belongs to the app.
Running but the page won't load
The container is up but nothing appears in your browser.
- Use your server's real IP:
http://your-server-ip:6379. The 0.0.0.0 link Portainer shows isn't a real address. - Give it a minute after first deploy, infisical can take a while to initialise.
- Make sure your firewall allows the port, e.g.
sudo ufw allow 6379
Image won't pull
Test the pull directly on the host: docker pull infisical/infisical:latest-postgres
- "manifest unknown" means the tag no longer exists.
- "toomanyrequests" is the Docker Hub rate limit. Log in with
docker loginto raise it. - "no space left on device" means a full disk. Reclaim space with
docker system prune
"exec format error"
This means the image was built for a different CPU architecture than your server.
- Check yours with
uname -m: x86_64 is amd64, aarch64 is arm64. Raspberry Pi and other ARM boards are the usual culprits.
Container keeps restarting
The unless-stopped restart policy relaunches the app after every crash, so the real error can scroll past.
- Check the logs right after a restart, the last few lines before it died are the useful ones.
- Get the exit code with
docker inspect <container> --format '{{.State.ExitCode}}' - Still stuck? Redeploy once with the restart policy set to
noso the failure stays visible.
Required settings are blank
DB_CONNECTION_URI, ENCRYPTION_KEY, AUTH_SECRET, SITE_URL, REDIS_URL, SMTP_HOST, SMTP_PORT, SMTP_NAME, SMTP_USERNAME, SMTP_PASSWORD, CLIENT_ID_HEROKU, CLIENT_SECRET_HEROKU, CLIENT_ID_VERCEL, CLIENT_SECRET_VERCEL, CLIENT_SLUG_VERCEL, CLIENT_ID_NETLIFY, CLIENT_SECRET_NETLIFY, CLIENT_ID_GITHUB, CLIENT_SECRET_GITHUB, CLIENT_ID_GITLAB, CLIENT_SECRET_GITLAB, CLIENT_ID_BITBUCKET, SENTRY_DSN, CLIENT_ID_GOOGLE_LOGIN, CLIENT_SECRET_GOOGLE_LOGIN, CLIENT_ID_GITHUB_LOGIN, CLIENT_SECRET_GITHUB_LOGIN, CLIENT_ID_GITLAB_LOGIN, CLIENT_SECRET_GITLAB_LOGIN, CAPTCHA_SECRET, NEXT_PUBLIC_CAPTCHA_SITE_KEY, PLAIN_API_KEY, PLAIN_WISH_LABEL_IDS, POSTGRES_PASSWORD, POSTGRES_USER, POSTGRES_DB have no default value, and infisical may crash or misbehave if left empty.
- Fill them in on the deploy screen before hitting deploy.
Stack won't deploy
Compose stacks fail fast on small mistakes, and Portainer shows the reason just above the editor.
- YAML only accepts spaces for indentation, a single tab breaks the whole file.
Raise an issue
Found something which isn't working as it should? Here's how to report it.
- Bug within the app: Open an issue within infisical's repo
- Template not working: Open an issue on shmolf/portainer-templates
- This website not working: Open an issue on lissy93/portainer-templates
A Compose stack
Infisical {shmolf} is a Compose stack, a set of containers (4 of them) defined in one file and brought up together by Portainer, then started and stopped as a single app.
The services
This stack is built from 4 containers that run side by side. Here's each one, with the image it runs and anything it waits for first:
db-migrationrunsinfisical/infisical:latest-postgres, starts after dbbackendrunsinfisical/infisical:latest-postgres, starts after db, redis, db-migrationredisrunsredisdbrunspostgres:14-alpine
Ports
A port is the door the app answers on. A mapping like 6379:6379 means it's reachable on port 6379 of your server, where the left number is yours to change and the right one belongs to the app. It opens:
6379:6379
Volumes
A volume is where Infisical {shmolf} keeps its files so they survive an update or a restart. Without one, anything it saves would sit inside the container and vanish the moment it's recreated. This template mounts:
/datakept in theredis_datavolume Docker manages/var/lib/postgresql/datakept in thepg_datavolume Docker manages
Environment variables
Environment variables are the settings you hand over when you deploy, things like a password or a timezone. Infisical {shmolf} takes 38 of them, and 36 need a value before it'll start properly:
DB_CONNECTION_URI, needs a valueNODE_ENV, defaults toproductionENCRYPTION_KEY, needs a valueAUTH_SECRET, needs a valueSITE_URL, needs a valueREDIS_URL, needs a valueSMTP_HOST, needs a valueSMTP_PORT, needs a valueSMTP_NAME, needs a valueSMTP_USERNAME, needs a valueSMTP_PASSWORD, needs a valueCLIENT_ID_HEROKU, needs a valueCLIENT_SECRET_HEROKU, needs a valueCLIENT_ID_VERCEL, needs a valueCLIENT_SECRET_VERCEL, needs a valueCLIENT_SLUG_VERCEL, needs a valueCLIENT_ID_NETLIFY, needs a valueCLIENT_SECRET_NETLIFY, needs a valueCLIENT_ID_GITHUB, needs a valueCLIENT_SECRET_GITHUB, needs a valueCLIENT_ID_GITLAB, needs a valueCLIENT_SECRET_GITLAB, needs a valueCLIENT_ID_BITBUCKET, needs a valueSENTRY_DSN, needs a valueCLIENT_ID_GOOGLE_LOGIN, needs a valueCLIENT_SECRET_GOOGLE_LOGIN, needs a valueCLIENT_ID_GITHUB_LOGIN, needs a valueCLIENT_SECRET_GITHUB_LOGIN, needs a valueCLIENT_ID_GITLAB_LOGIN, needs a valueCLIENT_SECRET_GITLAB_LOGIN, needs a valueCAPTCHA_SECRET, needs a valueNEXT_PUBLIC_CAPTCHA_SITE_KEY, needs a valuePLAIN_API_KEY, needs a valuePLAIN_WISH_LABEL_IDS, needs a valueALLOW_EMPTY_PASSWORD, defaults toyesPOSTGRES_PASSWORD, needs a valuePOSTGRES_USER, needs a valuePOSTGRES_DB, needs a value
Restart policy
The restart policy here is unless-stopped, so Docker restarts Infisical {shmolf} after a crash or reboot, but leaves it off when you stop it on purpose. You can change this on the deploy screen. The choices are no (never restart), on-failure (only after a crash), unless-stopped (restart unless you stop it), and always (bring it back no matter what).
Networking
Portainer puts these services on one shared private network, so they can find each other by name (like db-migration) while only the ports above are open to you.
Platform
The platform is linux, the kind of system the container is built to run on. Docker and Portainer handle this on a normal Linux server.
Portainer app templates
Zooming out, this whole page comes from a Portainer app template: a short recipe telling Portainer how to set Infisical {shmolf} up. Add the template list to Portainer once, then deploying Infisical {shmolf} is a click rather than a wall of config.