Search results

ftw.geo-1.3-1.lbn19.noarch

Introduction This product helps integrating the collective.geo.* packages and aims to provide some sensible defaults. Besides some integration glue it defines a new interface IGeocodableLocation that can be used to create adapters that knows how to represent the location of a content type with address-like fields as a string suitable for passing to a geocoding API. Purpose Automatic geocoding of IGeoreferenceable content types via an IGeocodableLocation adapter Caching of geocoding responses Only trigger geocoding lookups if location related fields on the content item changed Facilitate doing automatic geocoding based on location fields and still allow for manually setting custom coordinates Usage Automatically geocoding your content types In order for your content types to be automatically geocoded on ObjectEdited or ObjectInitialized events, you need to create an adapter for your content type that implements IGeocodableLocation and knows how to build a geocodable location string from the content type's location related fields. In order to implement the interface you need to define a getLocationString method on your adapter that returns the complete location as a comma separated string, with the location parts getting less specific from left to right.

ftw.jsondump-1.1.0-1.lbn25.noarch

ftw.jsondump provides JSON representations for Plone objects. By using adapters the JSON representation can easily be customized.

ftw.lawgiver-1.4.0-1.lbn19.noarch

Motivation Developing and maintaining complex Plone workflows is a time-consuming and cumbersome endeavor. Dozens of permissions need to be managed for different roles and different workflow states. Usually, this has to be done directly in the ZMI of Zope by selecting or unselecting thousands of checkboxes. This process has been shown to be very tedious and prone to errors. Furthermore, it is no simple task to document the workflow and the associated design decisions which led to the resulting configuration of permissions and roles. The extension or adaption of an existing workflow becomes very difficult, leading to workflows which are barely maintainable. Another problem poses the communication between workflow integrator and customer. The security system of Zope is based on a role-based access control (RBAC) which is intrinsically complex due to its use of roles, permissions, and workflow states. Experience has shown that these security concepts can be hard to convey to customers. How it works ftw.lawgiver helps solving these problems by using a DSL to describe how a workflow should work. The lawgiver then generates the complete workflow definition (definition.xml) based on this specification. By separating this specification from the resulting workflow definition (which is in XML) the specification does not have to use permissions--handling the permissions is the job of the lawgiver. Using the specification file the workflow can easily be regenerated at any time and will handle additional permissions automatically when regenerated. However, it is still the task of the developer to regenerate the definition.xml when more or other permissions have to be managed. He or she have to make sure that the workflow is properly installed with an upgrade step / reindexing security.

ftw.mobilenavigation-1.4.6-1.lbn19.noarch

This product helps to create a responsive design. There are following mobile_buttons in portal_actions defined: Toggle personaltools (default personaltools) Toggle searchbox (default searchbox) Toggle special navigation (special navigation, using AJAX to expand children) Navigation types You can choose between: Expandable navigation (install profile default) Sliding navigation (install profile slide navigation)

filebeat-7.3.0-1.git6f0ec01.lbn25.x86_64

Filebeat is an open source file harvester, mostly used to fetch logs files and feed them into logstash. Together with the libbeat lumberjack output is a replacement for logstash-forwarder. To learn more about Filebeat, check out https://www.elastic.co/products/beats/filebeat.

heartbeat-7.3.0-1.git6f0ec01.lbn25.x86_64

Heartbeat is a lightweight daemon that you install on a remote server to periodically check the status of your services and determine whether they are available. Unlike Metricbeat, which only tells you if your servers are up or down, Heartbeat tells you whether your services are reachable. Heartbeat is useful when you need to verify that you’re meeting your service level agreements for service uptime. It’s also useful for other scenarios, such as security use cases, when you need to verify that no one from the outside can access services on your private enterprise server. You can configure Heartbeat to ping all DNS-resolvable IP addresses for a specified hostname. That way, you can check all services that are load-balanced to see if they are available. When you configure Heartbeat, you specify monitors that identify the hostnames that you want to check. Each monitor runs based on the schedule that you specify. For example, you can configure one monitor to run every 10 minutes, and a different monitor to run between the hours of 9:00 and 17:00. Heartbeat currently supports monitors for checking hosts via: ICMP (v4 and v6) Echo Requests. Use the icmp monitor when you simply want to check whether a service is available. This monitor requires root access. TCP. Use the tcp monitor to connect via TCP. You can optionally configure this monitor to verify the endpoint by sending and/or receiving a custom payload. HTTP. Use the http monitor to connect via HTTP. You can optionally configure this monitor to verify that the service returns the expected response, such as a specific status code, response header, or content. The tcp and http monitors both support SSL/TLS and some proxy settings.

influxdb-1.3.1-0.1.git5887e92.lbn25.x86_64

InfluxDB is an open source distributed time series database with no external dependencies. It's useful for recording metrics, events, and performing analytics. It has a built-in HTTP API so you don't have to write any server side code to get up and running. InfluxDB is designed to be scalable, simple to install and manage, and fast to get data in and out. It aims to answer queries in real-time. That means every data point is indexed as it comes in and is immediately available in queries that should return in < 100ms.

influxdb-1.3.1-0.1.git5887e92.lbn25.x86_64

InfluxDB is an open source distributed time series database with no external dependencies. It's useful for recording metrics, events, and performing analytics. It has a built-in HTTP API so you don't have to write any server side code to get up and running. InfluxDB is designed to be scalable, simple to install and manage, and fast to get data in and out. It aims to answer queries in real-time. That means every data point is indexed as it comes in and is immediately available in queries that should return in < 100ms.

metricbeat-7.3.0-1.git6f0ec01.lbn25.x86_64

Metricbeat fetches a set of metrics on a predefined interval from the operating system and services such as Apache web server, Redis, and more.

nodejs-bigfunger-decompress-zip-0.2.0_stripfix2-1.lbn25.noarch

Extract files from a ZIP archive