Setting up a production-grade remote cache for Turborepo using self hosted remote cache with AWS S3 and Lambda helps improve monorepo performance, especially in CI/CD pipelines like GitHub Actions. Below is a modular and generic Terraform setup using variables for easy customization.
This is related to the other blog post about GitHub Shared Action.
I want to make the same change to multiple GitHub repos and I want to limit manual steps as much as possible. As an example, I would like to push the the files of a source folder (source) to three of my repos. Here is one of the file:
I need to set up 3 GitHub workflows for 10 repo. For each workflow, it will run a similar bash script.
On my first trial, I did the following:
I have to run a shell script at repo B from repo A which hosts a python app. While I can spend the time to reinvent the wheel and fork the logic into python, it is best to keep thing simple by reusing what is already out there and proved to be working fine.
The js script in repo B is already wired up with a Github workflow. What if I can kick off that workflow remotely from repo A?
Github repository dispatch is the answer.