Home on Bumgu

Vector vs OpenTelemetry Collector: Log Collector Comparison

Sat, 10 Oct 2026 00:00:00 +0900

When collecting a large volume of node logs on EKS, it is difficult to decide whether to use Vector or the OpenTelemetry Collector based only on product descriptions or feature lists. I wanted to know how CPU and memory usage differ along the actual path: reading files on the node, sending them centrally, parsing them, and routing them.

So I deployed both pipelines on Kubernetes and sent them the same kind of 1 KiB logs. To give the conclusion first: in this single-node run, OTel had lower average CPU usage at 10k logs/s, while Vector used less memory. However, that does not mean either is the operational winner. The final output was a discard sink rather than a real storage backend, and from 25k onward the load entering the two collectors was itself different.

Reducing Persistent Disk Usage in GitHub Actions Docker Builds

Wed, 23 Sep 2026 00:00:00 +0900

The Problem

We encountered a runner disk space shortage while building Docker images in GitHub Actions. An image with a compressed size of 1.40GB failed twice with no space left on device in the same shared workflow, but at different points each time. At first, we thought the Dockerfile was too large or the cache had accumulated for too long. In this case, however, the cause was that a single image build result was being replicated into multiple storage locations.

Routing with Nginx and Envoy Gateway

Sun, 02 Aug 2026 16:07:35 +0900

Can Nginx Regex Routing Be Moved to Envoy Gateway?

There was one question we had to answer first in order to migrate the edge gateway from OpenResty (nginx) to Envoy Gateway: Can the regex location settings in nginx conf be moved to the Gateway API as-is?

Reading the documentation did not provide an answer. The Gateway API specification classifies regex path matching as Extended and does not specify its priority at all. It only says that it is left to the discretion of the implementation.

Trying Out the Loki-VictoriaLogs Proxy

Sun, 19 Apr 2026 18:50:12 +0900

I use VictoriaLogs as the log store in my personal Kubernetes cluster. Compared with Loki, it uses fewer resources and is simpler to install and operate, making it suitable for small environments.

Although Grafana officially supports VictoriaLogs as a data source, autocomplete and the Explore UX are not yet as smooth as Loki’s, so I often ended up going back to vmui.
Then I discovered a project called loki-vl-proxy. It is a proxy that uses VictoriaLogs as a backend and provides Loki API-compatible endpoints, so from Grafana’s perspective it behaves just like Loki. The idea is to store data in VL and query it using the Loki UX, so I decided to deploy it right away.

Building GKE with Terraform and Accessing It with Tailscale

Thu, 18 Dec 2025 14:21:02 +0900

I had quite a bit of GCP Free trial Credit left, so I tried building GKE as if it were for a real-world environment and restricting access at the network layer through Tailscale.

1. Terraform

The directory structure is as follows.

.
├── main.tf
├── modules
│   ├── gke
│   │   ├── main.tf
│   │   └── variables.tf
│   ├── network
│   │   ├── main.tf
│   │   └── output.tf
│   └── vm
│   ├── main.tf
│   └── variables.tf

I modularized the configuration by defining the required resources inside modules and creating the actual resources from the root main.tf.

Contributing to the Open-Source VictoriaMetrics

Tue, 25 Nov 2025 22:50:21 +0900

The origin

Last April, I replaced my company’s logging tool, Loki, with VictoriaLogs. It was a decision I was quite happy with, but one of our team’s requirements was still unmet: “include the log body in alert messages.”
Because of its design, VictoriaLogs returns only numeric values when an alert is triggered, so it could not include log text in the alert. I opened an issue and looked for a way to do it, but in the end the only answer was to “build it myself.”
As a workaround, I implemented a simple Webhook Server to fetch logs in the middle and used that.
Then I noticed that a few people with the same inconvenience had found my repository through searches and were forking the code.
Seeing that made me want to solve the problem rather than leave it as a simple patch. So I implemented the feature directly in the official VictoriaMetrics repository (specifically, in Vmalert) and contributed it.

Contributing to Open Source

Wed, 22 Oct 2025 15:20:22 +0900

