I might classify this article under “rage post”, as it’s 4:30am and tomorrow’s early work prevents me from explaining things properly. Considering you have an nginx app proxying to /your/app.socket ; then the combination of the user and group and chmod value on the app.socket file itself & the directory containing it (in this example, […]Read More nginx proxying to unix sockets: lessons learned
Have you ever tried fetching a resource that would redirect to an HTTPS url whose SSL certificate is not recognised by your browser (or downright invalid)? Yep, of course the fetch will fail (in general). But how to catch it properly? Instinctively, one will probably think of something along this line: which is fair enough. […]Read More good luck catching fetch redirection ssl error
Photo by Mag Pole on Unsplash As a big fan of automation, I rarely decline an opportunity to setup a CI/CD flow for a new project, be it a React-stack website (with or without SSR), or a mobile application (native or cross-platform). A web application, be it based on Node.js, or PHP, or any other language, can be […]Read More bitrise hangs during Xcode Archive & Export for iOS
Alright, this is gonna be a big no brainer, but we’ve all spent 1 full hour looking for our glasses, wearing them the whole time, haven’t we? If you keep getting permission errors whenever you npm install (even if you’ve fully followed the official guide on how not to get npm permission error), then obviously […]Read More npm install keeps showing permission errors?
Okay, so the problem is obvious: we want to use mocha to run spec .js files written in ES6+ ( very likely with async await being utilised ‘cuz everybody loves ’em 😉 ). I’ll go ahead and state it upfront that: there is nothing special or challenging about this. I’m blogging this only for the sheer reason […]Read More Using mocha with ES6+ spec files
Context: if you use a node module having dtrace-provider as one of its dependencies, even primary or optional, once in a while you may notice a peculiar error spit out from your node processes: Error: Cannot find module ‘./build/Debug/DTraceProviderBindings’ This usually happens when I upgrade my Node.js version then go back to maintaining a few week […]Read More npm dtrace-provider occasional issue
So, in the past month, my Mac has been automatically restarting itself times and times again. While there is a possibility that some part inside it broke down, I really don’t even wanna think about that. Instead, I’ll just attribute it to the fact that my SSD is already 93% full, and apparently the hibernate […]Read More constant panic (my mac osx)
Hello there, If you’re a random reader, this post is exactly as its title reads. If you happen to be from Automattic Inc. itself, you know why this post is here! Now without further ado, I’ll tell you a story about how I came to choose and use some of Automattic’s products. A. WordPress itself […]Read More How do I (as a developer) use Automattic products (and their competitors) – Part 1
Howdies, npm@5 & Node.js@8 have been one of the hotter news recently within the NodeJS community. First of all, sincere kudos to the team behind for having going out of their ways in developing and maintaining such cool products that provide us developers with so much comfort to carry on in our daily work 🙂 […]Read More Finding your build scripts break after upgrading to npm@5 / node@8?