Matchu
b9b0db8b3a
I'm looking into what it would take to update the archive on a regular basis. The commands right now *are* pretty good at avoiding duplicate work… but the S3 upload still seems like it's taking very long even to just validate what's in the archive already. We might have to build our own little cache rather than using `aws s3 sync`, if we want faster incremental updates? Here, I make a few quality-of-life changes to add a `archive:create` command that runs everything in a straight line. That way, I can let it run and see how much wall-time it takes, to be able to decide whether speeding it up feels necessary. (vs whether it's a few-hours task I can just set a reminder to manually run every week or something) |
||
|---|---|---|
| .. | ||
| archive/create | ||
| exported-user-data | ||
| build-cached-data.js | ||
| cache-asset-manifests.js | ||
| delete-user.js | ||
| export-users-to-auth0.js | ||
| setup-mysql-dev-constants.sql | ||
| setup-mysql-dev-schema-id.sql | ||
| setup-mysql-dev-schema-impress.sql | ||
| setup-mysql.sql | ||
| validate-owls-data.js | ||