Block a user
MAIL_PASSWORD should be part of secrets
chore: Configure Renovate
Disclaimer proposal regarding https://docs.coopcloud.tech/federation/resolutions/in-progress/037/
devydave
deleted branch feat-cache-assets from coop-cloud/parasol-static-site
2026-02-21 09:27:04 +00:00
feat: adds caching of asset files
add caching to assets
feat: adds caching of asset files
I think for static sites it should not be a problem. You can also define your assets cache breaking in hugo when using their asset pipeline. I sent you a private message with the domain
private pull with deploy key seems broken
feat: adds caching of asset files
devydave
created branch feat-cache-assets in coop-cloud/parasol-static-site
2026-02-20 16:46:56 +00:00
fix: fails deployment when invalid HUGO_VERSION is given or download fails
devydave
created branch fail-deploy-on-invalid-version in coop-cloud/parasol-static-site
2026-02-20 14:56:40 +00:00
devydave
pushed to fail-deploy-on-invalid-version at coop-cloud/parasol-static-site
2026-02-20 14:56:40 +00:00
deployment does not fail when hugo version cannot be downloaded
Ok the error was copying the version tag from Github. The release is v0.130.0 but the recipe takes 0.130.0 as version without the v. But i think it is still helpful to fail the deployment if…
deployment does not fail when hugo version cannot be downloaded
@decentral1se The issue came up again after updating to the newest release, we set the HUGO_VERSION, but the request failed and we get the old 0.130.0 version. We are currently debugging it