I often use Github Actions as my CI tool.
As you all know, Github Actions workflows are written in YAML, and many of us have probably received a CI job failed notification because of indentation or incorrect syntax.
Then I came across this post on Twitter: This gha-ts project is open source software that generates a .yml file when you write a workflow in TypeScript.
It lets you generate type-safe workflows without worrying about indentation or syntax.
I noticed that setup already supported node, java, python, go, and dotnet, but not bun, so I decided to add bun setup.

(1) A First Look at Istio

Sun, 07 Sep 2025 11:17:37 +0900

1. What is Istio?

Many services are built using a microservices architecture (MSA).
MSA is particularly effective at reducing the propagation of failures by lowering dependencies between services.
However, as the number of services in an MSA grows, complexity also increases, making it difficult to know which services call which other services, whether communication is secure, and how to troubleshoot problems.
Istio is a tool that helps solve these complex problems.

(2) Replacing VMs by Building an In-House OpenStack - Nova, Neutron, Cinder

Sun, 06 Jul 2025 12:08:08 +0900

OpenStack Setup, Part 1

Nova

In OpenStack, Nova is the core component for managing compute resources in the cloud.
It manages the entire lifecycle of instances, including creation, management, and deletion.
It is also an essential component that works with Neutron, Cinder, and other services to connect networking and storage to instances.

Controller Node

1. Create Nova databases in MariaDB

create database nova_api
- Stores global information related to Nova’s API service (e.g. instance requests, cell information, high-level tracking, etc.)
create database nova
- The database for the default cell (cell1), where data about actual instances (virtual machines) is stored. It holds local information for each cell, such as instance state, allocated resources, and events.
create database nova_cell0
- A special-purpose database in Nova’s cell structure for instances that failed scheduling (instances that could not be assigned to any compute node).

GRANT ALL PRIVILEGES ON nova_api.* TO 'nova'@'localhost' IDENTIFIED BY 'NOVA_API_PASS';
GRANT ALL PRIVILEGES ON nova_api.* TO 'nova'@'%' IDENTIFIED BY 'NOVA_API_PASS';

GRANT ALL PRIVILEGES ON nova.* TO 'nova'@'localhost' IDENTIFIED BY 'NOVA_PASS';
GRANT ALL PRIVILEGES ON nova.* TO 'nova'@'%' IDENTIFIED BY 'NOVA_PASS';

GRANT ALL PRIVILEGES ON nova_cell0.* TO 'nova'@'localhost' IDENTIFIED BY 'NOVA_CELL0_PASS';
GRANT ALL PRIVILEGES ON nova_cell0.* TO 'nova'@'%' IDENTIFIED BY 'NOVA_CELL0_PASS';

2. Create the Nova user and grant permissions

Create the user
- openstack user create --domain default --password-prompt nova
Grant administrator privileges
- openstack role add --project service --user nova admin
Create the Nova service entity
- openstack service create --name nova --description "Openstack Compute" compute

3. Create Nova API service endpoints

$ openstack endpoint create --region RegionOne \
 compute public http://controller:8774/v2.1
+--------------+----------------------------------+
| Field | Value |
+--------------+----------------------------------+
| enabled | True |
| id | 08ab870ef54647399f31472a22e3ec23 |
| interface | public |
| region | RegionOne |
| region_id | RegionOne |
| service_id | 25ca5a23aa5b4375889d931e11467e61 |
| service_name | nova |
| service_type | compute |
| url | http://controller:8774/v2.1 |
+--------------+----------------------------------+
$ openstack endpoint create --region RegionOne \
 compute internal http://controller:8774/v2.1
+--------------+----------------------------------+
| Field | Value |
+--------------+----------------------------------+
| enabled | True |
| id | 59b80313047f41eb89e429600eff9a71 |
| interface | internal |
| region | RegionOne |
| region_id | RegionOne |
| service_id | 25ca5a23aa5b4375889d931e11467e61 |
| service_name | nova |
| service_type | compute |
| url | http://controller:8774/v2.1 |
+--------------+----------------------------------+
$ openstack endpoint create --region RegionOne \
 compute admin http://controller:8774/v2.1
+--------------+----------------------------------+
| Field | Value |
+--------------+----------------------------------+
| enabled | True |
| id | 12a2aab58e0f4a87b1f41e6e6486ef5c |
| interface | admin |
| region | RegionOne |
| region_id | RegionOne |
| service_id | 25ca5a23aa5b4375889d931e11467e61 |
| service_name | nova |
| service_type | compute |
| url | http://controller:8774/v2.1 |
+--------------+----------------------------------+

