Skip to main content

Moving to

My website was moved from WordPress to recently.

I used to run my blog on Bluehost. It was a three years contract. To be honest,  the Bluehost service was super stable. The website only failed less than three times in the last three years. However, the renewal price was over $300.

Hence, I started to explore an alternative. was an excellent option. However, I experienced it a few years ago. I want to try something new.

GitHub Pages is a trendy blog service. But it needs to be simpler to set up. Try if you have time. 

Eventually, I decided to go with I need something stable and long-lasting. has been a Google service since 1997. It is long enough to prove the service's stability. And it is free to use with some advanced features. Such as the custom domain, SSL and AdSense, etc...

It is easy to import WordPress content to Some online tools can convert the exported WordPress XML to format. It took me 15 minutes for data migration.

My website is a information technology blog. I post scripts and commands frequently in posts. does not have the code syntax highlighter. The highlightjs library is a common plugin for There are a lot of integration tutories on the internet.

Overall, is a lightweight content management service. Although it does not have many fancy features, it is enough for technical blogs.

Popular posts from this blog

Connect-NsxtServer shows "Unable to connect to the remote server"

When you run Connect-NsxtServer in the PowerCLI, it may show "Unable to connect to the remote server".  Because the error message is a little bit confusing with other login issues. It's not easy to troubleshoot. The actual reason is the NSX-T uses a self-signed certificate, and the PowerCLI cannot accept the certificate automatically. The fix is super easy. You need to set the PowerCLI to ignore the invalid certificate with the following command: Set-PowerCLIConfiguration -Scope User -InvalidCertificateAction:Ignore -Confirm:$false

How to List All Users in Terraform Cloud

Terraform has a rich API. However, the API documentation does not mention how to list all users. We can leverage the organization membership API and the PowerShell command  Invoke-RestMethod  to get a user list. 1. Create an organization token in Terraform Cloud. 2. Create the token variable ( $Token ) in PowerShell. $Token = "abcde" 3. Create the API parameters variable in PowerShell. $params = @{ Uri = "" Authentication = "Bearer" Token = $Token ContentType = "application/vnd.api+json" } Note: You need to replace ZHENGWU with your own organization name. And I used 100 at the end of the URI to retrieve the first 100 users. It can be any number.  4. Retrieve the API return and list the user's email address. $Test = Invoke-RestMethod @params $

Setup Terraform and Ansible for Windows provisionon CentOS

Provisioning Windows machines with Terraform is easy. Configuring Windows machines with Ansible is also not complex. However, it's a little bit challenging to combine them. The following steps are some ideas about handling a Windows machine from provisioning to post configuration without modifying the winrm configuration on the guest operating system. Install required repos for yum. yum -y install yum -y install yum -y install yum -y install epel-release yum -y install yum-utils yum-config-manager --add-repo Install  Terraform . sudo yum -y install terraform Install  Ansible . sudo yum -y install ansible Install  Kerberos . yum -y install gcc python-devel krb5-devel krb5-libs krb5-workstation