-
Notifications
You must be signed in to change notification settings - Fork 5
Switch to GitHub Actions? #11
Comments
Auto-update needs all existing versions to be able to determine what versions it needs to add currently, I'm not sure how we'd avoid that requirement for the whole repo. Package.min.json all needs the full repo to correctly generate the JSON file that contains information on every library, and every version, and every file -- this is used to powered the data displayed on the website & the API. |
it sounds feasible, we would need to redesign some parts (which would be great!). However, the security implications are concerning |
what would be ideal to me is to store all our data into a database (instead of git) and serve them using the API. We can then have all sort of cron to update the search or the website in CI |
A simple way to fix that, is changing the code to use
|
How long does it takes for |
Hi
I'm wondering if using GitHub Actions or a similar "CI" solutions was ever considered?
Doing a regular clone of https://github.com/cdnjs/cdnjs every X hour probably isn't feasible, but Git supports
sparse-checkout
andpartial clone
(improved greatly in 2.25.0)I had a quick look at the autoupdate and packages tool, and all the other files only seems to be required for SRI generation, but I think that is fixable.
Assuming it is doable, should we switch? The main argument, as I see it, is "fewer moving parts".
The text was updated successfully, but these errors were encountered: