I like to blog using the blogging tool I created called After Dark. After some time away from GitHub I began self-hosting my source code with {{ external “https://gitea.io/" “Gitea” />}}. Since the Microsoft acquisition there are some cool features in GitHub which have brought me back, at least to play around a little with what’s there.

One feature is the ability to showcase latest blog posts on a GitHub profile. I learned about this trick a couple of days ago while doing Kubernetes research for a project I’m working on during my semi-permanent remote placement in Bali.

In this post we’re going to take a look at the feature and see if it’ll be useful in helping showcase my writing for others when they visit my GitHub profile.

Reaction Commerce is a full-stack, self-hosted commerce platform you can run for as little as $10 on your own VPS. Think of Reaction Commerce as what WooCommerce might’ve become had it not been dependent on PHP/WordPress and instead was rewritten using modern coding languages and development techniques.

Using self-hosted commerce is like having your own personal Shopify, WIX or BigCommerce right at your fingertips. Only there’s no monthly costs to worry about just to use it. And there’s no vendor lock-in which would otherwise make it too difficult or risky to switch between platforms when the need arises.

After you’ve learned the basics of Getting Started you’re ready to dive deeper into the code and learn how things work. One of the best ways to learn any new system is to look for bugs and figure how to debug them. And in this tutorial I will show you some strategies for debugging source code in Reaction Commerce.

After upgrading my Invisible Arch box to use the new Deepin Desktop V20 beta I ran into a hiccup trying to start Ungoogled Chromium:

% chromium
/usr/lib/chromium/chromium: error while loading shared libraries: libre2.so.6:
cannot open shared object file: No such file or directory.

What the shit is libre2.so.6? Initial web searches were fruitless so I fell back to GNU IceCat for a minute while I explored Deepin 20’s buttery new interface. Later I found a debugging trick on bugs.archlinux.org to find the problem:

So I’m putting together this killer new JS front-end development stack called Brunch with Panache, which uses Jake tasks to kick off a custom set of commands for building and managing the app, and I hit a bug while code was running in Node.js. So what now?

Earlier today, while looking for a new solution to an older IE compatibility issue, I chanced across this nifty script for testing IE on macOS using virtual machines and VirtualBox: xdissent.github.com/ievms.

While working through the EGit User Guide I ran into difficulty pushing files upstream using Eclipse Indigo SR1 (build 20110916-0149). The difficulties manifested themselves at first with an auth failed error, which was quickly resolved with a visit to Stack Overflow. But after fixing that problem I began seeing the following error while trying to push to a remote repo:

Cannot get remote repository refs.

Reason:
ssh://git@github.com:22: Passphrase for C:\Users\...\.ssh\id_rsa

Web applications concatenate CSS files to improve performance, which can result in large numbers of style rules in a single file. Enter the 4095 selector limitation for IE browsers. An IE bug whereby the browser will only apply style for the first 4095 selectors declared per file. Impacted browsers include IE6, IE7, IE8 and IE9.

iTunes users opting not to allow the program to automatically keep their folders organized (the default setting) may be well aware that iTunes does not respond well after changing locations of or renaming files. In fact, any change in the file name or path renders the item inaccessible from within iTunes, almost as if your iTunes library disappeared. To make matters worse, there’s no easy way to have iTunes relocate files moved. iTunes prompts the user to relocate missing files but only one at a time with a dialog that says:

The [type] [name] could not be used because the original file could not be found. Would you like to locate it?

Not so useful when a lot of files are moved at once. But if a directory containing hundreds of files needs to be moved, to a larger hard drive for example, locating files individually becomes too much work.