Similar to https://wikitech.wikimedia.org/wiki/Help:Toolforge/My_first_Flask_OAuth_tool
Wanted: A detailed but not technical jargon-heavy guide explaining how to create a NodeJS OAuth tool
Should include:
Screenshots!
Cut-n-paste instructions for everything
Creating a new service group (ugh that name)
Choosing a license
Publishing source code
Adding a Tool:* documentation page
Where to look next for help with more advanced use cases
| Status | Subtype | Assigned | Task | ||
|---|---|---|---|---|---|
| Resolved | Lea_Lacroix_WMDE | T187319 Documentation sprint @Hackathon 2018 | |||
| Declined | None | T101659 Run a documentation sprint for Cloud VPS and Toolforge | |||
| Resolved | srishakatux | T192423 Create a "my first NodeJS OAuth tool" tutorial for Toolforge |
The first draft of the tutorial is here: https://www.mediawiki.org/wiki/User:SSethi_(WMF)/Sandbox/My_first_NodeJS_OAuth_tool. The tool works locally, a few more tweaks to get it to work in the Toolforge environment.
Very nice. One thing: when I last coded a nodejs toolforge web tool I found that express actually receives the toolname in the uri, i.e. if you request tools.wmflabs.org/toolname/ it receives /toolname/, unlike uwsgi which mounts / on /toolname/. Could you confirm whether that is still the case? If so, do you think it would worth to figure out a way to do the 'mount'?
@zhuyifei1999 Sorry for the late reply! Your comment here was helpful and you were right, express receives the tool name in the URI. I am now using the express router middleware that helps mount sub-apps on a mount point. I couldn't find anything cleaner than this :P I've made the related changes to the tutorial.