author Philippe Pepiot <>
Mon, 30 Mar 2020 15:45:40 +0200
changeset 12962 fa0cd558d829
parent 12734 d177d8ab4fd3
permissions -rw-r--r--
[server] implement dynamic database pooler Opening too much database connection has a cost at startup and also PostgreSQL as a maximum number of connection (100 by default). This get worse when starting multiple wsgi processes, since each process has its own database pool. Instead of opening `connections-pool-size` connections to the database at startup, just open one and open more only when needed.

CubicWeb semantic web framework

CubicWeb is a entities / relations based knowledge management system
developped at Logilab.

This package contains:

- a repository server
- a RQL command line client to the repository
- an adaptative modpython interface to the server
- a bunch of other management tools


More details at

Getting started


 python3 -m venv venv
 source venv/bin/activate
 pip install 'cubicweb[pyramid]' cubicweb-blog
 cubicweb-ctl create blog myblog
 # read how to create your ~/etc/cubicweb.d/myblog/pyramid.ini file here:
 # then start your instance:
 cubicweb-ctl pyramid -D myblog
 sensible-browser http://localhost:8080/

Details at

You can also look at the latest builds on Logilab's jenkins:


Simply run the `tox` command in the root folder of this repository:


How to install tox:


Look in the doc/ subdirectory or read

CubicWeb includes the Entypo pictograms by Daniel Bruce —


Patches should be submitted by email at the
mailing list in order to get reviewed by project integrators or any community
The simplest way of send patches is to use the ``hg email`` command available
through the *patchbomb* extension of Mercurial. Preferably, patches should be
*in the message body* of emails. When submitting a revised version of a patch
series, a prefix indicating the iteration number ``<n>`` of the series should
be added to email subject prefixes; this can be achieved by specifying a
``--flag v<n>`` option to ``hg email`` command. If needed you can also use the
--in-reply-to option.


    hg email --to --intro -r <start>::<end>
    hg email --flag V2 --to -r <start>::<end>

If you have any questions you can also come on Logilab's public XMPP room using
a XMPP client:

Mailing list:
Patchbomb extension:
Good practice on sending email patches:

Full .hg/hgrc example for contributors having ssh access to ```` :

    default =
    default-push = ssh://

    to =

    publicurl =
    flagtemplate = "{separate(' ', 'cubicweb', flags)}"

    url =
    job = cubicweb-default

If you don't have ssh access to ````, you can use your own Mercurial server and
change ``default-push`` and ``publicurl`` accordingly.
A list of services that provides hosting of Mercurial repositories is available

* ``hg pull`` will pull on master repo (public changesets).
* ``hg push`` will push on review repo using ssh.
* When sending an email to the list, it will add a "Available at" with command
  to pull the draft series on the public repo.
* Using
  mercurial extension, ``hg show jenkins`` display jenkins build status for
  each changeset. Read to learn how
  to enable a new extension in mercurial.