Posted Friday, July 26 at 12:36 AM (7 months ago)
Updated some packages.
Main things with Publ since the last release:
- Internal cleanups to how caching happens
- Stop spuriously-caching a bunch of stuff; in particular login/logout endpoint URLs no longer get cached
- Various cleanups
- Improve the way that built-in templates are managed
- Initial cruddy implementation of an admin authentication dashboard (although this isn’t quite ready for prime time)
The only Authl change is that email identities are now given as a full
mailto: URL; going forward all identity strings will be full URLs. This simplifies the UX for admin dashboards, in particular, and removes some ambiguity.
Posted Monday, May 13 at 11:11 PM (9 months ago)
Oh wow, I finally closed out the Publ 0.4.0 milestone. So, wow, this is a pretty big deal for me.
Changes since 0.3.23:
So that closes out the last three issues before I was ready to consider this usable by a wider audience. Neat.
There’s a lot of stuff I want to do for 1.0 of course, but also more importantly I need to vastly improve the documentation on this site, as well as collect things to make it easier for people to get started with Publ. I would absolutely invite people to make suggestions; have you looked into Publ, and been confused about what exactly to do? Please let me know!
The best ways to do so are to either hop onto my Discord channel or to open issues against the documentation site.
Posted Monday, March 4 at 3:47 PM (a year ago)
I’ve released Publ v0.3.19, which now finally has a tagging system, which is only one of the oldest issues that was still open.
Here’s a list of what’s been added or changed since 0.3.18:
I want to thank Karina Antonio for implementing image cropping.
Posted Wednesday, February 27 at 9:38 PM (a year ago)
I’ve just released v0.3.18, with the following changes:
- Add date grouping properties to entry
- Add a
pages property to
- Provide the current
category object to the error handler
- Support linking to non-image/non-entry local files
- Added, then removed, some performance micro-optimizations that only caused problems
More details about the major changes below!
Update: I released a hotfix as 0.3.18.1 because there was a last-minute bug that snuck in while I was trying to silence a new pylint error. Oops.
Posted Wednesday, February 20 at 3:42 PM (a year ago)
For those folks who want to import their content from Movable Type over to Publ, I’ve finally gotten around to writing an importer. Currently it only attempts to convert entry content and category metadata, and only using SQLite-formatted database dumps.
README.md for the (incredibly rough) usage instructions.
Eventually I want to try to automatically convert templates from MT’s scripting language to Jinja-Publ templates, although there’s a bunch of stuff that’s going to be difficult to port across and a lot of stuff is just plain not feasible to even try, so don’t expect that to become a major thing any time soon.
Posted Saturday, December 15 at 1:08 AM (a year ago)
v0.3.11 is now released, with the following changes:
- A more complete fix for how to handle image sets and inline images with respect to paragraphs
- Better cleanup for spurious empty paragraphs
- Improved internal entry link handling
Detailed descriptions of the changes are below.
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
- 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
Posted Friday, May 25 at 9:42 PM (2 years ago)
One of the overarching reasons I decided to build Publ the way I did was in order to take advantage of Dreamhost’s support for Passenger WSGI. I was expecting that to be the primary means of hosting my main site (which is way too big for a Heroku instance) and given how smoothly things were working with this site on Dreamhost I figured it wouldn’t be a big deal.
However, there was a huge monkey wrench thrown into things when I switched my site’s configuration over to Passenger; despite all of my configuration being exactly the same between publ.beesbuzz.biz and beesbuzz.biz, the rendition cache on beesbuzz.biz was getting its permissions set wrong, and there was some rather weird behavior with how it was making the temporary files to begin with.
In investigating this I attempted to upgrade my packages on publ.beesbuzz.biz, and all h*ck broke loose.
Posted Friday, May 18 at 12:00 PM (2 years ago)
There’s an old joke in programming, that the two hardest things to do are naming things, cache invalidation, and off-by-one errors. But this doesn’t pay sufficient respect to one of the other hardest things, namely handling date and time.
Posted Tuesday, May 8 at 12:00 AM (2 years ago)
I’ve had people ask me why I’m not building Publ using PHP. While much
has been written on this subject from
a standpoint of what’s wrong with the language (and with which I agree quite a lot!), that isn’t, to me, the core of the problem with PHP on the web.
So, I want to talk a bit about some of the more fundamental issues with PHP, which actually goes back well before PHP even existed and is intractibly linked with
the way PHP applications themselves are installed and run.
(I will be glossing over a lot of details here.)