A little more documentation for the first timers about mean

Can't truly complain when a boatload of the hard work's been done here, but it'd be nice to see a quick how-to for moving a build live?

[greggh]

Completely agreed, no room for complaining. I just felt it would be great to have.

[liorkesos]

@greggh Thanks for the headsup and emphasis - I might be able to look at this in the next weeks.
If you could setup a shared google doc and paste the readme there and annotate the areas that aren't clear it would be AMAZING.
We'll work on the code but your experience as a newcomer is somehting we can't really simulate so any help there would be invaluable.
Thanks
Lior

[greggh]

There isn't anything wrong with the readme that I can tell. It could just use more information. I will have time in a few days, I can revisit the code and go over all the things that look like they need editing in order to personalize the project / go live. Then build a list. It seems to be a pretty simple thing though. Anything that the developer should actually edit, like passwords or salts or API keys should probably be listed in the readme.

[paultannenbaum]

+1

[lacivert]

👍

[mattfrear]

Some documentation on how to setup mongohq would be helpful - especially since the README.md suggests using mongohq.

I've deployed my app to heroku, then I've created a mongohq account, setup the heroku mongohq addon - do I need to do anything else? My app crashes on startup in heroku with loads of "Error: failed to connect to [localhost:27017]" messages - which sounds like mongo I think.

Great work so far guys - I'm happy to have gotten this far, since I'm a node, angular, heroku and mongo newbie!

[dudo]

Newb, checking in. Something I'm dealing with now. I'm following the Quick Install... I'm curious of how mongo plays here. If I grunt, I get an error message Error: failed to connect to [localhost:27017] with some other stuff. That's mongo's port, so I assumed I had to start mongod. I did, then grunt fires the server up.

Does that sound right, or should grunt fire up the mongo server as well?

Also, on forms, is there a way to get the field_with_errors class added to the dom for the fields that don't meet validation? (I'm coming rails)

[liorkesos]

yeah thats the idea.
First fire up mongo and the run grunt.
Grunt does not start the mongo (typically mongo would be executed as a
daemon in production systems and grunt as a different user.
Lior

On Mon, Dec 23, 2013 at 8:40 AM, Brett Dudo [email protected]:

Newb, checking in. Something I'm dealing with now. I'm following the Quick
Install... I'm curious of how mongo plays here. If I grunt, I get an error
message Error: failed to connect to [localhost:27017] with some other
stuff. That's mongo's port, so I assumed I had to start mongod. I did,
then grunt fires the server up.

Does that sound right, or should grunt fire up the mongo server as well?

—
Reply to this email directly or view it on GitHubhttps://github.com//issues/17#issuecomment-31106247
.

Lior Kesos - http://www.linnovate.net
Linnovate - Community Infrastructure Care
mail: [email protected]
office: [phone]
cell: [phone]
skype: liorkesos

[melersh]

Referring to @mattfrear .. I managed to pass this error, by installing two addons to my Heroku app, mongoHQ and Papertail, create new user via mongoHQ db Admin web portal and reflecting the newly created username/password along with db url provided by mongoHQ in configuration files located /config/env/development.js and /config/env/development.js
from

mongodb://localhost/mean-test

to something like

mongodb://:@paulo.mongohq.com:10010/app21348612

Still I get another error copied captured by PaperTail. Any one got lucky passing by this stage. Support/Links are highly appreciated.

Jan 17 19:54:28 bodyshapers heroku/slug-compiler: Slug compilation finished 
Jan 17 19:54:29 bodyshapers heroku/web.1: State changed from crashed to starting 
Jan 17 19:54:34 bodyshapers heroku/web.1: Starting process with command ./node_modules/.bin/forever -m 5 server.js 
Jan 17 19:54:35 bodyshapers app/web.1: warn: --minUptime not set. Defaulting to: 1000ms 
Jan 17 19:54:35 bodyshapers app/web.1: warn: --spinSleepTime not set. Your script will exit if it does not stay up for at least 1000ms 
Jan 17 19:54:36 bodyshapers app/web.1: Express app started on port 44172 
Jan 17 19:54:36 bodyshapers app/web.1: /app/node_modules/mongoose/node_modules/mongodb/lib/mongodb/connection/base.js:242 
Jan 17 19:54:36 bodyshapers app/web.1: throw message;

Jan 17 19:54:36 bodyshapers app/web.1: ^ 
Jan 17 19:54:36 bodyshapers app/web.1: MongoError: auth fails 
Jan 17 19:54:36 bodyshapers app/web.1: at Object.toError (/app/node_modules/mongoose/node_modules/mongodb/lib/mongodb/utils.js:110:11) 
Jan 17 19:54:36 bodyshapers app/web.1: at /app/node_modules/mongoose/node_modules/mongodb/lib/mongodb/auth/mongodb_cr.js:39:33 
Jan 17 19:54:36 bodyshapers app/web.1: at /app/node_modules/mongoose/node_modules/mongodb/lib/mongodb/db.js:1806:9 
Jan 17 19:54:36 bodyshapers app/web.1: at Server.Base.callHandler (/app/nodemodules/mongoose/node_modules/mongodb/lib/mongodb/connection/base.js:442:41) 
Jan 17 19:54:36 bodyshapers app/web.1: at /app/node_modules/mongoose/node_modules/mongodb/lib/mongodb/connection/server.js:485:18 
Jan 17 19:54:36 bodyshapers app/web.1: at MongoReply.parseBody (/app/node_modules/mongoose/node_modules/mongodb/lib/mongodb/responses/mongo_reply.js:68:5) 
Jan 17 19:54:36 bodyshapers app/web.1: at null. (/app/node_modules/mongoose/node_modules/mongodb/lib/mongodb/connection/server.js:443:20) 
Jan 17 19:54:36 bodyshapers app/web.1: at EventEmitter.emit (events.js:95:17) 
Jan 17 19:54:36 bodyshapers app/web.1: at null. (/app/node_modules/mongoose/node_modules/mongodb/lib/mongodb/connection/connection_pool.js:191:13) 
Jan 17 19:54:36 bodyshapers app/web.1: at EventEmitter.emit (events.js:98:17) 
Jan 17 19:54:36 bodyshapers app/web.1: error: Forever detected script exited with code: 8

[melersh]

I believe i figured out the problem, was the need to add "forever" to list of dependencies in package.json file which solved the problem magically and every thing is working upon deployment on Heroku.

[pratik60]

Good enough documentation for first timers, I believe. A roadmap though would still be nice.

The direction kinda reminds of Drupal -: mean-cli vs drush, different packages vs modules etc. Lets just take the cool parts, and remember not to make it bulky etc

[liorkesos]

We tried to avoid the drupalization but in retrospect it seems Dries and
the gang got some things right...
As long time drupaladores we think 17 times before writing config stuff
into the db.
Lior
On Jul 5, 2014 7:39 PM, "Pratik Bothra" [email protected] wrote:

Good enough documentation for first timers, I believe. A roadmap though
would still be nice.

The direction kinda reminds of Drupal -: mean-cli vs drush, different
packages vs modules etc. Lets just take the cool parts, and remember not to
make it bulky etc

—
Reply to this email directly or view it on GitHub
#17 (comment).

[liorkesos]

@pratik60 I'll try to publish our roadmap, although most energy will be directed to contributing on packages and actually less on the core..