# Publ: Development Blog

Entries tagged release

# v0.3.10 released

Posted Monday, December 10 at 8:37 PM (a year ago)

Just some bug fixes with view caching and image handling; in particular, remote and static images will now respect max_width and max_height for the sizing, and I fixed the way that inline images work (insofar as now inline images can work).

# v0.3.9 Released

Posted Wednesday, November 28 at 3:33 PM (a year ago)

This entry marks the release of Publ v0.3.9. It has the following changes:

• Added more_text and related functionality to image sets (an example being visible over here)
• Improved and simplified the caching behavior (fixing some fiddly cases around how ETags and last-modified worked, or rather didn’t)

I also made, and then soon reverted, a change around how entry IDs and publish dates were automatically assigned to non-published entries. I thought it was going to simplify some workflow things but it only complicated the code and added more corner cases to deal with, all for something that doesn’t actually address the use case I was worried about. So never mind on that.

(What happened to v0.3.8? I goofed and forgot to merge the completed more_text et al changes into my build system first. Oops.)

See below for more on the caching changes.

# v0.3.7 released

Posted Wednesday, October 24 at 12:59 PM (a year ago)

I’ve released v0.3.7, which just fixes a few issues around transaction management and overall indexing performance. Namely:

• The indexer locks individual entries as it’s working on them
• If an entry is being worked on, watchdog will ignore it
• Cleaned up a couple of transaction failures that can occur due to PonyORM’s optimistic locking behavior

# Publ v0.3.6 released (minor update)

Posted Saturday, October 13 at 3:01 PM (a year ago)

I just released v0.3.6 of Publ, which just allows it to work with databases other than SQLite. In particular this is part of testing more advanced heroku deployment options.

Right now I’m primarily focusing on improving the documentation, especially the quickstart guide, since people are finally showing interest in Publ but aren’t quite sure where to begin!

# v0.3.5 released, and sample templates updated

Posted Friday, October 12 at 3:01 PM (a year ago)

I’ve now released v0.3.5 of Publ. Changelog:

• Add support for listing deleted entries (accessible via view.deleted)
• Improved how the last-modified/etag reference was determined (also fixing a nasty bug where a site might crash if a file is deleted)
• Fixed a minor shaping bug

I’ve also updated the sample site templates with all of the changes that have happened since, uh, June, and also included some sample content so it’s easier to get started with it.

# Oops, v0.3.4 released

Posted Friday, October 5 at 1:28 AM (a year ago)

Turns out I never actually tested the If-Modified-Since handler, because if I had I’d have seen the glaring exception it threw.

Oh well, that’s fixed now. I think.

# v0.3.3 - now with ETag and Last-Modified

Posted Monday, October 1 at 11:16 PM (a year ago)

I’ve started working on Pushl in earnest now, and one thing that was really bugging me about this is that anything which polls feeds and entries would really benefit from having client-side cache control working. Which was a big missing feature in Publ.

Well, I finally implemented it, and I’m pretty happy with how I did it.

The short version: for any given view it figures out (pessimistically) what’s the most recent file that would have affected the view (well, within reason; it only looks at the current template rather than any included templates, which is pretty difficult to do correctly) and uses that to generate an ETag (via metadata fingerprint) and a Last-Modified time (based either on the file modification time or the time the entry was actually published).

There’s probably a few corner cases this misses but in general this makes client-side caching of feeds and such work nicely.

# v0.3.2: a smol bugfix release

Posted Tuesday, September 25 at 2:55 PM (2 years ago)

I found a few more annoying bugs that were shaken out from the whole PonyORM transition, as well as a couple of bugs in the new shape functionality. There’s probably a few more of these bugs lurking in the codebase (I mean, in addition to the existing bugs I know about), but here’s what’s changed:

# The shape of the float (v0.3.1)

Posted Thursday, September 20 at 10:58 PM (2 years ago)

Did you know that CSS3 has a style called shape-outline? It’s pretty neat, it makes it so that a floated object gets a shape based on the alpha channel of its specified image. But it’s kind of a pain to set up; in plain HTML it looks something like this:

<img src="/path/to/image.png" width="320" height="320"
style="shape-outline:url('/path/to/image.png');float: left">


and if you want a different shape mask for your image than its own alpha channel, you have to do a bunch of stuff like making sure that the image sizes are the same and whatever.

# v0.3.0 released

Posted Wednesday, September 19 at 12:46 PM (2 years ago)

Version 0.3.0 is now released, with the change from peewee to PonyORM.

As a result of this change you’ll have to do two things to your config file:

1. The database configuration format has changed slightly
2. Any existing databases have to be manually deleted/dropped/etc.; unfortunately PonyORM doesn’t provide a mechanism for deleting tables not under its control

Everything else should work identically as before.

# v0.2.2 released… and 0.2.2.1… and 0.2.3…

Posted Wednesday, September 12 at 1:27 AM (2 years ago)

Earlier today I pushed v0.2.2, which was a minor configuration fix for the markdown library to support table syntax.

Then I pushed v0.2.2.1 which was another configuration fix to fix that fix (oops).

Then in deploying updates I upgraded to Python 3.7, and promptly discovered that Publ doesn’t actually work on Python 3.7, so just now I fixed that, and released the fixes as v0.2.3.

# v0.2.1 released

Posted Tuesday, August 21 at 11:48 PM (2 years ago)

Just a couple of minor fixes in this release:

# Update to v0.2.0

Posted Friday, July 6 at 3:57 PM (2 years ago)

A few changes since v0.1.24:

• Updated code to use the current Flask cache-control API
• Only set cache-control for responses that don’t have a natural cache response
• Entry IDs and UUIDs are now semi-stably generated, in order to prevent (or at least reduce) problems like the last time

Publ itself is stable enough (and enough has changed since v0.1.0) that I felt that a minor version bump was a reasonable thing to do.

Anyway! While Publ has been running quite nicely on my website, I’d love to see more people actively using and developing it. This site in particular needs a lot of attention and probably reworking; my other top priorities are:

• A better installation/deployment guide
• Proper test coverage (rather than manual smoke tests)

# Verson 0.1.24 released

Posted Wednesday, June 27 at 7:55 PM (2 years ago)

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

Posted Wednesday, June 6 at 9:30 PM (2 years ago)

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)

# v0.1.19: creeping ever closer to beta status

Posted Sunday, May 27 at 5:22 PM (2 years ago)

The amount of stuff I’m having to fix in Publ to support beesbuzz.biz is diminishing rapidly! Here’s what’s happened since 0.1.18:

• Improved the Path-Alias redirection logic; now it will do a 301 Permanently Moved for inbound Path-Aliased requests, and if a Path-Alias points to an entry with a Redirect-To it will redirect directly to that URL instead (and it will be a 302, same as the old Redirect-To behavior)
• Pagination can now be weekly; you can use entry.archive(paging='week'), and a ?date= view parameter ending in _w will provide a weekly view instead.
• Better default formatting for view.range, and an addition of a week format parameter there

# In better news, v0.1.18

Posted Saturday, May 26 at 1:19 AM (2 years ago)

So aside from the Dreamhost issues, I would like to share what’s new in the latest version as part of my big “get my website online” push:

• PERFORMANCE: Improved the threading mechanisms around image renditions for better stability and performance
• BUGFIX: Made markup tagging work consistently between image types
• FEATURE: view.link() now allows overriding category
• FEATURE: You can now mark an entry with an Entry-Status of DELETED or GONE, which results in a 410 error instead of a 404 (be the envy of your web-developer nerd friends!)
• FEATURE: Error templates will automatically use the x00 error code as a potential fallback (e.g. error code 503 will also fall back to a template for 500)
• FEATURE: Entry titles can now have Markdown in them, and it usually works most of the time!
• BUGFIX: Now when running in debug mode you don’t end up with two watchdog threads
• FEATURE/QUALITY: Refactored the way error pages are handled, and now if you get a 404-type error on a page while the index is being asynchronously scanned, it’ll turn into a 503 with a Retry-After disposition in case it’s just something that hasn’t been indexed yet
• UX: View pagination URLs now all use id as the query parameter rather than a miasma of contextually-dependent start, last, or first which made no sense anyway

# Lots of bug fixes, and more image features (v0.1.17)

Posted Tuesday, May 22 at 5:00 PM (2 years ago)

Oh, it’s been a little while since I’ve posted an update, hasn’t it? That’s because I’ve been very busy building the templates for my personal site! In doing so I’ve greatly improved the way that view refinements worked, fixed a few silly bugs with image search paths on templates, and also added an easier way to specify background images in CSS, via the image().get_css_background() method.

I’m really excited to be able to bring my first fully-realized Publ site to the public; I hope it gets other people interested in what a flexible publishing system allows them to do!

Posted Saturday, May 19 at 12:00 AM (2 years ago)

Today I added two new useful features:

I also implemented the better date sort mentioned previously.

These things are already making my new personal site look way better and easier to use! I feel like I’m almost ready to flip the switch.

Oh, and I also improved the getting started guide, including adding basic setup instructions for Linux and Windows. Not that I’ve gotten Publ to run on Windows, yet, but documenting how to get the environment set up is the first step, right?

# Asynchronous workers

Posted Tuesday, May 15 at 5:21 PM (2 years ago)

Today I got two major bits of functionality in: Publ will now asynchronously scan the content index (which speeds up startup and fixes some annoying race conditions with entry creation), and it also asynchronously generates image renditions (which makes pages not take forever to load on first render, and will also use multiple CPU cores if available). Seems to work well so far.

I was running into scaling problems with beesbuzz.biz (what with there being a couple thousand entries and some pages with hundreds of images on it) and this keeps it feeling pretty good.

So, this brings us up to version 0.1.14.