GitHub Actions

kick off github actions in github, if you go to back to the actions tab, you should see a dev deploy action click on it, and you should see a page showing its status, which should be all green checkmarks or indicators that things didn't run in the upper right, click re run all jobs this will start it again, and now that deployments enabled is set to true, it should attempt to build and deploy the builder (if actions were disabled at first, you'll have to merge additional code into the dev branch to get it to start the dev deploy process) overview of the build process the full build and deployment process works like this github actions builds just enough of the ir engine monorepo to fetch any installed ir engine projects github actions pushes this builder docker image to the repo ir engine \<release> builder in ecr github actions updates the builder deployment to point to the builder image it just created the builder deployment spins up the builder docker image on its single node the builder connects to the deployment's database and checks if there is a table user this is a proxy for the database being seeded; if it does not exist, it seeds the database with the basic ir engine schema, seeds the default project into the database and storage provider, and seeds various types the builder downloads any ir engine projects that the deployment has added the builder builds the docker image for each service concurrently using these projects, building them into the client files as well as copying them so that the api and instanceservers have access to them if serving client files from the storage provider, the client files will be pushed to s3 the builder pushes these final docker images to the repos ir engine \<release> \<service> in ecr (not the client image if serving client files from the storage provider) the builder caches all of the layers of each docker file in s3 for faster build times on subsequent builds the builder updates the main deployment to point to the final images it just created the main deployment spins up the final docker images for the api, client (optional), instanceserver and taskserver services