4. Install Nova packages

api install nova-api nova-conductor nova-novncproxy nova-scheduler -y

(1) Replacing VMs by Building an In-House OpenStack - Keystone, Glance, Placement

Sun, 29 Jun 2025 12:13:11 +0900

OpenStack Setup, Part 2

Background

Our VMs were no longer maintained and the license had expired, so I decided to replace them and started building OpenStack.
I had previously tried to ~~take the easy way out~~ install everything with OpenStack Helm, but it didn’t go well and the effort petered out…
At the Cloud bro seminar on June 4, I asked Seongsu Cho from NHN Cloud about it. He advised me not to try installing everything at once with Helm, but to follow the guide, install components one by one, and troubleshoot along the way. So I started from scratch, one component at a time.

Kubernetes Cluster Version Upgrade

Sun, 22 Jun 2025 13:25:06 +0900

Kubernetes Cluster Upgrade

Server: Vagrant VM (Ubuntu 22.04)
Current Kubeadm, Kubectl, Kubelet: 1.32.6
Kubeadm, Kubectl, Kubelet to upgrade: 1.33

Assuming the cluster is currently in production, I’ll perform the upgrade while a simple API server is running.

Kubernetes YAML, source code, Vagrantfile, etc.: GitHub

Current state

GET :8080/hello

method: GET 
Response:
{
Message: Hello world!
}

GET :8080/bye

method: GET 
Response:
{
Message: Bye world!
}

1. Control plane - Kubeadm

apt update
apt-cache madison kubeadm

If the command above only shows version 1.32.x, update the apt repository.

Log Aggregation with Kafka

Tue, 06 May 2025 15:52:28 +0900

Kafka is an MQ (Message Queue).
The original log collection pipeline was simple, as shown here:
The problem was that we had more than one or two servers.
As all the logs were inserted into VictoriaLogs simultaneously, bottlenecks caused processing delays and some logs were lost.
So we introduced Kafka as a Log Aggregator to centralize the logs. It can process large volumes of logs quickly and reliably, and preserve data safely without log loss even if a failure occurs. This led us to consider this structure:
However, unlike AMQP, Kafka is a Pub/Sub model where consumers subscribe to topics and pull messages, so the final structure became the following:

Building a Blog with Hugo

Tue, 22 Apr 2025 20:42:28 +0900

I was familiar with Markdown, so I used Velog as my blog, but I decided to host a blog with Hugo + GitHub Pages.
Here I’ll document the deployment process.

1. Hugo?

Hugo is an open-source SSG (Static Site Generator) written in Go.
I considered using Astro, based on JS/TS, but chose lightweight Hugo.
Hugo allows CSS and HTML customization through theme-override, and its GoTemplate supports constructs such as if and for loops.

Let's Try MCP (Model Context Protocol)

Sat, 01 Mar 2025 00:00:00 +0000

I attended Docker Community Day, held on February 27. One of the talks was by Geuncheol Yeom, an SRE at Karrot. It seemed like an interesting topic, so I gave it a quick try.

What is MCP?

Model Context Protocol (MCP) is an open protocol that enables seamless integration between LLM (Large Language Model) applications and external data sources and tools. Whether you are building an AI-powered IDE, improving a chat interface, or creating a custom AI workflow, MCP provides a standardized way to connect LLMs to the context they need.

Go - Functional Options Pattern

Sun, 16 Feb 2025 00:00:00 +0000

package main

import "fmt"

type Server struct {
	maxConn		int
	tls			bool
	id			string

}

func newServer(maxConn int, tls bool, id string) *Server {
	return &Server{
		maxConn:	maxConn,
		tls:		tls,
		id:			id,
	}
}

func main() {
	s := newServer(100, false, "server1")
	fmt.Println(s)
}

Here is a function that starts a server. When calling newServer(), you must pass arguments such as maxConn, tls, and id. There are only three for now, so it is hard to forget them, but with 10 or 20 arguments you may start forgetting some and the program will fail to run.

Resolving a TLS Error in Etcd Monitoring

Sat, 18 Jan 2025 00:00:00 +0000

