Not sure where to post this, so hopefully this is correct.
So in an effort to try and track down the bugs I’ve come across I decided to try my hand at running the dev environment. I think I am very close but for some reason I’m not seeing anything come up when I go the final
http://localhost:3000 page. The page loads, but its just the basic page (with the default infrastructure) without any specific content so the page is effectively empty. As part of the installation I did the mongodb snapshot restore thinking that might be the issue, but still no luck.
I’ve installed the system on Ubuntu 12.04 LTS and have tried both Firefox v26 and Chrome 31.0.1650.63–same problem on both.
I did the installation manually (I followed the “do-it-yourself way”) and wrote up my own installation guide for Ubuntu 12.04 (which I can post if that would be helpful), so there is likely something I missed vs. the “new, easy, buggy way”. I looked through the install scripts with that latter method and was afraid I might bork my Ubuntu environment hence the do-it-yourself approach (I’m a bit averse to running anything as root that hasn’t been pretty well tested).
There are no errors emitted from
bin/coco-dev-server. The only error I am seeing is during the start up of
bin/coco-brunch (which appear largely harmless):
$ bin/coco-brunch /bin/sh: 1: ulimit: error setting limit (Operation not permitted) 04 Jan 13:13:06 - warn: `-c, --config` option is deprecated. Use `--env` and `config.overrides` instead
The only part I really had to hack on to get to work was the
bower.json file located in the root of the tree so that
bin/coco-brunch wouldn’t complain. I had to copy it into several locations in the
bower_components directory until I stopped getting errors. The rest of the system came up pretty cleanly. Perhaps that’s the problem?