Modified items

All recently modified items, latest first.

python-munin.plone-1.2-2.lbn25.noarch: Introduction ------------ This package provides munin plugins for monitoring various aspects of a Plone instance. It uses `gocept.munin`_ for plugin registration. Please refer to its documentation if you want to write new plugins. Plugins ------- Currently there is 1 plugin available: * "contentcreation" - reports content creation and modification taken from portal_catalog How to use it ------------- * First include the package in your buildout `instance` slot:: [instance] ... eggs = ... munin.plone zcml = ... munin.plone * To create the pluging helper script you'll also need to include the following, additional section and extend your `parts` definition:: [buildout] parts = ... munin [munin] recipe = zc.recipe.egg eggs = munin.plone arguments = http_address='${instance:http-address}', user='${instance:user}', plone='plone' The `arguments` option is used to pass configuration values to the generated helper script, which is then used as the actual munin plugin (see below). Any settings for `ip-address`, `http-address`, `port-base` and `user` given in the `instance` section should be repeated here, separated by commas. .. |---| unicode:: U+2014 .. em dash Please be aware, that the variable names use underscores instead of dashes here |---| the following list shows all supported settings and their respective default values: * ip_address='<ip-address>' ['localhost'] * http_address=<http-address> [8080] * port_base=<port-base> [0] * user=<user-credentials> [n.a.] * plone=<plone-site-id> ['plone'] Either literal values or references to the `instance` part can be used here, i.e. "http_address='${instance:http-address}', user='${instance:user}'". Please note that the resulting line will be verbosely copied into the generated `bin/munin` script, so the extra quoting is required. * Now you should be able to call the plugins as follow:: http://localhost:8080/plone/@@munin.plone.plugins/contentcreation Where `contentcreation` is you plugin name. Please note that for security reasons the view requires the `View management screens` permission. * Next you need to make symlinks from the helper script inside your buildout's `bin/` to the munin plugin directory. The helper script itself can assist you with this:: $ bin/munin install /opt/munin/etc/plugins [<prefix>] [<suffix>] This will install the necessary symlinks in the given directory using either the provided prefix and suffix or else the hostname and current directory to assemble their names (see below). Alternatively, you may also install the desired symlinks yourself:: $ cd /opt/munin/etc/plugins $ ln -s ~/zope/bin/munin company_contentcreation_site1 Here `/opt/munin/etc/plugins` is your munin directory, `~/zope/` is the root directory of your buildout, `contentcreation` the name of the plugin you want to enable, `company` a placeholder for an arbitrary prefix and `site1` the name which will be shown in munin. * Finally configure the plugin in munin (this step can be skipped if you have correctly set up the `arguments` option as described in step 2 above):: $ cd /opt/munin/etc/plugin-conf.d/ $ vi munin.plone.conf ... [company_*_site1] ... env.AUTH myuser:myuser ... env.URL http://localhost:8080/plone/@@munin.plone .plugins/%s Here `myuser:myuser` are your Zope user credentials and `localhost:8080` your site url. Please check `munin`_ for more information about plugin configuration.

python-mr.migrator-1.2-1.lbn25.noarch: Transmogrifier is a powerful tool for creating transformation processes called "pipelines". Transmogrifier gives you the tools to create and share these pipelines but doesn't provide an easy way to run the pipeline. Mr.migrator aims to bridge that gap. Mr.Migrator provides the following: * A buildout recipe with you can override a given pipeline and will also create a the commandline script to run the pipeline. * A commandline script with help which lets you run pipelines and see their progress. This is useful used in conjunction with transmogrify.ploneremote or other blueprints which don't need expect to be run inside the Plone process. * A Plone plugin which when installed lets you pick which pipeline you want to run, provides a form to override the pipeline options and then provides progress on the running pipeline. This is useful when you want to use plone.app.transmogrifier blueprints which expect to be run inside the Plone process.

libtidy-5.1.25-1.lbn25.x86_64: Runtime library for tidy.

python-mxTidy-3.0.0-5.lbn25.x86_64: mxTidy is a library version of the popular HTML Tidy command line tool that can parse broken or incomplete HTML data and turn it into proper HTML or XHTML. It can also be used to remove custom tags and attributes that are sometimes added by word processors when exporting HTML data.

python-mx-3.1.1-3.lbn25.x86_64: The mx extensions for Python are a collection of Python software tools which enhance Python's usability in many areas.

zope.sendmail-4.0.1-2.lbn25.noarch: zope.sendmail is a package for email sending from Zope 3 applications. Email sending from Zope 3 applications works as follows: A Zope 3 application locates a mail delivery utility (IMailDelivery) and feeds a message to it. It gets back a unique message ID so it can keep track of the message by subscribing to IMailEvent events. The utility registers with the transaction system to make sure the message is only sent when the transaction commits successfully. (Among other things this avoids duplicate messages on ConflictErrors.) If the delivery utility is a IQueuedMailDelivery, it puts the message into a queue (a Maildir mailbox in the file system). A separate process or thread (IMailQueueProcessor) watches the queue and delivers messages asynchronously. Since the queue is located in the file system, it survives Zope restarts or crashes and the mail is not lost. The queue processor can implement batching to keep the server load low. If the delivery utility is a IDirectMailDelivery, it delivers messages synchronously during the transaction commit. This is not a very good idea, as it makes the user wait. Note that transaction commits must not fail, but that is not a problem, because mail delivery problems dispatch an event instead of raising an exception. However, there is a problem – sending events causes unknown code to be executed during the transaction commit phase. There should be a way to start a new transaction for event processing after this one is commited. An IMailQueueProcessor or IDirectMailDelivery actually delivers the messages by using a mailer (IMailer) component that encapsulates the delivery process. There currently is only one mailer: ISMTPMailer sends all messages to a relay host using SMTP.

