Hapi workshopper

[geek]

https://npmjs.org/package/makemehapi

Still a work in progress, but feel free to add to nodeschool.io

[max-mapper]

Hi, thanks for contributing.

Some feedback:

• I don't think it's a good idea to put the exact solutions in the hint area in the problem.txt
• Do you have a list of planned exercises? e.g. how do you plan to show uniquely what makes hapi awesome?
• It might be worthwhile to check out what @Raynos and @azat-co are working on, namely https://github.com/azat-co/expressworks/ and https://github.com/Raynos/http-framework and maybe coordinate efforts

[geek]

Thanks @maxogden

1. Fixed
2. Planned exercises are filed as issues in the repo
3. Thanks, will do

[Raynos]

I should build a workshopper this weekend. I think http-framework has enough in it to be able to build one.

There is a secondary question of can myself, @wpreul and @azat-co build a workshopper that has the same excercises and you can run either the express, http or hapi version. (even within http versions I have three different styles raw http, minimal http & modular http)

[geek]

@Raynos great idea.

Looking at expressworks... maybe a consistent list should include the following:

1. Hello World
   • Creating a server with a handler that responds with "Hello World"
2. Hello Route Param
   • Create a server with a route /hello/{param} and respond with "Hello {param}" where param is supplied from path param
3. Templating
   • Create a server with a route at / that responds with an HTML form
4. Form Submission
   • Using the form in 3 add a route that takes POST params for name/password and echos the POSTed name/password
5. Basic Auth
   • Create a route that can only be accessed with basic auth
6. Gzip/JSON
   • Build a route that inflates a gzipped request and then echo it back as JSON with an additional property added to the object

For hapi I am also adding
7. Adding a plugin
8. Creating a plugin
9. Events

[Raynos]

For http I might be interested in doing

• serve hello world
• serve multiple routes
• read and return JSON
• render a template
• handle a form POST
• handle a session
• handle multipart upload
• serve static files
• handle authentication & validation for an APIish route.

[max-mapper]

i'd like to see (for express-works, http-framework and hapi):

• how to hook up binary websockets to an existing server
• how to hook up socket.io to an existing server
• how to hook up oauth (e.g. log in with github) to an existing server

[Raynos]

@maxogden why binary websockets instead of normal ones ?

[max-mapper]

i'd like to see both as they both have their use cases.

all node core APIs return Buffers but for legacy reasons most big socket frameworks only return strings/JSON objects. binary websockets are super useful for high perf i/o in web apps but are often hard to use with big frameworks (in my experience)

[Raynos]

Also see conversation in nodeschool/nodeschool.github.io#14

[Raynos]

@wpreul @azat-co you guys should hang out in #stackvm on freenode, planning to do a workshop this weekend, would love to sync up.

[azat-co]

@Raynos I'm not on freenode, but available through other means (Twitter, email, Skype).

@maxogden
RE: "i'd like to see (for express-works, http-framework and hapi):

how to hook up binary websockets to an existing server
how to hook up socket.io to an existing server
how to hook up oauth (e.g. log in with github) to an existing server"

+1 for socket.io and oauth, any tips on how to implement the checking process in the workshopper? right now, all we do is compare outputed streams, with three-legged oauth (redirects and such), it might be tricky. ;-)

[martinheidegger]

It seems to me this issue is awesome but slightly misplaced. Maybe its better to close it and open issues in the respective repositories?

[azat-co]

I'm okay with closing it or leaving it open, it has good suggestions... but probably not for workshopper itself.