Update Vercel Deployment to Zola v0.15.3

[maydayv7]

No description provided.

[vercel]

This pull request is being automatically deployed with Vercel (learn more).
To see the status of your deployment, click below or on the icon next to each commit.

🔍 Inspect: https://vercel.com/ejmg/zerm/8NGTjSY9j34bKGZ4KnrehwLWuzei
✅ Preview: Failed

[maydayv7]

This is an already known issue:

• GLIBC error when deploying version 0.14.1+ to Vercel or CloudFlare getzola/zola#1713
• https://community.cloudflare.com/t/cloudflare-pages-zola-build-fails-glibcxx-3-4-26-not-found/316457

[maydayv7]

A quick dirty fix to get #53 to work would be to just upgrade Zola to v0.14.0 instead of the latest version

[kartva]

If I'm reading the documentation right, it seems that we can't change the build image. Instead, what we can do is build Zola from source, since Vercel does give an option to install Rust.

[ejmg]

adding rust into the deploy setup feels fragile but looking at this issue's history, it has been around for some time now.

that said, i've just spent the last 20 minutes or so trying to understand what /i/ would need to do in order to get this running so that zerm can handle > v0.14 zola features and still can't tell if we are allowed to define these changes locally to package.json or if I'll need to exclusively use the build settings (from my Vercel dashboard) as are described here

[ejmg]

man, it looks like keats got zola v0.15.3 working for his website using netflify. if changing the entire deployment setup turns out to be simpler, then maybe we should consider that too.

[kartva]

Any progress?

[ejmg]

unfortunately, no.

i haven't made the time to setup either a separate deployment mechanism (as i previously mentioned) or see how vercel can be made to work with a patch/work-around.

[ejmg]

i've knocked out a few PR's this past week, i will try to follow up on this one along with a few others.