Clean up the configuring-your-application document.
Move plone to the end instead of the beginning. Document how to use a configuration string instead of a file. Better links to ZConfig, repoze.zodbconn, and the ZODB.config functions. [skip ci]
This commit is contained in:
Jason Madden
parent
5ab2840552
commit
a821ec1147
|
|
@ -73,7 +73,7 @@ master_doc = 'index'
|
|||
|
||||
# General information about the project.
|
||||
project = u'RelStorage'
|
||||
copyright = u'2016, RelStorage contributors'
|
||||
copyright = u'2016-2018, RelStorage contributors'
|
||||
author = u'RelStorage contributors'
|
||||
|
||||
# The version info for the project you're documenting, acts as replacement for
|
||||
|
|
@ -363,8 +363,11 @@ texinfo_documents = [
|
|||
|
||||
|
||||
# Example configuration for intersphinx: refer to the Python standard library.
|
||||
intersphinx_mapping = {'https://docs.python.org/': None,
|
||||
'http://zodb.readthedocs.io/en/latest/': None}
|
||||
intersphinx_mapping = {
|
||||
'https://docs.python.org/': None,
|
||||
'http://www.zodb.org/en/latest/': None,
|
||||
'https://zconfig.readthedocs.io/en/latest/': None,
|
||||
}
|
||||
|
||||
extlinks = {'issue': ('https://github.com/zodb/relstorage/issues/%s',
|
||||
'issue #'),
|
||||
|
|
|
|||
|
|
@ -8,65 +8,29 @@ RelStorage, it's time to configure the application to use RelStorage.
|
|||
This means telling RelStorage about the database to use, how to
|
||||
connect to it, and specifying any additional options.
|
||||
|
||||
.. note:: This is just a quick-start guide. There is a :doc:`full list
|
||||
of supported options <relstorage-options>` in a separate
|
||||
document, as well as a :doc:`list of database-specific
|
||||
options <db-specific-options>`.
|
||||
.. note::
|
||||
This is just a quick-start guide. There is a :doc:`full list of
|
||||
supported options <relstorage-options>` in a separate document, as
|
||||
well as a :doc:`list of database-specific options
|
||||
<db-specific-options>`.
|
||||
|
||||
.. highlight:: guess
|
||||
|
||||
Configuring Plone
|
||||
=================
|
||||
|
||||
Plone uses the `plone.recipe.zope2instance`_ Buildout recipe to
|
||||
generate zope.conf, so the easiest way to configure RelStorage in a
|
||||
Plone site is to set the ``rel-storage`` parameter in ``buildout.cfg``.
|
||||
The ``rel-storage`` parameter contains options separated by newlines,
|
||||
with these values:
|
||||
|
||||
* ``type``: any database type supported (``postgresql``, ``mysql``,
|
||||
or ``oracle``)
|
||||
* RelStorage options like ``cache-servers`` and ``poll-interval``
|
||||
* Adapter-specific options
|
||||
|
||||
An example::
|
||||
|
||||
rel-storage =
|
||||
type mysql
|
||||
db plone
|
||||
user plone
|
||||
passwd PASSWORD
|
||||
|
||||
You'll also need to make sure that the correct version of RelStorage
|
||||
and its database drivers are installed (typically by adding them to
|
||||
the ``[eggs]`` section in the ``buildout.cfg``).
|
||||
|
||||
.. note:: For a detailed walk through of installing historic versions
|
||||
of RelStorage in historic versions of Plone 3, see `this blog
|
||||
post
|
||||
<http://shane.willowrise.com/archives/how-to-install-plone-with-relstorage-and-mysql/>`_.
|
||||
It's important to note that this information is not directly
|
||||
applicable to newer versions (Plone 4 does not use fake eggs,
|
||||
and the version of ZODB used by Plone 4, 3.9.5 and above,
|
||||
does not need patched). The comments section may contain
|
||||
further hints for newer versions.
|
||||
|
||||
.. _plone.recipe.zope2instance: https://pypi.python.org/pypi/plone.recipe.zope2instance
|
||||
|
||||
Configuring using ZConfig
|
||||
=========================
|
||||
|
||||
The most common way to configure RelStorage will involve writing a
|
||||
configuration file using the `ZConfig
|
||||
<https://github.com/zopefoundation/ZConfig/blob/master/doc/zconfig.pdf>`_
|
||||
syntax. You will write a ``<relstorage>`` element containing
|
||||
the general RelStorage options, and containing one database-specific
|
||||
element (``<postgresql>``, ``<mysql>`` or ``<oracle>``). (Where in the
|
||||
file the ``<relstorage>`` element goes is specific to the framework
|
||||
or application you're using and will be covered next.)
|
||||
configuration document (a file or string) using the `ZConfig
|
||||
<https://zconfig.readthedocs.io/en/latest/>`_ syntax. You will write a
|
||||
``<relstorage>`` element containing the general RelStorage options,
|
||||
and containing one database-specific element (``<postgresql>``,
|
||||
``<mysql>`` or ``<oracle>``). (Where in the document the ``<relstorage>``
|
||||
element goes is specific to the framework or application you're using
|
||||
and will be covered next.)
|
||||
|
||||
In all cases, you'll need to add ``%import relstorage`` to the
|
||||
top-level of the file to let ZConfig know about the RelStorage
|
||||
top-level of the file to let :mod:`ZConfig` know about the RelStorage
|
||||
specific elements.
|
||||
|
||||
|
||||
|
|
@ -110,8 +74,42 @@ where to store the blobs. For example::
|
|||
</relstorage>
|
||||
|
||||
|
||||
Configuring Zope 2
|
||||
------------------
|
||||
Without a Framework
|
||||
-------------------
|
||||
|
||||
You can manually open a ZODB database in Python code. Once you
|
||||
have a configuration file as outlined above, you can use the
|
||||
:func:`ZODB.config.databaseFromURL` API to get a ZODB database::
|
||||
|
||||
path = "path/to/configuration"
|
||||
import ZODB.config
|
||||
db = ZODB.config.databaseFromURL(path)
|
||||
conn = db.open()
|
||||
...
|
||||
|
||||
You can also skip the file and use a string with
|
||||
:func:`ZODB.config.databaseFromString`::
|
||||
|
||||
conf = """
|
||||
%%import relstorage
|
||||
<zodb main>
|
||||
<relstorage>
|
||||
<mysql>
|
||||
db %s
|
||||
user %s
|
||||
passwd %s
|
||||
</mysql>
|
||||
</relstorage>
|
||||
</zodb>
|
||||
""" % (dbname, user, passwd)
|
||||
|
||||
db = ZODB.config.databaseFromString(conf)
|
||||
conn = db.open()
|
||||
...
|
||||
|
||||
|
||||
With Zope 2
|
||||
-----------
|
||||
|
||||
To integrate RelStorage in Zope 2, specify a RelStorage backend in
|
||||
``etc/zope.conf``. Remove the main mount point replace it with the
|
||||
|
|
@ -128,12 +126,14 @@ To integrate RelStorage in Zope 2, specify a RelStorage backend in
|
|||
</zodb_db>
|
||||
|
||||
|
||||
Configuring ``repoze.zodbconn``
|
||||
-------------------------------
|
||||
With ``repoze.zodbconn``
|
||||
------------------------
|
||||
|
||||
To use RelStorage with ``repoze.zodbconn``, a package that makes ZODB
|
||||
available to WSGI applications, create a configuration file with
|
||||
contents similar to the following::
|
||||
To use RelStorage with `repoze.zodbconn
|
||||
<http://docs.repoze.org/zodbconn/>`_, a library that generically
|
||||
creates a ZODB DB given a URI and which has special support for WSGI
|
||||
applications, create a configuration file with contents similar to the
|
||||
following::
|
||||
|
||||
%import relstorage
|
||||
<zodb main>
|
||||
|
|
@ -145,20 +145,51 @@ contents similar to the following::
|
|||
cache-size 100000
|
||||
</zodb>
|
||||
|
||||
``repoze.zodbconn`` expects a ZODB URI. Use a URI of the form
|
||||
``zconfig://path/to/configuration#main`` where
|
||||
``repoze.zodbconn`` expects a `ZConfig URI
|
||||
<http://docs.repoze.org/zodbconn/narr.html#zconfig-uri-scheme>`_. Use a
|
||||
URI of the form ``zconfig://path/to/configuration#main`` where
|
||||
``path/to/configuration`` is the complete path to the configuration
|
||||
file, and ``main`` is the name given to the ``<zodb>`` element.
|
||||
file, and ``main`` is the name given to the ``<zodb>`` element::
|
||||
|
||||
Manually Opening a Database
|
||||
---------------------------
|
||||
from repoze.zodbconn.uri import db_from_uri
|
||||
db = db_from_uri('zconfig://path/to/configuration#main')
|
||||
|
||||
You can also manually open a ZODB database in Python code. Once you
|
||||
have a configuration file as outlined above, you can use the
|
||||
``ZODB.config.databaseFromURL`` API to get a ZODB database::
|
||||
|
||||
path = "path/to/configuration"
|
||||
import ZODB.config
|
||||
db = ZODB.config.databaseFromURL(path)
|
||||
conn = db.open()
|
||||
...
|
||||
Configuring Plone
|
||||
=================
|
||||
|
||||
Plone uses the `plone.recipe.zope2instance`_ Buildout recipe to
|
||||
generate zope.conf, so the easiest way to configure RelStorage in a
|
||||
Plone site is to set the ``rel-storage`` parameter in ``buildout.cfg``.
|
||||
The ``rel-storage`` parameter contains options separated by newlines,
|
||||
with these values:
|
||||
|
||||
* ``type``: any database type supported (``postgresql``, ``mysql``,
|
||||
or ``oracle``)
|
||||
* RelStorage options like ``cache-servers`` and ``poll-interval``
|
||||
* Adapter-specific options
|
||||
|
||||
An example::
|
||||
|
||||
rel-storage =
|
||||
type mysql
|
||||
db plone
|
||||
user plone
|
||||
passwd PASSWORD
|
||||
|
||||
You'll also need to make sure that the correct version of RelStorage
|
||||
and its database drivers are installed (typically by adding them to
|
||||
the ``[eggs]`` section in the ``buildout.cfg``).
|
||||
|
||||
.. note::
|
||||
|
||||
For a detailed walk through of installing historic versions of
|
||||
RelStorage in historic versions of Plone 3, see `this blog post
|
||||
<http://shane.willowrise.com/archives/how-to-install-plone-with-relstorage-and-mysql/>`_.
|
||||
It's important to note that this information is not directly
|
||||
applicable to newer versions (Plone 4 does not use fake eggs, and
|
||||
the version of ZODB used by Plone 4, 3.9.5 and above, does not need
|
||||
patched). The comments section may contain further hints for newer
|
||||
versions.
|
||||
|
||||
.. _plone.recipe.zope2instance: https://pypi.python.org/pypi/plone.recipe.zope2instance
|
||||
|
|
|
|||
|
|
@ -102,7 +102,10 @@ def generate_rst(do=True):
|
|||
assert os.path.exists('contents.rst'), 'Wrong directory, contents.rst not found'
|
||||
for module in modules:
|
||||
if module not in SKIP:
|
||||
generate_rst_for_module(module, do=do)
|
||||
try:
|
||||
generate_rst_for_module(module, do=do)
|
||||
except AttributeError as e:
|
||||
print("Failed to generate rst for", module, e, "; skipping")
|
||||
|
||||
|
||||
def iter_autogenerated():
|
||||
|
|
|
|||
Loading…
Reference in New Issue