Taskforce Connector

This small service allows you to connect queues to Taskforce acting as a proxy between your queues and the UI. It is useful for connecting local development queues as well as production grade queues without the need of sharing passwords or establishing SSH tunnels.

Currently the connector supports Bull queues, with more to come in later releases.

The connector is designed to be lightweight and using a minimal set of resources from the local queues.

Install

Using yarn

yarn global add taskforce-connector

Using npm:

npm install -g taskforce-connector

Usage

Call the tool and get a help on the options:

✗ taskforce --help

  Usage: taskforce [options]


  Options:

    -V, --version               output the version number
    -n, --name [name]           connection name [My Connection] (default: "My Connection")
    -t, --token [token]         api token (get yours at https://taskforce.sh)
    -p, --port [port]           redis port [6379] (default: "6379")
    --tls [tls]                 (default: "Activate secured TLS connection to Redis")
    -h, --host [host]           redis host [localhost] (default: "localhost")
    -d, --database [db]         redis database [0] (default: "0")
    --passwd [passwd]           redis password
    -u, --uri [uri]             redis uri
    --team [team]               specify team where to put the connection
    -b, --backend [host]        backend domain [api.taskforce.sh] (default: "wss://api.taskforce.sh")
    -s, --sentinels [host:port] comma-separated list of sentinel host/port pairs
    -m, --master [name]         name of master node used in sentinel configuration
    -h, --help                  output usage information

Example:

✗ taskforce -n "transcoder connection" -t 2cfe6a1b-5f0e-466f-99ad-12f51bea79a7

The token 2cfe6a1b-5f0e-466f-99ad-12f51bea79a7 is a private token that can be retrieved at your Taskforce account.

After running the command, you should be able to see the connection appear automatically on the dashboard.

Sentinel Example:

✗ taskforce -n "transcoder connection" -t 2cfe6a1b-5f0e-466f-99ad-12f51bea79a7 -s sentinel1.mydomain:6379,sentinel2.mydomain:6379 -m mymaster

Note: You can also specify the following with environment variables.

token     TASKFORCE_TOKEN
port      REDIS_PORT
host      REDIS_HOST
password  REDIS_PASSWD
uri       REDIS_URI
sentinels REDIS_SENTINELS
master    REDIS_MASTER

Secured TLS Connections

Services that support TLS can also be used using the connector, use the --tls flag. Note that some services such as Heroku expects the port number to be "one more" than the normal unencrypted port read more.

Teams

You can use the connector to spawn queue connections to any team that you created on your organization, just pass the team name as an option:

✗ taskforce -n "transcoder connection" -t 2cfe6a1b-5f0e-466f-99ad-12f51bea79a7 --team "my awesome team"

Use as a library

It is also possible to add the connector as a library:

As a commonjs dependency:

const { Connect } = require("taskforce-connector");

const taskforceConnection = Connect("my connection", "my token", {
  host: "my redis host",
  port: "my redis port",
  password: "my redis password",
});

or as a es6 module:

import { Connect } from "taskforce-connector";

const taskforceConnection = Connect("my connection", "my token", {
  host: "my redis host",
  port: "my redis port",
  password: "my redis password",
});

fairhopeweb / taskforce-connector Goto Github PK