Development Notes (For Contributors)

If experiencing SSL issues:

run this from the project directory. "git config http.sslVerify false" add --global for all projects

If you run into this while pushing changes:

error: RPC failed; result=55, HTTP code = 200 fatal: The remote end hung up unexpectedly fatal: The remote end hung up unexpectedly

Then run this: git config http.postBuffer 524288000 or git config --global http.postBuffer 524288000

Node:

SSL issues: (For people with using a proxy server which inject new certs into their chain)

npm config set strict-ssl false

On front-end

Git Node.js (node package manager)

If you haven’t already, you will probably want to add this to the git global config (run this line in a cmd prompt) git config --global http.sslVerify false

If you’re going to use npm with Ethernet, you’ll need to run this command

npm config set strict-ssl false

And after that, once you’re run yeoman once through (you’ll notice that bower brings up errors), you have to go in and manually edit the ‘.bowerrc’ file to add this line before it will ignore ssl issues.

"strict-ssl": false

Sadly, I have yet to find a way to add this to the global bower config… After that you’ll just have to remember that upon first setup, yeoman doesn’t add the “‘strict-ssl’: false” line to the ‘.bowerrc’ file automatically, so you may have to run it twice if you start any scaffolding projects on your own.

Ruby Install:

gem sources --add http://rubygems.org (Add this if having SSL issues) gem install compass