docker-compose.yaml

volumes:
  stormkit:
  redis:
  psql:

services:
  db:
    image: postgres
    restart: always
    ports:
      - published: 5432
        target: 5432
    environment:
      - POSTGRES_DB=${POSTGRES_DB}
      - POSTGRES_USER=${POSTGRES_USER}
      - POSTGRES_PASSWORD=${POSTGRES_PASSWORD}
    volumes:
      - psql:/var/lib/postgresql/data

  redis:
    container_name: redis
    image: redis:6.2.12
    restart: always
    ports:
      - published: 6379
        target: 6379
    volumes:
      - redis:/data

  redis-monitoring:
    image: hibiken/asynqmon
    ports:
      - published: 8086
        target: 8086
    environment:
      - PORT=8086
      - REDIS_ADDR=redis:6379

  workerserver:
    image: ghcr.io/stormkit-io/workerserver:latest
    restart: always
    container_name: workerserver
    volumes:
      # Share deployments folder between workerserver and hosting.
      # Deployments will be executed in the workerserver, and the artifacts
      # are shared with the hosting service through this shared folder.
      # This can be removed when using another service for deployments,
      # such as GitHub actions or other CI/CD platforms.
      - stormkit:/shared
    environment:
      - NODE_VERSION=22

      # This is the domain that will be used to create the endpoints.
      # For instance, for example.org, Stormkit creates these endpoints:
      #
      # health.example.org    => an endpoint to verify the service is up and running
      # api.example.org       => the api service that Stormkit uses
      # stormkit.example.org  => the user interface to access your applications
      # *.example.org         => development endpoints
      #
      # NOTE: This is not the domain that you'd like to host. You configure those from
      # the Stormkit UI.
      - STORMKIT_DOMAIN=${STORMKIT_DOMAIN}

      # The application secret that is used to encrypt/decrypt sensitive data.
      # Do not expose this.
      - STORMKIT_APP_SECRET=${STORMKIT_APP_SECRET}

      # If you'd like to bring your own, external runner for deployments, configure
      # this variable. Defaults to `local`. Possible values are: `github` (more services can be added on demand.)
      - STORMKIT_DEPLOYER_SERVICE=${STORMKIT_DEPLOYER_SERVICE:-local}

      # The maximum number of deployments that can run in parallel.
      # If you are running on a single server, we suggest keeping this number low.
      - STORMKIT_RUNNER_CONCURRENCY=1

      # When `STORMKIT_DEPLOYER_SERVICE` is `github`, this variable is needed to
      # trigger the GitHub Action.
      - GITHUB_APP_TOKEN=${GITHUB_APP_TOKEN:-}

      # Variables to access the PostgreSQL database
      - POSTGRES_HOST=${POSTGRES_HOST}
      - POSTGRES_PORT=${POSTGRES_PORT}
      - POSTGRES_DB=${POSTGRES_DB}
      - POSTGRES_USER=${POSTGRES_USER}
      - POSTGRES_PASSWORD=${POSTGRES_PASSWORD}

      # Variable(s) to access Redis
      - REDIS_ADDR=${REDIS_ADDR}

  hosting:
    image: ghcr.io/stormkit-io/hosting:latest
    restart: always
    container_name: hosting
    # Needed only when using a FileSys Deployment
    volumes:
      # Same as workerserver. Read above for more information.
      - stormkit:/shared
    environment:
      # Specifying this variable will tell the container to install Node.js
      # which is needed only if you're using serverless functions or server
      # commands in a VM. If you're hosting Stormkit in a cloud
      # provider such as AWS or Alibaba Cloud, and you're using only serverless
      # functionas, then you may not need installing Node.js as you can use their
      # cloud-native serverless services (such as Lambda or Function Compute).
      - NODE_VERSION=22

      # See Workerserver configuration for these environment variables' documentation.
      - STORMKIT_DOMAIN=${STORMKIT_DOMAIN}
      - STORMKIT_APP_SECRET=${STORMKIT_APP_SECRET}
      - STORMKIT_DEPLOYER_SERVICE=${STORMKIT_DEPLOYER_SERVICE:-local}
      - POSTGRES_HOST=${POSTGRES_HOST}
      - POSTGRES_PORT=${POSTGRES_PORT}
      - POSTGRES_DB=${POSTGRES_DB}
      - POSTGRES_USER=${POSTGRES_USER}
      - POSTGRES_PASSWORD=${POSTGRES_PASSWORD}
      - REDIS_ADDR=${REDIS_ADDR}

      ####################################################################################
      #                                                                                  #
      # Configure these variables when `STORMKIT_DEPLOYER_SERVICE` is other than `local` #
      #                                                                                  #
      ####################################################################################

      # When `STORMKIT_DEPLOYER_SERVICE` is `github`, this variable is needed to stop the GitHub Action.
      - GITHUB_APP_TOKEN=${GITHUB_APP_TOKEN:-}

      # The access and secret key used by the external runner.
      - STORMKIT_RUNNER_SECRET_KEY=${STORMKIT_RUNNER_SECRET_KEY:-}
      - STORMKIT_RUNNER_ACCESS_KEY=${STORMKIT_RUNNER_ACCESS_KEY:-}

      ##################################################################
      #                                                                #
      # Configure these variables when Authentication method is GitHub #
      #                                                                #
      ##################################################################

      # The account name
      - GITHUB_APP_NAME=${GITHUB_APP_NAME:-}

      # This is your GitHub App ID. This can be found under the General tab of your GitHub App page.
      - GITHUB_APP_ID=${GITHUB_APP_ID:-}

      # The client secret generated after creating the GitHub App.
      - GITHUB_SECRET=${GITHUB_SECRET:-}

      # The GitHub App client ID. This can be found under the General tab of your GitHub App page.
      - GITHUB_CLIENT_ID=${GITHUB_CLIENT_ID:-}

      # The Base64 encoded private key generated previously after creating the GitHub App.
      # You can use `openssl` to encode your string:
      #
      # cat my-key.pem | openssl base64 -A
      #
      # Make sure to enclose your variable with quotes.
      - GITHUB_PRIV_KEY=${GITHUB_PRIV_KEY:-}

      #########################################################################################
      #                                                                                       #
      # Configure these variables when Authentication method is BitBucket                     #
      # See: https://support.atlassian.com/bitbucket-cloud/docs/use-oauth-on-bitbucket-cloud/ #
      #                                                                                       #
      #########################################################################################

      - BITBUCKET_SECRET=${BITBUCKET_SECRET:-}
      - BITBUCKET_CLIENT_ID=${BITBUCKET_CLIENT_ID:-}

      ###################################################################
      #                                                                 #
      # Configure these variables when Authentication method is GitLab  #
      # See: https://docs.gitlab.com/ee/integration/oauth_provider.html #
      #                                                                 #
      ###################################################################

      - GITLAB_SECRET=${GITLAB_SECRET:-}
      - GITLAB_CLIENT_ID=${GITLAB_CLIENT_ID:-}

    ports:
      - mode: ingress
        target: 80
        published: 80
        protocol: tcp
      - mode: ingress
        target: 443
        published: 443
        protocol: tcp