In my previous article, I talked about why I am interested in Tuleap. But in this one, I am going to talk about my impressions of the software, in trying to set it up and get it running. And while not quite an article warranting a Core Dump category tag, I did realize that I needed a new one, as I have done a number of similar posts.

I became a huge fan of the Agile development methodology over a decade ago while working at Lumos Networks as a contract PHP developer. This is also where I learned Test Driven Development (TDD), and have much to thank Brian Johnston for bringing those skills into my toolbox, even after many years. And they say an old dog cannot learn new tricks.

I've talked about Ansible a number of times, including mentioning it in my last post.

If you have looked around this site, or know me and have heard me discuss it, I have an honest to goodness Red Hat Enterprise Linux subscription. I am not talking about the rebuilt version called Rocky Linux, which is the successor to CentOS after Red Hat changed that distro from being just a rebuilt/relabeled version of the corresponding RHEL version to a stream version sitting somewhere behind Fedora and before RHEL. 

So, I was doing some work on Heimdallr, and I notice that I was using Laravel 12, and should upgrade to Laravel 13. Upgrades from one major version of a another for frameworks in PHP projects always seems to be "painful" for some reason. In Zend Framework, they dropped core components, from what I have heard, for Drupal 7 to 8, you practically had to rebuild things from scratch. For L12 to L13, they talk about doing it in an estimated 10 mins, but my experience was far from it. My development VM runs on a hefty server, and is pretty hefty itself.

So, it has been awhile since I posted a major article. I have been working on my Job Application Tracker App, which I originally wrote to replace the Google spreadsheet I had been using to track jobs to which I have applied as a part of my job search, and which a friend said I should turn it into a demo site, make it multi-user and perhaps monetize it. And I did put it up as a demo site, and did a major amount of work to make it fully multi-user. But while working on it, I ran into some issues.

This is a revisit of sorts of Another WTF Chrome and the even older Google Chrome Frustrations, but is yet another facet of an overall flawed design. Once again, I caught Chrome doing something which I did not want it to do.

I wanted to add an emoji to a comment I just made on my last post, and I wanted something more than the old-style :) emoticon which I have used for (mumble) years. A quick Google told me about the ckeditor_emoji module for Dupal, with a comment by Jeff Geerling of all people (A YouTuber I occasionally watch, who has contributed many Ansible modules I regularly use), to make sure that your Drupal database supports the "utf8mb4" encoding.

There is a handy trick I use to keeping track of changes made to the configuration of a system, and one which I sometimes neglect in my rush. It has changed a bit over the years, and I never did figure out how to do it on AIX, where unlike other UN*X versions, the configuration was stored in a database called Object Data Manager, or simply ODM. The trick is track the changes using some form of version control.  At first, this was Revision Control System, or RCS, and from what I recall from those days, to say that it was "far from ideal" was an understatement.