not clear how to configure the task

[rvdwijngaard]

Hi,

It is not clear to me how to configure this task. If I read the documentation I would expect if I omit the config section that it will just run mb. That is not the case. I have tried several options but I cannot get it working without altering your code. Am I missing something?

I would prefer to use the global installation of mountebank.

Cheers,
Ron

[bbyars]

Hi there,
Sorry for the slow response - you caught me on vacation. You are correct
that if you leave off the options, it will simply use 'mb' as the path.
However, you can't leave off the entire config section, as the
start/restart/stop keys define the parameters passed to mb. When I tested
using the following config, I was able to confirm it used the global mb
correctly:

mb: {
start: ['--port', 7777, '--allowInjection', '--mock', '--debug',
'--pidfile', 'mb-grunt.pid'],
restart: ['--port', 7777, '--allowInjection', '--mock', '--debug',
'--pidfile', 'mb-grunt.pid'],
stop: ['--pidfile', 'mb-grunt.pid']
}

The grunt log outputs the actual command executed, so for example, in the
config above, I get the following on the console:

Running "mb:restart" (mb) task
mb restart --port 7777 --allowInjection --mock --debug --pidfile
mb-grunt.pid

Can you copy your grunt logs in so I can see what's going on?
Thanks,
-Brandon

On Mon, Dec 21, 2015 at 3:17 PM, Ron van der Wijngaard <
[email protected]> wrote:

Hi,

It is not clear to me how to configure this task If I read the
documentation I would expect if I omit the config section that it will just
run mb That is not the case I have tried several options but I cannot get
it working without altering your code Am I missing something?

I would prefer to use the global installation of mountebank

Cheers,
Ron

—
Reply to this email directly or view it on GitHub
#1.