Buildout recipe for downloading and installing RabbitMQ.
Copyright and License
Copyright 2009, 2010, 2011 Tobias Rodaebel
This software is released under the GNU Lesser General Public License, Version 3.
Credits
Thanks to Martijn Pieters for refactoring script generation to ensure that we always use an appropriate rabbitmq-server script for the installed version.
A brief documentation
This recipe takes a number of options:
- erlang-path
The path where to find the erlc command (default = find it in PATH).
- url
The URL to download the RabbitMQ source distribution.
- cookie
Optional string passed as cookie to the erl runtime (-setcookie).
- make
Alternate make command (e.g. gmake).
To further customize your RabbitMQ server configuration, create a rabbitmq-env file in the etc/ directory of your buildout, following the RabbitMQ configuration guide to set environment variables.
You can also create a rabbitmq.config file in the same location to provide erlang configuration statements.
Tests
We will define a buildout template used by the recipe:
>>> buildout_cfg = """ ... [buildout] ... parts = rabbitmq ... offline = true ... ... [rabbitmq] ... recipe = rod.recipe.rabbitmq ... url = http://www.rabbitmq.com/releases/rabbitmq-server/v2.4.1/rabbitmq-server-2.4.1.tar.gz ... """
We’ll start by creating a buildout:
>>> import os.path
>>> write('buildout.cfg', buildout_cfg)
Running the buildout gives us:
>>> output = system(buildout)
>>> if output.endswith("ebin ebin/rabbit.app < ebin/rabbit_app.in\n"): True
... else: print output
True
Changes
2.0.0 2011-05-18
Uses the buildout download cache if available.
Refactored script generation: reuses the existing scripts and customize them using the built-in rabbitmq-env sourcing option. This ensures we always use an appropriate rabbitmq-server script for the installed version.
Abandoned obsolete prefix buildout option.
Updated documentation.
1.1.7 2011-04-11
Added ‘make’ buildout option to specify an alternate make command (e.g. gmake).
1.1.6 2010-06-21
Using rabbit@localhost as NODENAME in order to provide portability of the database across machines independent of the hostname since you can not start RabbitMQ on a different machine with a different hostname (the database is tied to the hostname).
1.1.5 2010-06-21
Added support for setting an optional erlang cookie (-setcookie) through the ‘cookie’ option.
1.1.4 2010-05-09
Fixed issue where rabbitmq scripts used an incorrect default Erlang path when no erlang-path option was specified.
1.1.3 2010-05-03
Fixed parameter in generated rabbitmqctl script (-sname instead of -name).
1.1.2 2010-05-02
Fixed parameter in generated rabbitmq-server script (-sname instead of -name).
1.1.1 2010-03-21
Fixes an issue where the Erlang path wasn’t set correctly.
1.1.0 2010-03-20
Updated for RabbitMQ 1.7.2.
1.0.0 2009-08-23
Initial release.
Metadata
Release files for rod.recipe.rabbitmq 2.0.0
For a detailed explanation of source distributions (sdists) and built distributions (wheels), please see the package formats documentation.
Source distribution (sdist)
| File | Size | Uploaded | Provenance | |
|---|---|---|---|---|
| rod.recipe.rabbitmq-2.0.0.tar.gz | 11.9 kB | Without provenance | Details |
Release files / rod.recipe.rabbitmq-2.0.0.tar.gz
| Download URL | rod.recipe.rabbitmq-2.0.0.tar.gz |
|---|---|
| Size | 11.9 kB |
| Tags | Source |
|
SHA-256 checksum How to use checksums |
7c534008c5c7a4d303d6e920bdc86ba705df98fa869c60862c87efc44fa11b47
|
|
BLAKE2b-256 checksum How to use checksums |
874cadc1dfeee71b131a51e566eecb0587131e961232715495117a68cd50a3ff
|
| Upload date | |
|
Uploaded using Trusted Publishing? What is trusted publishing? |
No |
Security for rod.recipe.rabbitmq 2.0.0
Provenance
Provenance describes where a file came from. On PyPI, provenance is shared via attestations, which provide a verifiable record of the build or publishing details. View details, limitations and caveats.
No provenance found
None of the files in this release were uploaded with provenance metadata.
A note on package security
PyPI is a repository for distributing packages, not a service for auditing them. While third-party security researchers and our staff do their best to detect and remove malicious packages, PyPI cannot guarantee the quality, security or suitability of any given package.
To learn more about protecting yourself from malicious actors, visit our package security documentation.