You are here: Home

Modified items

All recently modified items, latest first.
RPMPackage raptus.article.lightbox-2.0b6-1.lbn25.noarch
Provides an inline lightbox component showing the images contained in the article. The following features for raptus.article are provided by this package: Components ---------- * Lightbox (Lightbox of the images contained in the article) * Lightbox teaser (Lightbox of the images contained in the article displayed above the columns)
RPMPackage raptus.article.images-2.0b5-1.lbn25.noarch
raptus.article.images provides support for multiple images per article. The following features for raptus.article are provided by this package: Content ------- * Image - add your images in a article.
RPMPackage raptus.article.hidecolumns-2.0b5-2.lbn25.noarch
Articles get the option to hide the left or the right column or both. The following features for raptus.article are provided by this package: Fields ------ * Option to hide the portlet columns
RPMPackage raptus.article.gallery-2.0b11-1.lbn25.noarch
Provides basic gallery components. The following features for raptus.article are provided by this package: Components ---------- * Gallery left (Gallery of the images contained in the article on the left side) * Gallery right (Gallery of the images contained in the article on the right side) * Gallery columns (Gallery of the images contained in the article arranged in columns)
RPMPackage raptus.article.form-2.0b6-1.lbn25.noarch
Provides support for PloneFormGen The following features for raptus.article are provided by this package: Content ------- * Form Folder - PloneFormGen - add your forms in an article. Components ---------- * Forms (List of forms contained in the article)
RPMPackage raptus.article.flash-2.0b4-2.lbn25.noarch
Provides support for flash movies The following features for raptus.article are provided by this package: Content ------- * Flash - add your flash files in an article. Components ---------- * Flash (displays flash files contained in the article over the whole width) * Flash left (displays flash files contained in the article on the left side) * Flash right (displays flash files contained in the article on the right side) * Flash teaser (displays flash files contained in the article over the whole width and displayed above t
RPMPackage raptus.article.files-2.0b6-1.lbn25.noarch
Provides support for adding attachments to articles. The following features for raptus.article are provided by this package: Content ------- * File - add files in an article. Components ---------- * Attachments (List of files contained in the article)
RPMPackage raptus.article.fader-2.0b5-2.lbn25.noarch
Provides a component which continually fades in and out the contained articles. The following features for raptus.article are provided by this package: Components ---------- * Content fader (continually fades in and out the contained articles) * Content fader teaser (continually fades in and out the contained articles and is displayed above the columns)
RPMPackage raptus.article.contentflow-2.0b4-2.lbn25.noarch
The following features for raptus.article are provided by this package: Components ---------- * Content flow (showing the contained articles like in iTunes) * Content flow teaser (showing the contained articles like in iTunes and is displayed above the columns)
RPMPackage raptus.article.contentfader-2.0b6-2.lbn25.noarch
Provides a component which continually fades in and out the contained articles.
RPMPackage raptus.article.additionalwysiwyg-2.0b7-1.lbn25.noarch
Extends the article by a second WYSIWYG text field to make it possible to split your text into two parts and display it for example above and below another component. The following features for raptus.article are provided by this package: Fields ------ * Additional WYSIWYG text field for the articles. Components ---------- * Additional text (displays your text above an image or a video) * Additional text left (displays your text in a separate column on the left) * Additional text right (displays your text in a separate column on the right)
RPMPackage python-raptus-2.0b12-1.lbn25.noarch
 
RPMPackage python-memcached-1.54-6.lbn25.noarch
This software is a 100% Python interface to the memcached memory cache daemon. It is the client side software which allows storing values in one or more, possibly remote, memcached servers. Search google for memcached for more information.
RPMPackage plone.scale-2.1-1.lbn25.noarch
This package contains image scaling logic for use in Zope environments. It supports Zope 2, grok and other systems build on using the Zope ToolKit (ZTK). Several design goals were used when writing this package: image scaling to any width, height, width&height should be supported using both up-scaling and down-scaling. Scaling parameters should never be fixed in code. This allows designers to use any image scale they want without having to modify python code. the result of scaling will be an image along with its new size, not a HTML or XHTML tag. We already have excellent tools to generate tags in the form of Zope Pagetemplates, Genshi and other template languages that are much better suited for this purpose. In addition several implementation goals were defined: image scaling must happen on demand instead of up-front. This reduces initial save time and prevents unnecessary scalings from being generated. image scaling parameters should not be part of the generated URL. Since the number of parameters can change and new parameters may be added in the future this would create overly complex URLs and URL parsing. no HTML rewriting (such as done by repoze.bitblt) should be required. it should be possibly to develop an external storage system which stores scaled images externally and returns a URL which bypasses the application server. This should be configurable via just a filesystem path & base URL. minimum number of external dependencies, allowing this package to be used in many environments. testable without requiring zope.testing. Running setup.py test should be sufficient. URLs for scaled images should have an extension which reflects their MIME type. This is facilitates cache (and other front-end services) configuration.
RPMPackage plone.registry-1.1.2-1.lbn25.noarch
This package provides debconf-like (or about:config-like) settings registries for Zope applications. A ``registry``, with a dict-like API, is used to get and set values stored in ``records``. Each record contains the actual value, as well as a ``field`` that describes the record in more detail. At a minimum, the field contains information about the type of value allowed, as well as a short title describing the record's purpose. See the following doctests for more details: * ``registry.rst``, which demonstrates how registries and records work * ``events.rst``, which shows the events that are fired from the registry * ``field.rst``, which describes the behaviour of persistent fields
RPMPackage plone.recipe.zope2zeoserver-1.4-3.lbn25.noarch
This recipe creates and configures a Zope 2 ZEO server in parts. It also installs a control script, which is like zeoctl, in the bin/ directory. The name of the control script is the the name of the part in buildout. You can use it with a part like this:: [zeoserver] recipe = plone.recipe.zope2zeoserver zope2-location = /path/to/zope2/install zeo-address = 8100 Options ------- zope2-location The path where Zope 2 is installed. If you are also using the plone.recipe.zope2install recipe, and you have that configured as a part called 'zope2' prior to the zope2zeoserver part, you can use ${zope2:location} for this parameter. You must ensure the zope2zeoserver part is run *after* the zope2install one. zeopack The path to the zeopack.py backup script. A wrapper for this will be generated in bin/zeopack, which sets up the appropriate environment to run this. Defaults to "${zope2-location}/utilities/ZODBTools/zeopack.py". Set this option to an empty value if you do not want this script to be generated. repozo The path to the repozo.py backup script. A wrapper for this will be generated in bin/repozo, which sets up the appropriate environment for running this. Defaults to "${zope2-location}/utilities/ZODBTools/repozo.py". Set this to an empty value if you do not want this script to be generated. zeo-conf A relative or absolute path to a zeo.conf file. If this is not given, a zeo.conf will be generated based on the the options below. The following options all affect the generated zope.conf. zeo-address Give a port for the ZEO server (either specify the port number only (with 'localhost' as default) or you use the format ``host:port``). Defaults to 8100. effective-user The name of the effective user for the ZEO process. Defaults to not setting an effective user. invalidation-queue-size The invalidation-queue-size used for the ZEO server. Defaults to 100. zeo-log The filename of the ZEO log file. Defaults to var/log/${partname}.log zeo-log-format Format of logfile entries. Defaults to %(asctime)s %(message)s zeo-log-custom A custom section for the eventlog, to be able to use another event logger than `logfile`. `zeo-log` is still used to set the logfile value in the runner section. storage-number The number used to identify a storage. file-storage The filename where the ZODB data file will be stored. Defaults to var/filestorage/Data.fs. blob-storage The folder where the ZODB blob data files will be stored. socket-name The filename where ZEO will write its socket file. Defaults to var/zeo.zdsock. authentication-database The filename for a authentication database. Only accounts listed in this database will be allowed to access the ZEO server. The format of the database file is:: realm <realm> <username>:<hash> Where the hash is generated via:: import sha string = "%s:%s:%s" % (username, realm, password) sha.new(string).hexdigest() authentication-realm The authentication realm. Defaults to 'ZEO' pack-days Specify of days for the zeopack script to retain of history. Defaults to one day. pack-user If the ZEO server uses authentication, this is the username used by the zeopack script to connect to the ZEO server. pack-password If the ZEO server uses authentication, this is the password used by the zeopack script to connect to the ZEO server. zeo-conf-additional Give additional lines to zeo.conf. Make sure you indent any lines after the one with the parameter. monitor-address The address at which the monitor server should listen. The monitor server provides server statistics in a simple text format. relative-paths Set this to `true` to make the generated scripts use relative paths. You can also enable this in the `[buildout]` section.
RPMPackage plone.recipe.zope2instance-4.3-1.lbn25.noarch
This recipe creates and configures a Zope 2 instance in parts. It also installs a control script, which is like zopectl, in the bin/ directory. The name of the control script is the the name of the part in buildout. You can use it with a part like this:: [instance] recipe = plone.recipe.zope2instance zope2-location = /path/to/zope2/install user = admin:admin http-address = 8080 eggs = ${buildout:eggs} my.package products = ${buildout:directory}/products zcml = my.package Options ------- zope2-location The path where Zope 2 is installed. If you are also using the plone.recipe.zope2install recipe, and you have that configured as a part called 'zope2' prior to the zope2instance part, you can use ${zope2:location} for this parameter. zope-conf A relative or absolute path to a zope.conf file. If this is not given, a zope.conf will be generated based on the the options below. repozo The path to the repozo.py backup script. A wrapper for this will be generated in bin/repozo, which sets up the appropriate environment for running this. Defaults to "${zope2-location}/utilities/ZODBTools/repozo.py". Set this to an empty value if you do not want this script to be generated. The following options all affect the generated zope.conf: products A list of paths where Zope 2 products are installed. The first path takes precedence in case the same product is found in more than one directory. site-zcml If you want a custom site.zcml file, put its content here. If this option is used the zcml and zcml-additional options are ignored. zcml Install ZCML slugs for the packages listed, separated by whitespace. You can specify the type of slug by appending '-' and the type of slug you want to create. The valid types are configure, overrides and meta. Some examples: my.package-overrides my.package-meta zcml-additional Extra ZCML statements that should be included in the generated site.zcml file. extra-paths A list of paths where additional python packages are installed. The paths are searched in the given order after all egg and products paths. default-zpublisher-encoding This controls what character set is used to encode unicode data that reaches ZPublisher without any other specified encoding. This defaults to 'utf-8'. debug-mode Set to 'on' to turn on debug mode in Zope. Defaults to 'off'. verbose-security Set to 'on' to turn on verbose security (and switch to the Python security implementation). Defaults to 'off' (and the C security implementation). effective-user The name of the effective user for the Zope process. Defaults to not setting an effective user. ip-address The default IP address on which Zope's various server protocol implementations will listen for requests. If this is unset, Zope will listen on all IP addresses supported by the machine. This directive can be overridden on a per-server basis in the servers section. Defaults to not setting an ip-address. port-base Offset applied to the port numbers used for ZServer configurations. For example, if the http-server port is 8080 and the port-base is 1000, the HTTP server will listen on port 9080. This makes it easy to change the complete set of ports used by a Zope server process. Zope defaults to 0. http-address Give a port for the HTTP server. Defaults to 8080. http-fast-listen Set to off to defer opening of the HTTP socket until the end of the Zope startup phase. Defaults to on. Note: This option requires Zope >= 2.11. ftp-address Give a port for the FTP server. This enables the FTP server. webdav-address Give a port for the WebDAV server. This enables the WebDAV server webdav-force-connection-close Valid options are off and on. Defaults to off client-home Sets the clienthome for the generated instance. Defaults to ${buildout:directory}/var/<name of the section>. var Used to configure the base directory for all things going into var. Defaults to ${buildout:directory}/var. event-log The filename of the event log. Defaults to var/log/${partname}.log event-log-custom A custom section for the eventlog, to be able to use another event logger than 'logfile' event-log-level Set the level of the console output for the event log. Level may be any of CRITICAL, ERROR, WARN, INFO, DEBUG, or ALL. Defaults to INFO. z2-log The filename for the Z2 access log. Defaults to var/log/${partname}-Z2.log. z2-log-level Set the log level for the access log. Level may be any of CRITICAL, ERROR, WARN, INFO, DEBUG, or ALL. Defaults to WARN. access-log-custom Like 'event-log-custom', a custom section for the access logger, to be able to use another event logger than `logfile`. file-storage The filename where the ZODB data file will be stored. Defaults to var/filestorage/Data.fs. demo-storage If 'on' it enables the demostorage. It is not compatible with blob-storage and rel-storage. blob-storage The name of the directory where the ZODB blob data will be stored. rel-storage Allows to set a RelStorage instead of a FileStorage. Contains settings separated by newlines, with these values: - type: any database type supported (postgresql, oracle, mysql) - all other keys are passed on to the database-specific RelStorage adapter. Example:: rel-storage = type oracle dsn (DESCRIPTION=(ADDRESS=(HOST=s01))(CONNECT_DATA=(SERVICE_NAME=d01))) user tarek password secret zeo-client Set to 'on' to make this instance a ZEO client. In this case, setting the zeo-address option is required, and the file-storage option has no effect. To set up a ZEO server, you can use the plone.recipe.zope2zeoserver recipe. Defaults to 'off'. shared-blob If 'zeo-client' is set to 'on' and 'blob-storage' is set to a directory that is shared between this instance and the ZEO server (as configured by the 'blob-dir' setting on zeo.conf, then setting 'shared-blob' to 'on' causes this instance not to stream the blob file through the ZEO connection, but just to send the information of the file location to the ZEO server. zeo-address Set the address of the ZEO server. Defaults to 8100. zeo-client-name Set the name of the ZEO client. Defaults to the name of the part. If a false value is provided no zeo-client-name will be set. zeo-client-cache-size Set the size of the ZEO client cache. Defaults to '30MB'. zeo-client-client Set the persistent cache name that is used to construct the cache filenames. Persistent cache files are disabled by default. zeo-storage Set the storage number of the ZEO storage. Defaults to '1'. zeo-var Used in the zeo storage snippets to configure the zeo var folder. Defaults to $INSTANCE_HOME/var. zeo-username Enable ZEO authentication and use the given username when accessing the ZEO server. It is obligatory to also specify a zeo-password. zeo-password Password to use when connecting to a ZEO server with authentication enabled. zeo-realm Authentication realm to use when authentication with a ZEO server. Defaults to 'ZEO'. zodb-cache-size Set the ZODB cache size, i.e. the number of objects which the ZODB cache will try to hold. Defaults to 5000. zodb-cache-size-bytes Set the ZODB cache sizes in bytes. Requires ZODB 3.9 or later. zserver-threads Specify the number of threads that Zope's ZServer web server will use to service requests. You shouldn't change this unless you know what you are doing. Zope's default is 4. zodb-temporary-storage If given Zope's default temporary storage definition will be replaced by the lines of this parameter. environment-vars Define arbitrary key-value pairs for use as environment variables during Zope's run cycle. Example:: environment-vars = TZ US/Eastern TMP /var/tmp DISABLE_PTS True zope-conf-additional Give additional lines to zope.conf. Make sure you indent any lines after the one with the parameter. Example:: zope-conf-additional = locale fr_FR http-realm Slipknot
RPMPackage plone.recipe.zope2install-3.2-5.lbn25.noarch
Options ------- To specify which Zope 2 to use, use one of the following options: url The URL to a tarball to use for the Zope 2 installation. svn The URL for an subversion checkout to use for the Zope 2 installation. location The path to a local, existing Zope 2 installation. Note: For this to work Zope must have been built with the same Python used to run buildout. fake-zope-eggs If set to true, add fake egg links to Zope 3 libraries, so that setuptools can see and use them for dependencies lookup. Enabled by default since version 3.0 of this recipe. additional-fake-eggs Specify an optional list of additional fake eggs. Only include packages which are available on the Python path. You can also specify an explicit version to fake for an egg. For example:: additional-fake-eggs = ZODB3 = 3.7.1 zope.annotation = 3.3.2 Otherwise the faked eggs will always have version 0.0. The default value includes Acquisition, ClientForm, DateTime, docutils, ExtensionClass, mechanize, Persistence, pytz, RestrictedPython, tempstorage, ZConfig, zLOG, zodbcode, ZODB3, zdaemon and Zope2. skip-fake-eggs Specify an optional list of packages, for whom no fake egg is created. This allows to pull in new versions of some of the Zope packages via normal version requirements. smart-recompile Will not recompile Zope if it finds .so or .pyd files. This means you can move your buildout around and speed up builds. If you use many buildouts with the same Zope 2 version, then you can add "zope-directory" in the "buildout" section in your ~/.buildout/default.cfg file like this:: [buildout] zope-directory = /home/me/buildout/zope For installations from a tarball that directory will be used instead of the parts directory in your buildout. Each version of Zope will get it's own directory but if it's already installed the existing one will be reused. Exported variables ------------------ The following variables are set by this recipe and can be used in other parts. location The path to the Zope installation root. Reporting bugs or asking questions ---------------------------------- We have a shared bug tracker and help desk on Launchpad: https://bugs.launchpad.net/collective.buildout/
RPMPackage plone.recipe.zeoserver-1.3.1-1.lbn25.noarch
ZC Buildout recipe for installing a ZEO server
RPMPackage plone.recipe.codeanalysis-1.0rc1-1.lbn25.noarch
Introduction plone.recipe.codeanalysis provides static code analysis for Buildout-based Python projects, including flake8, JSHint, CSS Lint, and other code checks. This buildout recipe creates a script to run the code analysis: bin/code-analysis By default plone.recipe.codeanalysis also creates a git pre-commit hook, in order to run the code analysis automatically before each commit. plone.recipe.codeanalysis comes with a Jenkins integration, that allows to use the same code analysis settings on your local machine as well as on Jenkins. plone.recipe.codeanalysis provides a Jenkins setting that allows to run it on a Jenkins CI server and to process and integrate the output via the Jenkins Violations plugin. Usually you do not want the recipe to create Jenkins output files on your local machine. Therefore it makes sense to enable the Jenkins output only on the CI machine. The Jenkins job itself should run "bin/code-analysis": The Jenkins Violations plugin needs to be configured to read the output files generated by this configuration. pep8 (to read the flake8 output): **/parts/code-analysis/flake8.log csslint: **/parts/code-analysis/csslint.xml jslint (to read the jshint output: **/parts/code-analysis/jshint.xml
 
Distributions
To see exactly what is included in BastionLinux™, visit our online RPMDistro Builder.
Buy Now
Bastion CD
Subscribe Now
and get BastionLinux™ ...
Sponsored Links