GitHub Fork

create github fork of ir engine repository the ir engine codebase is most easily deployed by forking it and configuring some secrets so that the included github actions can run the deployment for you you can run all of the commands that the \<dev/prod> deploy action runs manually if you so choose, and in that case, you don't need to fork the gh repo go to https //github com/ir engine/ir engine in the upper right hand corner, there's a button 'fork' click that, then click the account/organization you wish to fork it to you should be taken to your fork in a short time you'll need to set several secrets (runtime variables) for github actions by default github actions should be fully enabled, but you can double check by going to settings >actions allow all actions should be selected under actions permissions next click on secrets under settings there should be none by default click on new repository secret near the top of this page to make a new one you will need to make several secrets with the following names and values eks aws access key > the public key of the eksuser iam user aws region > the region of your ecr repos and eks cluster eks aws secret > the secret key of the eksuser iam user cluster name > the name of the eks cluster deployments enabled > set to true dev repo name > the base name of the dev ecr repository, e g ir engine dev (all references to the builder and service repos will append builder / \<service> to this value) dev repo url > the root url for your repos, i e everything before the /ir engine dev builder , e g 11111111111 dkr ecr us west 1 amazonaws com or public ecr aws/a1b2c3d4 if pushing to docker hub, this should have docker io/ before the organization name, e g `docker io/myorg private repo > set this to true if your repos are private; if they're public you don't need to set this at all repo provider > the provider of the container repos; currently allowed values are aws for ecr and dockerhub for docker hub if you go to the actions tab, you might see a few workflow runs with green checkmarks if so, you'll be re running the dev deploy workflow shortly; its initial run just ran a check to see if it should do a deployment based on deployments enabled , and since that wasn't set to true, it didn't do anything else now that that's set to true, re running it will trigger a deployment if you're asked to enable actions when going to the tab, and there are no runs listed after enabling actions, then you'll have to trigger the workflow by pushing new code to the dev branch