Multilingual Ghost CMS Blog: 0. Why I Chose Ghost

Sanghun Kang — Sat, 26 Sep 2026 14:51:34 +0000

💡 I wanted to run my English blog and Korean blog in one place

Why I Chose Ghost

The requirements I wanted were as follows.

It had to have a CMS. GitHub Pages was far too cumbersome for writing and editing posts.
It had to be easy to back up in case I moved the blog later.
It had to be customizable to some extent according to my preferences.
It had to support multiple languages. I wanted to post in both Korean and English.

There were several candidates, such as Naver Blog, Tistory, and Velog, but the only one that satisfied all of these was Ghost CMS. With Ghost, you can either host it yourself or use a managed hosting service. In the case of self-hosting, I confirmed that it runs well even at $5/month. For managed hosting, the price varies by service, but it is around $10/month and convenient.

In fact, this is my third Ghost blog.

First. I wanted to use it for free, so I tried deploying it on the fly.io free tier. Since the storage was 1GB, it was not sustainable. If it is for a profile or landing page, this method might still be fine. If you want to try deploying on fly.io, this post explains the process in detail.
Second. I self-hosted it on a Vultr $5/month instance. Self-hosting itself is not difficult. If you use DigitalOcean's Official Ghost Droplet, you can deploy it right away even if you do not know anything. Self-hosting was not difficult, but to use the newsletter feature I had to configure Mailgun myself, and various small issues kept coming up, such as certificate expiration. None of it was particularly hard, and I could deal with it, but a lot of my time was wasted on these minor things.
Third. This blog. In the end, I paid for a managed hosting service. Why do I run a blog? To write. So the key is to focus on writing, and for that, a managed hosting service was the best option.

Money talks

After learning a bit of coding, I planned to host everything myself and try attaching all sorts of plugins, but the resources required for operations were greater than I expected, and for me, a managed service was the right answer.

Building a Multilingual Ghost Blog

However, Ghost itself does not natively support multilingual features. I bought several paid themes that claimed to support multiple languages, but they only offered half-baked functionality. Their approach was to create two Ghost blogs, set each one to a different language, and then tie them together under a single domain (in other words, making a separate English blog and Korean blog and combining them under one domain). But then you have to use two CMSs as well, right? I really did not like that approach. In the end, I decided to build it myself. It is not particularly difficult.

The approach I chose is as follows.

I solve everything in the theme without touching Ghost Core. In other words, it can be applied even if you are not self-hosting.
You only need one Ghost blog. This is not a method that uses multiple Ghost blogs.

I figured someone out there might have the same needs as me, so I decided to organize the trial-and-error process I went through.

Next post

Multilingual Ghost CMS Blog: 1. Making Posts and Pages Multilingual

Ghost can create a Collection of specific posts. Let's create tags for each language we want to support and make a Collection for each one to build a multilingual blog.

Originally published by Sanghun Kang on Sanghun's Blog.

Running Uniswap Frontend Locally for Testnet Environment

Sanghun Kang — Sat, 26 Sep 2026 11:57:18 +0000

Using Uniswap in a testnet environment is simple. You can change the network of the connected wallet to a testnet or specify the chain in the query string. For example, if you want to use Uniswap on the Ethereum Sepolia testnet, you can use the following URL:

https://app.uniswap.org/swap?chain=sepolia

However, the current Uniswap web interface does not work properly in the Sepolia testnet environment.

Uniswap Sepolia issues
We do have Sepolia v3 setup, although the Sepolia testnet is currently having issues in the Uniswap app. The developers are aware, and a fix is planned. Currently, there is no estimation for this completion.

Here is an older version without the bug. (two links are the same version, just different types of IPFS routing as some browsers will only use one) 
The v2 setup here is broken, please don’t use the v2. v2 is currently not available.
Verify these are official here.
Version 1 link 1
Version 1 link 2

This issue first occurred earlier this year, and I have been waiting for it to be resolved, but it has been neglected for almost half a year. I tried to access an older version of Uniswap that was provided in the official Discord, but it also doesn't work. The URL listed as 'Official here' is https://github.com/Uniswap/interface/releases?page=3, but it is unclear which version it refers to due to the passage of time. Which version on page 3?🧐

The Uniswap Interface is open source and available on GitHub. However, even following the guide, it still does not work properly.

GitHub - Uniswap/interface: 🦄 Open source interfaces for the Uniswap protocol

I have documented the process of running the Uniswap Interface locally and confirming that it works well in the testnet environment.

Issues and Solutions:

.env.defaults does not exist
- Solution: Create .env.defaults in the root folder
- Reference: https://github.com/Uniswap/interface/issues/7678
apps/web/src/utils/generated does not exist
- Solution: Create it manually
- Reference: https://github.com/Uniswap/interface/issues/7631
There are versions that work well in the testnet environment and versions that have issues. Below are the versions I have tested. I am currently using version 5.19.3.
- Works well in testnet
- 5.17.0
- 5.19.1
- 5.19.3
- Does not work in testnet
- 5.27.2

Below is the script I used.

Copy and paste this as it is, and it should work fine.

git clone https://github.com/Uniswap/interface
cd interface
git fetch --all --tags
git checkout tags/web/5.19.3
mkdir apps/web/src/utils/__generated__  # https://github.com/Uniswap/interface/issues/7631
# create .env.defaults file under project root.
# https://github.com/Uniswap/interface/issues/7678
cat <<EOL > .env.defaults
ALCHEMY_API_KEY='key'
AMPLITUDE_EXPERIMENTS_DEPLOYMENT_KEY='key'
APPSFLYER_API_KEY='key'
APPSFLYER_APP_ID="123"
FIAT_ON_RAMP_API_URL='https://api.uniswap.org'
MOONPAY_API_KEY='key'
MOONPAY_API_URL='https://api.moonpay.com'
MOONPAY_WIDGET_API_URL='https://api.moonpay.com'
INFURA_PROJECT_ID="123"
ONESIGNAL_APP_ID="123"
QUICKNODE_BNB_RPC_URL='https://api.uniswap.org'
SENTRY_DSN='http://sentry.com'
SHAKE_CLIENT_ID="123"
SHAKE_CLIENT_SECRET="123"
SIMPLEHASH_API_KEY='key'
SIMPLEHASH_API_URL='https://api.simplehash.com'
STATSIG_PROXY_URL='https://api.statsig.com'
TEMP_SCANTASTIC_URL='https://api.uniswap.org'
TRADING_API_KEY='key'
TRADING_API_URL='https://api.uniswap.org'
UNISWAP_API_KEY='key'
UNISWAP_API_BASE_URL='https://api.uniswap.org'
UNISWAP_APP_URL='https://app.uniswap.org'
WALLETCONNECT_PROJECT_ID="123"
UNITAGS_API_URL='https://api.uniswap.org/unitags'
FIREBASE_APP_CHECK_DEBUG_TOKEN='token'
EOL

yarn
yarn web start

This article was originally published on Sanghun Kang’s blog.