Hello Jekyll

I’d like to divide it into three parts:

  1. Incentives
  2. Preparation
  3. Deploy

Incentives

Since six months ago I purchased a host with the most economic plan in Godaddy, trouble comes one after another.

  • Delay: timeout from L.A. to P.R.C is insufferable. I am still receiving caution mail from my DNS server.
  • Complexity: cPanel is a messy system and it is out of control without VPS plan.
  • Ceiling Effect: Imagine those difficulties could be solved, but there is no room for me to study the IT through blogging. Because everything is JUST pre-defined by Godaddy. I cannot conduct experimental work on that.

Preparation

First Attempt

WP deploying in host but not VPS is so dangerous that you would have NO idea about what would happen after you conducted several normal actions.

At first I followed this article to export my data. One of the most damned thing is that the tool it mentioned to export lead my host resources to upper bound.

Coincidently, my backup system just backed up the server after I install the plugin. Here are the table showing comparison:

date expire version size location
2014-12-11 Auto 3.9.2 258MB Server
2014-12-10 4:35am Auto 3.9.2 705MB Server
2014-12-09 4:35am Auto 3.9.2 33.2MB Server

More terrible thing is the overall host, including CPU Usage, Physical Memory Usage, I/O Usage, all went to high. I tried UI or SSH, but no access to restart the system. Damnned Godaddy!!!

Second one and Succeed

Later I got the useful toolkit. Just follow Binux’s article to normally export WP contents into XML files.

One thing I need to say concretely is about this plugin exitwp, which was used to convert WP .xml into .MDs.

Assume that I’ve put the xml file(s) into RamDisk (a directory)

1
2
3
4
5
6
7
8
9
10
11
12
13
14
cd /Volumn/RamDisk/		##	This is a temp directory
git clone https://github.com/thomasf/exitwp.git
xmllint wordpress.2014-12-10.xml > exitwp/wordpress-xml/wp.xml
cd exitwp

## Install dependencies, choose one of the methods
## method 1
pip install --upgrade -r pip_requirements.txt
## method 2
sudo easy_install pyyaml
sudo easy_install BeautifulSoup4
## go on next

python exitwp.py

Now, your old WPs had been convert into markdowns in the directory: exitwp/build/

Deploy

Next thing we need to do is install Jekyll on the local in order to do debug.
Create a new repo called $USER.github.io in your github.

1
2
3
4
5
6
7
8
sudo HTTP_PROXY="http://127.0.0.1:8087" gem install jekyll
sudo pip install Pygments
cd ~/Documents/github/ ## this is the place where you would like to host locally
git clone https://github.com/plusjade/jekyll-bootstrap.git hasset.github.com
cd hasset.github.com
git remote set-url origin [email protected]:hasset/hasset.github.com.git
git push origin master
jekyll serve

If you’ve successfully done the job above, now feel free visit your local demo.
After modification, you can repush this repo. The Github Pages would be updated within 30 minutes.

Bottom Line

  1. I used to comment on some blogs and found a strange issue, after refresh the comment would be vanished. Up to now I realized that this is because of the updating delay of git-pages system.
  2. The typo issues on my old diaries, which is not image links but also contains Latex zoteros and downloads, may not be fix until I got free time.
  3. I will continue opening my old blog until the host expired. But I will only post on github from now on.

References

0%