[rabbitmq-discuss] RabbitMQ cluster on a single machine, OSX Lion, Homebrew

[Brendan Hay]

Note: The claimed 'no clashes' below, doesn't account for things like the
management plugin port ..

On Wed, Aug 15, 2012 at 6:13 PM, Brendan Hay <brendan at soundcloud.com> wrote:

> Rather than going through with all the *-env.conf shenanigans for
> development, I have a reusable bash mess that sets up N* nodes.
> It uses ruby foreman (gem install foreman) so I can enjoy colorfully
> interleaved rabbit startup output, and then Ctrl-C/SIGTERM to bring down
> the house.
>
> You'll need this entire directory:
> https://github.com/brendanhay/vanguard/tree/master/dev
> And is runnable via ./dev/run
>
> It looks for *.config files in ./dev, and sets up a node based on the
> filename with an incrementing port range and adjusted environment variables
> so there should be no clashes.
> (So your nodes from the default above, will be rabbit@`hostname` and
> chinchilla@`hostname`, add more configs as needed).
>
> If you're testing clustering, you will need to do all the
> rabbitmqctl shenanigans yourself.
>
> - Brendan
>
>
>
> On Wed, Aug 15, 2012 at 4:16 PM, Chris Johnson <wchrisjohnson at gmail.com>wrote:
>
>> If that is the case, would it make sense to update the RMQ online docs on
>> clustering to mention that as a caveat for Homebrew users? I just spent the
>> better part of a couple of DAYS trying to get this working. I kept thinking
>> it was user error on my part due to my inexperience with RMQ…
>>
>> I've updated the config file.
>>
>> Chris
>>
>> From: "Gavin M. Roy" <gmr at meetme.com>
>> Reply-To: Discussions about RabbitMQ <rabbitmq-discuss at lists.rabbitmq.com
>> >
>> Date: Wednesday, August 15, 2012 10:08 AM
>> To: Discussions about RabbitMQ <rabbitmq-discuss at lists.rabbitmq.com>
>> Subject: Re: [rabbitmq-discuss] RabbitMQ cluster on a single machine,
>> OSX Lion, Homebrew
>>
>>
>>
>> On Wed, Aug 15, 2012 at 10:01 AM, Chris Johnson <wchrisjohnson at gmail.com>wrote:
>>
>>>
>>
>> Good catch. I will either file a ticket for
>>> the homebrew change or just submit a pull request and make the change
>>> myself.
>>
>>
>> Update the rabbitmq-env.conf file with the node info you want to use. The
>> behavior of setting a default host in brew for RabbitMQ came out of a
>> compromise with the brew formula maintainers who did not want users to have
>> to use sudo to install RabbitMQ to insure it could start up. I can dig up
>> the pull request discussion if people are interested.
>>
>> Gavin
>> _______________________________________________ rabbitmq-discuss mailing
>> list rabbitmq-discuss at lists.rabbitmq.com
>> https://lists.rabbitmq.com/cgi-bin/mailman/listinfo/rabbitmq-discuss
>>
>> _______________________________________________
>> rabbitmq-discuss mailing list
>> rabbitmq-discuss at lists.rabbitmq.com
>> https://lists.rabbitmq.com/cgi-bin/mailman/listinfo/rabbitmq-discuss
>>
>>
>
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.rabbitmq.com/pipermail/rabbitmq-discuss/attachments/20120815/61b2c786/attachment.htm>