Server OS: Ubuntu 22.04 Kubernetes environment: Kubespray
Prometheus: kube-prometheus-stack v65.1.1

1. Overview

The etcd service itself was installed directly on the Kubernetes nodes (on the host, outside Pods), rather than running in a Pod; the Grafana etcd dashboard is only for viewing metrics. Because etcd runs outside the cluster’s Pod network, Prometheus did not have a scrape target for it by default. I added <etcd-server>:2379/metrics as a target, but scraping failed because Prometheus could not access etcd due to a TLS issue.

Go - The Difference Between http.HandleFunc and http.HandlerFunc

Tue, 07 Jan 2025 00:00:00 +0000

1. http.HandleFunc

http.HandleFunc is a function.
It registers a handler to process requests for a particular path.
The registered function follows the func(http.ResponseWriter, *http.Request) signature.

1-1. Usage example

package main

import (
	"encoding/json"
	"fmt"
	"net/http"
)

type Response struct {
	Message		string `json:"message"`
}

func helloHandler(w http.ResponseWriter, r *http.Request) {
	w.Header().Set("Content-Type", "application/json") // Set the response header
	w.WriteHeader(http.StatusOK) // Set the status code in the header

	response := Response {
		Message:	"hello world",
	}

	if err := json.NewEncoder(w).Encode(response); err != nil {
		fmt.Errorf("failed to encode json reponse", err)
	}
}

func main() {
	http.HandleFunc("/", helloHandler) // Register the handler for the '/' route

	fmt.Println("Server start on port :8080")

	if err := http.ListenAndServe(":8080", nil); err != nil {
		panic("failed to start server")		
	}
}

kube-prometheus-stack: Managing Scrape Targets with an External Secret

Sun, 22 Dec 2024 00:00:00 +0000

As you add targets directly to additionalScrapeConfigs, the values.yaml file can grow to 1,000 or 2,000 lines and become difficult to manage.

So I changed the setup to keep Scrape Targets in an external Secret and manage them by referencing that Secret.

1. Create the existing ScrapeTarget in a file

Write the configuration that was previously in prometheus.prometheusSpec.additionalScrapeConfigs in values.yaml to a separate file.

prometheus-scrape-target.yaml

- job_name: server1
 static_configs:
 - targets: ["1.1.1.1:9100"]
 labels:
 alias: "server1"
 job: "node-exporter"
 component: "linux-server"
- job_name: server2
 static_configs:
 - targets: ["1.1.1.2:9100"]
 labels:
 alias: "server2"
 job: "node-exporter"
 component: "linux-server"

2. Generate a Secret manifest from the file

kubectl create secret generic --from-file=prometheus-scrape-target.yaml --dry-run=client -o yaml > additional-scrape-target.yaml The command above generates a Secret manifest YAML file that can create a Kubernetes Secret based on the file we just wrote.

Grafana, Loki ERROR - Failed to load the data source configuration for loki: Unable to fetch alert rules. Is the loki data source properly configured?

Sun, 08 Dec 2024 00:00:00 +0000

I deployed Loki on Kubernetes and connected it to Grafana as a Data Source, and it had been working well. However, on the Alerting rulers page, I saw an error message like Failed to load the data source configuration for loki: Unable to fetch alert rules. Is the loki data source properly configured?.

The Loki Helm Chart I use is version 6.22 from here.

1. Existing values

rulerConfig:
 storage:
 type: local
 local:
 directory: /etc/loki/rules
 rule_path: /rules
 enable_api: true
 alertmanager_url: "<alertmanager_url>"

/etc/loki/rules is read-only because it is the directory where alert rules are stored persistently. Rules created by clients such as Grafana are temporarily stored in the directory specified by rule_path, so that directory needs to be writable. Therefore, we need to mount rule_path as a volume.

Installing MetalLB When Using Kubespray

Sun, 22 Sep 2024 00:00:00 +0000

Last time, when I used kubespray and ansible to build a Kubernetes cluster, the final MetalLB installation failed. Today I’ll install it.

1. Install MetalLB

I followed the official documentation.

kubectl apply -f https://raw.githubusercontent.com/metallb/metallb/v0.14.8/config/manifests/metallb-native.yaml

Run the command above to install it.

1-1. Modify the kube-proxy ConfigMap

