[pyramid] Add a "pyramid" instance configuration type
In a new module 'cubicweb.pyramid.config' we define a "pyramid" instance
configuration type. The noticeable feature of this configuration is that it
manages a 'development.ini' file that gets installed in application home
(along with `.conf` file). This file is templated and includes generated
values for secrets of session and authtk tokens.
This means that we can just call:
pserve etc/cubicweb.d/<appname>/development.ini
or
gunicorn --paste etc/cubicweb.d/<appname>/development.ini -b :8080
just after instance creation to get a pyramid instance running without having
to hack around a 'pyramid.ini' file.
This patch drops 'development.ini' from skeleton and moves it in
cubicweb/pyramid so that it gets installed at instance creation which is more
appropriate than in cube creation.
The new configuration class sets "cubicweb.bwcompat" setting to false so it is
not intended to replace the "all-in-one" configuration type (which would
require a bit more work). This configuration is close to the the 'repository'
configuration type with just a couple of options from WebConfiguration that
are needed for Pyramid (anonymous user/password plus some miscellaneous
options that I'm not so sure are really needed). Note, in particular, that we
do not pull CORS settings to be injected as a WSGI middleware like in
wsgi_application_from_cwconfig() since I believe this should be left as an
end-user responsibility and since this can be defined in a standard way in
paste configuration. This configuration inherits from ServerConfiguration but
registers the same appobjects as WebConfiguration.
In cubicweb.web.request._CubicWebRequestBase, we guard against access to
"uiprops" and "datadir_url" of the config because this new "pyramid" config
does not have these (this does not make sense without bwcompat mode). At some
point, we should either avoid using `cw_request`'s pyramid request attribute
or make cubicweb's web request really independant of existing implementation
and drop these assumptions.
.. -*- coding: utf-8 -*-
The development team is pleased to announce the 3.0.0 release of CubicWeb, also
know as ShowTime.
What is CubicWeb?
-----------------
With CubicWeb, the Semantic Web is a construction game!
CubicWeb_ is a semantic web application framework, licensed under the LGPL, that
empowers developers to efficiently build web applications by reusing components
(called cubes) and following the well known object-oriented design principles.
Its main features are:
* an engine driven by the explicit data model of the application,
* a query language named RQL similar to W3C’s SPARQL,
* a selection+view mechanism for semi-automatic XHTML/XML/JSON/text generation,
* a library of reusable components (data model and views) that fulfill common needs,
* the power and flexibility of the Python programming language,
* the reliability of SQL databases, LDAP directories, Subversion and Mercurial for storage backends.
Being built since 2000 by an R&D project still going on today, supporting
100,000s of daily visits at some production sites, CubicWeb is a proven end to
end solution for semantic web application development that promotes quality,
reusability and efficiency.
The unbeliever will read the quick overview_ of CubicWeb.
The hacker will join development at the forge_.
The impatient will move right away to installation_ and set-up of a CubicWeb
environment.
.. _cubicweb: https://www.cubicweb.org/
.. _overview: https://docs.cubicweb.org/tutorials/base/index.html
.. _forge: https://www.cubicweb.org/project?vtitle=All%20cubicweb%20projects
.. _installation: https://docs.cubicweb.org/book/admin/setup.html#setupenv
Home page
---------
http://www.cubicweb.org/
Download
--------
http://ftp.logilab.org/pub/cubicweb/
Mailing list
------------
http://lists.cubicweb.org/mailman/listinfo/cubicweb