Eleventy vs Express - Githubissues

pdehaan / repo-health-report

Issue tracker stats for repos.

https://repo-health-report.now.sh/

Mozilla Public License 2.0

3 stars 0 forks source link

Eleventy vs Express #1

Open pdehaan opened 4 years ago

pdehaan commented 4 years ago

Currently, the site is just statically built via the awesome Eleventy library.

Not sure if we should port it to Express so it can be more dynamic.

Eleventy:

PROS:

I don't have to care about GitHub API request limits since those are generated once and then blah.

CONS:

Need to do a cron job which will fetch data for specified repos, then build site, then deploy site. Could do 2x day (noon and midnight) to keep it somewhat fresh, or just only at midnight to keep things less confusing (and not display a partial day of stats).

Express

PROS:

Site is dynamic and doesn't need to be deployed.

CONS:

Need to cache GitHub API calls so we don't exhaust API limits for our token.
If data is fetched and stored locally, without redeployment, how do we reliably store data so it isn't lost if we need to redeploy. 3rd party Redis sync? Something on GCP or AWS?

Either way, we can probably deploy using Zeit Now which is super easy and free.

pdehaan commented 4 years ago

If we stick with Eleventy, I wonder if we can somehow leverage GitHub actions to run our cron scripts and possibly see if it can do a Now server deployment.