In IPVS mode, MetalLB performs load balancing by strictly controlling ARP responses. When strictARP is enabled in this mode, kube-proxy ensures that only the explicitly designated node handles ARP responses for an IP assigned to a node.

Connecting to a Database with Go and GORM

Wed, 18 Sep 2024 00:00:00 +0000

Recently, I’ve been studying Go to build a custom exporter for my company’s service application. I tried connecting to a database and inserting data with GORM, the Go ecosystem’s ORM.

1. Setup

1-1. Set up Go

go mod init // Initialize the project
go get -u gorm.io/gorm // Download the GORM package
go get -u gorm.io/driver/mysql // Download the MySQL driver

1-2. Run MariaDB with Docker

docker run -d -p 3306:3306 --name maria \
-e MYSQL_ALLOW_EMPTY_PASSWORD=true mariadb:10.9

2. Connect to the database

Now let’s connect GORM to the database.

Building a Kubernetes Cluster with Kubespray

Sun, 15 Sep 2024 00:00:00 +0000

Let’s build a Kubernetes cluster using Ansible and Kubespray.

1. Create VMs using Vagrant

I referred to kubernetes-certification-guide for the Vagrant configuration file.

setting.yaml

# settings.yaml
# box_name: "sloopstash/ubuntu-22-04"
box_name: "bento/ubuntu-22.04"
# box_version: "2.1.1"
vm:
- name: "controlplane"
 ip: "192.168.64.163"
 memory: "2048"
 cpus: "2"
- name: "node01"
 ip: "192.168.64.164"
 memory: "2048"
 cpus: "2"
- name: "node02"
 ip: "192.168.64.165"
 memory: "2048"
 cpus: "2"

Vagrantfile

require 'yaml'
settings = YAML.load_file(File.join(File.dirname(__FILE__), 'settings.yaml'))

Vagrant.configure("2") do |config|
 config.vm.box = settings['box_name']
 # config.vm.box_version = settings['box_version']
 config.vm.box_check_update = false

 settings['vm'].each do |vm_config|
 config.vm.define vm_config['name'] do |vm|
 vm.vm.hostname = vm_config['name']
 vm.vm.network "public_network", ip: vm_config['ip']
 vm.vm.synced_folder ".", "/vagrant", disabled: false

 vm.vm.provider "vmware_fusion" do |vb|
 vb.gui = true
 vb.memory = vm_config['memory']
 vb.cpus = vm_config['cpus']
 end

 vm.vm.provision "shell", inline: <<-SHELL
 apt update
 apt upgrade -y
 apt install -y wget vim net-tools gcc make tar git unzip sysstat tree
 echo "192.168.201.10 controlplane" >> /etc/hosts
 echo "192.168.201.11 node01" >> /etc/hosts
 echo "192.168.201.12 node02" >> /etc/hosts
 SHELL
 # vm.vm.provision "shell", path: "scripts/common.sh"
 end
 end
end

Create the VMs with the vagrant up command. After creation, connect and check with vagrant ssh <vm name>. You can also connect with ssh vagrant@<ip>. The initial password for the vagrant user is vagrant.

Building a k3s Cluster on Debian

Sun, 30 Jun 2024 00:00:00 +0000

I originally built a k8s cluster (one master and two workers) for testing at work, but it ended up being used in production. The servers are running Ubuntu Desktop, and because intermittent network disconnections have been occurring, I’m considering rebuilding it, so I did this exercise.

Download the official ISO

From the link above, I chose the desired architecture under the netinst CD image, downloaded it, and installed it in a VM.
Local environment: Mac OS Sonoma 14.5 | Macbook Air M1 | 16G RAM
VM installation environment: Debian 12.6 | 2 cores | 4G RAM

Issuing a Gmail OAuth2 Token (Bun, Elysia)

Wed, 19 Jun 2024 00:00:00 +0000

1. What is Bun?

bun is a JavaScript runtime like node.js. You can find more information and installation instructions at bun.sh. In this post, I’ll use the elysia framework, similar to express in node.js, and walk through issuing a Google Gmail OAuth2 token.

2. Create an Elysia app

Let’s create an elysia app. You can create one with the command bun create elysia ${app name}

If you look at the src/index.ts file:

AWS Summit Seoul 2024: A Retrospective

