Post another thought from Fargo

I’ve been playing with the Fargo blogging software from Dave Winer at Scripting.com It puts your blog info into an S3 bucket, then has links to WordPress, so that you can use Fargo’s outliner to edit your post, then publish it directly to WordPress.

I just found something else that’s really cool. I moved my “Posts” page to a sub-page (after creating a static home page on my WordPress blog) and the postings automatically followed my “Posts” page. Nice job, Dave!

 

Another thought on Fargo…

It’s a bit odd/disconcerting to see that the postings in Fargo _(the outliner)_ are in oldest-to-newest order (top-to-bottom), while the home page shows newest on top. This is as it should be – there’s just a need to make that mental conversion.

Ahah. Just create the new item in Fargo above the older ones and it all comes out OK.

Back to IPv6…

I purchased this VPS from HostFolks for testing IPv6. The VPS came with a handful of IPv6 addresses in addition to the single IPv4 address they normally provide. (Be sure you ask for a server in Germany, or verify that the VPS does have IPv6 capability – not all their sites do.)

IPv6 really “just works out of the box”, unless you need to do something tricky on your system. The web server, ssh connection, etc. all acted as expected. I did have to add special configuration (udp6) for the SNMP agent, but that’s a pretty specialized configuration.

Building a small server

This is a VPS with only 128Mbyte RAM and a 500 MHz processor (!) It’s tricky to configure it.

I may get around to documenting how I installed Ubuntu 10.04 (32-bit, to save RAM), installed the WordPress, then tweaked the system to remove as much cruft as possible. I also minimized the number of Apache processes, since I never expect more than a couple people to use the blog at the same time.

Yeah. And I also installed webmin to make it easier to administer.

Of course, the real reason I set up this server was so that I could play with IPv6. The name of the server is, after all, ipv6-richb.com. I’ll probably write about that later.