New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
A little more documentation for the first timers #17
Comments
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? |
Completely agreed, no room for complaining. I just felt it would be great to have. |
@greggh Thanks for the headsup and emphasis - I might be able to look at this in the next weeks. |
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. |
+1 |
1 similar comment
👍 |
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! |
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 Does that sound right, or should grunt fire up the mongo server as well? Also, on forms, is there a way to get the |
yeah thats the idea. On Mon, Dec 23, 2013 at 8:40 AM, Brett Dudo notifications@github.comwrote:
Lior Kesos - http://www.linnovate.net |
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
to something like
Still I get another error copied captured by PaperTail. Any one got lucky passing by this stage. Support/Links are highly appreciated.
|
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. |
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 |
We tried to avoid the drupalization but in retrospect it seems Dries and
|
@pratik60 I'll try to publish our roadmap, although most energy will be directed to contributing on packages and actually less on the core.. |
It would be nice to have a quick start list on the github page for the project. Something that shows the simple things you need to edit to get functionality working. Example:
Right now there is no document that tells people what variables/settings they might need to go change throughout the entire app.
The text was updated successfully, but these errors were encountered: