Ci/optimize site deployment

[f-hollow]

Description

This PR does some cleanup:

• Awesome pages are removed, no plans to use them for now
• Comments in the workflows are cleaned up
• Some workflows are limited to running only in this repo and not fork repos

However, the main change in this PR is the addition of a cron job to redeploy the portal every midnight at 0:05 AM (UTC time). There are two reasons for that:

• As we are likely to merge articles with publication dates in the future, this cron job will allow us to publish such articles automatically once the designated date comes.
• The deployment time from CI to our S3 bucket is currently around 2 minutes. We want to use the cron-deploy-hugo-website workflow to redeploy all files and reduce the deploy time in the deploy-hugo-site workflow by copying only the changed files in a merged PR as opposed to all almost all the files due to updated timestamps.
  • Implementing the upload of only changed files proved to be challenging due to the issues described in Issues syncing files. As a result, both deploy-hugo-website and cron-deploy-hugo-website will redeploy all files for the time being. The current deployment time of 2 minutes is still acceptable, so we can return to this feature when the upload time becomes less tolerable.

Issues syncing files #

The aws s3 sync command apparently compares files according to their timestamp and size. There are numerous threads where users discuss this and suggest that the sync should be based on the file hashes.

One common workaround suggested by users is to use the sync option --size-only, however, others warn that it might be a bad idea.

The workarounds in this issue and on stachoverflow might be worth implementing, but it will add complexity. As suggested above, we can return to this issue when the deploy time becomes less tolerable.

[f-hollow]

@marekmatej Thank you for your feedback regarding the awesome pages!