Crates.io | amiquip |
lib.rs | amiquip |
version | 0.4.2 |
source | src |
created_at | 2019-03-31 21:42:08.371971 |
updated_at | 2022-01-12 22:34:43.56739 |
description | Pure Rust RabbitMQ client |
homepage | |
repository | https://github.com/jgallagher/amiquip |
max_upload_size | |
id | 125051 |
size | 343,250 |
amiquip is a RabbitMQ client written in pure Rust.
Add this to your Cargo.toml
:
[dependencies]
amiquip = "0.4"
For usage, see the documentation and examples.
The minimum supported Rust version for amiquip 0.4.2 is currently Rust 1.46.0, but that may change with a patch release (and could change with a patch release to a dependency without our knowledge).
By default, amiquip enables TLS support via the native-tls crate. You can disable support for TLS by turning off default features:
[dependencies]
amiquip = { version = "0.4", default-features = false }
If you disable TLS support, the methods Connection::open
,
Connection::open_tuned
, and Connection::open_tls_stream
will no longer be
available, as all three only allow secure connections. The methods
Connection::insecure_open
, Connection::insecure_open_tuned
, and
Connection::insecure_open_stream
will still be available; these methods
support unencrypted connections.
amiquip contains integration tests that require a RabbitMQ server. To run these,
set the AMIQUIP_TEST_URL
environment variable to an amqp://
or amqps://
URL
before running cargo test
. For example, if you have a RabbitMQ instance running
with the default guest account on your development machine:
bash$ AMIQUIP_TEST_URL=amqp://guest:guest@localhost cargo test
If the AMIQUIP_TEST_URL
environment variable is not set, all integration tests
will be skipped (and silently pass). If you run with --nocapture
, you will see
a warning printed on the first such skipped test:
bash$ cargo test -- nocapture
...
test integration_tests::exchange::test_declare ... AMIQUIP_TEST_URL not defined - skipping integration tests
...
This project is licensed under either of
at your option.
Unless you explicitly state otherwise, any contribution intentionally submitted for inclusion in amiquip by you, as defined in the Apache-2.0 license, shall be dual licensed as above, without any additional terms or conditions.