My WordPress site is now on AWS! I spent a good chunk of my time debugging the All-in-One WP Migration plugin to get my migration working, and I finally realized I skipped an important step in their migration documentation:
It’s funny, I was confident I was going to post more often this year. I promise myself I would back in January, and here we are, half a year later, for my second post of the year. So many things have happened, which I hope to write about in later posts.
I recently took an AWS class under the UCLA extension program. It felt like a long 10 weeks, but I am very glad I went through with it. With some AWS experience now under my belt, I feel like I have enough knowledge to start my migration from Hostmonster to AWS.
Happy new year! I have been lazy with my posts the past months (years?) so as part of my new resolutions I plan to write more.
While I am here, I will leave a tip on how to better yourself as a software developer/enthusiast: practice, learn, practice. Continue to learn, and repetition is key to nailing information in your brain! Also, check out https://www.pluralsight.com or https://www.lynda.com for study material.
While working on ETL (Extract, Transform, Load) projects at work, I ran into an unusual issue using xlsjs:
Error: Unrecognized ExtProp type: 2 0
After digging through the xlsjs source code, I realized that it was following the MS-XLS Specifications, as it should, and section 2.5.108 ExtProp, the extType value that I was running into was not defined in the table. Seeing as the format structure was related to formatting, I forked the xlsjs library and created a version that was more forgiving.
If you are running into this issue and want a workaround, try xlsjs2.
I get frustrated when I browse a file from a git repository only to realize its history was lost due to improper renaming/moving of the file. It seems common for developers to manually rename/move a file in a git repository by using regular file system commands rather than git commands.
For example, let’s look at the following:
$git add test.txt
$git commit-m"add test.txt"
So what have we here? We start off by creating a new directory called test. We then go into the directory and start a new local git repository using git init. Next we create a new file called test.txt that contains simple text “hi”. test.txt is then added and committed to the repository. Finally, we use the mv command to rename the file to test2.txt.
git status shows us the result:
This is not what we were expecting. This shows that the original file test.txt was deleted and now there is an untracked new file called test2.txt, when it really should say that test.txt was renamed to test2.txt.
Btw, this goes for moving files as well. For example, rather than renaming the file, if it was moved to, say, a different folder, e.g. newFolder/test.txt, the result would be the same.
So how can this be solved? It’s actually not far off from the steps above. Let’s start with backtracking by reverting the rename:
Proper way to rename/move
$git checkout test.txt
Running the above commands produces the following result:
Much better, isn’t it? Renaming/moving files from git repositories the proper way will allow retention of their history, which is what we want.