A good day with the boys on the course today. The big yin and I didn’t play too great, but the wee guy played brilliantly.

Family guy and web developer
A good day with the boys on the course today. The big yin and I didn’t play too great, but the wee guy played brilliantly.

Over the weekend, I spent time getting my GitLab account, working with a single repository, and migrating the CI script from GitHub to GitLab.
The biggest issue was the CI script, and why shouldn’t it be? There’s rarely a “one script fits all” regarding CI scripts. When I started this project, I had issues getting the CI script working in GitHub. After a few pushes on the one branch, I eventually got there. Migrating this script to GitLab’s CI ways was more straightforward than I thought, but I still had a few issues I managed to resolve.
In addition to all the usual source code management goodies that GitLab offers, a few stood out.
Private repositories are available on GitLab’s free tier. Having used GitLab in the past, I already knew this, but it’s refreshing to see that GitLab is sticking with offering this feature on a free tier.
Feature flags are available on GitLab’s free tier. They are a means of configuring how your code behaves by using toggles and checks to ensure that it only carries out certain functionality. I have a number of feature flags in my application, but they are all based on a YML file in the source code. I will be migrating these to GitLab, though, so that I can toggle them without having to deploy any changes to the YML file that controls them.
Error tracking is available on GitLab’s free tier. Previously, I used Sentry for this, but GitLab also uses Sentry under the hood for their own error tracking feature. Yes, I can probably get more information by having a dedicated Sentry account, but at the moment, I am just checking to see if users raise any errors in the application.
For developers building on the side, these features on GitLab’s free tier are of great value and definitely swing my vote from GitHub to GitLab. Over the next few weeks, I hope to migrate the feature flags over, use more of GitLab’s platform, and see what it can help me with.
I’ve been juggling several app changes over the past few weeks.
Gone are the GitHub and Copilot accounts and subscriptions I used to build a product. I’ve replaced them with a GitLab account on the free tier. The GitLab free tier offers quite a lot compared to GitHub, but there are downsides, like no security alerts. However, I can manage for the moment. I’m still not sold on the GitLab Duo subscription, but I’ve covered that with the following subscription change.
I upgraded my ChatGPT account to the Plus plan over the last month, and I think I will keep it for the immediate future. It’s not quite as integrated as Copilot when it comes to assisting with coding, but it works well for diagnosing issues in my code when needed. I also use it more when searching the web for something specific. I still use DuckDuckGo for general searches that I can filter by the most relevant results, but I use ChatGPT for more targeted searches.
Finally, after a few months with Ulysses, I’m just not using it how I thought I would, so I downloaded Bear again and started moving some of my notes over to that to start using it again. Bear feels less formal than Ulysses, which is why I don’t think Ulysses is sticking for me.
We’ll see how the change goes over the next few weeks.
For the first time this year, I’m working from outside in the back garden. Over the summer, I’ll work a lot more between here and the golf club. Once all the usual chores have been done, I’ll share a picture of the back garden office.
Finally, can get a few holes in after work now the light nights are here.

After a much-needed lazy Saturday morning, I spent the afternoon doing a dry run of the base for my greenhouse. The bricks are lined up and level, but they need a final layer of concrete to keep them in place. I’m happy with the first run at it, though.
With all the recent activity and updates to browsers and search engines such as Brave and Kagi, I’m still happy and content with DuckDuckGo and Firefox. They continue to work well for me and do what I need them to do.
Enjoying the lighter nights again.

I’ve been flying under the radar for the last couple of weeks due to circumstances beyond my control. Now that everything is settling back to normal, I can follow my usual plan and get a few things back on track.
I spent the better part of a day preparing a section of the garden for the new greenhouse. Now, I’m reaping the benefits of a hard day’s work by chilling on the couch with a rum, watching golf, and doing some Rails coding on my MacBook.