nodejs
At the office, a manager recently picked random people from every team and tasked them with deciding on a common code formatting style that would then be enforced on the entire codebase. The tool that will be used for performing the actual formatting is astyle. His plan was for the group to talk to everyone in their respective teams and settle upon a style that would be acceptable to most of our colleagues.
Having moved my website from Wordpress to Poet recently, you’d think that a sane person would settle down and patiently blog for a while. And you’d be right, that’s exactly what a sane person would do.
In totally unrelated news, this website is now hosted on GitHub pages with the help of Jekyll-Bootstrap. Why, you ask? Well, as I wrote about previously, I’ve had some issues with Poet, and the creator sometimes takes a while to reply to raised issues or pull requests.
Welp, as seems to be the norm with me, my blog appears to have once again fallen into a state of disrepair. Quick, time to make another long post covering everything that’s happened over the past few months! This time around I think I’ll eschew lists in favor of just letting my mind wander.
At the office, I started working on a hush-hush project. The only thing I can say is that it involves integrating a third-party user-agent into our software, thereby allowing customers the freedom to interact with our network elements and configure network services in a variety of ways (including a few popular ones that we haven’t supported so far).
I’d noticed that my blog would randomly become inaccessible as the node.js server I have running would (presumably) throw an error and crash. My current setup involves one instance of Apache to run Wordpress on and a bunch of other instances of node.js that run on different ports, and one central node.js router instance that listens on port 80 and then routes connections to different ports depending on the subdomain in the HTTP request.