|
|
|
|
|
by the_concussed
4652 days ago
|
|
Great feedback, and agreed on both fronts! I added Redis to the mix because it has support for a really nice rate limiter pattern that's simple to implement, but its probably overkill for what people want when they deploy locally for experimentation or to contribute to ConcussionJS. I should probably have a production fork of concussionjs-proxy for the short term with the rate limiter, and a master fork built exclusively on mongo. RE the built in dependencies to the $HOME directory, I agree that it's a weakness of the install scripts. I'll add this as an issue at https://github.com/concussionjs/concussionjs-core/issues. BTW, there is a command-line tool that I've yet to document that you might find handy. It supports: $ cjs app --create YOUR_APP_NAME
$ cjs app --start YOUR_APP_NAME
$ cjs app --stop YOUR_APP_NAME
$ cjs app --restart YOUR_APP_NAME You can see the documentation by typing: $ cjs --create also supports a --template argument (e.g., cjs app --create YOUR_APP_NAME --template YOUR_TEMPLATE_NAME) which copies the contents of the specified folder with the matching name in concussionjs-core/app_template. Behind the scenes the command line uses a cool util called mon (https://github.com/visionmedia/mon), a super lightweight version of Monit, to keep the nodejs process running for the app specified (e.g., monitoring the process and restarting as necessary). |
|