proxy /_api requests to hoodie using grunt-connect-proxy about hoodie-grunt-test HOT 6 CLOSED

Nice! Will test and update. Also switching to stylus to get rid of sass / ruby.

from hoodie-grunt-test.

I can read the file. API requests already get proxied to the hard coded hoodie port. But:

How to find out if hoodie started and wrote the file? The grunt-bg-shell (and similar plugins) have a callback function which gets executed when the shell command finished. hoodie keeps running so the callback doesn't get triggered.

Any ideas on how to trigger the "hoodie ready" event for grunt?

/cc @gr2m @janl @svnlto

from hoodie-grunt-test.

Another problem I see is that ask for a password on the first run. So we should wait with the following tasks until the stack.json file has been written or updated and eventually show the password prompt to the user

from hoodie-grunt-test.

The password issue can be solved with the requirement to run hoodie start solo at least once. I hope that is satisfactory.

from hoodie-grunt-test.

what @janl said.

from hoodie-grunt-test.

Updated this test repository. I Wrote a grunt-hoodie plugin that starts hoodie and checks for the stack.json. As soon as the stack.json is present the plugin triggers a callback which then sets the correct port in the Gruntfile.

Currently there is no output of hoodie visible (except when there is an error) and the hoodie child process does not get terminated when the Grunt task exits because of an error. Will open issues at grunt-hoodie for that.

As this issue is about the proxy which just got resolved, I'll close it.

from hoodie-grunt-test.