Taskforce.sh on-premises
Run the Taskforce.sh dashboard for BullMQ and Bull on your own infrastructure, with Docker or on AWS. Same features as the hosted version, with unlimited connections and teams, and your queue data never leaves your network.
Two ways to deploy
Both run the same dashboard and use the same license.
Docker
A Docker image from the private registry at docker.taskforce.sh, for any platform that runs containers, such as Kubernetes, ECS or a single server with Docker Compose. You can run several instances behind a load balancer.
AWS Marketplace
An AMI from AWS Marketplace, with a configuration service for the initial setup. To upgrade, launch the new AMI and switch the load balancer to it.
Requirements
The dashboard relies on a few services that you provide. None of them needs to be large.
PostgreSQL and Redis
PostgreSQL stores all persistent data; a minimal instance is enough. A Redis 7.0 or newer instance of about 128 MB is used for monitoring and internal communication.
Auth0 and HTTPS
Users sign in through your own Auth0 application, and the free plan is enough. Auth0 requires the dashboard to be served over HTTPS.
Mailgun
Used to send alerts and team invitations by email. The free plan is often enough.
On-premises or hosted?
Both have the same features. The difference is who runs the dashboard.
Choose on-premises when
- Queue data must stay inside your own network.
- You need more connections or teams than the hosted plans offer.
- Your organization requires self-hosted tools.
On-premises questions
Can't find an answer? Get in touch.
Yes. The Docker image has the same functionality as the hosted version at taskforce.sh, with unlimited connections and teams.
A PostgreSQL database for persistent data, a Redis 7.0 or newer instance, an Auth0 application for sign in (the free plan is enough), a Mailgun account for email notifications, and HTTPS in front of the dashboard, which Auth0 requires.
No. The container validates its license with taskforce.sh when it starts and every 15 minutes, and stops after 5 failed checks in a row. Your queue data stays in your network; only the license is checked.
Subscribe to an on-premises license from the Subscriptions page of your Taskforce.sh account. The license key then appears in the Enterprise section of your account, and gives access to the private Docker registry. For a trial, contact us.
All persistent data lives in your PostgreSQL database. With Docker, run the new image version with the same configuration. On AWS, launch the new AMI and switch the load balancer to it, as described in Upgrading.
With Docker, you can run several instances behind a load balancer. On AWS you can currently configure one instance per region; contact us if you need more.
