Welcome to digger EE trial! In order to get started with EE as a self-hosted option, the first step to get started with digger EE is to have the license key at hand. This would have been shared with you by the digger team. If you don’t have a license key, please contact us to arrange a demo: https://digger.dev/pricing

​

Step 1: Setting up the orchestrator:

Setting up the backend is the same as in CE so you can follow the relevant guide to setup using a docker image here:

• Helm chart guide: https://docs.digger.dev/self-host/deploy-helm
• Docker image guide: https://docs.digger.dev/self-host/deploy-docker

By the end of this you should have your orchestrator up and running internally, you will also have setup the internal github app for your org internally.

​

Step 2: Setting up the POC Repo

After you have the orchestrator up and running you will need a repo to test digger on. For using it with terragrunt you can rely on this example as a starting point: https://github.com/diggerhq/demo-terragrunt-parallel-ee feel free to fork it or clone and re-push it as an internal repo, or you can just copy the same structure, with digger.yml in the root of the repo as well as a workflow file digger_workflow.yml

Once you have the repo ready you need to install it to the image. So make sure to install the github app in your organisation, adding the POC repository to it.

In order to proceed with an example plan you will also need to set a secret called DIGGER_LICENSE_KEY and the value of the license key that has been provided above.

Since you are using

​

Step 3: Test an example plan

To test digger with a plan you can create a PR to one of your terragrunt directories. You will see that digger will start performing a plan and comment it in your Pull request like in the image below:

Now in order to perform the apply for this change you just need to comment digger apply which will go ahead and apply the changes in the right environment.