Page MenuHomePhabricator

Create a "my first NodeJS OAuth tool" tutorial for Toolforge
Closed, ResolvedPublic


Similar to

Wanted: A detailed but not technical jargon-heavy guide explaining how to create a NodeJS OAuth tool

Should include:

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

Event Timeline

Restricted Application added a subscriber: Aklapper. · View Herald TranscriptApr 18 2018, 1:43 AM
srishakatux triaged this task as Medium priority.Apr 18 2018, 1:43 AM
Quiddity renamed this task from Create a "my first NodeJS OAuth tool" tutorial for Tool Labs to Create a "my first NodeJS OAuth tool" tutorial for Toolforge.Apr 19 2018, 5:32 PM
Quiddity moved this task from Backlog to Cloud Services on the Documentation board.
srishakatux raised the priority of this task from Medium to High.May 3 2018, 11:48 PM

The first draft of the tutorial is here: 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 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.

srishakatux moved this task from Triage to Backlog on the Toolforge board.Jun 6 2018, 11:44 PM