Search results

python2-libselinux-2.9-1.lbn25.x86_64

The libselinux-python package contains the python bindings for developing SELinux applications.

python2-libsemanage-2.9-1.lbn25.x86_64

The libsemanage-python package contains the python bindings for developing SELinux management applications.

python2-pymongo-3.9.0-1.lbn25.x86_64

The Python driver for MongoDB. This package contains the python3 version of this module.

python2-pymongo-gridfs-3.9.0-1.lbn25.x86_64

GridFS is a storage specification for large objects in MongoDB. This package contains the python3 version of this module.

rubygem-gettext-3.2.6-1.lbn25.noarch

Ruby-GetText-Package is a GNU GetText-like program for Ruby. The catalog file(po-file) is same format with GNU GetText. So you can use GNU GetText tools for maintaining. This package provides gem for Ruby-Gettext-Package.

rubygem-gettext-setup-0.25-3.lbn25.noarch

This is a simple gem to set up i18n for Ruby projects (including Sinatra web apps) using gettext and fast gettext. This project sets the default locale to English. If the user has set a different locale in their browser preferences, and we support the user's preferred locale, strings and data formatting will be customized for that locale.

rubygem-locale-2.1.2-1.lbn25.3.noarch

Ruby-Locale is the pure ruby library which provides basic and general purpose APIs for localization. It aims to support all environments which ruby works and all kind of programs (GUI, WWW, library, etc), and becomes the hub of other i18n/l10n libs/apps to handle major locale ID standards.

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.

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-munin.zope-2.1-4.lbn25.noarch

Introduction ------------ This package provides munin plugins for monitoring various aspects of a Zope instance. It uses `gocept.munin`_ for plugin registration. Please refer to its documentation if you want to write new plugins. Bits of the code is based on plugins found at `munin exchange`_ (many thanks to Gaute Amundsen and Arthur Lutz). Plugins ------- Currently there are 4 plugins available: * "zopethreads" - reports free Zope threads * "zopecache" - reports database cache parameters * "zodbactivity" - reports ZODB activity * "zopememory" - reports Zope memory usage (only works on Linux) How to use it ------------- * First include the package in your buildout `instance` slot:: [instance] ... eggs = ... munin.zope zcml = ... munin.zope * 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.zope arguments = http_address='${instance:http-address}', user='${instance:user}' 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.] 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. * When monitoring more than one Zope instance, i.e. in a ZEO setup, separate helper scripts need to be generated. In order to do so the `scripts` option of `zc.recipe.egg` can be used like so:: [buildout] parts = ... munin1 munin2 [munin1] recipe = zc.recipe.egg eggs = munin.zope scripts = munin=munin1 arguments = http_address='${instance1:http-address}', user='${instance1:user}' [munin2] recipe = zc.recipe.egg eggs = munin.zope scripts = munin=munin2 arguments = http_address='${instance2:http-address}', user='${instance2:user}' The necessary symlinks can then be created with each of the scripts in turn (see below). Please note, that in this case you should explicitly provide at least a differing `prefix` argument. * Now you should be able to call the plugins as follow:: http://localhost:8080/@@munin.zope.plugins/zopethreads Where `zopethreads` 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_zodbactivity_site1 Here `/opt/munin/etc/plugins` is your munin directory, `~/zope/` is the root directory of your buildout, `zodb_activity` 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.zope.conf ... [company_*_site1] ... env.AUTH myuser:myuser ... env.URL http://localhost:8080/@@munin.zope.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.