Sat, 18 May 2024 00:00:00 +0000

I attended AWS Summit Seoul 2024, held on May 16 and 17. I only went on May 17, and this is my recap.

After scanning the QR code I received by email to enter, I was given a name tag. Although I work in SRE, DevOps, and systems engineering, I listed my role as systems engineer, so that is what appeared on it.

9:30 Keynote

The keynote began at 9:30 in the auditorium on the third floor. We could watch videos and hear talks by the AWS Senior Tech Evangelist, Infralab CTO Dongwook Lee, Sendbird CTO Jeongjin Koo, and AWS’s Werner Vogels and Matt Wood. One of the key points was Frugal Architect. Cloud environments remove the hardware constraints that existed on premises and make it easy to build, with high scalability and flexibility. However, costs can be higher than expected, so an architecture that takes all of this into account and sets constraints is called Frugal Architecture. I thought this was an important point for a junior engineer to keep in mind. (Although our company is on premises.)

Persistent Data (PV) with NFS in an On-Premises Kubernetes Environment

Sun, 28 Apr 2024 00:00:00 +0000

Master Server

1. Install the NFS server on the master server

Install NFS (Network File System) apt-get install nfs-kernel-server
Start the NFS server systemctl start nfs-server

2. Specify the shared directory

Create the directory to share mkdir /data/nfsk8s
Specify the shared directory vim /etc/expoerts Add <directory path> <\IP>(\<permissions>) to the bottom of the file. Do not add spaces when entering permissions: (ro, rw) X → (ro,rw) O Apply permissions to all IPs /data/nfsk8s *(rw,sync,no_root_squash)

Kubernetes Errors I Encountered

Thu, 25 Apr 2024 00:00:00 +0000

When setting up a cluster with kubeadm in an on-premises environment to build a monitoring server (prometheus, zabbix), I ran into several errors. Here I’ve collected them.

1.

Unable to connect to the server: x509:
certificate signed by unknown authority
(possibly because of "crypto/rsa: verification error" while trying to verify candidate authority certificate "kubernetes")

This error can occur when running kubeadm init or kubeadm join. It usually happens when using an old or incorrectly configured config.

Docker - Creating an Image: Install Git on Ubuntu

Mon, 18 Mar 2024 00:00:00 +0000

Let’s use Docker to create an Ubuntu image with git installed.

1. Run Vanilla Ubuntu

Let’s run an Ubuntu image with nothing installed.

docker run -it --name velog-docker ubuntu:latest
This means run a container using the image from the latest tag of the Ubuntu repository, and name it velog-docker.

docker run -it --name velog-docker ubuntu:latest
Unable to find image 'ubuntu:latest' locally
latest: Pulling from library/ubuntu
f4bb4e8dca02: Already exists
Digest: sha256:77906da86b60585ce12215807090eb327e7386c8fafb5402369e421f44eff17e
Status: Downloaded newer image for ubuntu:latest
root@edd8a22995f6:/#

I had run it before, so it showed Already exists. I connected to Ubuntu and opened bash. Then, running the git --version command reports that it can’t find the git command. That’s expected, since it hasn’t been installed yet.

Practicing Kubernetes with Minikube

Sun, 10 Mar 2024 00:00:00 +0000

I followed the guide by subicura to do this practice.

If you’ve installed minukube and kubectl, you can start right away.

What is Minikube?

miniKube is a tool that quickly sets up a local Kubernetes cluster on macOS, Linux, and Windows. In other words, minikube makes it easy to create a Kubernetes cluster locally. It can even manage multiple clusters. To run a Kubernetes cluster, you need to install at least the scheduler, controller, api-server, etcd, kubelet, and kube-proxy. Depending on your needs, you may also need to install DNS, an ingress controller, a storage class, and so on. Installing Kubernetes is an important process, but when you’re first learning, it’s more important to learn how to use it in practice than to focus on installation. Minikube is a tool that makes this setup easy and quick. It can be used on Windows, macOS, and Linux, supports various virtual environments, and runs without problems in most environments. Source

Next.js-like Routing in React with vite-plugin-next-react-router

Mon, 26 Feb 2024 00:00:00 +0000

While taking a course, I ran into an error because vite-plugin-next-react-router no longer worked: its installed version differed from the version at the time the course was recorded. I resolved the error by referring to the official GitHub repository and this blog post.

