Skip to content
This repository was archived by the owner on Nov 16, 2020. It is now read-only.

How to generate an .ez archive to be used? #16

Closed
MattBlack85 opened this issue Feb 15, 2018 · 2 comments
Closed

How to generate an .ez archive to be used? #16

MattBlack85 opened this issue Feb 15, 2018 · 2 comments

Comments

@MattBlack85
Copy link

MattBlack85 commented Feb 15, 2018

As per title, I have installed rabbitMQ server 3.7.3 and I'd like to use this plugin but I cannot see any instruction about how generating the needed .ez archive. There was #4 but the guide linked is about building from scratch the server + the plugins which is not something I'd like to do in my case

@michaelklishin
Copy link
Contributor

Thank you for your time.

Team RabbitMQ uses GitHub issues for specific actionable items engineers can work on. GitHub issues are not used for questions, investigations, root cause analysis, discussions of potential issues, etc (as defined by this team).

We get at least a dozen of questions through various venues every single day, often light on details.
At that rate GitHub issues can very quickly turn into a something impossible to navigate and make sense of even for our team. Because GitHub is a tool our team uses heavily nearly every day, the signal/noise ratio of issues is something we care about a lot.

Please post this to rabbitmq-users.

Thank you.

@michaelklishin
Copy link
Contributor

From RabbitMQ documentation:

Additional peer discovery mechanisms are available via plugins.
The following peer discovery plugins ship with RabbitMQ as of 3.7.0:

 * AWS (EC2)

michaelklishin added a commit that referenced this issue Feb 15, 2018
michaelklishin added a commit that referenced this issue Feb 15, 2018
References #16.

(cherry picked from commit 3f77107)
michaelklishin added a commit to rabbitmq/rabbitmq-website that referenced this issue Feb 15, 2018
Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.
Labels
None yet
Projects
None yet
Development

No branches or pull requests

2 participants