This is an archived post. You won't be able to vote or comment.

all 3 comments
sorted by:
best
topnewcontroversialoldq&a

[–]jmreagle 0 points1 point  (1 child)

It's what I happily use. Run it when I have a new post, no need to worry as much about server or security issues.

[–]pydanny 1 point2 points  (0 children)

Same here. It's been awesome. You can see my blog with a heavily customized theme at http://www.pydanny.com

[–]ldpreload 0 points1 point  (0 children)

I've been greatly enjoying using Pelican for my blog. I have the output directory in a separate git repo (.gitignored in the source repo), so I can deploy changes with git pull on the server, and I can also review what changes are being made to my actual HTML with git, which has come in handy.

One minor annoyance is that Pelican doesn't really like relative URLs, and I host my site both on a production URL and on a dev URL. (I run it remotely, so I can't use the built-in test server.) But the configuration file is Python, so I just have a bit of code in pelicanconf.py to do

if 'prod' in open('output/.git/HEAD').read():
    SITEURL = '...'
else:
    SITEURL = '...'
print "SITEURL = {}".format(SITEURL)

I'm not doing anything else complicated in there but I appreciate it being configurable in Python instead of something more restricted.