@faizmokh - Posts

Ramadan Menubar: A Simple Ramadan Countdown App

2025-02-24T13:52:10.377+00:00

With Ramadan approaching, I built a simple macOS menubar app for counting down to Ramadan.

It shows how many days remain until Ramadan begins. Once Ramadan starts, it displays the current Hijri month and after Ramadan ends, it begins counting down to next year's Ramadan. That's it.

You can get it from Github Releases page</a>. If you experience any issues, please create an issue on GitHub.

Migrating My Obsidian Vault From iCloud to Git

2024-06-22T09:07:44.980+00:00

I have been using Obsidian for note-taking for quite some time now, having switched from Logseq. Both are quite similar in functionality to me, but I much prefer Obsidian’s “File over app</a>” approach. In case the product get discontinued, I still get to keep my notes because, in the end, they are .md</code> files.

I use iCloud to back up my Obsidian notes and i has worked very well so far. Never encounter any out-of-sync issue but now since I can’t use iCloud on my work machine, I need a new alternative. I considered paying for Obsidian Sync, but I already have too many subscriptions. So, a Git-based setup it is.

The migrations process are seamless. Here are the steps I took to migrate my Obsidian Vault to Git:


Copy Obsidian folder</strong>

Copy my Obsidian folder to ~/Developer/obsidian</code> , out of iCloud folder.</li>
Initialize local & remote git repository</strong>

Initialized git repository in my local vault. Then, I created a remote repository on Github and added it as origin.

{{< highlight bash >}}

cd /Developer/obsidian

git init</del>

git remote add origin git@github.com:username/repo.git`
{{</highlight>}}</p>
</blockquote>
</li>
Configure .gitignore</code></strong>

Added .gitignore</code> to exclude unnecessary files. While some suggest to ignore the .obsidian</code> folder, I included it so that my configurations and plugins are synchronized across devices. I also ignore work/</code> folder to exclude any sensitive info.</li>
Commit and push</strong>></span> git commit -am </span>"</span>Initial commit</span>"</span>  </span></span>
></span> git push -u origin main</span>`</span></span></code></pre></li>
Install git plugin in Obsidian</strong>

</li>
Configure the plugin</strong>

I  set the Vault Backup interval to 60 minutes (might change in the future), set the sync method as Merge and to automatically pull updates on startup.</li>
Clone the repo on work machine</strong>

Once done, I cloned the repo on my work machine, copied over any existing notes I had on my work machine and deleted the old vault.</li>
</ol>
This setup has been working well for me for a few weeks. Hopefully, I will never encounter any issues.</p>

Some Notes While Setting Up My New MacBook

2024-06-10T12:30:03.606+00:00

I finally did it—I bought a MacBook! I've worked as a software engineer for almost nine years but never had my own personal machine. I have a very old MacBook Air, but that was different. It was kind of a gift. Still have it stored somewhere, but it's pretty much useless. I can't upgrade the macOS anymore and the battery requires servicing.
I always wanted to buy one, but I kept putting the idea aside because every company I worked for always provided one and based on my observations, most of my friends or colleagues who have both a personal and a company-provided MacBook rarely use theirs. I figured the same thing would happen if I bought one.
Anyway, my current company’s device policy is very strict (banking industry), which makes me feel anxious about using it for personal stuff, so I figured it’s probably a good time for me to get one. So here I am.
I jot down some of my thoughts while setting up my MacBook:

I find it crazy how my dotfiles configuration</a> still works fine after all these years, but some installation steps are out of order. For example, to install SwiftLint, I need to have Xcode installed. I probably should fix this and turn it into a single bash script. Someday soon.</li>
I can’t praise asdf</a> enough. I installed Python, Ruby, and Node with it. Convenient.</li>
14-inch MacBook Pro is nice to hold and carry. I always got issued a 16-inch MacBook Pro at work, so while the large screen density is impressive, I really don’t like how heavy it is.</li>
Space Black</a> is beautiful. However, I don’t really like! how the power adapter is white while everything else is mostly black. I'm not the only one who complained about it, by the way</a>.</li>
I still can’t decide which code editor theme to use. I’ve been using Dracula theme</a> for years, but I feel like trying out other themes, especially high-contrast themes. Currently, I’m trying out the Catpuccin Mocha theme</a>.</li>
There are applications specified in my Brewfile that I’m not using anymore</a>. I took the liberty to clean it up</a>.</li>
I am planning to buy a Proxyman</a> license next. I use it at work and really like how convenient it is. It definitely helps boost my development speed.</li> </ul>
So far, it’s been a pleasant experience. I guess I still got the hedonistic pleasure from buying expensive things. I just hope that Apple won’t release the MacBook M4 Pro tonight.

Installing Python 3.12.0 with asdf

2024-05-27T04:04:32.676+00:00

