fix(infisical): update to v0.162.6

- Bump image from v0.135.0-postgres to v0.162.6 (upstream dropped the -postgres tag suffix after v0.146.0; plain tags are the postgres build) - Remove the db-migration service: the standalone image runs database migrations automatically on boot (auto-start-migrations), matching the official docker-compose.prod.yml which no longer ships that service - Generate ENCRYPTION_KEY (${hash:32}) and AUTH_SECRET (${base64:32}) per deployment instead of shipping hardcoded example secrets - Fix SITE_URL to http://${main_domain} (no :8080; the domain is proxied) - Refresh SMTP env names (SMTP_FROM_ADDRESS/SMTP_FROM_NAME; SMTP_SECURE was removed upstream) and drop unused CLIENT_* env placeholders that were never passed to the container Closes #215 Co-Authored-By: Claude Fable 5 <noreply@anthropic.com>
2026-11-10 01:33:12 -06:00 · 2026-07-14 11:30:46 -06:00
8 changed files with 23 additions and 168 deletions
@@ -1,58 +1,29 @@
 services:
-  db-migration:
-    depends_on:
-      db:
-        condition: service_healthy
-    image: infisical/infisical:v0.135.0-postgres
-    environment:
-      - NODE_ENV=production
-      - ENCRYPTION_KEY
-      - AUTH_SECRET
-      - SITE_URL
-      - DB_CONNECTION_URI=postgres://${POSTGRES_USER}:${POSTGRES_PASSWORD}@db:5432/${POSTGRES_DB}
-      - REDIS_URL=redis://redis:6379
-      - SMTP_HOST
-      - SMTP_PORT
-      - SMTP_FROM_NAME
-      - SMTP_USERNAME
-      - SMTP_PASSWORD
-      - SMTP_SECURE=true
-    command: npm run migration:latest
-    pull_policy: always
-
  backend:
+    image: infisical/infisical:v0.162.6
    restart: unless-stopped
    depends_on:
      db:
        condition: service_healthy
      redis:
        condition: service_started
-      db-migration:
-        condition: service_completed_successfully
-    image: infisical/infisical:v0.135.0-postgres
-    pull_policy: always
    environment:
      - NODE_ENV=production
-      - ENCRYPTION_KEY
-      - AUTH_SECRET
-      - SITE_URL
+      - ENCRYPTION_KEY=${ENCRYPTION_KEY}
+      - AUTH_SECRET=${AUTH_SECRET}
+      - SITE_URL=${SITE_URL}
      - DB_CONNECTION_URI=postgres://${POSTGRES_USER}:${POSTGRES_PASSWORD}@db:5432/${POSTGRES_DB}
      - REDIS_URL=redis://redis:6379
-      - SMTP_HOST
-      - SMTP_PORT
-      - SMTP_FROM_NAME
-      - SMTP_USERNAME
-      - SMTP_PASSWORD
-      - SMTP_SECURE=true
-
+      - SMTP_HOST=${SMTP_HOST}
+      - SMTP_PORT=${SMTP_PORT}
+      - SMTP_FROM_ADDRESS=${SMTP_FROM_ADDRESS}
+      - SMTP_FROM_NAME=${SMTP_FROM_NAME}
+      - SMTP_USERNAME=${SMTP_USERNAME}
+      - SMTP_PASSWORD=${SMTP_PASSWORD}

  redis:
    image: redis:7.4.1
-    env_file: .env
    restart: always
-    environment:
-      - ALLOW_EMPTY_PASSWORD=yes
-
    volumes:
      - redis_infisical_data:/data

@@ -60,12 +31,11 @@ services:
    image: postgres:14-alpine
    restart: always
    environment:
-      - POSTGRES_PASSWORD
-      - POSTGRES_USER
-      - POSTGRES_DB
+      - POSTGRES_PASSWORD=${POSTGRES_PASSWORD}
+      - POSTGRES_USER=${POSTGRES_USER}
+      - POSTGRES_DB=${POSTGRES_DB}
    volumes:
      - pg_infisical_data:/var/lib/postgresql/data
-
    healthcheck:
      test: "pg_isready --username=${POSTGRES_USER} && psql --username=${POSTGRES_USER} --list"
      interval: 5s
@@ -75,6 +45,3 @@ services:
 volumes:
  pg_infisical_data:
  redis_infisical_data:
