Oh that is more than a little annoying.
Older versions of #Hugo supported escaping special characters in markdown links. Newer versions removed the ability to parse the escape syntax when they removed the need to escape special characters.
Going to have to get my versions of Hugo in sync.
Hugo is nice enough to provide official #NetBSD binaries, so ill probably switch to those short term.
Definitely going to submit a patch to upgrade Hugo in #PkgSrc when im done though.
@satchmoz not recommending, just sharing my setup: I run Hugo via snap, and it gets autoupdated within hours of a new release most days (I always check and am already updated when I read the announcement posts).
I deploy my site via GitLab CI, and an Alpine Linux image, where I install the latest Hugo binary to run the build. Since I keep the Hugo version in git (https://allthe.codes/maiki/interi/blob/master/.gitlab-ci.yml), I update it when I write the changelog post I do.
@maiki slick setup. Im not going to be that slick.
Right now the tentative plan is to have my NetBSD VPS check repositries setup on the SDF MettArray at some interval for changes and automatically pull down new versions of the site.
But that is as slick as im getting. My hugo binary is probably going to stay unmanaged by that workflow, but im inclined to work out of the #pkgsrc version once I get it up to date.
@satchmoz yeah, I'm doing that because I want to make money doing this, as well as the novelty of it. However, a **strong** advantage of Hugo over a DB-driven CMS is that it is highly portable, and has no security model to worry about!
It does sometimes bite folks in the ass when they want to do something a newer version does, but some other portion keeps them back, because that limits our ability to troubleshoot. However, even then it isn't overtly difficult to update. No DB schemas! ^_^
@maiki its the "no security model" thing that is really REALLY appealing to me.
Trying to build all my net exposed infrastructure with as little surface area for attack as I can imagine.
@satchmoz my initial drive to find an SSG was to create small sites for small clients that don't need to update anything except maybe once a year, but I would be stuck hosting as a target that whole time.
Single page bakery and restaurant sites, they don't need WordPress. But I also don't want to hand copy and paste them either. SSGs hit that sweet spot.
But then I really got into it, and haven't really marketed it yet! 😜
@maiki though I doubt im ever going to be get to the point where I need to follow hugo's current release immediately like your doing.