How to set up hive.js in web?
39 views
Skip to first unread message
YakovL
Apr 13, 2016, 9:28:00 AM4/13/16
to hive.js
Hi Marcel,
what's the simplest way to set up hive.js that you'd recommend? May be you have already tested some free node.js hostings? I think it can be useful on some maker sprints I'm participating when it gets to coding, so I'd like to try it out.. I also think that if a how-to for such setup is added, it will increase interest to hive.js from those who think about setting it up and testing with friends/colleages but who is not that advanced user (unlike etherpad in the past, there's now possibility to create a new doc right on the site, and 3 publicly shown demo docs is not enough to test it as in a real case).
Best regards,
Yakov.
what's the simplest way to set up hive.js that you'd recommend? May be you have already tested some free node.js hostings? I think it can be useful on some maker sprints I'm participating when it gets to coding, so I'd like to try it out.. I also think that if a how-to for such setup is added, it will increase interest to hive.js from those who think about setting it up and testing with friends/colleages but who is not that advanced user (unlike etherpad in the past, there's now possibility to create a new doc right on the site, and 3 publicly shown demo docs is not enough to test it as in a real case).
Best regards,
Yakov.
Marcel Klehr
Apr 13, 2016, 11:44:43 AM4/13/16
to hiv...@googlegroups.com
Hey Yakov,
I'm glad you reached out!
1. The demo: The demo is indeed not a substitute for a complete testing instance/environment. It mostly serves as a quick what-does-it-look-like-and-does-it-work-at-all satisfier. I'm a bit reluctant to provide a full instance, because I don't want this to be the main instance that everyone uses. I want to encourage people to install the software themselves. Even if I allowed new documents to be created, there would be no security (at least at the moment) -- anybody can figure out a document id, because they're incremental. Etherpad provides security by obscurity in that it suggests random document ids, but I think a better way is to integrate an authentication service (there's a github auth provider already, for example) and allow people to own documents and manage access rights for other people. I do recognize the need for instances that non-technical people can use, but I'm not sure whether I should / want to host such an instance myself. I value any input you may have here, though.(
2. On hosting providers: Hive should be pretty easy to integrate with most hosting providers. Heroku <https://heroku.com> allows free hosting if you only need your app 18 hours a day (see https://www.heroku.com/pricing), but others like CloudFoundry, AWS or App Engine should work equally fine. The only "difficulty" is probably that you cannot install the hive command globally on these platforms. Instead you can just install run it locally. Most platforms also need you to specify the node and npm versions and a start script, but those should be obvious from the docs. If you do have a problem or you're stuck somewhere, you can always get back to me here. I'm happy to help.
Cheers,
Marcel
I'm glad you reached out!
1. The demo: The demo is indeed not a substitute for a complete testing instance/environment. It mostly serves as a quick what-does-it-look-like-and-does-it-work-at-all satisfier. I'm a bit reluctant to provide a full instance, because I don't want this to be the main instance that everyone uses. I want to encourage people to install the software themselves. Even if I allowed new documents to be created, there would be no security (at least at the moment) -- anybody can figure out a document id, because they're incremental. Etherpad provides security by obscurity in that it suggests random document ids, but I think a better way is to integrate an authentication service (there's a github auth provider already, for example) and allow people to own documents and manage access rights for other people. I do recognize the need for instances that non-technical people can use, but I'm not sure whether I should / want to host such an instance myself. I value any input you may have here, though.(
2. On hosting providers: Hive should be pretty easy to integrate with most hosting providers. Heroku <https://heroku.com> allows free hosting if you only need your app 18 hours a day (see https://www.heroku.com/pricing), but others like CloudFoundry, AWS or App Engine should work equally fine. The only "difficulty" is probably that you cannot install the hive command globally on these platforms. Instead you can just install run it locally. Most platforms also need you to specify the node and npm versions and a start script, but those should be obvious from the docs. If you do have a problem or you're stuck somewhere, you can always get back to me here. I'm happy to help.
Cheers,
Marcel
--
You received this message because you are subscribed to the Google Groups "hive.js" group.
To unsubscribe from this group and stop receiving emails from it, send an email to hivejs+un...@googlegroups.com.
To post to this group, send email to hiv...@googlegroups.com.
To view this discussion on the web visit https://groups.google.com/d/msgid/hivejs/8da4e7a3-2ef4-41d8-bf66-71720e0b4de0%40googlegroups.com.
For more options, visit https://groups.google.com/d/optout.
Marcel Klehr
Apr 13, 2016, 3:15:39 PM4/13/16
to hiv...@googlegroups.com
By the way -- hive also works on windows, so you can test it on your
machine and in your local network. I updated the installation
instructions, so that it's not required to know how to translate
unix commands into windows commands.
To view this discussion on the web visit https://groups.google.com/d/msgid/hivejs/570E6968.2060700%40gmx.net.
j.a.l...@gmail.com
Apr 25, 2016, 11:29:53 AM4/25/16
to hive.js
Hello Marcel,
thanks for the answer and sorry for the long delay.
I've tried Heroku and am puzzled a bit. I've installed the heroku toolbelt and other stuff (node.js was installed previously), then cloned hive.js:
git clone https://github.com/hivejs/hive
to a new folder, then in that folder proceeded as they suggest [1]:
to a new folder, then in that folder proceeded as they suggest [1]:
heroku create
which gave me some expected messages, but I don't see any .git folder either inside hive/ or in the same folder as it is. Then I've tried
heroku ps:scale web=1
and it responded as
Scaling dynos... done, now running web at 1:Free
Which suggests everything is ok. But when I've opened my app page, it said "An error occurred in the application and your page could not be served. Please try again in a few moments. If you are the application owner, check your logs for details." heroku logs told me:
2016-04-25T14:34:33.459783+00:00 heroku[api]: Release v2 created by ________@________
2016-04-25T14:34:33.459783+00:00 heroku[api]: Enable Logplex by ________@________
2016-04-25T14:46:38.716970+00:00 heroku[api]: Scale to web=1 by ________@________
2016-04-25T14:46:38.772999+00:00 heroku[api]: Release v3 created by ________@________
2016-04-25T14:46:38.772999+00:00 heroku[api]: Deploy 59632f4 by ________@________
2016-04-25T14:46:39.200646+00:00 heroku[slug-compiler]: Slug compilation started
2016-04-25T14:46:39.200652+00:00 heroku[slug-compiler]: Slug compilation finished
2016-04-25T14:46:40.025291+00:00 heroku[web.1]: Starting process with command `npm start`
2016-04-25T14:46:42.600746+00:00 app[web.1]: npm ERR! Linux 3.13.0-79-generic
2016-04-25T14:46:42.601570+00:00 app[web.1]: npm ERR! argv "/app/.heroku/node/bin/node" "/app/.heroku/node/bin/npm" "start"
2016-04-25T14:46:42.601947+00:00 app[web.1]: npm ERR! node v5.10.1
2016-04-25T14:46:42.602343+00:00 app[web.1]: npm ERR! npm v3.8.3
2016-04-25T14:46:42.604099+00:00 app[web.1]:
2016-04-25T14:46:42.605615+00:00 app[web.1]: npm ERR! missing script: start
2016-04-25T14:46:42.605849+00:00 app[web.1]: npm ERR!
2016-04-25T14:46:42.606044+00:00 app[web.1]: npm ERR! If you need help, you may report this error at:
2016-04-25T14:46:42.606203+00:00 app[web.1]: npm ERR! <https://github.com/npm/npm/issues>
2016-04-25T14:46:42.614895+00:00 app[web.1]: npm ERR! Please include the following file with any support request:
2016-04-25T14:46:42.614683+00:00 app[web.1]:
2016-04-25T14:46:42.614957+00:00 app[web.1]: npm ERR! /app/npm-debug.log
2016-04-25T14:46:43.552582+00:00 heroku[web.1]: Process exited with status 1
2016-04-25T14:46:43.570904+00:00 heroku[web.1]: State changed from starting to crashed
2016-04-25T14:46:43.572079+00:00 heroku[web.1]: State changed from crashed to starting
2016-04-25T14:46:44.853339+00:00 heroku[web.1]: Starting process with command `npm start`
2016-04-25T14:46:47.740351+00:00 app[web.1]: npm ERR! Linux 3.13.0-79-generic
2016-04-25T14:46:47.741107+00:00 app[web.1]: npm ERR! argv "/app/.heroku/node/bin/node" "/app/.heroku/node/bin/npm" "start"
2016-04-25T14:46:47.741516+00:00 app[web.1]: npm ERR! node v5.10.1
2016-04-25T14:46:47.742110+00:00 app[web.1]: npm ERR! npm v3.8.3
2016-04-25T14:46:47.744969+00:00 app[web.1]: npm ERR! missing script: start
2016-04-25T14:46:47.744010+00:00 app[web.1]:
2016-04-25T14:46:47.745495+00:00 app[web.1]: npm ERR! <https://github.com/npm/npm/issues>
2016-04-25T14:46:47.755948+00:00 app[web.1]:
2016-04-25T14:46:47.756263+00:00 app[web.1]: npm ERR! Please include the following file with any support request:
2016-04-25T14:46:47.756426+00:00 app[web.1]: npm ERR! /app/npm-debug.log
2016-04-25T14:46:47.745150+00:00 app[web.1]: npm ERR!
2016-04-25T14:46:47.745308+00:00 app[web.1]: npm ERR! If you need help, you may report this error at:
2016-04-25T14:46:48.638395+00:00 heroku[web.1]: Process exited with status 1
2016-04-25T14:46:48.651870+00:00 heroku[web.1]: State changed from starting to crashed
2016-04-25T15:00:37.740566+00:00 heroku[router]: at=error code=H10 desc="App crashed" method=GET path="/" host=morning-eyrie-26758.herokuapp.com request_id=b8e0a999-41b1-4c6c-840e-934eb65a08cc fwd="83.149.244.216" dyno= connect= service= status=503 bytes=
2016-04-25T15:00:41.375452+00:00 heroku[router]: at=error code=H10 desc="App crashed" method=GET path="/favicon.ico" host=morning-eyrie-26758.herokuapp.com request_id=b3740055-05fa-47ff-9fda-936f6147474b fwd="83.149.244.216" dyno= connect= service= status=503 bytes=
(I've substituted the used mail with ________@________) I can see this is about npm, but this doesn't help me much as the only thing I've done with npm is successful calls like npm install ajax so I don't really know much about it.
So it would be lovely if you can give me some hint about this. Or should I ask on StackOverflow or somewhere else? I've already reported the problem to Heroku using the button inside their guide, may be they'll help.
Best regards,
Yakov.
[1] https://devcenter.heroku.com/articles/getting-started-with-nodejs?c=70130000000NhRJAA0&utm_campaign=Onboarding-Nurture-Email-1&utm_medium=email&utm_source=nurture&utm_content=devcenter&utm_term=start-nodejs#deploy-the-app
среда, 13 апреля 2016 г., 18:44:43 UTC+3 пользователь Marcel Klehr написал:
среда, 13 апреля 2016 г., 18:44:43 UTC+3 пользователь Marcel Klehr написал:
Marcel Klehr
Apr 25, 2016, 11:50:23 AM4/25/16
to hiv...@googlegroups.com
Hey Yakov,
By all means, asking here is fine. There's not much traffic here yet anyway ;)
hivejs/hive is just the hive cli, so it won't help you much ;)
I recommend installing hive.js using `hive init` as explained in the docs: http://docs.hivejs.org/setup/installation.html
After you've completed this step you need to install the hive command in your hive dir to be able to push it to heroku, too: `npm install hive`
Then you need to add a start script to your package.json: https://docs.npmjs.com/misc/scripts
The start script should be `hive -s queue -s http`
If you need to change settings dynamically, you can set env vars in the start script declaration as well: e.g. `hive_yoursetting=blub`
(I just noticed, this is broken, though... :/)
Hope this gets you farther.
Cheers,
Marcel
By all means, asking here is fine. There's not much traffic here yet anyway ;)
hivejs/hive is just the hive cli, so it won't help you much ;)
I recommend installing hive.js using `hive init` as explained in the docs: http://docs.hivejs.org/setup/installation.html
After you've completed this step you need to install the hive command in your hive dir to be able to push it to heroku, too: `npm install hive`
Then you need to add a start script to your package.json: https://docs.npmjs.com/misc/scripts
The start script should be `hive -s queue -s http`
If you need to change settings dynamically, you can set env vars in the start script declaration as well: e.g. `hive_yoursetting=blub`
(I just noticed, this is broken, though... :/)
Hope this gets you farther.
Cheers,
Marcel
To view this discussion on the web visit https://groups.google.com/d/msgid/hivejs/f080722d-b2ec-4a76-af31-e95ad0fbee15%40googlegroups.com.
YakovL
Apr 27, 2016, 9:52:39 AM4/27/16
to hive.js
Hi Marcel,
Yeah, I have to admit, that's a quite number of steps. During hive init there was a number of choises which I've made as kind of "educated guesses" althought I have almost no idea what some of them mean (especially broadcast transport, "Should I write package.json?", "Should I install the necessary hive components?").
In fact, I've got a number of errors/warnings during npm install -g hive:
npm WARN peerDependencies The peer dependency gulf@4.x included from hive-interface-shoe will no
npm WARN peerDependencies longer be automatically installed to fulfill the peerDependency
npm WARN peerDependencies in npm 3+. Your application will need to depend on it explicitly.
npm WARN peerDependencies The peer dependency gulf@3.x included from gulf-textarea will no
npm WARN peerDependencies longer be automatically installed to fulfill the peerDependency
npm WARN peerDependencies in npm 3+. Your application will need to depend on it explicitly.
--\-
npm WARN unmet dependency <some path>\heroku_hive\hive\node_modules\hive-interface-shoe\node_modules\dataplex\node_modules\concat-stream requires readable-stream@'~2.0.0' but will load
npm WARN unmet dependency <some path>\heroku_hive\hive\node_modules\hive-interface-shoe\node_modules\dataplex\node_modules\readable-stream,
npm WARN unmet dependency which is version 1.1.14
npm WARN unmet dependency <some path>\heroku_hive\hive\node_modules\hive-interface-shoe\node_modules\dataplex\node_modules\multiplex requires through2@'^0.5.1' but will load
npm WARN unmet dependency <some path>\heroku_hive\hive\node_modules\hive-interface-shoe\node_modules\dataplex\node_modules\through2,
npm WARN unmet dependency which is version 1.1.1
npm WARN unmet dependency <some path>\heroku_hive\hive\node_modules\hive-interface-shoe\node_modules\dataplex\node_modules\through2 requires xtend@'>=4.0.0 <4.1.0-0' but will load
npm WARN unmet dependency <some path>\heroku_hive\hive\node_modules\hive-interface-shoe\node_modules\dataplex\node_modules\xtend,
npm WARN unmet dependency which is version 3.0.0
npm WARN unmet dependency <some path>\heroku_hive\hive\node_modules\hive-interface-shoe\node_modules\dataplex\node_modules\concat-stream requires readable-stream@'~2.0.0' but will load
npm WARN unmet dependency <some path>\heroku_hive\hive\node_modules\hive-interface-shoe\node_modules\dataplex\node_modules\readable-stream,
npm WARN unmet dependency which is version 1.1.14
npm WARN unmet dependency <some path>\heroku_hive\hive\node_modules\hive-interface-shoe\node_modules\dataplex\node_modules\multiplex requires through2@'^0.5.1' but will load
npm WARN unmet dependency <some path>\heroku_hive\hive\node_modules\hive-interface-shoe\node_modules\dataplex\node_modules\through2,
npm WARN unmet dependency which is version 1.1.1
npm WARN unmet dependency <some path>\heroku_hive\hive\node_modules\hive-interface-shoe\node_modules\dataplex\node_modules\through2 requires xtend@'>=4.0.0 <4.1.0-0' but will load
npm WARN unmet dependency <some path>\heroku_hive\hive\node_modules\hive-interface-shoe\node_modules\dataplex\node_modules\xtend,
npm WARN unmet dependency which is version 3.0.0
npm WARN unmet dependency <some path>\heroku_hive\hive\node_modules\hive-core\node_modules\duplexify\node_modules\readable-stream\node_modules\inline-process-browser\node_modules\falafel requires isarray@'0.0.1' but will load
npm WARN unmet dependency <some path>\heroku_hive\hive\node_modules\hive-core\node_modules\duplexify\node_modules\readable-stream\node_modules\isarray,
npm WARN unmet dependency which is version 1.0.0
npm WARN unmet dependency <some path>\heroku_hive\hive\node_modules\hive-core\node_modules\duplexify\node_modules\readable-stream\node_modules\inline-process-browser\node_modules\through2 requires readable-stream@'>=1.0.33-1 <1.1.0-0' but will load
npm WARN unmet dependency <some path>\heroku_hive\hive\node_modules\hive-core\node_modules\duplexify\node_modules\readable-stream,
npm WARN unmet dependency which is version 2.1.0
npm WARN deprecated npm...@2.0.9: this package has been reintegrated into npm and is now out of date with respect to npm
npm WARN unmet dependency <some path>\heroku_hive\hive\node_modules\hive-core\node_modules\waterline\node_modules\anchor requires lodash@'3.10.1' but will load
npm WARN unmet dependency <some path>\heroku_hive\hive\node_modules\hive-core\node_modules\waterline\node_modules\lodash,
npm WARN unmet dependency which is version 3.9.3
npm WARN unmet dependency <some path>\heroku_hive\hive\node_modules\hive-core\node_modules\waterline\node_modules\switchback requires lodash@'~2.4.1' but will load
npm WARN unmet dependency <some path>\heroku_hive\hive\node_modules\hive-core\node_modules\waterline\node_modules\lodash,
npm WARN unmet dependency which is version 3.9.3
npm WARN unmet dependency <some path>\heroku_hive\hive\node_modules\hive-core\node_modules\waterline\node_modules\waterline-criteria requires lodash@'~2.4.1' but will load
npm WARN unmet dependency <some path>\heroku_hive\hive\node_modules\hive-core\node_modules\waterline\node_modules\lodash,
npm WARN unmet dependency which is version 3.9.3
npm WARN unmet dependency <some path>\heroku_hive\hive\node_modules\hive-core\node_modules\waterline\node_modules\waterline-schema requires lodash@'~3.10.0' but will load
npm WARN unmet dependency <some path>\heroku_hive\hive\node_modules\hive-core\node_modules\waterline\node_modules\lodash,
npm WARN unmet dependency which is version 3.9.3
npm WARN unmet dependency <some path>\heroku_hive\hive\node_modules\hive-ui\node_modules\babelify\node_modules\babel-core\node_modules\babel-register\node_modules\source-map-support requires source-map@'0.1.32' but will load
npm WARN unmet dependency <some path>\heroku_hive\hive\node_modules\hive-ui\node_modules\babelify\node_modules\babel-core\node_modules\source-map,
npm WARN unmet dependency which is version 0.5.5
npm WARN unmet dependency <some path>\heroku_hive\hive\node_modules\hive-ui\node_modules\babel-polyfill\node_modules\babel-runtime requires core-js@'^1.0.0' but will load
npm WARN unmet dependency <some path>\heroku_hive\hive\node_modules\hive-ui\node_modules\babel-polyfill\node_modules\core-js,
npm WARN unmet dependency which is version 2.3.0
npm WARN unmet dependency <some path>\heroku_hive\hive\node_modules\hive-ui\node_modules\hive-client-shoe\node_modules\dataplex\node_modules\multiplex\node_modules\multibuffer requires varint@'^3.0.1' but will load
npm WARN unmet dependency <some path>\heroku_hive\hive\node_modules\hive-ui\node_modules\hive-client-shoe\node_modules\dataplex\node_modules\multiplex\node_modules\varint,
npm WARN unmet dependency which is version 1.0.0
npm WARN unmet dependency <some path>\heroku_hive\hive\node_modules\hive-ui\node_modules\hive-client-shoe\node_modules\dataplex\node_modules\multiplex\node_modules\through2 requires readable-stream@'~1.0.17' but will load
npm WARN unmet dependency <some path>\heroku_hive\hive\node_modules\hive-ui\node_modules\hive-client-shoe\node_modules\dataplex\node_modules\readable-stream,
npm WARN unmet dependency which is version 1.1.14
npm WARN unmet dependency <some path>\heroku_hive\hive\node_modules\hive-core\node_modules\waterline\node_modules\anchor\node_modules\geojsonhint\node_modules\optimist requires minimist@'~0.0.1' but will load
npm WARN unmet dependency <some path>\heroku_hive\hive\node_modules\hive-core\node_modules\waterline\node_modules\anchor\node_modules\geojsonhint\node_modules\minimist,
npm WARN unmet dependency which is version 1.1.1
npm WARN unmet dependency <some path>\heroku_hive\hive\node_modules\hive-core\node_modules\waterline\node_modules\prompt\node_modules\utile requires async@'~0.2.9' but will load
npm WARN unmet dependency <some path>\heroku_hive\hive\node_modules\hive-core\node_modules\waterline\node_modules\async,
npm WARN unmet dependency which is version 1.2.1
npm WARN unmet dependency <some path>\heroku_hive\hive\node_modules\hive-core\node_modules\waterline\node_modules\prompt\node_modules\winston requires async@'0.2.x' but will load
npm WARN unmet dependency <some path>\heroku_hive\hive\node_modules\hive-core\node_modules\waterline\node_modules\async,
npm WARN unmet dependency which is version 1.2.1
npm WARN unmet dependency <some path>\heroku_hive\hive\node_modules\hive-core\node_modules\waterline\node_modules\prompt\node_modules\winston requires pkginfo@'0.3.x' but will load
npm WARN unmet dependency <some path>\heroku_hive\hive\node_modules\hive-core\node_modules\waterline\node_modules\prompt\node_modules\pkginfo,
npm WARN unmet dependency which is version 0.4.0
npm WARN unmet dependency <some path>\heroku_hive\hive\node_modules\hive-ui\node_modules\babel-polyfill\node_modules\babel-runtime requires core-js@'^1.0.0' but will load
npm WARN unmet dependency <some path>\heroku_hive\hive\node_modules\hive-ui\node_modules\babel-polyfill\node_modules\core-js,
npm WARN unmet dependency which is version 2.3.0
npm WARN unmet dependency <some path>\heroku_hive\hive\node_modules\hive-core\node_modules\waterline\node_modules\anchor\node_modules\geojsonhint\node_modules\optimist requires minimist@'~0.0.1' but will load
npm WARN unmet dependency <some path>\heroku_hive\hive\node_modules\hive-core\node_modules\waterline\node_modules\anchor\node_modules\geojsonhint\node_modules\minimist,
npm WARN unmet dependency which is version 1.1.1
npm WARN unmet dependency <some path>\heroku_hive\hive\node_modules\hive-core\node_modules\waterline\node_modules\prompt\node_modules\utile requires async@'~0.2.9' but will load
npm WARN unmet dependency <some path>\heroku_hive\hive\node_modules\hive-core\node_modules\waterline\node_modules\async,
npm WARN unmet dependency which is version 1.2.1
npm WARN unmet dependency <some path>\heroku_hive\hive\node_modules\hive-core\node_modules\waterline\node_modules\prompt\node_modules\winston requires async@'0.2.x' but will load
npm WARN unmet dependency <some path>\heroku_hive\hive\node_modules\hive-core\node_modules\waterline\node_modules\async,
npm WARN unmet dependency which is version 1.2.1
npm WARN unmet dependency <some path>\heroku_hive\hive\node_modules\hive-core\node_modules\waterline\node_modules\prompt\node_modules\winston requires pkginfo@'0.3.x' but will load
npm WARN unmet dependency <some path>\heroku_hive\hive\node_modules\hive-core\node_modules\waterline\node_modules\prompt\node_modules\pkginfo,
npm WARN unmet dependency which is version 0.4.0
npm WARN unmet dependency <some path>\heroku_hive\hive\node_modules\hive-ui\node_modules\babel-polyfill\node_modules\babel-runtime requires core-js@'^1.0.0' but will load
npm WARN unmet dependency <some path>\heroku_hive\hive\node_modules\hive-ui\node_modules\babel-polyfill\node_modules\core-js,
npm WARN unmet dependency which is version 2.3.0
npm WARN unmet dependency <some path>\heroku_hive\hive\node_modules\hive-core\node_modules\waterline\node_modules\anchor\node_modules\geojsonhint\node_modules\optimist requires minimist@'~0.0.1' but will load
npm WARN unmet dependency <some path>\heroku_hive\hive\node_modules\hive-core\node_modules\waterline\node_modules\anchor\node_modules\geojsonhint\node_modules\minimist,
npm WARN unmet dependency which is version 1.1.1
npm WARN unmet dependency <some path>\heroku_hive\hive\node_modules\hive-core\node_modules\waterline\node_modules\prompt\node_modules\utile requires async@'~0.2.9' but will load
npm WARN unmet dependency <some path>\heroku_hive\hive\node_modules\hive-core\node_modules\waterline\node_modules\async,
npm WARN unmet dependency which is version 1.2.1
npm WARN unmet dependency <some path>\heroku_hive\hive\node_modules\hive-core\node_modules\waterline\node_modules\prompt\node_modules\winston requires async@'0.2.x' but will load
npm WARN unmet dependency <some path>\heroku_hive\hive\node_modules\hive-core\node_modules\waterline\node_modules\async,
npm WARN unmet dependency which is version 1.2.1
npm WARN unmet dependency <some path>\heroku_hive\hive\node_modules\hive-core\node_modules\waterline\node_modules\prompt\node_modules\winston requires pkginfo@'0.3.x' but will load
npm WARN unmet dependency <some path>\heroku_hive\hive\node_modules\hive-core\node_modules\waterline\node_modules\prompt\node_modules\pkginfo,
npm WARN unmet dependency which is version 0.4.0
npm WARN unmet dependency <some path>\heroku_hive\hive\node_modules\hive-ui\node_modules\babel-polyfill\node_modules\babel-runtime requires core-js@'^1.0.0' but will load
npm WARN unmet dependency <some path>\heroku_hive\hive\node_modules\hive-ui\node_modules\babel-polyfill\node_modules\core-js,
npm WARN unmet dependency which is version 2.3.0
> cldr...@29.0.1 install <some path>\heroku_hive\hive\node_modules\hive-ui\node_modules\cldr-data
> node install.js
GET `https://github.com/unicode-cldr/cldr-core/archive/29.0.0.zip`
GET `https://github.com/unicode-cldr/cldr-dates-modern/archive/29.0.0.zip`
GET `https://github.com/unicode-cldr/cldr-cal-buddhist-modern/archive/29.0.0.zip`
GET `https://github.com/unicode-cldr/cldr-cal-chinese-modern/archive/29.0.0.zip`
GET `https://github.com/unicode-cldr/cldr-cal-coptic-modern/archive/29.0.0.zip`
GET `https://github.com/unicode-cldr/cldr-cal-dangi-modern/archive/29.0.0.zip`
GET `https://github.com/unicode-cldr/cldr-cal-ethiopic-modern/archive/29.0.0.zip`
GET `https://github.com/unicode-cldr/cldr-cal-hebrew-modern/archive/29.0.0.zip`
GET `https://github.com/unicode-cldr/cldr-cal-indian-modern/archive/29.0.0.zip`
GET `https://github.com/unicode-cldr/cldr-cal-islamic-modern/archive/29.0.0.zip`
GET `https://github.com/unicode-cldr/cldr-cal-japanese-modern/archive/29.0.0.zip`
GET `https://github.com/unicode-cldr/cldr-cal-persian-modern/archive/29.0.0.zip`
GET `https://github.com/unicode-cldr/cldr-cal-roc-modern/archive/29.0.0.zip`
GET `https://github.com/unicode-cldr/cldr-localenames-modern/archive/29.0.0.zip`
GET `https://github.com/unicode-cldr/cldr-misc-modern/archive/29.0.0.zip`
GET `https://github.com/unicode-cldr/cldr-numbers-modern/archive/29.0.0.zip`
GET `https://github.com/unicode-cldr/cldr-segments-modern/archive/29.0.0.zip`
GET `https://github.com/unicode-cldr/cldr-units-modern/archive/29.0.0.zip`
Unpacking it into `./`---------------------] 31220543/Infinity 0% 0.0s/
npm WARN peerDependencies The peer dependency virtual-dom@^2.0.0 included from vdom-to-html will no
npm WARN peerDependencies longer be automatically installed to fulfill the peerDependency
npm WARN peerDependencies in npm 3+. Your application will need to depend on it explicitly.
npm WARN unmet dependency <some path>\heroku_hive\hive\node_modules\hive-ui\node_modules\babel-polyfill\node_modules\babel-runtime requires core-js@'^1.0.0' but will load
npm WARN unmet dependency <some path>\heroku_hive\hive\node_modules\hive-ui\node_modules\babel-polyfill\node_modules\core-js,
npm WARN unmet dependency which is version 2.3.0
npm WARN unmet dependency <some path>\heroku_hive\hive\node_modules\sails-mysql\node_modules\waterline-sequel requires lodash@'3.10.0' but will load
npm WARN unmet dependency <some path>\heroku_hive\hive\node_modules\sails-mysql\node_modules\lodash,
npm WARN unmet dependency which is version 3.10.1
npm WARN unmet dependency <some path>\heroku_hive\hive\node_modules\sails-mysql\node_modules\waterline-sequel requires lodash@'3.10.0' but will load
npm WARN unmet dependency <some path>\heroku_hive\hive\node_modules\sails-mysql\node_modules\lodash,
npm WARN unmet dependency which is version 3.10.1
npm WARN unmet dependency <some path>\heroku_hive\hive\node_modules\sails-mysql\node_modules\waterline-sequel requires lodash@'3.10.0' but will load
npm WARN unmet dependency <some path>\heroku_hive\hive\node_modules\sails-mysql\node_modules\lodash,
npm WARN unmet dependency which is version 3.10.1
npm ERR! Windows_NT 10.0.10586
npm ERR! argv "C:\\1my\\tools_and_components\\coding_and_components\\nodejs\\node.exe" "C:\\1my\\tools_and_components\\coding_and_components\\nodejs\\node_modules\\npm\\bin\\npm-cli.js" "update" "--loglevel=warn"
npm ERR! node v4.4.3
npm ERR! npm v2.15.1
npm ERR! code EPEERINVALID
npm ERR! peerinvalid The package gu...@4.0.4 does not satisfy its siblings' peerDependencies requirements!
npm ERR! peerinvalid Peer gulf-t...@4.0.0 wants gulf@3.x
Yeah, I have to admit, that's a quite number of steps. During hive init there was a number of choises which I've made as kind of "educated guesses" althought I have almost no idea what some of them mean (especially broadcast transport, "Should I write package.json?", "Should I install the necessary hive components?").
In fact, I've got a number of errors/warnings during npm install -g hive:
npm WARN peerDependencies The peer dependency gulf@4.x included from hive-interface-shoe will no
npm WARN peerDependencies longer be automatically installed to fulfill the peerDependency
npm WARN peerDependencies in npm 3+. Your application will need to depend on it explicitly.
npm WARN peerDependencies The peer dependency gulf@3.x included from gulf-textarea will no
npm WARN peerDependencies longer be automatically installed to fulfill the peerDependency
npm WARN peerDependencies in npm 3+. Your application will need to depend on it explicitly.
--\-
npm WARN unmet dependency <some path>\heroku_hive\hive\node_modules\hive-interface-shoe\node_modules\dataplex\node_modules\concat-stream requires readable-stream@'~2.0.0' but will load
npm WARN unmet dependency <some path>\heroku_hive\hive\node_modules\hive-interface-shoe\node_modules\dataplex\node_modules\readable-stream,
npm WARN unmet dependency which is version 1.1.14
npm WARN unmet dependency <some path>\heroku_hive\hive\node_modules\hive-interface-shoe\node_modules\dataplex\node_modules\multiplex requires through2@'^0.5.1' but will load
npm WARN unmet dependency <some path>\heroku_hive\hive\node_modules\hive-interface-shoe\node_modules\dataplex\node_modules\through2,
npm WARN unmet dependency which is version 1.1.1
npm WARN unmet dependency <some path>\heroku_hive\hive\node_modules\hive-interface-shoe\node_modules\dataplex\node_modules\through2 requires xtend@'>=4.0.0 <4.1.0-0' but will load
npm WARN unmet dependency <some path>\heroku_hive\hive\node_modules\hive-interface-shoe\node_modules\dataplex\node_modules\xtend,
npm WARN unmet dependency which is version 3.0.0
npm WARN unmet dependency <some path>\heroku_hive\hive\node_modules\hive-interface-shoe\node_modules\dataplex\node_modules\concat-stream requires readable-stream@'~2.0.0' but will load
npm WARN unmet dependency <some path>\heroku_hive\hive\node_modules\hive-interface-shoe\node_modules\dataplex\node_modules\readable-stream,
npm WARN unmet dependency which is version 1.1.14
npm WARN unmet dependency <some path>\heroku_hive\hive\node_modules\hive-interface-shoe\node_modules\dataplex\node_modules\multiplex requires through2@'^0.5.1' but will load
npm WARN unmet dependency <some path>\heroku_hive\hive\node_modules\hive-interface-shoe\node_modules\dataplex\node_modules\through2,
npm WARN unmet dependency which is version 1.1.1
npm WARN unmet dependency <some path>\heroku_hive\hive\node_modules\hive-interface-shoe\node_modules\dataplex\node_modules\through2 requires xtend@'>=4.0.0 <4.1.0-0' but will load
npm WARN unmet dependency <some path>\heroku_hive\hive\node_modules\hive-interface-shoe\node_modules\dataplex\node_modules\xtend,
npm WARN unmet dependency which is version 3.0.0
npm WARN unmet dependency <some path>\heroku_hive\hive\node_modules\hive-core\node_modules\duplexify\node_modules\readable-stream\node_modules\inline-process-browser\node_modules\falafel requires isarray@'0.0.1' but will load
npm WARN unmet dependency <some path>\heroku_hive\hive\node_modules\hive-core\node_modules\duplexify\node_modules\readable-stream\node_modules\isarray,
npm WARN unmet dependency which is version 1.0.0
npm WARN unmet dependency <some path>\heroku_hive\hive\node_modules\hive-core\node_modules\duplexify\node_modules\readable-stream\node_modules\inline-process-browser\node_modules\through2 requires readable-stream@'>=1.0.33-1 <1.1.0-0' but will load
npm WARN unmet dependency <some path>\heroku_hive\hive\node_modules\hive-core\node_modules\duplexify\node_modules\readable-stream,
npm WARN unmet dependency which is version 2.1.0
npm WARN deprecated npm...@2.0.9: this package has been reintegrated into npm and is now out of date with respect to npm
npm WARN unmet dependency <some path>\heroku_hive\hive\node_modules\hive-core\node_modules\waterline\node_modules\anchor requires lodash@'3.10.1' but will load
npm WARN unmet dependency <some path>\heroku_hive\hive\node_modules\hive-core\node_modules\waterline\node_modules\lodash,
npm WARN unmet dependency which is version 3.9.3
npm WARN unmet dependency <some path>\heroku_hive\hive\node_modules\hive-core\node_modules\waterline\node_modules\switchback requires lodash@'~2.4.1' but will load
npm WARN unmet dependency <some path>\heroku_hive\hive\node_modules\hive-core\node_modules\waterline\node_modules\lodash,
npm WARN unmet dependency which is version 3.9.3
npm WARN unmet dependency <some path>\heroku_hive\hive\node_modules\hive-core\node_modules\waterline\node_modules\waterline-criteria requires lodash@'~2.4.1' but will load
npm WARN unmet dependency <some path>\heroku_hive\hive\node_modules\hive-core\node_modules\waterline\node_modules\lodash,
npm WARN unmet dependency which is version 3.9.3
npm WARN unmet dependency <some path>\heroku_hive\hive\node_modules\hive-core\node_modules\waterline\node_modules\waterline-schema requires lodash@'~3.10.0' but will load
npm WARN unmet dependency <some path>\heroku_hive\hive\node_modules\hive-core\node_modules\waterline\node_modules\lodash,
npm WARN unmet dependency which is version 3.9.3
npm WARN unmet dependency <some path>\heroku_hive\hive\node_modules\hive-ui\node_modules\babelify\node_modules\babel-core\node_modules\babel-register\node_modules\source-map-support requires source-map@'0.1.32' but will load
npm WARN unmet dependency <some path>\heroku_hive\hive\node_modules\hive-ui\node_modules\babelify\node_modules\babel-core\node_modules\source-map,
npm WARN unmet dependency which is version 0.5.5
npm WARN unmet dependency <some path>\heroku_hive\hive\node_modules\hive-ui\node_modules\babel-polyfill\node_modules\babel-runtime requires core-js@'^1.0.0' but will load
npm WARN unmet dependency <some path>\heroku_hive\hive\node_modules\hive-ui\node_modules\babel-polyfill\node_modules\core-js,
npm WARN unmet dependency which is version 2.3.0
npm WARN unmet dependency <some path>\heroku_hive\hive\node_modules\hive-ui\node_modules\hive-client-shoe\node_modules\dataplex\node_modules\multiplex\node_modules\multibuffer requires varint@'^3.0.1' but will load
npm WARN unmet dependency <some path>\heroku_hive\hive\node_modules\hive-ui\node_modules\hive-client-shoe\node_modules\dataplex\node_modules\multiplex\node_modules\varint,
npm WARN unmet dependency which is version 1.0.0
npm WARN unmet dependency <some path>\heroku_hive\hive\node_modules\hive-ui\node_modules\hive-client-shoe\node_modules\dataplex\node_modules\multiplex\node_modules\through2 requires readable-stream@'~1.0.17' but will load
npm WARN unmet dependency <some path>\heroku_hive\hive\node_modules\hive-ui\node_modules\hive-client-shoe\node_modules\dataplex\node_modules\readable-stream,
npm WARN unmet dependency which is version 1.1.14
npm WARN unmet dependency <some path>\heroku_hive\hive\node_modules\hive-core\node_modules\waterline\node_modules\anchor\node_modules\geojsonhint\node_modules\optimist requires minimist@'~0.0.1' but will load
npm WARN unmet dependency <some path>\heroku_hive\hive\node_modules\hive-core\node_modules\waterline\node_modules\anchor\node_modules\geojsonhint\node_modules\minimist,
npm WARN unmet dependency which is version 1.1.1
npm WARN unmet dependency <some path>\heroku_hive\hive\node_modules\hive-core\node_modules\waterline\node_modules\prompt\node_modules\utile requires async@'~0.2.9' but will load
npm WARN unmet dependency <some path>\heroku_hive\hive\node_modules\hive-core\node_modules\waterline\node_modules\async,
npm WARN unmet dependency which is version 1.2.1
npm WARN unmet dependency <some path>\heroku_hive\hive\node_modules\hive-core\node_modules\waterline\node_modules\prompt\node_modules\winston requires async@'0.2.x' but will load
npm WARN unmet dependency <some path>\heroku_hive\hive\node_modules\hive-core\node_modules\waterline\node_modules\async,
npm WARN unmet dependency which is version 1.2.1
npm WARN unmet dependency <some path>\heroku_hive\hive\node_modules\hive-core\node_modules\waterline\node_modules\prompt\node_modules\winston requires pkginfo@'0.3.x' but will load
npm WARN unmet dependency <some path>\heroku_hive\hive\node_modules\hive-core\node_modules\waterline\node_modules\prompt\node_modules\pkginfo,
npm WARN unmet dependency which is version 0.4.0
npm WARN unmet dependency <some path>\heroku_hive\hive\node_modules\hive-ui\node_modules\babel-polyfill\node_modules\babel-runtime requires core-js@'^1.0.0' but will load
npm WARN unmet dependency <some path>\heroku_hive\hive\node_modules\hive-ui\node_modules\babel-polyfill\node_modules\core-js,
npm WARN unmet dependency which is version 2.3.0
npm WARN unmet dependency <some path>\heroku_hive\hive\node_modules\hive-core\node_modules\waterline\node_modules\anchor\node_modules\geojsonhint\node_modules\optimist requires minimist@'~0.0.1' but will load
npm WARN unmet dependency <some path>\heroku_hive\hive\node_modules\hive-core\node_modules\waterline\node_modules\anchor\node_modules\geojsonhint\node_modules\minimist,
npm WARN unmet dependency which is version 1.1.1
npm WARN unmet dependency <some path>\heroku_hive\hive\node_modules\hive-core\node_modules\waterline\node_modules\prompt\node_modules\utile requires async@'~0.2.9' but will load
npm WARN unmet dependency <some path>\heroku_hive\hive\node_modules\hive-core\node_modules\waterline\node_modules\async,
npm WARN unmet dependency which is version 1.2.1
npm WARN unmet dependency <some path>\heroku_hive\hive\node_modules\hive-core\node_modules\waterline\node_modules\prompt\node_modules\winston requires async@'0.2.x' but will load
npm WARN unmet dependency <some path>\heroku_hive\hive\node_modules\hive-core\node_modules\waterline\node_modules\async,
npm WARN unmet dependency which is version 1.2.1
npm WARN unmet dependency <some path>\heroku_hive\hive\node_modules\hive-core\node_modules\waterline\node_modules\prompt\node_modules\winston requires pkginfo@'0.3.x' but will load
npm WARN unmet dependency <some path>\heroku_hive\hive\node_modules\hive-core\node_modules\waterline\node_modules\prompt\node_modules\pkginfo,
npm WARN unmet dependency which is version 0.4.0
npm WARN unmet dependency <some path>\heroku_hive\hive\node_modules\hive-ui\node_modules\babel-polyfill\node_modules\babel-runtime requires core-js@'^1.0.0' but will load
npm WARN unmet dependency <some path>\heroku_hive\hive\node_modules\hive-ui\node_modules\babel-polyfill\node_modules\core-js,
npm WARN unmet dependency which is version 2.3.0
npm WARN unmet dependency <some path>\heroku_hive\hive\node_modules\hive-core\node_modules\waterline\node_modules\anchor\node_modules\geojsonhint\node_modules\optimist requires minimist@'~0.0.1' but will load
npm WARN unmet dependency <some path>\heroku_hive\hive\node_modules\hive-core\node_modules\waterline\node_modules\anchor\node_modules\geojsonhint\node_modules\minimist,
npm WARN unmet dependency which is version 1.1.1
npm WARN unmet dependency <some path>\heroku_hive\hive\node_modules\hive-core\node_modules\waterline\node_modules\prompt\node_modules\utile requires async@'~0.2.9' but will load
npm WARN unmet dependency <some path>\heroku_hive\hive\node_modules\hive-core\node_modules\waterline\node_modules\async,
npm WARN unmet dependency which is version 1.2.1
npm WARN unmet dependency <some path>\heroku_hive\hive\node_modules\hive-core\node_modules\waterline\node_modules\prompt\node_modules\winston requires async@'0.2.x' but will load
npm WARN unmet dependency <some path>\heroku_hive\hive\node_modules\hive-core\node_modules\waterline\node_modules\async,
npm WARN unmet dependency which is version 1.2.1
npm WARN unmet dependency <some path>\heroku_hive\hive\node_modules\hive-core\node_modules\waterline\node_modules\prompt\node_modules\winston requires pkginfo@'0.3.x' but will load
npm WARN unmet dependency <some path>\heroku_hive\hive\node_modules\hive-core\node_modules\waterline\node_modules\prompt\node_modules\pkginfo,
npm WARN unmet dependency which is version 0.4.0
npm WARN unmet dependency <some path>\heroku_hive\hive\node_modules\hive-ui\node_modules\babel-polyfill\node_modules\babel-runtime requires core-js@'^1.0.0' but will load
npm WARN unmet dependency <some path>\heroku_hive\hive\node_modules\hive-ui\node_modules\babel-polyfill\node_modules\core-js,
npm WARN unmet dependency which is version 2.3.0
> cldr...@29.0.1 install <some path>\heroku_hive\hive\node_modules\hive-ui\node_modules\cldr-data
> node install.js
GET `https://github.com/unicode-cldr/cldr-core/archive/29.0.0.zip`
GET `https://github.com/unicode-cldr/cldr-dates-modern/archive/29.0.0.zip`
GET `https://github.com/unicode-cldr/cldr-cal-buddhist-modern/archive/29.0.0.zip`
GET `https://github.com/unicode-cldr/cldr-cal-chinese-modern/archive/29.0.0.zip`
GET `https://github.com/unicode-cldr/cldr-cal-coptic-modern/archive/29.0.0.zip`
GET `https://github.com/unicode-cldr/cldr-cal-dangi-modern/archive/29.0.0.zip`
GET `https://github.com/unicode-cldr/cldr-cal-ethiopic-modern/archive/29.0.0.zip`
GET `https://github.com/unicode-cldr/cldr-cal-hebrew-modern/archive/29.0.0.zip`
GET `https://github.com/unicode-cldr/cldr-cal-indian-modern/archive/29.0.0.zip`
GET `https://github.com/unicode-cldr/cldr-cal-islamic-modern/archive/29.0.0.zip`
GET `https://github.com/unicode-cldr/cldr-cal-japanese-modern/archive/29.0.0.zip`
GET `https://github.com/unicode-cldr/cldr-cal-persian-modern/archive/29.0.0.zip`
GET `https://github.com/unicode-cldr/cldr-cal-roc-modern/archive/29.0.0.zip`
GET `https://github.com/unicode-cldr/cldr-localenames-modern/archive/29.0.0.zip`
GET `https://github.com/unicode-cldr/cldr-misc-modern/archive/29.0.0.zip`
GET `https://github.com/unicode-cldr/cldr-numbers-modern/archive/29.0.0.zip`
GET `https://github.com/unicode-cldr/cldr-segments-modern/archive/29.0.0.zip`
GET `https://github.com/unicode-cldr/cldr-units-modern/archive/29.0.0.zip`
Unpacking it into `./`---------------------] 31220543/Infinity 0% 0.0s/
npm WARN peerDependencies The peer dependency virtual-dom@^2.0.0 included from vdom-to-html will no
npm WARN peerDependencies longer be automatically installed to fulfill the peerDependency
npm WARN peerDependencies in npm 3+. Your application will need to depend on it explicitly.
npm WARN unmet dependency <some path>\heroku_hive\hive\node_modules\hive-ui\node_modules\babel-polyfill\node_modules\babel-runtime requires core-js@'^1.0.0' but will load
npm WARN unmet dependency <some path>\heroku_hive\hive\node_modules\hive-ui\node_modules\babel-polyfill\node_modules\core-js,
npm WARN unmet dependency which is version 2.3.0
npm WARN unmet dependency <some path>\heroku_hive\hive\node_modules\sails-mysql\node_modules\waterline-sequel requires lodash@'3.10.0' but will load
npm WARN unmet dependency <some path>\heroku_hive\hive\node_modules\sails-mysql\node_modules\lodash,
npm WARN unmet dependency which is version 3.10.1
npm WARN unmet dependency <some path>\heroku_hive\hive\node_modules\sails-mysql\node_modules\waterline-sequel requires lodash@'3.10.0' but will load
npm WARN unmet dependency <some path>\heroku_hive\hive\node_modules\sails-mysql\node_modules\lodash,
npm WARN unmet dependency which is version 3.10.1
npm WARN unmet dependency <some path>\heroku_hive\hive\node_modules\sails-mysql\node_modules\waterline-sequel requires lodash@'3.10.0' but will load
npm WARN unmet dependency <some path>\heroku_hive\hive\node_modules\sails-mysql\node_modules\lodash,
npm WARN unmet dependency which is version 3.10.1
npm ERR! Windows_NT 10.0.10586
npm ERR! argv "C:\\1my\\tools_and_components\\coding_and_components\\nodejs\\node.exe" "C:\\1my\\tools_and_components\\coding_and_components\\nodejs\\node_modules\\npm\\bin\\npm-cli.js" "update" "--loglevel=warn"
npm ERR! node v4.4.3
npm ERR! npm v2.15.1
npm ERR! code EPEERINVALID
npm ERR! peerinvalid The package gu...@4.0.4 does not satisfy its siblings' peerDependencies requirements!
npm ERR! peerinvalid Peer gulf-t...@4.0.0 wants gulf@3.x
npm ERR! Please include the following file with any support request:
npm ERR! <some path>\heroku_hive\hive\npm-debug.log
Mh. npm seems to have failed. You'll have to install the components yourself.
(I've substituted the path to my folder with <some path>). hive init tells me that
There is already a hive instance in this directory. Continue anyway?
so I aborted. I've tried npm install hive and that gave me
npm ERR! Windows_NT 10.0.10586
npm ERR! argv "C:\\1my\\tools_and_components\\coding_and_components\\nodejs\\node.exe" "C:\\1my\\tools_and_components\\coding_and_components\\nodejs\\node_modules\\npm\\bin\\npm-cli.js" "install" "hive"
npm ERR! node v4.4.3
npm ERR! npm v2.15.1
npm ERR! code EPEERINVALID
npm ERR! peerinvalid The package gu...@4.0.4 does not satisfy its siblings' peerDependencies requirements!
npm ERR! peerinvalid Peer gulf-t...@4.0.0 wants gulf@3.x
Mh. npm seems to have failed. You'll have to install the components yourself.
(I've substituted the path to my folder with <some path>). hive init tells me that
There is already a hive instance in this directory. Continue anyway?
so I aborted. I've tried npm install hive and that gave me
npm ERR! Windows_NT 10.0.10586
npm ERR! argv "C:\\1my\\tools_and_components\\coding_and_components\\nodejs\\node.exe" "C:\\1my\\tools_and_components\\coding_and_components\\nodejs\\node_modules\\npm\\bin\\npm-cli.js" "install" "hive"
npm ERR! node v4.4.3
npm ERR! npm v2.15.1
npm ERR! code EPEERINVALID
npm ERR! peerinvalid The package gu...@4.0.4 does not satisfy its siblings' peerDependencies requirements!
npm ERR! peerinvalid Peer gulf-t...@4.0.0 wants gulf@3.x
npm ERR! Please include the following file with any support request:
npm ERR! C:\1my\tools_and_components\heroku_hive\hive\npm-debug.log
(I've attached the log here; not sure if it's better to attach those large responses as txt files instead of putting them here inline). Ehm.. any idea what's next? :)
Best regards,
Yakov.
понедельник, 25 апреля 2016 г., 18:50:23 UTC+3 пользователь Marcel Klehr написал:
(I've attached the log here; not sure if it's better to attach those large responses as txt files instead of putting them here inline). Ehm.. any idea what's next? :)
Best regards,
Yakov.
понедельник, 25 апреля 2016 г., 18:50:23 UTC+3 пользователь Marcel Klehr написал:
Marcel Klehr
Apr 27, 2016, 4:04:38 PM4/27/16
to hiv...@googlegroups.com
Hey Yakov,
all's not lost -- don't panic ;)
First up, this is also a learning experience for me as some things, of course, seem obvious to me as a node developer that I haven't considered writing documentation about yet, so, I value your input and feel sorry at the same time, because you have to go through this :)
The paragraphs below `hive init` at http://docs.hivejs.org/setup/installation.html should explain what the less obvious things are.
Usually if you're installing hive the first time, you want to answer the questions "Should I install ..." / "Should I write ..." with *yes*, those are just fail-safes, in case you have altered anything, so it doesn't overwrite your changes. For testing I recommend the memory broadcast transport, it's basically a stub, though, so you will not be able to scale the app.
When working with node applications, package.json files are manifests for programs and libraries that (among other things) specify the name, the version and the dependencies of the package.
The warnings can be considered harmless, they come from hive's dependencies. The error that terminated the installation is a regression on hive's part, though. I've just fixed it.
If you like you could join the gitter or IRC chat rooms, so I'd be able to help you more quickly when you have questions, doubts or you get errors.
Cheers,
Marcel
all's not lost -- don't panic ;)
First up, this is also a learning experience for me as some things, of course, seem obvious to me as a node developer that I haven't considered writing documentation about yet, so, I value your input and feel sorry at the same time, because you have to go through this :)
The paragraphs below `hive init` at http://docs.hivejs.org/setup/installation.html should explain what the less obvious things are.
Usually if you're installing hive the first time, you want to answer the questions "Should I install ..." / "Should I write ..." with *yes*, those are just fail-safes, in case you have altered anything, so it doesn't overwrite your changes. For testing I recommend the memory broadcast transport, it's basically a stub, though, so you will not be able to scale the app.
When working with node applications, package.json files are manifests for programs and libraries that (among other things) specify the name, the version and the dependencies of the package.
The warnings can be considered harmless, they come from hive's dependencies. The error that terminated the installation is a regression on hive's part, though. I've just fixed it.
If you like you could join the gitter or IRC chat rooms, so I'd be able to help you more quickly when you have questions, doubts or you get errors.
Cheers,
Marcel
To view this discussion on the web visit https://groups.google.com/d/msgid/hivejs/a284d881-e0ae-40ed-9869-fce87b497a0e%40googlegroups.com.
Marcel Klehr
May 3, 2016, 1:59:44 PM5/3/16
to hiv...@googlegroups.com
Hey again,
it just occurred to me that it might be even simpler if I just set up a git repo with a hive instance in it ready to be deployed to heroku.
I would need some more information on how you'd like your instance to be configured. Would you be available for a skype or jitsi call?
Cheers,
Marcel
it just occurred to me that it might be even simpler if I just set up a git repo with a hive instance in it ready to be deployed to heroku.
I would need some more information on how you'd like your instance to be configured. Would you be available for a skype or jitsi call?
Cheers,
Marcel
To view this discussion on the web visit https://groups.google.com/d/msgid/hivejs/57211B2E.6080000%40gmx.net.
YakovL
May 9, 2016, 5:12:03 PM5/9/16
to hive.js
Hello Marcel,
sorry for being absent this long, I somehow failed to set the option to recieve replies by mail and missed your replies except the one in the other thread; but also I got quite busy because all the PhD texts should be ready rather soon.
Anyways,
sorry for being absent this long, I somehow failed to set the option to recieve replies by mail and missed your replies except the one in the other thread; but also I got quite busy because all the PhD texts should be ready rather soon.
Anyways,
> The error that terminated the installation is a regression on hive's part, though. I've just fixed it.
so from which step should I go again? Should I delete smth to prevent conflicts with the previous ~installation?
> you could join the gitter or IRC chat rooms
Ah, I have to admit, I haven't used any instant messages clients for quite a while (since they implemented IM in social networks; by the way, do you have a vk.com account?). Would you recommend a client or may be a web-client? I've got Telegram for desktop, though, used for a little collaboration recently.
As an offtopic I have to admit, this WYSIWYGish stuff brought me some new ideas and I've made a very early prototype of WYSIWYG plugin for TiddlyWiki Classic. May be some day I can connect it with hive.js, too :)
As for Skype, I can install it (even got an account), but most of the time I'll be able to chat, no video-call (at least at work).
Best regards,
Yakov.
вторник, 3 мая 2016 г., 20:59:44 UTC+3 пользователь Marcel Klehr написал:
As an offtopic I have to admit, this WYSIWYGish stuff brought me some new ideas and I've made a very early prototype of WYSIWYG plugin for TiddlyWiki Classic. May be some day I can connect it with hive.js, too :)
As for Skype, I can install it (even got an account), but most of the time I'll be able to chat, no video-call (at least at work).
Best regards,
Yakov.
вторник, 3 мая 2016 г., 20:59:44 UTC+3 пользователь Marcel Klehr написал:
Hey again,
it just occurred to me that it might be even simpler if I just set up a git repo with a hive instance in it ready to be deployed to heroku.
I would need some more information on how you'd like your instance to be configured. Would you be available for a skype or jitsi call?
Cheers,
Marcel
On 27.04.2016 22:03, Marcel Klehr wrote:
Hey Yakov,
all's not lost -- don't panic ;)
First up, this is also a learning experience for me as some things, of course, seem obvious to me as a node developer that I haven't considered writing documentation about yet, so, I value your input and feel sorry at the same time, because you have to go through this :)
The paragraphs below `hive init` at http://docs.hivejs.org/setup/installation.html should explain what the less obvious things are.
Usually if you're installing hive the first time, you want to answer the questions "Should I install ..." / "Should I write ..." with *yes*, those are just fail-safes, in case you have altered anything, so it doesn't overwrite your changes. For testing I recommend the memory broadcast transport, it's basically a stub, though, so you will not be able to scale the app.
When working with node applications, package.json files are manifests for programs and libraries that (among other things) specify the name, the version and the dependencies of the package.
The warnings can be considered harmless, they come from hive's dependencies. The error that terminated the installation is a regression on hive's part, though. I've just fixed it.
If you like you could join the gitter or IRC chat rooms, so I'd be able to help you more quickly when you have questions, doubts or you get errors.
Cheers,
Marcel
On 27.04.2016 15:52, YakovL wrote:
Hi Marcel,
Yeah, I have to admit, that's a quite number of steps. During hive init there was a number of choises which I've made as kind of "educated guesses" althought I have almost no idea what some of them mean (especially broadcast transport, "Should I write package.json?", "Should I install the necessary hive components?").
In fact, I've got a number of errors/warnings during npm install -g hive:
npm WARN peerDependencies The peer dependency gu...@4.x included from hive-interface-shoe will no
npm WARN peerDependencies longer be automatically installed to fulfill the peerDependency
npm WARN peerDependencies in npm 3+. Your application will need to depend on it explicitly.
npm WARN peerDependencies The peer dependency gu...@3.x included from gulf-textarea will no
npm WARN peerDependencies The peer dependency virtu...@^2.0.0 included from vdom-to-html will no
npm WARN peerDependencies longer be automatically installed to fulfill the peerDependency
npm WARN peerDependencies in npm 3+. Your application will need to depend on it explicitly.
npm WARN unmet dependency <some path>\heroku_hive\hive\node_modules\hive-ui\node_modules\babel-polyfill\node_modules\babel-runtime requires core-js@'^1.0.0' but will load
npm WARN unmet dependency <some path>\heroku_hive\hive\node_modules\hive-ui\node_modules\babel-polyfill\node_modules\core-js,
npm WARN unmet dependency which is version 2.3.0
npm WARN unmet dependency <some path>\heroku_hive\hive\node_modules\sails-mysql\node_modules\waterline-sequel requires lodash@'3.10.0' but will load
npm WARN unmet dependency <some path>\heroku_hive\hive\node_modules\sails-mysql\node_modules\lodash,
npm WARN unmet dependency which is version 3.10.1
npm WARN unmet dependency <some path>\heroku_hive\hive\node_modules\sails-mysql\node_modules\waterline-sequel requires lodash@'3.10.0' but will load
npm WARN unmet dependency <some path>\heroku_hive\hive\node_modules\sails-mysql\node_modules\lodash,
npm WARN unmet dependency which is version 3.10.1
npm WARN unmet dependency <some path>\heroku_hive\hive\node_modules\sails-mysql\node_modules\waterline-sequel requires lodash@'3.10.0' but will load
npm WARN unmet dependency <some path>\heroku_hive\hive\node_modules\sails-mysql\node_modules\lodash,
npm WARN unmet dependency which is version 3.10.1
npm ERR! Windows_NT 10.0.10586
npm ERR! argv "C:\\1my\\tools_and_components\\coding_and_components\\nodejs\\node.exe" "C:\\1my\\tools_and_components\\coding_and_components\\nodejs\\node_modules\\npm\\bin\\npm-cli.js" "update" "--loglevel=warn"
npm ERR! node v4.4.3
npm ERR! npm v2.15.1
npm ERR! code EPEERINVALID
npm ERR! peerinvalid The package gu...@4.0.4 does not satisfy its siblings' peerDependencies requirements!
npm ERR! peerinvalid Peer gulf-t...@4.0.0 wants gu...@3.x
npm ERR! Please include the following file with any support request:
npm ERR! <some path>\heroku_hive\hive\npm-debug.log
Mh. npm seems to have failed. You'll have to install the components yourself.
(I've substituted the path to my folder with <some path>). hive init tells me that
There is already a hive instance in this directory. Continue anyway?
so I aborted. I've tried npm install hive and that gave me
npm ERR! Windows_NT 10.0.10586
npm ERR! argv "C:\\1my\\tools_and_components\\coding_and_components\\nodejs\\node.exe" "C:\\1my\\tools_and_components\\coding_and_components\\nodejs\\node_modules\\npm\\bin\\npm-cli.js" "install" "hive"
npm ERR! node v4.4.3
npm ERR! npm v2.15.1
npm ERR! code EPEERINVALID
npm ERR! peerinvalid The package gu...@4.0.4 does not satisfy its siblings' peerDependencies requirements!
npm ERR! peerinvalid Peer gulf-t...@4.0.0 wants gu...@3.x
Marcel Klehr
May 20, 2016, 9:56:29 AM5/20/16
to hiv...@googlegroups.com
Hi Yakov,
as you've probably noticed, I've gotten around to releasing v0.8. I upgraded the heroku app repo to the new version and added some instructions to the README.
Let me know if you have trouble following the steps provided here: https://github.com/hivejs/heroku-app
Cheers,
Marcel
as you've probably noticed, I've gotten around to releasing v0.8. I upgraded the heroku app repo to the new version and added some instructions to the README.
Let me know if you have trouble following the steps provided here: https://github.com/hivejs/heroku-app
Cheers,
Marcel
To view this discussion on the web visit https://groups.google.com/d/msgid/hivejs/7f6c0113-ca2f-4712-b6c1-56d3ebc89a10%40googlegroups.com.
Reply all
Reply to author
Forward
0 new messages