don't have the best grasp of Docker but the image appears
to serve up a functioning layerindex.
Signed-off-by: Diana Thayer
---
Dockerfile | 10 --
README | 10 +-
TODO| 1 -
layerindex/tasks.py | 24
layer
don't have the best grasp of Docker but the image appears
to serve up a functioning layerindex.
Signed-off-by: Diana Thayer
---
Dockerfile | 18 --
README | 10 +-
TODO| 1 -
layerindex/tasks.py
When a user submits a layer, notification emails are sent to users
with a certain permission. Superusers technically have all
permissions, but Q ignores them currently so that such emails
are not sent to superusers. This patch expands the check to
include superusers.
A few folks have discussed inc
pdates the 'edit_layer_view' function to send
emails to administrators about new and updated layers asynchronously,
and modifies the 'settings.py' to include a default configuration
for a RabbitMQ connection.
Signed-off-by: Diana Thayer
---
README | 10 +-
TODO
w and updated layers asynchronously,
and modifies the 'settings.py' to include a default configuration
for a RabbitMQ connection.
Signed-off-by: Diana Thayer
---
README | 10 +-
TODO| 1 -
layerindex/tasks.py | 24
layerindex/views.py
This patch adds asynchronous task execution using a Celery backend
and RabbitMQ task queue.
It updates the README to reflect the installation and configuration
of a basic RabbitMQ setup, adds a 'tasks.py' file to contain task
definitions, updates the 'edit_layer_view' function to send
emails to ad
Hello! Did you get a chance to look at the PR
<https://github.com/garbados/layerindex-web/pull/1>?
On Wed, Jul 26, 2017 at 6:02 PM, Diana Thayer wrote:
> Great! Thanks for testing it out and identifying that issue.
>
> I've put together a PR on GitHub
> <https://gith
Configuring a development environment for the project can be non-obvious.
This WIP patch updates the readme and includes example dev settings
in "dev_settings.py" which can be used (hopefully) in a general case
to get new contributors into a development environment quickly.
Signed-off
7 4:15:26 PM CEST Paul Eggleton wrote:
> > On Tuesday, 27 June 2017 1:59:23 AM CEST Diana Thayer wrote:
> > > This is a work-in-progress solution to issue 11197 within
> layerindex-web:
> > > adding asynchronous task execution.
> > > I used RabbitMQ and Cel
Hello!
This is a work-in-progress solution to issue 11197 within layerindex-web:
adding asynchronous task execution.
I used RabbitMQ and Celery. I'm still working with Paul Eggleton on adding
install instructions for RabbitMQ to
the site's Dockerfile.
Previously, when a user submitted a layer,
- updated readme to include RabbitMQ as a dependency
- updated settings.py to include RABBIT_BROKER and RABBIT_BACKEND
- added celery to requirements.txt
- defined celery tasks in layerindex/tasks.py
- separated layerindex/update#main into two functions: main (which parses
sys.argv) and do_update
Hello!
This is a work-in-progress solution to issue 11197 within layerindex-web:
adding asynchronous task execution.
I used RabbitMQ and Celery. I'm still working with Paul Eggleton on adding
install instructions for RabbitMQ to
the site's Dockerfile.
Previously, when a user submitted a layer,
12 matches
Mail list logo
