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

Using the taskforce connector

PreviousDocker composeNextSecurity primer

Last updated 2 years ago

Was this helpful?

When your on-premises instance is running, you can connect to your Redis instances either by creating direct connections, but also using the

By default the connector will try to connect to the SaaS version of Taskforce.sh. But when we are running an on-premises instance we need to specify the websocket address hosting the api. For this you should use the "-b" argument. For example, assuming your instance is running at "https://my.taskforce.domain":

taskforce -b wss://my.taskforce.domain -t my-token-xxx
taskforce-connector.