banner
月落星河Tsukistar

月落星河Tsukistar

浩瀚中的伟大,孤独间的渺小
github
twitter
youtube
bilibili
email

The brief experience of migrating to WordPress and then migrating back to Gridea.

The cover image is from Ирина Мищенко on Pixabay.

I really overestimated Tencent Cloud's serverless version of WordPress application. If you want to ensure that the website stays online continuously, the database must be open 24 hours, and the cost of the database is too burdensome. Actually, the main cost is on the database. If the minimum computing power can be configured as 0.1 CCU, which is the minimum CCU required to maintain the connection, the cost can be reduced by half. Unlike general serverless applications, a blog built with WordPress requires both network requests to be responded to at any time and the database to maintain a connection when it needs to be queried.

In fact, if the database is not connected, it can be redirected to a guide page before entering the blog. However, due to the lack of technical ability, this solution had to be abandoned. Upon careful consideration, I don't really need to use a database. I just need a place to store articles and a place to put comments. By switching back to Gridea instead of WordPress, I don't have to worry about keeping the backend service running even if no one visits. I can open Gridea anytime to create and modify articles, which seems to be a joyful thing now.

The articles about migrating WordPress are on WeChat public account, and I don't plan to move them again. There are also some particularly useful plugins that I discovered when I started using WordPress again.

The blog built with WordPress is not very flexible, but after solving the issues with comments and adding header code to static pages, it is much more flexible than WordPress. I will write another article later to talk about the bitter process of configuring Waline comments.

Loading...
Ownership of this post data is guaranteed by blockchain and smart contracts to the creator alone.