-
-
-
@@ -1,7 +1,7 @@
 {
  "id": "infisical",
  "name": "Infisical",
-  "version": "0.135.0",
+  "version": "0.162.6",
  "description": "All-in-one platform to securely manage application configuration and secrets across your team and infrastructure.",
  "logo": "infisical.jpg",
  "links": {
@@ -3,56 +3,27 @@ main_domain = "${domain}"
 postgres_password = "${password}"
 postgres_user = "infisical"
 postgres_db = "infisical"
+encryption_key = "${hash:32}"
+auth_secret = "${base64:32}"

 [config]
 env = [
-  "ENCRYPTION_KEY=6c1fe4e407b8911c104518103505b218",
-  "AUTH_SECRET=5lrMXKKWCVocS/uerPsl7V+TX/aaUaI7iDkgl3tSmLE=",
+  "ENCRYPTION_KEY=${encryption_key}",
+  "AUTH_SECRET=${auth_secret}",
  "POSTGRES_PASSWORD=${postgres_password}",
  "POSTGRES_USER=${postgres_user}",
  "POSTGRES_DB=${postgres_db}",
-  "SITE_URL=http://${main_domain}:8080",
+  "SITE_URL=http://${main_domain}",
  "SMTP_HOST=",
-  "SMTP_PORT=",
-  "SMTP_NAME=",
+  "SMTP_PORT=587",
+  "SMTP_FROM_ADDRESS=",
+  "SMTP_FROM_NAME=Infisical",
  "SMTP_USERNAME=",
  "SMTP_PASSWORD=",
-  "CLIENT_ID_HEROKU=",
-  "CLIENT_ID_VERCEL=",
-  "CLIENT_ID_NETLIFY=",
-  "CLIENT_ID_GITHUB=",
-  "CLIENT_ID_GITHUB_APP=",
-  "CLIENT_SLUG_GITHUB_APP=",
-  "CLIENT_ID_GITLAB=",
-  "CLIENT_ID_BITBUCKET=",
-  "CLIENT_SECRET_HEROKU=",
-  "CLIENT_SECRET_VERCEL=",
-  "CLIENT_SECRET_NETLIFY=",
-  "CLIENT_SECRET_GITHUB=",
-  "CLIENT_SECRET_GITHUB_APP=",
-  "CLIENT_SECRET_GITLAB=",
-  "CLIENT_SECRET_BITBUCKET=",
-  "CLIENT_SLUG_VERCEL=",
-  "CLIENT_PRIVATE_KEY_GITHUB_APP=",
-  "CLIENT_APP_ID_GITHUB_APP=",
-  "SENTRY_DSN=",
-  "POSTHOG_HOST=",
-  "POSTHOG_PROJECT_API_KEY=",
-  "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=",
-  "SSL_CLIENT_CERTIFICATE_HEADER_KEY=",
 ]
 mounts = []

 [[config.domains]]
 serviceName = "backend"
-port = 8_080
+port = 8080
 host = "${main_domain}"
@@ -1,13 +0,0 @@
-version: "3.8"
-services:
-  spacetimedb:
-    image: clockworklabs/spacetime:v2.6.1
-    restart: unless-stopped
-    command: start
-    ports:
-      - 3000
-    volumes:
-      - spacetimedb-data:/home/spacetime
-
-volumes:
-  spacetimedb-data: {}
@@ -1,45 +0,0 @@
-# SpacetimeDB
-
-SpacetimeDB is a database and server runtime in one: your clients connect directly to the database and your application logic runs inside it as WebAssembly modules. There is no web UI — the domain assigned to this service exposes the SpacetimeDB HTTP/WebSocket API (so opening `/` in a browser returns a plain 404; that is expected).
-
-## Verify the server is running
-
-```bash
-curl -i https://your-domain.com/v1/ping
-```
-
-A `200 OK` response means the server is up.
-
-## Connect with the SpacetimeDB CLI
-
-1. Install the CLI on your local machine:
-
-   ```bash
-   curl -sSf https://install.spacetimedb.com | sh
-   ```
-
-2. Register your Dokploy instance as a server and make it the default:
-
-   ```bash
-   spacetime server add --url https://your-domain.com dokploy --default
-   ```
-
-3. Log in (or create an anonymous local identity) and publish a module:
-
-   ```bash
-   spacetime login
-   spacetime publish --server dokploy my-database
-   ```
-
-4. Check connectivity at any time:
-
-   ```bash
-   spacetime server ping dokploy
-   ```
-
-From your game or app, connect with any SpacetimeDB client SDK (Rust, C#, TypeScript) using `https://your-domain.com` as the host URI. See the [getting started guide](https://spacetimedb.com/docs/getting-started) for a full walkthrough.
-
-## Notes
-
- All server state (databases, logs and the JWT signing keys used for identities) is persisted in the `spacetimedb-data` volume, so identities survive restarts and upgrades.
- Client connections use WebSockets over the same domain; no extra configuration is needed.
@@ -1,17 +0,0 @@
-{
-  "id": "spacetimedb",
-  "name": "SpacetimeDB",
-  "version": "v2.6.1",
-  "description": "SpacetimeDB is a relational database with a built-in server runtime. Clients connect directly to the database and run server-side logic (modules) inside it, making it ideal for real-time multiplayer games, chat and collaborative applications without a separate backend.",
-  "logo": "logo.png",
-  "links": {
-    "github": "https://github.com/clockworklabs/SpacetimeDB",
-    "website": "https://spacetimedb.com/",
-    "docs": "https://spacetimedb.com/docs"
-  },
-  "tags": [
-    "database",
-    "realtime",
-    "backend"
-  ]
-}
@@ -1,8 +0,0 @@
-[variables]
-main_domain = "${domain}"
-
-[config]
-[[config.domains]]
-serviceName = "spacetimedb"
-port = 3000
-host = "${main_domain}"