author Laurent Peuch <>
Fri, 08 May 2020 03:03:31 +0200
changeset 12966 c49d78859c6b
parent 12950 1c41cba17775
permissions -rw-r--r--
[gitlab-ci] add py3-from-forge

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 forge:


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 can be submitted on Logilab's forge (
If you do not have a write-access, please contact us at

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


Alternatively, patches could be submitted by email at the mailing list in order to get reviewed by
project integrators or any community member.  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>

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