Package: rq-scheduler-dashboard
rq-scheduler-dashboardis a copy of rq-dashboard for rq-scheduler jobs,
based on the code from this PR:https://github.com/ducu/rq-dashboard/pull/95.
This just wraps the code from @helenst into a separate package.It looks like thisInstalling$pipinstallrq-scheduler-dashboardRunning the dashboardRun the dashboard standalone, like this:$rq-scheduler-dashboard* Running on http://127.0.0.1:9181/
...$rq-scheduler-dashboard--helpUsage: rq-scheduler-dashboard [OPTIONS]

  Run the RQ Scheduler Dashboard Flask server.

  All configuration can be set on the command line or through environment
  variables of the form RQ_SCHEDULER_DASHBOARD_*. For example RQ_SCHEDULER_DASHBOARD_USERNAME.

  A subset of the configuration (the configuration parameters used by the
  underlying flask blueprint) can also be provided in a Python module
  referenced using --config, or with a .cfg file referenced by the
  RQ_SCHEDULER_DASHBOARD_SETTINGS environment variable.

Options:
  -b, --bind TEXT               IP or hostname on which to bind HTTP server
  -p, --port INTEGER            Port on which to bind HTTP server
  --url-prefix TEXT             URL prefix e.g. for use behind a reverse proxy
  --username TEXT               HTTP Basic Auth username (not used if not set)
  --password TEXT               HTTP Basic Auth password
  -c, --config TEXT             Configuration file (Python module on search
                                path)
  -H, --redis-host TEXT         IP address or hostname of Redis server
  -P, --redis-port INTEGER      Port of Redis server
  --redis-password TEXT         Password for Redis server
  -D, --redis-database INTEGER  Database of Redis server
  -u, --redis-url TEXT          Redis URL connection (overrides other
                                individual settings)
  --interval INTEGER            Refresh interval in ms
  --help                        Show this message and exit.Integrating the dashboard in your Flask appThe dashboard can be integrated in to your ownFlaskapp by accessing the
blueprint directly in the normal way, e.g.:fromflaskimportFlaskimportRQ_SCHEDULER_DASHBOARDapp=Flask(__name__)app.config.from_object(RQ_SCHEDULER_DASHBOARD.default_settings)app.register_blueprint(RQ_SCHEDULER_DASHBOARD.blueprint)@app.route("/")defhello():return"Hello World!"if__name__=="__main__":app.run()Thecli.py:mainentry point provides a simple working example.DevelopingWe usepiptoolsto keep our development dependencies up to date$ pip install --upgrade pip
$ pip install git+https://github.com/nvie/pip-tools.git@futureNow make changes to therequirements.infile, and resolve all the
2nd-level dependencies intorequirements.txtlike so:$ pip-compile --annotate requirements.inDevelop in a virtualenv and make sure you have all the necessary build time (and
run time) dependencies with$ pip install -r requirements.txtDevelop in the normal way with$ python setup.py developThen use Fabric to perform various development tasks. For example, to tag, build
and upload to testpypi$ git tag 0.3.5   # no 'v' prefix or anything
$ fab build
$ fab uploadThis requires write access to both the GitHub repo and to the PyPI test site.Seefab-lfor more options andfab-d<subcommand>for details.Maturity notesThe RQ Scheduler Dashboard is currently being developed and is in beta stage.