ultimate-seed
ultimate-seed copied to clipboard
VERY intrigued with this project. Anyone successfully running this on Win8?
I'm eye-balling the MEAN stack but I like what I see with ultimate-seed. I don't mind getting my hands dirty tweaking things but just curious.. has ANYONE successfully installed this project on Windows 8? Thank You
@LarryEitel We'd love to add support for windows but we unfortunately do not have dev environment set up. Please refer to this page for some hints or clues how some others were able to run on Windows. We'd love to merge your pull request if you ever figure out what to do.
Got a dial-tone with your project on Win8 dev box!
I was having issues with running bcrypt
on Windows. I forgot that I crossed this bridge before. In this case, I ripped out "bcrypt": "~0.7.7"
from package.json
and replaced with "bcrypt-nodejs": "~0.0.3"
. See: https://npmjs.org/package/bcrypt-nodejs. In /server/models/User.js'
, I replaced bcrypt = require('bcrypt')
with bcrypt = require('bcrypt-nodejs')
.
I look forward to further exploring this excellent project.
@LarryEitel That's great to hear. In the past we actually switched to from bcrypt
to bcrypt-nodejs
but had to switch back as someone reported an issue with it. (https://github.com/pilwon/ultimate-seed/commit/655be0a74df35722aebf9244d84d1f3afac45b5d) Maybe that person got it the other way around. Please test and see if we could safely use the node.js native implementation version of bcrypt and let us know (or send PR). Thanks!
I'll look into it. I remember I had to also comment out the code inside /npm-scripts.js
postinstall()
. I manually created configs based on samples.
Switching to bcrypt-nodejs also fixed a "node-gyp" compile / binding error upon 'npm install' with Fedora 20 64-bit as well. Thanks @LarryEitel.