server

I did that! I hope you are not the person who suffered that from me (did you use Picnic CSS a few years back?). So for a newer project I put some setup code that will look for all code snippets with a specific comment and run that with the code after the comment. For generating the website documentation that test bit can be stripped (though I kept it for now). Example: https://github.com/franciscop/server/blob/master/docs/docume...

I am not sure if it's missing or it's part of one of these four, but another very important part for me is the introduction/README. Probably the most important one. Introductions include: - Project health indicators, all green. [tests | passing] and such. - Quick general description of the problem the project solves. - A simple code snippet showing how easy it is to use it. Not the most complex way of using it as many do, please. - Screenshots and gifs if it's UI-related. Very important if it's UI-related. - Quick installation guide if using a common way, or a link to an in-depth guide if it's not easy to install. - Links to other parts, in-depth articles, etc. Some examples where I think I got it right (feedback welcome!): https://github.com/franciscop/server https://github.com/franciscop/ola That said, good documentation takes a lot of

I did it the other way around; I wrote the tests within the code snippet (https://news.ycombinator.com/item?id=17837016). I was going to remove them when rendering, but in the end I thought they might actually be helpful and clarify things, so I left the tests within the snippets. For reference, here is the JS test builder (fairly rough): https://github.com/franciscop/server/blob/master/test/exampl...

> Note: this option can be ignored and server.js will work with both .pug and .hbs (Handlebars) file types. [1] : https://github.com/franciscop/server/blob/master/package.jso... I think around express 3 the guys decided to go with a modular approach and decouple the server from any of those heavy ( render ) libraries, as well as body-parser ( once it was core module in express itself ). My really friendly feedback is that I think express carries so much experience that it will be really hard to replace it with something so monolithic. I use express for REST APIs as well as full web app, where I need no render engine and having this installed on my server is an overkill. Best approach I would think of is having someone rewrite express from scratch and call it express 5, while keeping the same balance of core and extra functionality, as wel

That is interesting, I think the way I do it is quite similar: normally I write the examples that would go in the documentation first then work around it, but I don't write the whole text+proofreading which is what takes most of the time for me. Edit: see this "others" folder for example: https://github.com/franciscop/server/tree/master/others

Good article and callout for those projects (and mine). I am doing an express alternative[1] with something that is not secure as a temporary session secret[2] formed with `secret: 'secret-' + parseInt(1000000 * Math.random())` so I'll modify it to use a real random key from a crypto library or display a prominent warning. Then I am also documenting it in a small production security guide [3]. Also, if the key in the documentation is used there's a warning[4] similar to how Dropbox stops you from using 'correct-horse-battery-stapler' as a password. If you have any other tip/recommendation I'd be really thankful. BTW, doesn't SSL/TLS mitigate this a lot? Like, if the user is using SSL then only with physical access to a decrypted device would an attacker be able to impersonate the user, limiting greatly the possible attacks. And if someone

Well I just did it a few days back [1]. It is working great, I am closer and closer to release server [2] and working on my Japanese which got rustly. [1] https://medium.com/@fpresencia/i-am-not-superman-54b54e8ab49... [2] https://github.com/franciscop/server

I've been publishing around 1 library (some small and some medium for 1 person) every other week. However, most of them are related around building front-ends using ES6[0][1] or building websites with Node.js[2][3]. I am also doing some experimentation with robotics/AI (voice/image recognition) but those are just side projects like [4], not publishing anything. [0] http://superdom.site/ [1] https://github.com/franciscop/uwork [2] https://github.com/franciscop/loadware [3] http://github.com/franciscop/server [4] http://anchor.science/ PS, I think all of those (and some more) were done within the last 2-3 months.