pelican installed, started, up we go
It's so easy to startup if you know, which software is fitting your needs:
Hundreds of different blog-tools exist. Few of them are pythonic some are complicated pelican seems to be beautiful
Pelican http://getpelican.com fits all I want: It is simple, pythonic and it produces static content. So the produced web-pages follow the keep it simple stupid principle. ReStructuredText is already known from writing sphinx documentation for adm6, but that is far from beeing blogged for now.
sl0, what is that?
In the linux operating system we can have a lot of different interfaces to be used for ip (internet protocol) connections. Most common there is ethernet today, these interfaces will be named eth0, eth1, eth2 and so on. At the times before we had DSL (digital subscriber line) widely spread, modems and isdn-lines did the job. The very first way of using these technologies for transportation of ip was called slip (serial line ip), and the first interface in linuxkernel was named sl0. OK?
Since those first impressions with RFC792 conform technology in 1994 I was convinced, all those specific vendor technologies would disappear. Thanks to Linus Torvalds and to all those cool guys spending their time in this arousing system until today.
only truth!
My blog will only have content of my own real life. Perhaps not the full truth, but never anything else but truth. And we know from the rest of the internet, about 50% of the news are faked. We just don't know, which 50%. ;-)
The main guidline is always kept:
Python 2.7.3 (default, Jan 2 2013, 13:56:14) [GCC 4.7.2] on linux2 Type "help", "copyright", "credits" or "license" for more information. >>> import this The Zen of Python, by Tim Peters . Beautiful is better than ugly. Explicit is better than implicit. Simple is better than complex. Complex is better than complicated. Flat is better than nested. Sparse is better than dense. Readability counts. Special cases aren't special enough to break the rules. Although practicality beats purity. Errors should never pass silently. Unless explicitly silenced. In the face of ambiguity, refuse the temptation to guess. There should be one-- and preferably only one --obvious way to do it. Although that way may not be obvious at first unless you're Dutch. Now is better than never. Although never is often better than *right* now. If the implementation is hard to explain, it's a bad idea. If the implementation is easy to explain, it may be a good idea. Namespaces are one honking great idea -- let's do more of those! >>>
Here I show you some bits from my memory, keep in mind: These computers work with electric current.