Tech Notes

This is personal record for building a blog site using Astro web framework with Cloudflare integration. Consult with this pages: https://docs.astro.build/ and https://codeberg.org/minsoehan/cloudflare-astro-blog-sample for more details.

Create Cloudflare Worker with Astro Framework

npm create cloudflare@latest -- project-name --framework=astro

When you run this command, C3 creates a new project directory, initiates Astro’s official setup tool, select empty template there, and configures the project for Cloudflare. It then offers the option to instantly deploy your application to Cloudflare.

When designing for the web, one small but important detail is how browsers handle very long words or strings of text. On mobile screens especially, an unbroken word can stretch beyond the viewport and cause horizontal scrolling — something no user enjoys.

The modern solution is simple: add this to your stylesheet:

body {
  overflow-wrap: break-word;
}

With this rule in place, the browser can gracefully break long words when needed, ensuring text always stays inside the screen width.

Google Sheets isn’t just for storing data—it can also act as a lightweight database for your projects. With a few lines of Google Apps Script, you can transform your spreadsheet into a JSON API that any web app, static site, or script can consume.

In this post, we’ll walk through a script that reads a Google Sheet and serves its content as JSON.

Why Use Google Sheets as a JSON API?

• No extra server required: Everything runs inside Google Apps Script, hosted by Google.
• Friendly interface: Non-technical users can update the data directly in Google Sheets.
• Free & fast: For small projects, it’s cost-effective and quick to set up.
• Integration ready: Your frontend or external services can fetch structured data via a simple endpoint.

The Code

Here’s the complete Google Apps Script function:

Arch linux installation is not that hard if you do it simple as if:

• you don’t need dual boot and just want to install it as first OS on your drive.
• your computer is not too old and it supports GPT , UEFI , etc.
• you don’t need LVM, system encryption or RAID .
• you don’t mind to read the wiki pages.

See also: Official Installation Guide

Neovim is a fork of aiming to improve the codebase, allowing for easier implementation of APIs, improved user experience and plugin implementation.

Setting up Neovim

This is my neovim setup of personal preference. The setup or configuration is all included in ~/.config/nvim/init.lua file. Except native user settings, the following plugins are installed:

1. savq/paq-nvim plugin manager written in Lua.
2. hrsh7th/nvim-cmp auto-completion.
3. neovim/nvim-lspconfig language server protocol (LSP).
4. L3MON4D3/LuaSnip snippet engine.
5. rafamadriz/friendly-snippets snippets.
6. nvim-treesitter/nvim-treesitter treesitter for better syntax highlighting colors.
7. marko-cerovac/material.nvim material colorscheme.
8. nvim-telescope/telescope.nvim telescope search tool.
9. nvim-tree/nvim-tree.lua side bar file explorer.
10. nvimdev/indentmini.nvim indent line.
11. windwp/nvim-ts-autotag autoclose and autorename html tag.

The above plugins are not all plugins required because most of them require other plugins as dependencies. For example, nvim-cmp requires the followings:

In the following scenario, the safest option is using git pull --rebase or setting configuration by git config pull.rebase true.

Analysis of the scenario

1. Current state on Remote:
   file aaa.txt exits and file bbb.txt does not exist yet.
2. Current state on Local:
   file aaa.txt does not exist and file bbb.txt has been created.

In above scenario and local repository on the computer, git push will fail with the following message:

We often need to run our script avoiding certain situations like the followings.

1. Avoiding running a script as ROOT.
2. Avoiding running a script in background.
3. Avoiding running a script if the script is already running.
4. Avoiding unnecessary remains exist.

Avoiding running a script as ROOT

It is undesirable if a script was accidentally run as ROOT while the script is supposed to be run as normal user. To avoid this situation:

If you type Myanmar language online, you’ve probably met this problem:
Everything’s fine — until you type ေ (the “E-vowel”) second time (E.g. the second ေ in ကောင်း ေကာင်း) in a Disqus comment box. Suddenly, the whole page reloads and even Disqus comment box disappears.

This is not a random glitch. It’s a combination of:

• The Myanmar typing system, where the vowel ေ is traditionally typed before the consonant (e.g., type ေ then က to get ေက) for typing ကောင်း.
• Unicode order rules, which expect consonants first (e.g., ကောင်း).
• A Disqus input handling bug, which misinterprets the second typing of ေ as a “Back” or “Reload” key sequence in certain browsers.

The result? Your carefully typed comment is gone.