Open jag3773 opened 7 years ago
For openness of workflow and reducing the barrier to entry for others, would these make sense to run as CI scripts instead of Lambda? Make a simple JavaScript or Ruby or Python script and Travis-CI picks up the changes in the branch and runs the scripts. It's easier to show other organizations how to setup Travis than AWS Lambda. What do you think?
@klappy I definitely agree. We may even want this to be part of the Sphinx RTD generation process, that way it's baked in to every commit. Travis could run checks on it and deploy it to the correct S3 bucket on merge to master
.
We need to write an export function, triggered via webhook that collates the tD data together into a replica of the existing langnames.json endpoint.
This should be implemented as either a sphinx hook or possibly a standalone script trigger by Travis CI. On merge to
master
the resulting langnames.json file should be deployed to the appropriate S3 bucket.