I tried installing Python on my work machine last week using asdf</a>.
The steps to install it are easy. All I had to do was add the Python plugin and run asdf install</code>
> asdf plugin-add python # add python plugin > asdf install python 3.12.0</code></pre> It was not exactly a smooth process. I got the following error:
python-build 3.12.0 /Users/xxx/.asdf/installs/python/3.12.0 python-build: use openssl@3 from homebrew python-build: use readline from homebrew Downloading Python-3.12.0.tar.xz... -> https://www.python.org/ftp/python/3.12.0/Python-3.12.0.tar.xz Installing Python-3.12.0... python-build: use readline from homebrew python-build: use zlib from xcode sdk Traceback (most recent call last): File "<string>", line 1, in <module> File "/Users/xxx/.asdf/installs/python/3.12.0/lib/python3.12/lzma.py", line 27, in <module> from _lzma import * ModuleNotFoundError: No module named '_lzma' WARNING: The Python lzma extension was not compiled. Missing the lzma lib? Installed Python-3.12.0 to /Users/xxx/.asdf/installs/python/3.12.0 asdf: Warn: You have configured asdf to preserve downloaded files (with always_keep_download=yes or --keep-download). But asdf: Warn: the current plugin (python) does not support that. Downloaded files will not be preserved.</code></pre>
After some googling, I found out that I needed to have xz</code> installed. Yes, that xz</code></a>. I was a bit worried but it seems like running brew install xz</code> will install the older version</a>, 5.4.6</code> which is free from the backdoor</a>.
Once I had xz</code> installed I just had to run the following commands to install Python on my work machine:
> asdf install python 3.12.0 > asdf global python 3.12.0 # will set 3.12.0 as the global default</code></pre>
How to Stash Only Staged Changes in Git 2024-05-21T07:28:55.179+00:00 Normally, when I need to stash my code changes, I run git stash</code>. This command stashes all my changes in the Git staging area. Then, I manage my stashes (pop, apply, drop) using Sublime Merge. I am pretty comfortable with this workflow. However, while working on a task recently, I needed to quickly switch branches to check an issue for a colleague. Normally, I would run git stash</code> before changing branches, but this time I didn't want to stash all the changes in the staging area. Instead, I wanted to stash only the staged files and leave the unstaged files as they were. Luckily, there's a command for this: git stash -- $(git diff --staged --name-only)</code></pre> Let's break it down: git diff --staged --name-only</code> outputs a list of files with changes in the staging area</li> git stash -- $()</code> stashes only the files listed by the previous command.</li> This ensures that only the staged changes are stashed, while any unstaged changes remain in the staging area.</li> </ul> Pretty neat, right? I hope this tip helps! My Essentials Tools 2024-03-26T02:23:32.303+00:00 I am going to hand over my work device this Friday since it will be my last day here in Boost. I thought it would be interesting to document the collection of tools I have used over the years. Many of these have been already documented in my dotfiles repo</a> but still, I just want to share it here for fun. Selected CLI tools</h2> I think I have countless CLI apps installed for development and most of it are pretty common to have, like git</code>, mysql</code> or too low-level (coreutils</code>, cmake</code>) so I will exclude those. Here is the list of tools that I like and somewhat uncommon, most of which are installed using brew</code>. ack</a>: the better grep</code></li> antigen</a>: plugin manager for zsh</code>. It’s similar to oh-my-zsh</code>, but it has faster startup times.</li> asdf</a>: to manage multiple versions of ruby</code>, node</code>, python</code>, etc. I don’t have to install and remember how to use nvm</code> or rbenv</code> anymore.</li> carthage</a>: dependency manager for iOS, similar to Cocoapods. Installed it since my current company uses it, but I don’t really prefer it.</li> diff-so-fancy</a>: to prettify git diff</code> output in terminal.</li> chisel</a>: Collection of LLDB commands to help debug iOS apps. Created by the Facebook team.</li> gh</a>: CLI to interact with GitHub API. I use it to quickly create or delete remote repo from terminal.</li> goreleaser</a>: to package go app as binaries.</li> mkcert</a>: to create local self-signed certificates. I usually use it when I need to create certs during app development.</li> quicktype</a>: to convert JSON to model quickly. Rarely used it since I mostly use their app</a> instead.</li> tree</a>: to quickly inspect the directory structure from CLI</li> swiftlint</a>: linter for Swift to enforce coding style guidelines.</li> vim</a>: :q!</code></li> xcbeautify</a> to prettify the xcodebuild</code> logs. Installed when I was working on setting up iOS CI/CD pipelines.</li> xcodes</a>: to install Xcode from CLI. Friends don’t let friends installed Xcode through AppStore. It helps me too easily switch between multiple Xcodes versions too.</li> youtube-dl</a>: to download videos</li> z</a>: to easily jump around between directories.</li> </ul> Noteworthy Apps</h2> Beyond CLI tools, here are some applications that have been integral to my development workflow: Xcode</a> : the main tool I use for my day-to-day development. I have multiple Xcode installed in fact. Xcode-15.0.0, Xcode-14.3.1 and Xcode-14.1.0. All installed using xcodes</code></a> .</li> Copilot for Xcode</a>: 3rd-party app that I use to have GitHub Copilot on Xcode. It’s not as good as Copilot on VSCode, but it works.</li> Android Studio</a>: official IDE for Android. I use it sometimes when I feel like learning Android or Flutter development.</li> VSCode</a>: code editor I use for anything besides Swift.</li> Ulysses</a>: app focus on writing. Bought a 1-year subscription when I first published a post on my SubStack account, SwiftByte</a>. 🙈</li> Raycast</a>: Spotlight on steroids. I used to use Alfred 3</a>, but I don’t really feel like paying for the upgrades, so I tried RayCast. Fell in love with it right away.</li> Figma</a>: the native app for Figma. I used it whenever I want to hyper-focus on building UIs.</li> DBeaver</a>: database browser. Can support multiple types of DB like mysql, postgresql, sqlite etc through plugins. Installed using Cask</li> DB Browser for sqlite</a>: similar to DBeaver. I use it whenever I need to inspect local database in mobile apps since it has a much simpler interface. Installed using Cask.</li> Logseq</a>: a note-taking app or personal knowledge base? I don’t know, but I used it for quick note-taking and also document my learnings. Though I have since migrated to Obsidian. Installed using Cask.</li> Obsidian</a>: somewhat similar to Logseq.</li> NetNewsWire</a>: RSS reader.</li> Arc</a>: the better Chrome browser. Although I feel like migrating to Safari soon since it already supports multiple profiles.</li> Deckset</a>: to make pretty presentations using Markdown. Usually, I use this whenever I have a knowledge sharing session.</li> Hammerspoon</a>: macOS automation tools through Lua scripting. I use it to script tiling-window manager and some other stuffs. Installed using Cask.</li> The Unarchiver</a>: for unarchiving any non .zip</code> files. Installed using Cask.</li> ImageOptim</a>: to compress images before uploading it to web. Installed using Cask.</li> Postman</a>: for debugging and testing HTTP requests</li> Apple Developer</a>: honestly, I hate the fact that most of Apple docs are hidden behind WWDC videos.</li> SF Symbols</a>: for inspecting Apple SF Symbols icons.</li> Discord</a>: for chats. I joined programming related groups here.</li> iTerm2</a>: terminal emulator. Just better features compared to stock terminal. Installed using Cask</li> Docker</a>: Don’t really use it that much, but it’s nice to have whenever I want to fire up an instance since most OSS these days provide docker images. Installed using Cask.</li> Dash</a>: API documentation browser. I still have the old version. Planning to upgrade soon.</li> Sublime Merge</a>: git client. I use it together with git</code> CLI. Mostly for resolving conflicts and visualising git tree.</li> Telegram</a>: for chats. Joined a couple of programming related groups here as well. Installed using Cask</li> tomato</a>: my own app. A simple pomodoro app that lives in my menu bar. Installed using Cask.</li> </ul> Others</h2> font-iosevka</a>: my favourite monospace fonts. Installed using brew</code>.</li> </ul> These tools have speed up my workflow over the years and made my life easier. I hope you find some of these useful. How to Delete Github Repository Quickly 2023-10-31T08:51:54.646+00:00 I did some spring-cleaning on my Github repositories a few days ago. I was doing it manually at first, by going through the repository settings page, clicked on the delete button in the Danger Zone section, went through several popups and finally entered the repository name to confirm the deletion. Yeah… it’s such a boring chore. Then, I remembered that Github has a cli client</a> that I have been using for creating repo and pull requests. Figured I might take a look again at their docs to see if there’s a command for deleting a repository or setting a repository to private, and there is one! The usage is simple too. Here’s how. Install gh</code></h2> If you don’t have it install yet, simply run the following command: brew install gh</code></pre> Once that’s done, run the following command to authenticate with Github: gh auth login</code></pre>To delete a repository</h2> To delete a repository, run the following command # add --yes to confirm deletion without prompting gh repo delete $REPO --yes</code></pre>To change from public to private repository</h2> To modify repository access, run the following command: gh repo edit $REPO --visibility=private</code></pre> Replace $REPO</code> with the repo name. You can use either the full URL or the repo name. For example. # to delete using url gh repo delete https://github.com/faizmokh/dummyrepo # to modify access using repo name gh repo edit faizmokh/dummyrepo --visibility=private</code></pre> That's all. Go through the docs, if you want to know what else you can do with gh</code> References:</h2> gh cli documentation</a></li> </ol> A Cheaper Way to Renew Apple Developer Account 2023-10-26T04:27:27.051+00:00 My Apple Developer account renewal lapsed early last year because my bank flagged it as foreign transaction. They did call me to verify it but the transaction had been declined by Apple by the time my bank approved it. Long story short, I did not renew my membership. But now I felt like renewing it again to release all my “almost finished” side projects. I headed to the Apple Developer website, but to my surprised, the price is RM399/year now. I’m pretty sure it was cheaper last year. So I checked the Developer app to see if the price is different, and it is! It is still RM369/year on the app. Somewhat weird, but my guess is this has something to do with the App Store having less “dynamic” pricing as compared to the website. From what I noticed over the years, there will be a lot of news whenever they upgrade their App Store Tier pricing</a>. So if you’re looking to subscribe or renew your Apple Developer account, maybe you can try subscribing it through the app. How to Convert SSL Certificate From CER to DER Format 2023-08-17T07:28:00.790+00:00 Today I learned how to convert SSL certificate that is using crt</code> format to der</code> format while working on updating the certificate that was pinned in our iOS app. Here's a quick guide on the how-to. First of all make sure you have openssl</code> installed in your machine. Then run the following command in your terminal: openssl x509 -in input_cert.crt -out output_cert.der -outform der</code></pre> Make sure to replace input_cert.crt</code> and output_cert.der</code> with the actual filenames of your certificates. That's it. Easy right? Additional info</h3> Make sure you pass in the -outform der</code> flag. Otherwise openssl</code> will default to pem</code> format</li> x509</code> subcommand stands for X.509 certificate</a>, which is a standard format for public key certificates.</li> </ol> How to Install Specific Version of Brew Cask 2023-07-28T02:57:10.350+00:00 Brew Cask</a> is an extension of Homebrew</a> that allows us to install GUI tools or 3rd party binaries easily just by using command line. It is so convenient and I have been using it to install most of my app like Chrome, Android Studio or VSCode for years. One of the app I used regularly is Periphery</a>, which is a tool for identifying unused codes in iOS projects. Recently, I ran brew upgrade</code> and unfortunately the update caused Periphery</a> app to stop working. The latest version(2.15.0</a>) requires Swift 5.7 but I'm still using Xcode 14.1. I thought I could just run brew install periphery@2.14.0</code> to downgrade the version but it did not work. Did some googling but the steps aren't straightforward so I will document it down here for my future self. So here's the steps: Google the casks that you want to install the specific version of here</a>. If it's not part of brew</a>, search it on Github. For example here's the page for periphery</a></li> Go through the commits history. Find the version that you want and the cask file</a></li> Copy the URL of the raw file</a></li> Run brew install --cask [RAW_FILE_URL]</code>. For example if I want to install periphery@2.14.0</code> I need to run the following command:brew install --cask https://raw.githubusercontent.com/peripheryapp/homebrew-periphery/6f8d7a080fc41e336ec6f1dca9039117a7886875/Casks/periphery.rb</code></pre></li> </ol> Other Ways to Install</h3> There's another way to install by using brew edit</code>. Here's the steps: Run brew edit [APP_NAME]</code>. Note that running this for the first time will trigger the following warning message since you will be editing the Cask file directly Warning: edit is a developer command, so Homebrew's developer mode has been automatically turned on. To turn developer mode off, run: brew developer off</code></pre></li> Update the version and sha256</code> value based on the version that you want to install. You can find the info on Github. Using the same example: cask 'periphery' do - version '2.15.0' - sha256 '7f0d05c7e9d04925f8c8ed4365146c23abd3b4ac1a5865f125438ce9851f93f7' + version '2.14.0' + sha256 'f44af8004706416610709ed4f913cedc06e458941a6968c095c475bef54e1920' url "https://github.com/peripheryapp/periphery/releases/download/#{version}/periphery-#{version}.zip" name 'Periphery' homepage 'https://github.com/peripheryapp/periphery' binary 'periphery' depends_on macos: '>= :catalina' ``` zap delete: [ '~/Library/Caches/com.github.peripheryapp', '~/Library/Caches/com.peripheryapp.periphery' ] end</code></pre></li> Save it and simply run brew reinstall [APP_NAME]</code>. </li> </ol> That's all. Hope this helps. How to Fix Xcode 14.3 libarclite_iphonesimulator.a Error 2023-07-27T03:30:39.626+00:00 While upgrading Carthage libraries for Xcode 14.3.1</a>, one of the libraries that my team depends on is throwing errors. I checked the repo and found out that the library have been archived</a>. I forked the repo</a> and tried to run it locally. It threw the following error when I ran it: ld: file not found: /Applications/Xcode-14.3.1.app/Contents/Developer/Toolchains/XcodeDefault.xctoolchain/usr/lib/arc/libarclite_iphonesimulator.a clang: error: linker command failed with exit code 1 (use -v to see invocation)</code></pre> Apparently, this is because with Xcode 14.3.1</a> the minimum deployment target have been set to iOS 11. DZNEmptyDataSet</a> is still using iOS 8 as its minimum deployment target. Upgrading it to iOS 11 fixed the error. p/s: Yeah I know the usage of this library is somewhat unecessary but it's already being used everywhere and replacing it with our implementation will require huge effort. Maybe some day. Not today. How To Use Git Worktree To Checkout Multiple Branches At Once 2023-05-09T03:33:21.014+00:00 git worktree</code> allows you to checkout multiple branches at the same time. It's somewhat similar to git checkout -b</code> except that it will create the branch at a new path. For example, running this command in your repository will create a new example-worktree</code> folder outside of your repository and a new git branch</code> named example-worktree</code> $~ git worktree add ../example-worktree</code></pre> If you have an existing branch that you want to use worktree</code> with, you need to run the following command instead $~ git worktree add ../example-worktree $REPLACE_WITH_EXISTING_BRANCH_NAME</code></pre>To get a list of worktree</h2> To see all available working trees that you have created, you can run $~ git worktree list</code></pre> This will print out the following outputs /ROOT/go-projects/main-project-folder 14e218b [main] /ROOT/go-projects/example-worktree 14e218b [example-branch]</code></pre> The first prefix is the worktree's folder path and the suffix is the name of the branch it's on To remove a worktree</h2> I would recommend you to delete a worktree once you've done using it. To delete it use the following command: $~ git worktree remove $WORKTREE_PATH_NAME</code></pre>Caveats</h2> One thing that I noticed when using worktree is that you can't checkout to the same branch that's already in worktree. For example, I can't checkout to example-branch</code> from main</code> branch. Conclusion</h2> git worktree</code> is a pretty useful feature but I would recommend you use it sparingly. It can get confusing if you have too many worktree available. I would recommend you to remove it once you're done with it. Hopefully you find this helpful as a quick references. PHP missing dependencies 2023-02-14T07:47:50.523+00:00 I was having some issues with my PHP package installed through asdf</a> yesterday. Something about missing libiconv and when I ran php -v</code> it returns me this response: No php executable found for php 8.2.0</code></pre> To fix the issue, I followed this tips on Github issues</a> Install the optional dependencies: $~ brew install gmp libsodium imagemagick</code></pre> Reinstall the possible missing dependencies. brew</code> will just skipped any packages that I've already installed. $~ brew install autoconf automake bison freetype gd gettext icu4c krb5 libedit libiconv libjpeg libpng libxml2 libzip pkg-config re2c zlib</code></pre> Reinstall latest php with asdf</a> and set it as the default $~ asdf install php latest $~ asdf global php latest</code></pre> I reshimed it just to make sure $~ asdf reshim php</code></pre> That's all Replacing nvm with asdf to manage NodeJS versions 2021-02-17T04:58:16.292+00:00 I've been using zsh</code> with antigen</a> as the package manager for years. Over time as I add more customizations, I noticed that my shell startup time has become slow. Sometimes, it would take more than 3 seconds to start up. I read few months (or a year) ago that nvm, a version manager for nodejs</code> can cause this issue</a> so I thought maybe it's the right time I should try asdf</a>. asdf</a> is basically just another tool to manage versions but instead of having to install multiple tools like rbenv</a> for ruby or nvm</a> for nodejs</code>, you can just use asdf</a> and use its plugins to manage all the language versions that you're using. Anyway, I'm not going to talk about what's so good about it. For that, you can read the docs yourself. I'm just going to document the steps I did here. Removing nvm completely</h2> First of all, I have to completely remove nvm</a>. Here are the steps: # list out all the nodes version I'm using $~ nvm ls # uninstall nodejs $~ nvm uninstall <NODEJS_VERSION> # uninstall nvm with brew (since I install it using Brew) $~ brew uninstall nvm # delete related dotfiles and directory $~ rm -rf ~/.nvm/ ~/.nvmrc</code></pre>Installing asdf</h2> Then, I installed asdf</a> using Brew # install asdf using Brew $~ brew install asdf</code></pre> Then, I have to add the following in my ~/.zshrc</code> file to load asdf</a> properly. ... # setup asdf . /usr/local/opt/asdf/asdf.sh ...</code></pre> That basically completes the asdf</a> setup. Next I have to install the nodejs</code> plugin. To install the nodejs</code> plugin, I run the following command: $~ asdf plugin-add nodejs # install nodejs plugin $~ bash -c '${ASDF_DATA_DIR:=$HOME/.asdf}/plugins/nodejs/bin/import-release-team-keyring # import nodejs release team OpenPGP keys</code></pre> I got an error when trying to import the keys. Apparently, I don't have gpg2</code> installed yet so I have to install it first. $~ brew install gpg2</code></pre> After installing gpg2</code>, I can finally run the nodejs</code> installation without any error. $~ asdf install nodejs 15.8.0 # install nodejs version 15.8.0 $~ asdf global nodejs 15.8.0 # set it as the global version</code></pre> That's pretty much it. I finally have a working nodejs</code> environment and I notice that my terminal startup time is a little bit faster now. Nice. I just need to replace rbenv</a> and pyenv</a> next. Runners - iOS app to manage Gitlab Runners 2021-01-06T05:41:21.605+00:00 I made a thing! It's an iOS app to remotely manage Gitlab runners. I wrote this app to solve one of the pain points that I frequently face back when I managed the CI/CD machine that hosted the Gitlab runners for my teams. My coworkers would frequently ask me to check why their pipelines or runners were failing and so in a begrudging manner, I would VNC'd</a> into the machine and checked them. so... 🥁🥁🥁 TADAA! This app solved these problems by providing an easy access for me to: Quickly check the runners status</li> Pause, resume, or delete a runner remotely</li> </ul> Oh! Did I mentioned that this is my first SwiftUI and paid app? SwiftUI is really fun to write but there are some weird bugs that Apple needs to fix still. Anyway, it's available now on the App Store</a> for the price of US$1.99 or MYR 7.90. Do check it out from the links below! 👉 Download it from the AppStore</a> 👈 How to list all the git commits history for a specific file 2020-12-16T02:24:09.782+00:00 Assuming the following situation: You work on a large project that has an extensive git commits history and a lot of files</li> You need to debug a certain issue that was caused by a certain file</li> You look at the commits history to see which commit is causing the issue but going through it one by one is like finding a needle in a haystack</li> </ul> Well, worry not because you can use the following git log</code> command to solve your issue: $~ git log --follow -- path/to/file.txt</code></pre> This will list down all the commits history for that specific file. It will work even if the file was deleted or renamed. However please be aware that it will only work for a single file at a time. How to undo a git rebase 2020-11-05T03:15:13.196+00:00 Given the following situation: You're on feature/*</code> branch and you have your latest changes already pushed to origin</code></li> Now, you want to rebase your feature/*</code> branch with the latest master</code></li> You type in git rebase master</code> from your feature/*</code> branch</li> You fix all conflicts and finish the rebase</li> OH SHIT SOMETHING'S WRONG I NEED TO UNDO IT BUT HOW?</li> </ul> Okay, take a deep breath and just calm down. Use the following to reset it to your latest origin. $~ git reset --hard ORIG_HEAD</code></pre> That's it. This will only work if you haven't push your changes to origin</code> yet. If you have, then you need to use git reflog</code> How to setup Jenkins with Docker 2020-09-26T08:57:56.525+00:00 Here is an easy way to setup Jenkins</a> with Docker</a> Run the following commands in your terminal</li> </ol> docker pull jenkins/jenkins:lts docker run --detach --publish 8080:8080 --volume jenkins_home:/var/jenkins_home --name jenkins jenkins/jenkins:lts docker exec jenkins cat /var/jenkins_home/secrets/initialAdminPassword</code></pre> The above command will generate a password. Copy said password </li> Open localhost:8080</code> and paste in the password </li> Setup your user account and install suggested plugins. </li> </ol> That's it! What is the difference between Docker container and Docker image? 2020-08-25T07:54:01.914+00:00 Today I learned the difference between image and container in Docker</a>. An image is a template that can be used to create a container while container is the instances of said Docker images. The container is the one that runs your application. To explain it in cake term, image is the recipe of the cake and container is the cake itself. You can create multiple cakes based on the same recipe. To see all the images available, you can run the following: $~ docker images</code></pre> and to see the container that's currently running, you can run: $~ docker ps</code></pre> or if you want to see the list of available containers, run: $~ docker ps -a</code></pre> That's it. 🎂 References: https://stackoverflow.com/questions/23735149/what-is-the-difference-between-a-docker-image-and-a-container</li> </ol> How to Clone a Git Repository With Submodules 2020-08-16T16:13:21.548+00:00 Today I learned how to git clone a repository that has git submodules</a> inside of it. I realized that when I cloned a project it will clone the parent repo but the submodules will be empty. Here are the steps on how to clone it properly. If you haven't cloned the repository yet, you can use --recurse-submodules</code> option: $ git clone --recurse-submodules https://github.com/sample/sample-repo.git</code></pre> Otherwise, If you already cloned the project then you can use the following command. Run the command inside your git repository. $ git submodule update --init --recursive</code></pre> This will initialize, fetch and checkout any nested submodules for the repository. That's it. How to fix Xcode: "Could Not Locate Device Support Files" error 2020-05-27T04:43:29.783+00:00 There may be a time when you try to run your app in your device and you get the following error: Could not locate device support files. This iPhone (Model ...) is running iOS 13.4 (11E608c), which may not be supported by this version of Xcode. </blockquote> This issue usually happened when you are still developing your app using old version of Xcode but your device have already been upgraded to latest iOS version that is not supported by Xcode. There are multiple ways to solve this issue: Upgrade your Xcode to the latest version - While this is the most obvious way to fix the issue, it could be your most hardest too. Depending on the situation, you might have to update all your projects issues before upgrading (Unsupported swift version, Unsupported SDK version, etc). That's a lot of work</li> Keep two versions of Xcode installed - This have been my preferred option whenever there's a new iOS beta version dropped and I couldn't wait to upgrade my device (living on the edge baby!). You have to symlink the DeviceSupport/</code> folder from the beta or latest version to the stable version that you've been using.1</a> However this option might not be feasible if you have a limited disk space on your machine.</li> Copying the latest device support files to DeviceSupport</code> folder - I just discovered this today and still in awe on how simple it is. I will list the steps down below.</li> </ol> To fix "Could Not Locate Device Support Files" Error Issue with new device support file</h2> Go to the following Github repo: iGhibli/iOS-DeviceSupport</a> </li> Find the zip files that's matching your device's iOS version and download it. </li> Open the following path in Finder: $~ open /Applications/Xcode.app/Contents/Developer/Platforms/iPhoneOS.platform/DeviceSupport/</code></pre></li> Copy and paste the zip files that you have downloaded to DeviceSupport/</code> folder </li> Close and restart your Xcode. </li> </ol> That's it. You should be able to run your app in your device now. Hope you will find this tips useful. Until next time. ✌️ ^1@steipete</a> did an awesome job of maintaining a gist of the command</a> to refer too. </div> References:</h2> github.com/iGhibli/iOS-DeviceSupport</a></li> StackOverflow - Could not locate device support files in Xcode</a></li> </ol> How to Completely Remove Git Submodules Within a Repository 2020-05-18T14:13:29.189+00:00 I found myself having to google this multiple times so I decide to write it here as a quick references for myself. Git submodules</a> is a way for you to keep a git repository as a subdirectory of another git repository. It's useful when you want to incorporate and keep track of external code or framework that your project depends on. It's like a poor man's version of npm</code> or cocoapods</code>. Anyway, to add a git submodules is very easy. It's just simple a one liner. Eg: git submodule add git@github.com:faizmokhtar/example-repo library/example-submodule</code></pre> That's it. But the steps to remove it are very tedious and it's something that I always forgot how to. So here are the steps to completely remove it from your repository. To Completely Remove Git Submodule</h2> Open and edit the .gitmodules</code> with your text editor.</li> Find and delete the relevant submodule lines:[submodule "library/example-submodule"] path = library/example-submodule url = git@github.com:faizmokhtar/example-repo.git</code></pre></li> Open and edit .git/config</code> file.</li> Find and delete the relevant submodule lines:[submodule "library/example-submodule"] url = git@github.com:faizmokhtar/example-repo.git</code></pre></li> Delete the submodules.$~ rm -rf library/example-submodule</code></pre></li> Delete the files in .git/modules</code>$~ rm -rf .git/modules/example-submodule</code></pre></li> Now, there should be some unstaged changes in your git staging area. Stage it and commit all the changes.</li> </ol> That should be it. Maybe you can turn this into a one liner bash script. Until next time. ✌️ How to connect to Google Cloud SQL with Cloud SQL Proxy 2020-05-10T14:26:04.287+00:00 Cloud SQL Proxy</a> is one of the ways to connect to your Cloud SQL</a> instance. It's useful if you want to securely connect to Cloud SQL</a> from your local applications. Here are the steps to setup Cloud SQL Proxy</a> on your local machines: 1. Download and Setup Cloud SQL Proxy (macOS)</h2> First of all you have to download it. I would recommend putting it at root (~/</code>) folder. $~ cd ~/ $~ curl -o cloud_sql_proxy https://dl.google.com/cloudsql/cloud_sql_proxy.darwin.amd64 $~ chmod +x cloud_sql_proxy</code></pre>2. Create a Google Service Account for the Proxy</h2> A service account</a> is a special type of Google account that belongs to your project. Instead of using your individual user's credential, you can use service account to authenticate your application. To set it up, follow these commands. You can replace "my-proxy-user"</code> to your likings $~ gcloud iam service-accounts create proxy-user --display-name "my-proxy-user"</code></pre> Once you have created it, list it down to get the email of the service account. $~ gcloud iam service-accounts list</code></pre> Next, allow your service account to connect to the Cloud SQL proxy on your behalf. You can do this by giving Cloud SQL Client</code> role to the service account. Run the following commands. Replace [PROJECT_ID]</code> and [SERVICE_ACCOUNT_EMAIL]</code> with your own Google Project ID and the service account email that you got from the command before. $~ gcloud projects add-iam-policy-binding [PROJECT_ID] --member \ serviceAccount:[SERVICE_ACCOUNT_EMAIL] --role roles/cloudsql.client</code></pre>3. Create key.json</code></h2> Next, generate a key.json</code> for authentication to the service account. (I would recommend you to ignore this file in git) $~ gcloud iam service-accounts keys create key.json --iam-account [SERVICE_ACCOUNT_EMAIL]</code></pre>4. Start Cloud SQL Proxy</h2> Finally to start the Cloud SQL Proxy, run the following commands. Replace the [INSTANCE_CONNECTION_NAME]</code> with your own and the [PORT]</code> based on the database you want to connect to. $~ ./cloud_sql_proxy -instances=[INSTANCE_CONNECTION_NAME]=tcp:[PORT] -credential_file=key.json</code></pre> If everything is working fine, you will get an output similar like this 2020/05/10 22:23:07 Listening on 127.0.0.1:5432 for [INSTANCE_CONNECTION_NAME] 2020/05/10 22:23:07 Ready for new connections</code></pre> That's pretty much it. You should be connected to your Cloud SQL from your local machine now. Error Troubleshooting</h2> If you happened to get following error: listen tcp 127.0.0.1:5432: bind: address already in use</code></pre> It's likely you already have a local database instance running on your local machine that's using the port 5432</code> (In this case it's Postgresql). If this is the case, stop the running instance first. How to create multiple screen previews in SwiftUI 2020-04-06T12:39:36.964+00:00 Today I learned that you can actually create multiple Xcode screen previews in SwiftUI. Assuming you have a SwiftUI View</code> named ContentView</code>. In the PreviewProvider</code>, create a Group</code> and init multiple ContentView()</code> children inside of it. For example: struct ContentView_Previews: PreviewProvider { static var previews: some View { Group { ContentView() .previewDevice(PreviewDevice(rawValue: "iPhone 11")) .previewDisplayName("iPhone 11") // Optional ContentView() .previewDevice(PreviewDevice(rawValue: "iPhone 8")) .previewDisplayName("iPhone 8 Dark") .environment(\.colorScheme, .dark) .environment(\.sizeCategory, .accessibilityLarge) ContentView() .previewDevice(PreviewDevice(rawValue: "iPhone SE")) .previewDisplayName("iPhone SE") } } }</code></pre> This will display the View</code> that you have created in 3 previews with the following order: Display it in iPhone 11</li> Display it in iPhone 8 with dark mode enabled and large accessibility size font set</li> Display it in iPhone SE</li> </ol> Here's how the above code will look like in action This is going to be super useful when you want to quickly preview your View</code> in different screen sizes, accessibility mode or color schemes. Neat huh? References: Hacking With Swift - SwiftUI tips and tricks</a></li> </ul> How to use SwiftUI in a UIKit project 2020-04-04T10:09:30.345+00:00 Did you know that SwiftUI can be use in UIKit project? To use SwiftUI in UIKit project, you have to make use of UIHostingViewController</code>. It is a UIViewController</code> that basically "host" a SwiftUI view. Assuming you have a SwiftUI View</code> named SwiftUIView</code> like so: let swiftUIView = SwiftUIView()</code></pre>Initializing it programmatically</h2> To initialize it programmatically, set the SwiftUI View</code> as the rootView</code> of the UIHostingController</code>. let vc = UIHostingController(rootView: swiftUIView) self.present(vc, animated: true, completion: nil)</code></pre>Initializing it in Storyboard</h2> Using it in Storyboard requires a little bit more work. First, add a Hosting View Controller and create a segue to it </li> Then, create an IBSegueAction</code> where you can init the UIHostingController</code> like so </li> </ol> @IBSegueAction func openSwiftUIView(_ coder: NSCoder) -> UIViewController? { return UIHostingController(coder: coder, rootView: swiftUIView)) }</code></pre> That's it. References:</h5> Apple documentation on UIHostingController</a></li> </ol> How to use Xcode 11's Swift Package Manager in your project 2019-10-12T13:21:59.275+00:00 Similar like Cocoapods</a> or Carthage</a>, you can use Swift Package Manager</a> to manage the dependencies in your Cocoa project. With the latest Xcode 11, there is now a native support for Swift Package Manager for you to use it directly in your project. Adding a new package</h2> To add a new package with Swift Package Manager is really easy. Go to the following Xcode's menu: File > Swift Packages > Add Package Dependency...</code></pre> and add the package's repository URL. That's it. For example, to add Alamofire</a> library you just have to add https://github.com/Alamofire/Alamofire.git</code> in the search field. You then will have the option to configure the package based on the version, branch or even commit. Once you have chosen the package target, you will noticed the newly added package at the bottom of Xcode's Project Navigator. Now, you can import</code> the package as usual. Removing a package</h2> To remove a package is easy too. Navigate to your project settings and you will noticed that there is a new section called Swift Packages. Navigate to it, click on your library and click on the minus button below to remove it. Caveats</h2> From my limited understanding of how it works, I was expecting Swift Package Manager to create a Package.swift</code> file but instead it creates a references of the package in .xcodeproj</code> file. Based on my experience of how painful it is to solve a merge conflict in .xcodeproj</code> file, this is definitely something that I probably would think twice before using it in a team project. Otherwise, using Swift Package Manager is really easy. Hey, no rubygems</code> dependencies is already a plus! 😉 Understanding LLDB contexts in Xcode 2019-03-26T16:35:41+08:00 Sometimes when debugging on Xcode with LLDB's p</code> or po</code> on a a codebase that have both Objective-C and Swift, Xcode will throw a syntax error at you and you might be wondering out why? You checked for any typos but everything seems to be correct. So what gives? Well, that's because you might be using it in the wrong context. Here's a quick rundown: When you stop in Objective-C code using breakpoint, LLDB will use Objective-C debugging context. So you have to use Objective-C syntax to debug: (lldb) po [ViewController description]</code></pre></li> Similarly when you add a breakpoint in Swift code, LLDB will use Swift debugging context instead. So you have to use Swift syntax to debug: (lldb) po ViewController.description()</code></pre></li> And finally, Xcode will always use Objective-C as the default context. Meaning if you pause the program execution without using breakpoint, you'll have to use Objective-C syntax. </li> </ol> That's it. Hopefully this tips will helps you a little bit when debugging a project that have a mixture of both Swift and Objective-C codes. ✌️ How to use Go Dep to Manage Dependencies 2019-02-11T22:09:13+08:00 dep</code></a> is a dependency management tool for golang. If you have work on other programming languages, dep</code></a> is similar to npm</code></a>, pod</code></a> or pip</code></a>. In simple words, it is a package manager to manage your project's third party libraries. How to install it</h1> There's a few ways to install dep</code></a>. Personally, I prefer to install it with Homebrew</code></a> To install it run: $~ brew install dep</code></pre>Initializing a project with dep</code></a></h1> To initialize it in your go</code> project, go to your project directory and run the following $~ dep init</code></pre> This will create three things in your directory Gopkg.toml</code>: This where you specifies the project dependencies</li> Gopkg.lock</code>: File generated as a result from running dep</code>. It's a complete dependency graph for your project. You shouldn't edit this manually.</li> vendor/</code>: This is where the dependencies are stored</li> </ol> dep init</code> will behave differently depending on the state of your project. If it is a new project, Gopkg.toml</code> and vendor/</code> will be essentially empty aside from the usual commented out guides on how to use it. If it is an existing project, Gopkg.toml</code> adn vendor/</code> will add all the dependencies that you have added in your project with go get</code>. How to use dep</code></a>?</h1> Adding a new depencies</h3> To add a new depencies in your project, run the following $~ dep ensure -add <DEPENDENCIES></code></pre> Replace <DEPENDENCIES></code> with the path to its project repo. For example $~ dep ensure -add github.com/gorilla/mux</code></pre>Others</h3> A few more commands that I find useful: dep status</code>: Will report the status of your project dependencies</li> dep prune</code>: Will tell you which libraries that are out of sync</li> </ol> Conclusion</h1> I am sure by now you are asking "why should I use go dep</code> when go already comes with go get</code>?". Well, imagine you are working in a team project that uses a lot of dependencies. Each having their own version of libraries. Pretty soon you will have those "Works on my machine!" real quick. dep</code> solve this by making sure everyone who works on the project is guaranteed to be using the same version of dependencies. That's it. Hopefully now you have learned the basic usage sof go dep</code> to manage your project dependencies. How to Change Git Branch Name 2018-09-13T17:26:34+08:00 Here's a quick reference on how you can change your git branch name: If you want to rename of your current local branch: git branch -m new-branch-name</code></pre> If you want to change the name of a different local branch git branch -m old-branch new-branch-name</code></pre> That's it. Bye. How to set default git push behaviour 2018-08-22T18:44:01+08:00 Oftentimes, I forget that I have to specify the current branch name when pushing it to a remote. For example: $~ git push</code></pre> or like this $~ git push -u origin</code></pre> Either way, these commands will fail since I didn't specify the upstream branch. git</code> will return an error similar like this: fatal: The current branch develop has no upstream branch. To push the current branch and set the remote as upstream, use git push --set-upstream origin <INSERT BRANCH NAME HERE></code></pre> To avoid this error, I have to set the upstream branch name explicitly first before pushing it to the remote repository. For example: $~ git push -u origin <INSERT BRANCH NAME HERE></code></pre> However, this approach can get pretty tedious since the name of my branches are usually long and usually prefixes with feature/</code>, chore/</code> or fix/</code>. I can't exactly depend on tab-completion either since I have to tab multiple times before pushing in the branch that I wanted to. Good thing that there is a way for me to implicitly push the current branch by configuring the default git behaviour. Regardless if the branch already exists in upstream or not. Neat right? To do this simply run the following in your terminal: $~ git config --global push.default current</code></pre> git</code> will then implicitly assume that I want to push my current branch to upstream. With the configuration set up, I can now simply push my current branch to upstream with the simple command of: $~ git push</code></pre> That's really short and simple. Pretty neat right? Disclaimer: It's probably not a good practice but I like it since it fits my current git workflow. If I want to avoid using Git GUI tools, I definitely need to reduce the learning curve by making it simpler and easier than the tools that I'm used too. How to set zsh as the default terminal shell 2018-08-20T22:41:07+08:00 I prefer zsh</code></a> over bash</code></a> as my everyday shell. Unfortunately, zsh</code></a> is not the default shell on macOS. Here's a quick guide on how to make it as a default shell for your machine: 1. Install zsh</code></h2> Make sure zsh is available on your system. If not, install it with brew</code></a>. $~ brew install zsh $~ which zsh /usr/local/bin/zsh #output</code></pre>2. Set zsh</code> as default shell</h2> To set is as default shell, run the following in your terminal: $~ sudo sh -c "echo $(which zsh) >> /etc/shells" $~ chsh -s $(which zsh)</code></pre> Then, simply reopen your shell again and it should used zsh</code></a> as the default shell. That's it. To check which shell you're using</h3> If you are still unsure whether your shell is running zsh</code></a> or bash</code></a>, run the following in your terminal: $~ echo $0 -zsh #output</code></pre>✌️</center> Viewing the git diff since the last git pull 2018-08-07T17:32:55+08:00 To view the changes between your latest git pull</code> $~ git pull origin $~ git diff @{1}..</code></pre> @{n}</code> means the n-th previous value of HEAD</code>. You can refer the official docs on reflog Shortnames</a> for more. p/s: I am currently trying to dissociate myself from becoming too dependent on SourceTree</a> for daily git operations.

@faizmokh - Posts

Ramadan Menubar: A Simple Ramadan Countdown App

Migrating My Obsidian Vault From iCloud to Git

Some Notes While Setting Up My New MacBook

Installing Python 3.12.0 with asdf

How to Stash Only Staged Changes in Git

My Essentials Tools

Noteworthy Apps</h2> Beyond CLI tools, here are some applications that have been integral to my development workflow:</p>

How to Delete Github Repository Quickly

To delete a repository</h2> To delete a repository, run the following command</p>

To change from public to private repository</h2> To modify repository access, run the following command:</p>

References:</h2> gh cli documentation</a></li> </ol>

A Cheaper Way to Renew Apple Developer Account

How to Convert SSL Certificate From CER to DER Format

Additional info</h3> Make sure you pass in the -outform der</code> flag. Otherwise openssl</code> will default to pem</code> format</li>

How to Install Specific Version of Brew Cask

How to Fix Xcode 14.3 libarclite_iphonesimulator.a Error

How To Use Git Worktree To Checkout Multiple Branches At Once

Caveats</h2> One thing that I noticed when using worktree is that you can't checkout to the same branch that's already in worktree. For example, I can't checkout to example-branch</code> from main</code> branch.</p>

Conclusion</h2> git worktree</code> is a pretty useful feature but I would recommend you use it sparingly. It can get confusing if you have too many worktree available. I would recommend you to remove it once you're done with it.</p> Hopefully you find this helpful as a quick references.</p>

PHP missing dependencies

Replacing nvm with asdf to manage NodeJS versions

Runners - iOS app to manage Gitlab Runners

How to list all the git commits history for a specific file

How to undo a git rebase

How to setup Jenkins with Docker

What is the difference between Docker container and Docker image?

How to Clone a Git Repository With Submodules

How to fix Xcode: "Could Not Locate Device Support Files" error

How to Completely Remove Git Submodules Within a Repository

How to connect to Google Cloud SQL with Cloud SQL Proxy

How to create multiple screen previews in SwiftUI

How to use SwiftUI in a UIKit project

Initializing it programmatically</h2> To initialize it programmatically, set the SwiftUI View</code> as the rootView</code> of the UIHostingController</code>.</p>

Initializing it in Storyboard</h2> Using it in Storyboard requires a little bit more work.</p>

References:</h5> Apple documentation on UIHostingController</a></li> </ol>

How to use Xcode 11's Swift Package Manager in your project

Understanding LLDB contexts in Xcode

How to use Go Dep to Manage Dependencies

How to Change Git Branch Name

How to set default git push behaviour

How to set zsh as the default terminal shell

Viewing the git diff since the last git pull

`References:</h2> gh cli documentation</a></li> </ol>`

`Additional info</h3>`

Make sure you pass in the `-outform der</code> flag. Otherwise openssl</code> will default to pem</code> format</li>`
`x509</code> subcommand stands for` `X.509 certificate</a>, which is a standard format for public key certificates.</li> </ol>`

Caveats</h2>
One thing that I noticed when using worktree is that you can't checkout to the same branch that's already in worktree. For example, I can't checkout to `example-branch</code> from main</code> branch.</p>`

`Conclusion</h2> git worktree</code> is a pretty useful feature but I would recommend you use it sparingly. It can get confusing if you have too many worktree available. I would recommend you to remove it once you're done with it.</p> Hopefully you find this helpful as a quick references.</p>`

References:</h5>

Apple documentation on UIHostingController</a></li> </ol>