Kuma, on the Django side, needs modifications to use the node.js kumascript service on document viewing and previewing.
This is what I *think* needs doing in wiki.views.document():
* The code that handles redirects and translation stays the same.
* Leave the code path handling the ?raw option alone.
* If no ?raw parameter: Perform an HTTP GET to the kumascript service to get document HTML, rather than access doc.html directly
The kumascript service should, in turn, request the doc source with ?raw and respond with macros evaluated. On the Django side, that content should still be processed for sections and editing links, etc
Going ahead and adding this to 2.4.5 with 3 pts. I'm already underway with this and some ancillary tasks it brought up:
Commits pushed to mdn at https://github.com/mozilla/kuma
bug 730704: Changes to kuma to use kumascript service
* Document view performs a request to the kumascript service to evaluate
macros before rendering response
* Tweak to CKEditor setup, skips setting it up on Template:* pages in
advance of more work for bug 731651
* Tests for kumascript usage in document view
* Constance config setting to enforce kumascript request timeout (or to
disable entirely, which is the default)
* Tweaks to document view and model to support HTTP ETag and
Last-Modified headers, in advance of caching support for
bug 730714 and bug 730715
* Add kumascript service as a submodule
* Add node.js and kumascript config to vagrant/puppet
* Added tmux to vagrant install, because it's very handy
* Updates to .gitignore
* Bugfix to 404 on js/libs/jqueryui-min.js
bug 730704: advise using forked runserver in MOTD, kumascript update
Merge pull request #126 from lmorchard/bug-730704-kumascript-integration
Bug 730704 kumascript integration
Depends on bug 730705 for QA. Let's leave this resolved and get it onto stage9 during 2.5 for QA.