-
Notifications
You must be signed in to change notification settings - Fork 1k
Make install process Windows compatible #1333
Make install process Windows compatible #1333
Conversation
@@ -70,7 +70,7 @@ | |||
}, | |||
"scripts": { | |||
"main": "devserver.js", | |||
"postinstall": "./node_modules/bower/bin/bower install && tar -zcf dev/node_modules.tar.gz node_modules/;", | |||
"postinstall": "./node_modules/bower/bin/bower install", |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
for it to work on windows this needs to be
"postinstall": "node ./node_modules/bower/bin/bower install",
Makes this so it only runs on Heroku and allows Windows peeps to call `bower install`
bbbf48f
to
4c50b7c
Compare
Updated @vernak2539 . I'm sorry I didn't understand the comment. |
👍 |
web: tar -zcf dev/node_modules.tar.gz node_modules/ && grunt dist && node devserver.js |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
The tar step is to insure the node_modules in the dev environment deploy quickly to heroku correct? Or is there more going on here?
The archive is created in order to allow TravisCI to not run It's what Bootstrap does, except they use Python and AWS. I'm just using Heroku as my AWS, because...I can. "Free Heroku" should really be listed as a dev perk on our Salesforce job posts. |
right on |
Make install process Windows compatible
👍 |
Move node_module archiving to Procfile
tar
command, so it only run on Heroku, and fixes #1331 for those that run on Windows or don't havetar
installed. It also addsnode
before the bower command which makes it Windows compatible.