Closed
Bug 730706
Opened 13 years ago
Closed 13 years ago
kumascript: Build forking, robust server runner
Categories
(developer.mozilla.org Graveyard :: Editing, defect)
Tracking
(Not tracked)
RESOLVED
FIXED
People
(Reporter: lorchard, Unassigned)
References
Details
The HTTP service for kumascript is a JS module that can be run as a socket listener. That's not enough, though: It needs to be wrapped in a deployable server runner that will keep the service running through exceptions and errors, and can fork processes to take advantage of multiple CPU cores.
This may need some IT consultation to determine what's the best arrangement for deployment.
Reporter | ||
Updated•13 years ago
|
Comment 1•13 years ago
|
||
Preempting some IT questions - the http service is served by node.js? Is it express? Are there existing node.js practices and tools for this?
Reporter | ||
Comment 2•13 years ago
|
||
The HTTP service is node, based on express, and there are many existing node practices and tools. Still working on picking the right one, though "up" [1] looks promising.
There's also "forever" [2], but that doesn't handle forking off child processes. I'd probably need to DIY that with the new "cluster" support in node [3].
[1]: https://github.com/learnboost/up
[2]: https://github.com/nodejitsu/forever
[3]: http://nodejs.org/docs/v0.6.0/api/cluster.html
Reporter | ||
Comment 3•13 years ago
|
||
Using learnboost/up, going to say this is done:
https://github.com/lmorchard/kumascript/commit/d2208a612648bbdc373bd73498c84fd2cfc6b1cc
https://github.com/lmorchard/kumascript/commit/d74c0016a0ed276d9bb8f4d5206956632713c129
https://github.com/lmorchard/kumascript/commit/b3f6628add9371d4c0a125524892397c815341d8
Status: NEW → RESOLVED
Closed: 13 years ago
Resolution: --- → FIXED
Assignee | ||
Updated•12 years ago
|
Version: MDN → unspecified
Assignee | ||
Updated•12 years ago
|
Component: Docs Platform → Editing
Updated•5 years ago
|
Product: developer.mozilla.org → developer.mozilla.org Graveyard
You need to log in
before you can comment on or make changes to this bug.
Description
•