Getting Kue working on Heroku

100%

Getting Kue working on Heroku

✓ Published0🌍 Public

Last edited Sep 29, 2011

Created on Sep 26, 2011

This example shows how to run a Kue job queue on Heroku with separate web and worker processes. The web server, built with Express, creates a job on an HTTP request, while the worker processes it using `jobs.process`. Both the web app and the consumer connect to a RedisToGo instance by overriding `kue.redis.createClient` to parse the `REDISTOGO_URL`, and the `Procfile` defines the process types that Heroku scales independently.

AI-generated description

Workers can be activated with heroku scale:

heroku scale web=1 worker=1

Each process is $0.05/hr (or about $35/month).

You'll need a Redis instance. For RedisToGo you need a mini or higher to accept two connections AFAICS. Not sure what the upper limit is on workers yet.

heroku addons:add redistogo:mini

A mini instance is just $5 a month and should be billed by the second. To remove, do:

heroku addons:remove redistogo

Similar vizzes

Loading thumbnail…

generating SSL keys and Certificate Signing Requests for Heroku / Nginx / RapidSSL

This example shows a step-by-step terminal transcript of generating an SSL key and certificate signing request, then unlocking, combining, and uploading the certificate to Heroku. The process uses the OpenSSL command-line API (`openssl genrsa`, `openssl req`, `openssl rsa`, `cat` for concatenation) and Heroku’s CLI (`heroku ssl:add`, `heroku addons:add`). The text-based log traces the flow from key creation through DNS activation, with shell prompts and command outputs as the visual data.

RRandomEtc

51% match

Loading thumbnail…

NodeJS GAE Issue Reproduction

This example shows a Node.js application configured for deployment on Google App Engine, with a focus on reproducing an issue across multiple microservices. It demonstrates how the project orchestrates separate services—such as a gateway, user service, and add-message service—using npm scripts that set environment variables and ports. The code relies on Express for routing, Babel for ES2015 transpilation, and PM2 for process management, while testing uses Mocha, Chai, and Supertest. The visualization highlights the deployment and development workflow, showing how build commands and service-specific start scripts manage the multi-service architecture.

55un

48% match

Loading thumbnail…

Gist fa674a3db25bd721df50e36efa7736b3

This example demonstrates a Dockerized React application configured for development, testing, and production deployment using Dockerfiles and docker-compose. The development setup mounts source code as a volume, enables live reload, and runs tests via a separate service, while the production build uses a multi-stage Dockerfile that compiles the app with `npm run build` and serves static files through Nginx. Travis CI automates the pipeline, building the Docker image, running tests with `npm run test -- --coverage`, and deploying to AWS Elastic Beanstalk. The code leverages React’s development server and Node’s Alpine image for a lightweight containerized workflow, though no external data-viz libraries appear in this configuration.

HHuyAms

47% match

Loading thumbnail…

Work-at-home Challenge for Blue Bottle Coffee DevOps Engineer

This example visualizes the DevOps challenge workflow for a Blue Bottle Coffee engineering role, showing the sequential stages of S3 bucket manipulation, directory-tree microservice generation, monitoring, containerization, and deployment. The code uses the AWS SDK for JavaScript to interact with S3 buckets and Redis for key-value storage, while the visualization maps the tree command output and JSON file handling steps. It highlights the integration of SNS/SQS for upload monitoring and Terraform for infrastructure provisioning, with Docker and ECS for virtualized state persistence. The rendering approach relies on d3.js to illustrate the branching logic and data flow across the pipeline.

BBBischof

47% match

Loading thumbnail…

Express authentication using Redis for session store and Couchdb for database (in coffeescript!)

This example demonstrates user authentication and session management in a CoffeeScript-built Express application, showing how login, signup, and logout routes handle password hashing and session regeneration. The code uses Redis as the session store via `connect-redis` and CouchDB for user persistence through the `couchdb` client, with CSRF protection from `express-csrf` and password salting via `hash.sha1`. The visualization highlights the request flow across these middleware and database calls, including error handling for duplicate users and failed logins, while relying on the Fugue cluster for deployment.

AAnsonT

47% match

Loading thumbnail…

Running Flask with Gunicorn

This example shows how to integrate a Flask application into a custom Gunicorn server by subclassing `gunicorn.app.base.BaseApplication`. It defines a Flask app with a single `/` route that renders `index.html`, then passes that app to a `StandaloneApplication` class, which overrides `load_config` and `load` to apply runtime options. The server binds to `127.0.0.1:8080` and sets the worker count using `multiprocessing.cpu_count()`. The code demonstrates the required structure for launching Flask via Gunicorn’s custom WSGI interface, relying on the `gunicorn.six.iteritems` helper for configuration handling.

KKatiRG

45% match

Loading thumbnail…

[heroku] Error when upgrading prod app form cedar to cedar-14 (no error on the staging app)

This example visualizes the deployment error logs from a Heroku app upgrade from Cedar to Cedar-14, contrasting the failing production app with a successful staging app. It uses a gist-sourced log file to display the repeated `ValueError: unsupported hash type` and `ImportError` messages during the Python build process. The visualization likely employs a scrollable or annotated text-rendering approach, highlighting the repetitive stack traces and error patterns. The rendering may use d3 or a custom log parser to structure the raw log entries into a readable, categorized display emphasizing the cascade of hash-related failures.

EEleonore9

45% match

Loading thumbnail…

Gist eeac85f83bbc682a4f2d

This example demonstrates how to run a simple inline Web Worker that greets a user by name, with a fallback to executing the worker script on the main thread when the browser lacks necessary APIs. It uses a `<script type="javascript/worker">` block for the worker code and the `runWorkerJs` helper, which checks for `Blob`, `BlobBuilder`, `URL.createObjectURL`, and `Worker` support. If those are available, it creates a worker from the script’s text and posts a parameter object; otherwise, it evals the script in a proxy scope. The result updates the page body text.

PPhilippe Rivière

44% match