Cassandra is configured via cassandra.yaml and log4j-server.properties files. Queuey doesn’t have any specific configuration requirements for Cassandra, though availability and durability guarantees depend on appropriate Cassandra settings.
Please refer to the Datastax community edition documentation for further details.
Queuey is implemented on top of the Pyramid web framework. Documentation for configuring WSGI servers and general deployment techniques therefor also apply to Queuey. The Pyramid cookbook contains some advice on a variety of web servers.
The simplest example of a Pyramid pipeline contains of the following:
[app:pyramidapp]
use = egg:queuey
[filter:catcherror]
paste.filter_app_factory = mozsvc.middlewares:make_err_mdw
[pipeline:main]
pipeline = catcherror
pyramidapp
Queuey is configured via an ini-style file, which is also used to configure general Pyramid settings. This ini file contains a number of sections. The following sections contain Queuey specific settings.
Contains a mapping of application name to application key. The application key acts as a shared secret between server and client. For example:
[application_keys]
app_1 = f25bfb8fe200475c8a0532a9cbe7651e
Configures the storage for message data.
Further settings are dependent on the storage.
Configures the storage for message metadata.
Further settings are dependent on the storage.
The Cassandra storages support the following additional settings:
Queuey uses metlog for logging metrics. For detailed information see the metlog docs.