8 allow to switch off internal connection pooling for use with others poolers |
8 allow to switch off internal connection pooling for use with others poolers |
9 such as pgbouncer_. |
9 such as pgbouncer_. |
10 |
10 |
11 .. _pgbouncer: https://pgbouncer.github.io/ |
11 .. _pgbouncer: https://pgbouncer.github.io/ |
12 |
12 |
|
13 * In `deleteconf` view (confirmation before deletion), the list of first-level |
|
14 composite objects that would be deleted along with the primary entity is |
|
15 displayed (01eeea97e549). |
|
16 |
|
17 * The ``cubicweb.pyramid`` module now provides a Paste application factory |
|
18 registered as an entry point named ``pyramid_main`` and that can be used to |
|
19 run a Pyramid WSGI application bound to a CubicWeb repository. |
|
20 |
|
21 * A new configuration type ``pyramid`` has been added to create CubicWeb's |
|
22 instances (through ``cubicweb-ctl create -c pyramid <basecube> <appid>``). |
|
23 This configuration bootstraps a CubicWeb instance that is essentially a |
|
24 repository plus the minimal setup to run a Pyramid WSGI application on top |
|
25 of it. Noticeably, it does not ship all *web* configuration but rather |
|
26 relies on configuration declared in a ``development.ini`` file for any |
|
27 Pyramid application. |
13 |
28 |
14 * A new way to declare workflows as simple data structure (dict/list) has been |
29 * A new way to declare workflows as simple data structure (dict/list) has been |
15 introduced. Respective utility functions live in ``cubicweb.wfutils`` |
30 introduced. Respective utility functions live in ``cubicweb.wfutils`` |
16 module. This handles both the creation and migration of workflows. |
31 module. This handles both the creation and migration of workflows. |
|
32 |
|
33 * A new IDublinCore adapter has been introduced to control the generation of |
|
34 Dublin Core metadata that are used in several base views. |
|
35 |
|
36 * It is now possible to *derive* rtags using their ``derive`` method |
|
37 (0849a5eb57b8). |
|
38 |
|
39 * A new ``cubicweb-ctl scheduler <appid>`` command has been introduced to run |
|
40 background and periodic tasks of the repository (previously called *looping |
|
41 tasks*). In a production environment, a process with this command should be |
|
42 run alongside with a WSGI server process (possibly running multiple |
|
43 processes itself). |
|
44 |
|
45 |
|
46 Backwards incompatible changes |
|
47 ------------------------------ |
|
48 |
|
49 * As a consequence of the replacement of the old looping tasks manager by a |
|
50 scheduler, all cubicweb-ctl's "start" commands (i.e. ``start``, ``pyramid``, |
|
51 ``wsgi``) do not start repository *looping tasks manager* anymore, nor do |
|
52 they start the scheduler. Site administrators are thus expected to start |
|
53 this scheduler as a separate process. |
|
54 |
|
55 |
|
56 API changes |
|
57 ----------- |
|
58 |
|
59 * In ``cubicweb.pyramid``, function ``make_cubicweb_application`` got renamed |
|
60 into ``config_from_cwconfig`` (950ce7d9f642). |
|
61 |
|
62 * Several cleanups in repository's session management have been conducted |
|
63 resulting from changes introduced in 3.19 release. |
|
64 |
|
65 |
|
66 Removals |
|
67 -------- |
|
68 |
|
69 * Support for 'https-url' configuration option has been removed |
|
70 (4516c3956d46). |
|
71 |
|
72 * The `next_tabindex` method of request class has been removed (011730a4af73). |