mjhea0/flask-redis-queue

Example of how to handle background processes with Flask, Redis Queue, and Docker

Flask Redis Queue

Example of how to handle background processes with Flask, Redis Queue, and Docker

Quick Start

Spin up the containers:

$ docker-compose up -d --build

Open your browser to http://localhost:5004

flask-redis-queue's Issues

ID is the same for the list of task

Am I experience a bug?
Why the id is all the same?
Thanks!

add better error handling

Add error handlers on both the client in the AJAX requests as well as on the server for failed jobs.

Web repository does not exists

On using docker-compose up, it tries to pull web image which is not there and stops.

Pulling worker (web:)...
ERROR: pull access denied for web, repository does not exist or may require 'docker login'

how to deploy to kubernetes

I looking same on kubernetes cluster.
Let me know if you have any suggestion

Adding nginx and gunicorn configuration to docker-compose.yml

Could you show how to handle this additional service inside docker-compose?

Render template after Job finishes

Hi Michael, is it possible to pass the data back from ajax to flask view and render a template with a different URL? I want to check when the jobs are done, display a loading page, and then render the home.html with the results of the job.

Debugging the app

I am trying to extend this template for my usecase.

Can you suggest an easy route for debugging the app, potentially with a capability to apply a breakpoint etc., maybe using VS code?

Project doesn't run with the specified version of flask in requirements file

When you try to build the docker image using the provided docker-compose configuration file, the build will fail and exit with an error clearly caused by incompatibility with werkzeug package as the trace show:
ImportError: cannot import name 'url_quote' from 'werkzeug.urls'.

I've managed to fix it by just upgrading flask version to Flask==2.3.3 which is the latest version in 2.x.x series.