zope.securitypolicy-4.1.0-1.lbn25.noarch: This package implements a role-based security policy similar to the policy found in Zope 2. The security policy is responsible for deciding whether an interaction has a permission on an object. This security policy does this using grant and denial information. Managers can grant or deny: roles to principals, permissions to principals, and permissions to roles

zope.security-4.3.0-1.lbn25.x86_64: The Security framework provides a generic mechanism to implement security policies on Python objects. This introduction provides a tutorial of the framework explaining concepts, design, and going through sample usage from the perspective of a Python programmer using the framework outside of Zope.

zope.security-4.3.0-1.lbn25.x86_64: The Security framework provides a generic mechanism to implement security policies on Python objects. This introduction provides a tutorial of the framework explaining concepts, design, and going through sample usage from the perspective of a Python programmer using the framework outside of Zope.

zope.schema-4.9.3-1.lbn25.noarch: ============== Zope 3 Schemas ============== Introduction ------------ Schemas extend the notion of interfaces to detailed descriptions of Attributes (but not methods). Every schema is an interface and specifies the public fields of an object. A *field* roughly corresponds to an attribute of a python object. But a Field provides space for at least a title and a description. It can also constrain its value and provide a validation method. Besides you can optionally specify characteristics such as its value being read-only or not required. Zope 3 schemas were born when Jim Fulton and Martijn Faassen thought about Formulator for Zope 3 and PropertySets while at the Zope 3 sprint at the Zope BBQ in Berlin. They realized that if you strip all view logic from forms then you have something similar to interfaces. And thus schemas were born.

zope.rdb-3.5.0-2.lbn25.noarch: Zope RDBMS transaction integration

zope.ramcache-2.2.0-1.lbn25.noarch: This package provides a RAM-based cache implementation for Zope.

zope.publisher-4.3.2-1.lbn25.noarch: zope.publisher allows you to publish Python objects on the web. It has support for plain HTTP/WebDAV clients, web browsers as well as XML-RPC and FTP clients. Input and output streams are represented by request and response objects which allow for easy client interaction from Python. The behaviour of the publisher is geared towards WSGI compatibility.

zope.ptresource-4.0.0-1.lbn25.noarch: This package is at present not reusable without depending on a large chunk of the Zope Toolkit and its assumptions. It is maintained by the Zope Toolkit project. This package provides a “page template” resource class, a resource which content is processed with Zope Page Templates engine before returning to client. The resource factory class is registered for “pt”, “zpt” and “html” file extensions in package’s configure.zcml file.

zope.proxy-devel-4.3.1-1.lbn25.x86_64: This package provides the support files which can be used to build applications using the Zope proxy infrastructure

zope.proxy-4.3.1-1.lbn25.x86_64: Proxies are special objects which serve as mostly-transparent wrappers around another object, intervening in the apparent behavior of the wrapped object only when necessary to apply the policy (e.g., access checking, location brokering, etc.) for which the proxy is responsible. Editorial note: Unfortunately, we don't have separate documentation for zope.proxy at this time. This is a shame because they are generically useful. We are publishing this release without documentation mainly because it is a dependency of other releases.

zope.proxy-4.3.1-1.lbn25.x86_64: Proxies are special objects which serve as mostly-transparent wrappers around another object, intervening in the apparent behavior of the wrapped object only when necessary to apply the policy (e.g., access checking, location brokering, etc.) for which the proxy is responsible. Editorial note: Unfortunately, we don't have separate documentation for zope.proxy at this time. This is a shame because they are generically useful. We are publishing this release without documentation mainly because it is a dependency of other releases.

zope.processlifetime-2.1.0-1.lbn25.noarch: This package provides interfaces / implementations for events relative to the lifetime of a server process (startup, database opening, etc.) It is derived from Zope 3.4’s zope.app.appsetup.

zope.principalregistry-3.7.1-2.lbn25.noarch: zope.principalregistry

zope.principalannotation-4.1.1-1.lbn25.noarch: This package implements annotations for zope.security principals. Common annotation techniques, like AttributeAnnotations cannot be applied to principals, since they are created on the fly for every request. Principal Annotations This package implements annotations for zope.security principals. To make it clear, the principal here is the object that provides zope.security.interfaces.IPrincipal interface and annotations is the object providing zope.annotation.interfaces.IAnnotations. The problem is that principals is dynamic, non-persistent objects created on the fly for every security participation (request or something), so common annotation techniques, like AttributeAnnotations cannot be applied to them. This package provides a persistent storage of principal annotations, storing annotations by principal ID as well as an adapter from IPrincipal to IAnnotations.

« Previous 20 items Next 20 items » 1 ... 631 632 633 634 635 636 637 ... 2449


	Copyright © 2000-2026 Corporation of Balclutha Inc. All rights reserved.

Sections

Modified items