How to manage multiple projects with their own NodeJS version? 

Simple, use nvm.

But how do I automatically change NodeJS version?

Simple use a .nvmrc inside each project and a .env loaded by autoenv when cding inside the project to automatically change NodeJS version between project just by using cd.

It's not DRY, I want to stay DRY and don't duplicate NodeJS version inside both package.json and .nvmrc, what do I do?

Well, remove your .nvmrc and replace .env content by:

And now you're DRY :)

I gave a talk at Polytech Nantes on how we use automated constraints at iAdvize and Redsmin to speed up our team maturity and efficiency as well as raising up the overall quality automatically. The slides are included below:

Context

Today I received an email on Redsmin Support from @christiankakesa telling me that one of the SSL certificate we use for payments.redsmin.com was expired.

Problem

Indeed the payments website — that we use to recover failed Stripe payments thanks to Bestunning — was unusable with a NET::ERR_CERT_DATE_INVALID exception (on Google Chrome). We had not be notified automatically, I had not been notified automatically, it goes against everything I stand for and we had to fix this.

Solution

We already use Jenkins for a lot of things at Redsmin/Bringr (and now iAdvize) and it knows how to run jobs daily to check multiple things. Why not using it to verify SSL certificates validity as well?

So create a new jenkins job, configure it to be built daily (or even hourly) and run the shell script above:

Don't forget to configure email notifications in case of unstable build and you're done! Next time something's wrong with your website or app SSL certificate you will be notified.