Taskforce.sh
  • Documentation
  • Getting started
    • Direct Redis Connection
    • Taskforce connector
  • Account
    • Settings
  • Connections
    • Queues
    • Jobs
    • Workers
  • Metrics
  • Monitoring
    • Enable notifications
      • Slack
      • Pagerduty
    • Connection monitor
    • Failed jobs monitor
    • Missing workers monitor
    • Max Memory monitor
    • Backlog Monitor
  • Alerts
  • Organizations
  • BullMQ Pro
    • Connector Pro
  • On Premises
    • AWS
      • Launch AWS AMI.
      • Create role with SSM permissions
      • Assign SSM Role
      • Configure your instance
        • Create a PostgreSQL instance
        • Configure Auth0
          • Configure API
        • Configure Mailgun
      • Setup loadbalancer
      • Setup route 53
      • Monitors
      • Upgrading
      • Troubleshooting
    • Docker
      • Docker registry
      • Environment variables
      • Docker compose
    • Using the taskforce connector
  • Security primer
  • Troubleshooting
Powered by GitBook
On this page

Was this helpful?

  1. On Premises
  2. Docker

Docker compose

PreviousEnvironment variablesNextUsing the taskforce connector

Last updated 1 year ago

Was this helpful?

In order to facilitate the initial installation of the dashboard, please refer to this compose file that you can run locally to check that everything is running, just note that if you run the containers in localhost, you will need to configure accordingly.

services:
  backend:
    image: docker.taskforce.sh/onprem/dashboard:1.0.0
    restart: always
    ports:
      - "9876:9876"
    environment:
      LICENSE_KEY: ${LICENSE_KEY}
      HOST: ${HOST}
      POSTGRES_HOST: postgres
      POSTGRES_PASSWD: ${POSTGRES_PASSWORD}
      POSTGRES_DB: ${POSTGRES_DB}
      AUTH0_CLIENTID: ${AUTH0_CLIENTID}
      AUTH0_DOMAIN: ${AUTH0_DOMAIN}
      AUTH0_AUDIENCE: ${AUTH0_AUDIENCE}
      REDIS_URL: redis://redis:6379
      MAILGUN_DOMAIN: ${MAILGUN_DOMAIN}
      MAILGUN_API_KEY: ${MAILGUN_API_KEY}

  postgres:
    image: postgres:latest
    expose:
      - "5432"
    restart: always
    ports:
      - "5432:5432"
    environment:
      POSTGRES_PASSWORD: ${POSTGRES_PASSWORD}
      POSTGRES_USER: ${POSTGRES_USER}
      POSTGRES_DB: ${POSTGRES_DB}

  redis:
    image: redis:latest
    restart: always
    ports:
      - "6379:6379"

As soon as the instance is up and running, you could try to use the to expose the Redis instance that is running in docker to your Taskforce.sh instance. Then you should be able to see the "" queue that handles the monitor checks and alerts for the rest of your connections.

Auth0
taskforce-connector
monitoring