Guest User

Untitled

a guest
Feb 16th, 2026
23
0
Never
4
Not a member of Pastebin yet? Sign Up, it unlocks many cool features!
text 5.70 KB | None | 0 0
  1. services:
  2. zitadel:
  3. restart: unless-stopped
  4. image: ghcr.io/zitadel/zitadel:latest
  5. command: start-from-init --masterkey "xxxxxxxxx"
  6. environment:
  7. # See "What's next" to learn about how to serve Zitadel on a different domain or IP.
  8. ZITADEL_EXTERNALDOMAIN: auth.xxxxx.com
  9. ZITADEL_EXTERNALPORT: 443
  10.  
  11. # See "What's next" to learn about how to enable TLS.
  12. ZITADEL_EXTERNALSECURE: true
  13. ZITADEL_TLS_ENABLED: false
  14.  
  15. # Database connection settings.
  16. ZITADEL_DATABASE_POSTGRES_HOST: db
  17. ZITADEL_DATABASE_POSTGRES_PORT: 5432
  18. # The database is created by the init job if it does not exist.
  19. ZITADEL_DATABASE_POSTGRES_DATABASE: zitadel
  20. # The admin user must already exist in the database.
  21. ZITADEL_DATABASE_POSTGRES_ADMIN_USERNAME: postgres
  22. ZITADEL_DATABASE_POSTGRES_ADMIN_PASSWORD: postgres
  23. ZITADEL_DATABASE_POSTGRES_ADMIN_SSL_MODE: disable
  24. # The zitadel user is created by the init job if it does not exist.
  25. ZITADEL_DATABASE_POSTGRES_USER_USERNAME: zitadel
  26. ZITADEL_DATABASE_POSTGRES_USER_PASSWORD: zitadel
  27. ZITADEL_DATABASE_POSTGRES_USER_SSL_MODE: disable
  28.  
  29. # By configuring a login application, the setup job creates a user of type machine with the role IAM_LOGIN_CLIENT.
  30. # It writes a PAT to the path specified in ZITADEL_FIRSTINSTANCE_LOGINCLIENTPATPATH.
  31. # The PAT is passed to the login container via the environment variable ZITADEL_SERVICE_USER_TOKEN_FILE.
  32. ZITADEL_FIRSTINSTANCE_LOGINCLIENTPATPATH: /current-dir/login-client.pat
  33. ZITADEL_FIRSTINSTANCE_ORG_HUMAN_PASSWORDCHANGEREQUIRED: false
  34. ZITADEL_FIRSTINSTANCE_ORG_LOGINCLIENT_MACHINE_USERNAME: login-client
  35. ZITADEL_FIRSTINSTANCE_ORG_LOGINCLIENT_MACHINE_NAME: Automatically Initialized IAM_LOGIN_CLIENT
  36. ZITADEL_FIRSTINSTANCE_ORG_LOGINCLIENT_PAT_EXPIRATIONDATE: '2029-01-01T00:00:00Z'
  37. # Activate the login v2 on an installation from scratch.
  38. # To activate the login v2 on an existing installation, read the "What's next" section.
  39. ZITADEL_DEFAULTINSTANCE_FEATURES_LOGINV2_REQUIRED: false # To use the login v1, set this to false.
  40. ZITADEL_DEFAULTINSTANCE_FEATURES_LOGINV2_BASEURI: https://auth.xxxxx.com/ui/v2/login/
  41. # Configure the redirection paths to the login v2.
  42. ZITADEL_OIDC_DEFAULTLOGINURLV2: https://auth.xxxxx.com/ui/v2/login/login?authRequest=
  43. ZITADEL_OIDC_DEFAULTLOGOUTURLV2: https://auth.xxxxx.com/ui/v2/login/logout?post_logout_redirect=
  44. ZITADEL_SAML_DEFAULTLOGINURLV2: https://authxxxxx.com/ui/v2/login/login?samlRequest=
  45.  
  46. # By configuring a machine, the setup job creates a user of type machine with the role IAM_OWNER.
  47. # It writes a personal access token (PAT) to the path specified in ZITADEL_FIRSTINSTANCE_PATPATH.
  48. # The PAT can be used to provision resources with [Terraform](/guides/manage/terraform-provider), for example.
  49. # ZITADEL_FIRSTINSTANCE_PATPATH: /current-dir/admin.pat
  50. # ZITADEL_FIRSTINSTANCE_ORG_MACHINE_MACHINE_USERNAME: admin
  51. # ZITADEL_FIRSTINSTANCE_ORG_MACHINE_MACHINE_NAME: Automatically Initialized IAM_OWNER
  52. # ZITADEL_FIRSTINSTANCE_ORG_MACHINE_PAT_EXPIRATIONDATE: '2029-01-01T00:00:00Z'
  53.  
  54. # To change the initial human admin users username and password, uncomment the following lines.
  55. # The first login name is formatted like this: <username>@<org_name>.<external_domain>
  56. # With the following incommented configuration, this would be [email protected]
  57. # Visit http://localhost:8080/ui/console to check if the login name works.
  58. # If you can't log in, check the available login names:
  59. # echo "select * from projections.login_names3;" | psql -h localhost -U postgres -d zitadel
  60. # The postgres users password is postgres.
  61. ZITADEL_FIRSTINSTANCE_ORG_NAME: XXXX
  62. ZITADEL_FIRSTINSTANCE_ORG_HUMAN_USERNAME: root
  63. ZITADEL_FIRSTINSTANCE_ORG_HUMAN_PASSWORD: RootPassword1!
  64.  
  65. # Enable debug logs
  66. # ZITADEL_LOG_LEVEL: debug
  67. # Write Access Logs to stdout.
  68. # ZITADEL_LOGSTORE_ACCESS_STDOUT_ENABLED: true
  69. hostname: zitadel
  70. healthcheck:
  71. test:
  72. - CMD
  73. - /app/zitadel
  74. - ready
  75. interval: 10s
  76. timeout: 60s
  77. retries: 5
  78. start_period: 10s
  79. user: "0"
  80. volumes:
  81. - .:/current-dir:delegated
  82. networks:
  83. - zitadel
  84. - proxied
  85. depends_on:
  86. db:
  87. condition: service_healthy
  88.  
  89. login:
  90. restart: unless-stopped
  91. hostname: zitadellogin
  92. image: ghcr.io/zitadel/zitadel-login:latest
  93. # If you can't use the network_mode service:zitadel, you can pass the environment variables ZITADEL_API_URL=http://zitadel:8080 and CUSTOM_REQUEST_HEADERS=Host:localhost instead.
  94. environment:
  95. - ZITADEL_API_URL=http://zitadel:8080
  96. - NEXT_PUBLIC_BASE_PATH=/ui/v2/login
  97. - ZITADEL_SERVICE_USER_TOKEN_FILE=/current-dir/login-client.pat
  98. - USTOM_REQUEST_HEADERS=Host:auth.xxxxx.com
  99. networks:
  100. - zitadel
  101. - proxied
  102. user: "0"
  103. volumes:
  104. - .:/current-dir:ro
  105. depends_on:
  106. zitadel:
  107. condition: service_healthy
  108. restart: false
  109.  
  110. db:
  111. restart: unless-stopped
  112. image: postgres:17
  113. environment:
  114. PGUSER: postgres
  115. POSTGRES_PASSWORD: postgres
  116. healthcheck:
  117. test:
  118. - CMD-SHELL
  119. - pg_isready
  120. - -d
  121. - zitadel
  122. - -U
  123. - postgres
  124. interval: 10s
  125. timeout: 30s
  126. retries: 5
  127. start_period: 20s
  128. networks:
  129. - zitadel
  130. ports:
  131. - 5432:5432
  132. volumes:
  133. - 'data:/var/lib/postgresql/data:rw'
  134.  
  135. networks:
  136. zitadel:
  137. proxied:
  138. external: true
  139.  
  140. volumes:
  141. data:
Advertisement
Comments
  • User was banned
  • User was banned
  • User was banned
  • User was banned
Add Comment
Please, Sign In to add comment