The downside to running on Heroku

So, sorry to anyone who was subscribed to the RSS feed for this and got spammed with v0.1.24 release announcements. I made a mistake and pushed a version of the entry that didn’t have a canonical ID assigned yet, and as a result, every time Heroku spun up, it assigned a new ID. This is something that’s happened before and I really ought to do something about it.

Three things come to mind:

1. Figuring out how to always make IDs get assigned in an idempotent manner (hard to do correctly)
2. Don’t run on Heroku so the assignments persist between executions (easy)
3. Add a pre-push hook to the repo that verifies that all entries alread have an assigned ID (???)

2 seems like the easiest approach for now, so that’s what I’ll probably do.

Verson 0.1.24 released

New functionality:

• The image rendition cache now gets periodically purged; the default is to delete renditions which haven’t been used in the last week (this can be disabled)

Bug fixes:

• entry.title can now accept the no_smartquotes parameter, which is necessary in Atom feeds
• entry.card now uses the same Markdown extensions as entry.body

v0.1.23 updates, oh yeah this is beta now

I neglected to mention that I set Publ to beta status in v0.1.22, which was a minor bugfix release, rather than moving to 0.2 like I previously stated. The changes for 0.1.22 were:

• Fixes to category Sort-Name
• Added support for regex path-alias hooks (this is configured on the Python/WSGI side, and has been working quite nicely over on beesbuzz.biz)
• Fixed a dumb bug in the cache-control headers

And then the changes for 0.1.23:

• Enable automatic smart-quote substitutions (this is the default setting, and can be overridden by passing no_smartquotes=True to entry.body/entry.more/entry.title)
• Improve the handling of last-modified times on entries (now there’s a Last-Modified header which only gets set when you want it to be)

My site templates

I released some of my site templates; hopefully this will be helpful to others.