Yep, those are the local development instructions. That’s not how you deploy a production build on a remote server. None of the JS is concatenated and you’re probably downloading about 50 JS files (should only be 1 in production). It’s a very inefficient build that is intended to only be used on your local machine while developing.
Such as setting install mongo to true even if I already have an existing mongo db. Only works with certain versions of node. I have more details written down ill share shortly.
@bokarino-touch Here's a word that may save the headache. I agree the documentation is a bit un organized. There isn't a true guide that shows from a developer's perspective building a custom design. It lacks true "CMS" support. All of these are things that have been promised to come in the .15 release. With that being said, I can attest this is the best framework written in Node.js. I too have searched for quite some time, all leading to roadblocks that suggest moving outside of the node ecosystem.
I've written 3 custom cart solutions. All of which are major headaches to build. When you start looking at the framework from a modular perspective this is where things get complicated. Hence Customer A want's this , customer B want's that. Sure you could write a cart but can it fit the needs of 50,000 + developers or just your 1 customer. This is the issue I came across and that's why i put my bets with reaction.
I don’t disagree that our docs could use some work, but I do feel like the Customization Guide does walk you through much of what most developers want to do
If you are going to solve one problem for one customer I think sometimes rolling your own from scratch can sometimes be easier. And if it’s a learning project for you, then I totally get that. I’ve done it
RC is not for everybody
Unfotunately a lof of the times the problems that get you, you only discover when you get pretty far in.