The following section documents environment variables for configuring AIStor to publish audit logs to an HTTP webhook endpoint. See Publish Audit Logs to HTTP Webhook for more complete documentation and tutorials on using these environment variables. Example Environment Variables You can specify multiple webhook endpoints as audit log targets by appending a unique identifier _ID for each set of related logging settings.

options: CAUTION This page on docs. ruby-lang.

Install a project with a clean slate and run tests

This page documents settings for configuring an MQTT service as a target for Bucket Notifications. See Publish Events to MQTT for a tutorial on using these settings. You can establish or modify settings by defining: an environment variable on the host system prior to starting or restarting the AIStor Server. Refer to your operating system’s documentation for how to define an environment variable. a configuration setting using mc admin config set. If you define both an environment variable and the similar configuration setting, AIStor uses the environment variable value.

Update packages

The following section documents settings for configuring AIStor to publish minio server logs to an HTTP webhook endpoint. See Publish Server Logs to HTTP Webhook for more complete documentation and tutorials on using these settings. Example Environment Variables You can specify multiple webhook endpoints as log targets by appending a unique identifier _ID for each set of related logging environment variables. For example, the following settings define two distinct server log webhook endpoints:

NEWS-2.1.0: NEWS for Ruby 2. This document is a list of user visible feature changes made between releases except for bug fixes.

Manage package owners

hash_inclusion: Hash Inclusion A hash is set-like in that it cannot have duplicate entries (or even duplicate keys). en.

Search for packages