Skip to content

CONFIGURE.md

Latest commit

 

History

History
52 lines (45 loc) · 1.77 KB

CONFIGURE.md

File metadata and controls

52 lines (45 loc) · 1.77 KB
  • Using environment variables and command line:
    • Adjust environment variables (optional):
      • ODOO_QUEUE_JOB_CHANNELS=root:4 or any other channels configuration. The default is root:1
      • ODOO_QUEUE_JOB_PORT=8069, default --http-port
      • ODOO_QUEUE_JOB_SCHEME=https, default http
      • ODOO_QUEUE_JOB_HOST=load-balancer, default --http-interface or localhost if unset
      • ODOO_QUEUE_JOB_HTTP_AUTH_USER=jobrunner, default empty
      • ODOO_QUEUE_JOB_HTTP_AUTH_PASSWORD=s3cr3t, default empty
      • QUEUE_JOB__NO_DELAY=1, disables the queue for testing purposes
      • Start Odoo with --load=web,queue_job and --workers greater than 1.1
  • Using the Odoo configuration file:
[options]
(...)
workers = 6
server_wide_modules = web,queue_job

(...)
[queue_job]
channels = root:2
scheme = https
host = load-balancer
port = 443
http_auth_user = jobrunner
http_auth_password = s3cr3t
queue_job__no_delay=True # disables the queue
  • Confirm the runner is starting correctly by checking the odoo log file:
...INFO...queue_job.jobrunner.runner: starting
...INFO...queue_job.jobrunner.runner: initializing database connections
...INFO...queue_job.jobrunner.runner: queue job runner ready for db <dbname>
...INFO...queue_job.jobrunner.runner: database connections ready
  • Create jobs (eg using base_import_async) and observe they start immediately and in parallel.
  • Tip: to enable debug logging for the queue job, use --log-handler=odoo.addons.queue_job:DEBUG
  • Jobs that remain in enqueued or started state (because, for instance, their worker has been killed) will be automatically re-queued.

Footnotes

  1. It works with the threaded Odoo server too, although this way of running Odoo is obviously not for production purposes. ↩