Closed anadahz closed 4 years ago
@anadahz I think this has to do with the fact that with the introduction of https://github.com/PrivacyLx/devops/pull/10 the mechanism for updating the website from git changed.
Now it does (check source) in the caddy config file:
{% if caddy_git_interval %}
interval {{ caddy_git_interval }}
{% endif %}
repo {{ website_git }}
args --recursive
path {{ website_docker_webroot }}
then hugo --destination={{ website_public }}
}
And I'm guessing that this tries to pull the git repo but if it doesn't detect changes it doen't execute the then command
.
I haven't tested this hypothesis yet.
Just redeploy the role
if the issue is in fact the one stated above, then we should add a cron job that redeploys the website. Or another solution.
Here's the previous code for the update job. It's the best so we might not use it:
Events on the website should expire right after the end of the event. Currently an old event with
date: 2019-11-02T18:00:00
is active and displayed on the homepage.