1. Create a Vite project

Create a Vite project with yarn create vite.

➜ yarn create vite
yarn create v1.22.19
(node:11216) [DEP0040] DeprecationWarning: The `punycode` module is deprecated. Please use a userland alternative instead.
(Use `node --trace-deprecation ...` to show where the warning was created)
[1/4] 🔍 Resolving packages...
[2/4] 🚚 Fetching packages...
[3/4] 🔗 Linking dependencies...
[4/4] 🔨 Building fresh packages...
success Installed "create-vite@5.1.0" with binaries:
 - create-vite
 - cva
✔ Project name: … vite-practice
✔ Select a framework: › React
✔ Select a variant: › TypeScript

Scaffolding project in /Users/location/toyour/project/vite-practice...

Done. Now run:

 cd vite-practice
 yarn
 yarn dev

✨ Done in 13.75s.

Enter a project name and choose the options that suit your needs. I chose React and TypeScript.

Applying SSG to a Next.js Project

Sun, 11 Feb 2024 00:00:00 +0000

My website is built with Next.js. Although the Project and Career tabs here are small web pages, I wanted to try pre-rendering them with SSG, so I gave it a try.

I’ll apply it to this page.

Development environment Next.js 13 TypeScript

1. Existing code

import thumbnailLively from '../public/images/works/Lively_main.png';
import thumbnailWhatCandy from '../public/images/works/whatCandy.png';
import thumbnailSpotify from '../public/images/works/know-your-spotify.png';


const Projects = () => {
 return (
 <Container>
 <Heading as="h3" fontSize={20} mb={4}>
 Projects
 </Heading>
 <Layout title="works">
 <Section>
 <ProjectGridItem title="Lively" thumbnail={thumbnailLively} gitRepo="Lively">
 Description...
 </ProjectGridItem>
 </Section>
 <Section>
 <ProjectGridItem title="what candy" thumbnail={thumbnailWhatCandy} gitRepo="what-candy">
 Description...
 </ProjectGridItem>
 </Section>
 <Section>
 <ProjectGridItem title="know your Spotify" thumbnail={thumbnailSpotify} gitRepo="know-your-spotify">
 Description...
 </ProjectGridItem>
 </Section>
 </Layout>
 </Container>
 );
};

Previously, I passed prop values to components and rendered them as shown above.

Using the Spotify API (Node.js, Express, React)

Wed, 31 Jan 2024 00:00:00 +0000

GitHub link

I originally planned to implement this with Next.js, but since this was my first time implementing OAuth2.0-based login and I was not very experienced with Next.js, I built it with Node.js + Express + React instead.

Spotify uses the OAuth2.0 framework.

First, here is what we need to use the API:

code: Used to exchange for an access_token and refresh_token
access_token: The token required to retrieve the actual information
refresh_token: Used to obtain a new access_token when it expires
client_id: The identifier for the Spotify Developer app (issued to the developer)
client_secret: The secret key for the Spotify Developer app (issued to the developer)

The flow is:

Data Fetching with CSR and SSR

Fri, 26 Jan 2024 00:00:00 +0000

While developing, you’ll encounter both CSR and SSR. In this post, I’ll show how to use these two approaches in Next.js to make a GET request and receive JSON data.

1. The difference between CSR and SSR

CSR (Client-Side Rendering)

Concept When a website initially loads, the server sends only HTML and basic JavaScript code to the client; the content that will actually be visible is initially empty.
How it works When the JavaScript code runs on the client, the client requests and receives the necessary data from the server, then uses that data to build and render the page dynamically.

About Next.js getStaticProps()

Tue, 23 Jan 2024 00:00:00 +0000

Hello. In this post, we’ll take a look at pre-rendering, one of Next.js’s defining features.

1. Pre-rendering

Before talking about fetching data, let’s discuss one of the most important concepts in Next.js: pre-rendering. By default, Next.js pre-renders every page. This means that instead of having client-side JavaScript do all the work, Next.js generates each page’s HTML in advance. Pre-rendering can improve performance and SEO. Each generated HTML page is associated with the minimum JavaScript code needed for that page. When the page loads in the browser, that JavaScript runs and makes the page fully interactive. (This process is called hydration.)