We're stable! v1.0.1

backend/pyproject.toml

@@ -4,7 +4,7 @@
 [tool.poetry]
 name = "backend"
 # name = "qaboard" # used to be backend, poetry issues..
-version = "0.3.0"
+version = "1.0.1"
 description = "Backend for QA-Board"
 authors = ["Arthur Flam <[email protected]>"]
 license="Apache-2.0"

qaboard/__init__.py

@@ -1,5 +1,5 @@
 # need to be update setup.py as well
-__version__ = '0.8.13'
+__version__ = '1.0.1'
 from .check_for_updates import check_for_updates
 check_for_updates()
 

setup.py

@@ -16,7 +16,7 @@
 
 setup(
   name='qaboard',
-  version="0.8.13", # __version__ needs to be updated in qaboard/__init__.py as well
+  version="1.0.1", # __version__ needs to be updated in qaboard/__init__.py as well
   license="Apache-2.0",
 
   url="https://github.com/Samsung/qaboard",

website/docs/celery-integration.md

@@ -55,6 +55,9 @@ qa batch --runner=local my-batch
 
 Note that unless you have a transparent shared storage for your working directory, you'll need to use `qa --share batch` to see runs in QA-Board...
 
+## Monitoring
+- A [`flower`](https://flower.readthedocs.io/en/latest/) instance is available at `<QABOARD_HOST>/flower`
+- Read the [docs](http://docs.celeryproject.org/en/latest/userguide/monitoring.html).
 ## Advanced Celery Configuration 
 To configure Celery at the **project level**:
 
@@ -98,5 +101,3 @@ Read [Celery's tutorial](http://docs.celeryproject.org/en/latest/getting-started
 :::
 
 Celery's [worker user guide](https://docs.celeryproject.org/en/stable/userguide/workers.html) has lots of information on how to run [worker in the background](https://docs.celeryproject.org/en/stable/userguide/daemonizing.html#daemonizing), set [concurrency](https://docs.celeryproject.org/en/stable/userguide/workers.html#concurrency)... Check it out too as needed!
-
-If you need worker monitoring, read the [docs](http://docs.celeryproject.org/en/latest/userguide/monitoring.html).