This post is here for archival purpose, it is about how I moved my posterous blogs.
As I have written in a elsewhere, I recently consolidated all of various blogs into this one. Big one was posterous, especially because it is going away in a few days time, and I had two separate blogs (spaces as they used to call it) with them. While the other posts talked about why this one talks about How
Posterous provides a backup of all your articles, in XML format. while initially I thought this format may not be useful for importing into pelican, looking back, it might be. I haven\’t tried it, so I don’t know whether it helps. For more details refer to the pelican documentation Hopefully this is easier of the two routes.
First you need to \“get\” your postreous posts from their server to your local machine. You can use this original script.
I had to make some changes to the script, to make it work for me. I suggest you keep both of them handy. I am not a ruby developer. so my changes are rudimentary, not the way ruby developer would do. But based on the logic, some old style debugging, and stackover help for ruby syntax, I was able to get it to work.
For the script to work, you need (ruby off course) posterous \“gem\“. Consider this as a library or a package, if you aren\’t familair with Ruby. not being a ruby programmer, I didn’t know this, so I got the following error:
$ sudo gem install posterous [sudo] password for mandar: Fetching: ffi-1.7.0.gem (100%) Building native extensions. This could take a while... ERROR: Error installing posterous: ERROR: Failed to build gem native extension. /usr/bin/ruby1.9.1 extconf.rb /usr/lib/ruby/1.9.1/rubygems/custom_require.rb:36:in `require': cannot load such file -- mkmf (LoadError) from /usr/lib/ruby/1.9.1/rubygems/custom_require.rb:36:in `require' from extconf.rb:4:in `<main>' Gem files will remain installed in /var/lib/gems/1.9.1/gems/ffi-1.7.0 for inspection. Results logged to /var/lib/gems/1.9.1/gems/ffi-1.7.0/ext/ffi_c/gem_make.out
Some googline revealed that this is a know problem which can be fixed by
sudo apt-get install ruby1.9.1-dev
Now I was successfully able to install the posterous gem.
Modifying posterous gem
Original error went away, the script moved forward till the next error.
The option: username is invalid. (Ethon::Errors::InvalidOption) Please try userpwd instead of username.
Found the workaround on github posterous gem issues list
Now that initial problem went away, I started getting the problems in
the script itself. Good thing was I learnt
ruby script via printf method. Realized there was problem w/
save_media. So at first I commented this function call, and then
eveything was OK. I successfuly downloaded all my posts from one of the
Getting the images
Now that I was partially successful, I wanted to make sure I get the
images as well. So I added further debug/printf like statements, and in
the process learnt about
idiom With that I was able to
get the images as well from my second blog. (and then another pass at my
first blog, with images)
This is just the beginning
Now that you have your posts from posterous secured, the “deadline” pressure of posterous going away on April 30th, 2013 is removed. But I coulnd’t just use the converted files as is.
- Markdown files didn’t work with pelican directly, even after installing Markdown python module in my virtual environment. I ran into this error. (BTW, you should totally boormark the article on which the comment is made) So I hand converted the md files to rst. It didn’t take that long, but was a manual process.
- Links from posterous don’t work, especially for images that were uploaded to posterous. These links point to posterous\’ own Amazon S3 (which will also go away soon) But you have the images downloaded by the ruby script, so all the links need to be fixed (manually)
- I also did some editing. Not all my posts were moved. e.g. One of my posts “Why posterous rocks” didn’t make it to this blog :)
I am still learning the rst and pelican, so reference to local images folder works “partially” Luckily, most other places, I was already referring to third party image URL, so it didn’t matter.