Fix auto-deploy issues

[badboy]

It would be nice if we can auto-deploy every day to update the "Next Meetup" on the frontpage.

However, we ... uhm ... might have been a bit excessive with that:

We can use the travis daily cronjob, but should make sure:

1. Only commit if last run was not within X hours (Travis can do "if not within 24 hours"
2. Don't trigger another deploy because of the commit (thus include the "[skip ci]" in the commit message)
3. Stretch-goal: Auto-import next RustBerlin/Hack'n'Learn meetups?

[LeoniePhiline]

Is there currently any auto-deployment functionality present?

Last week’s even is/was still shown as current.

The reason is that multiple Hack & Learn editions have been prepared, so no new deployments occur when these become current.

I’ve rerun the build and deploy job from last week to fix that:

https://github.com/berlinrs/berline.rs/actions/runs/18037204951

I wonder if auto-deployment should be in place but is broken, or if we should consider setting it up. Daily or even weekly might be enough.

[badboy]

No, no auto-deployment is there. It just was not enough for me to spend time on it ever. An empty commit or re-running a task was good enough.

[LeoniePhiline]

What I meant is a scheduled, regular, non-interactive rebuild and redeployment.

It becomes necessary to have the start page always up to date when meetups have been planned in advance.

[badboy]

I get that. I just answered your question and gave some context why I never implemented it more automatic. That doesn't mean it can't get fixed.