Digger Docs
Search…
🚀
Deploy your first app
This tutorial shows you how to deploy a sample node application with digger. The repository we would like to deploy is here: https://github.com/diggerhq/a-nodeapp (opens new window).

To be able to deploy an application with Digger you should have:
  • GitHub account
  • AWS account

Let's try to deploy a simple node application as a container

Open https://dashboard.digger.dev and log in with your GitHub account.
Authorize Digger HQ. At this point, Digger is only accessing your email ID for login.
2.png

Press on the big orange tile that says "Press here to open AWS console Website"
You will then be redirected to the AWS CloudFormation template that securely creates a role and policy in your AWS account which allows Digger's AWS account to make changes.
-> Click the "Create Stack" button at the bottom of the page. This may take a minute or two, before you can move to the next stage.
Watch a video explainer here. It's also possible (but not recommended) to connect with a key/secret pair. It can be needed in a federated setup. More information on how to do this can be found here
Note: if you are deploying our example app, you will first need to fork the example app onto your GitHub account.
Click “Select repository to deploy” button and allow digger to access the repo you want to deploy.
Click on "Install and Authorise" DiggerHQ so that Digger can securely access your repositories.
5.png
You will then get the following screen. You can close the tab and return to Digger.
A list of repositories should now be visible on the Dashboard.
Pick the repo you would like to deploy
You will then be guided to the Summary screen

Review the options before clicking the “Deploy” button. Make changes if needed.
Check: have you selected the correct branch name e.g. main?
Some of the less frequently used options can be found under the "More options" toggle.
Additional options
When you're happy, press “Deploy”!
It can take 5-7 minutes to deploy a container. In the meantime you can check logs and deployment progress.

Yay - the deployment is finished!
-> Click the "Open App" button to see it live
Application deployed
This is it! Your AWS account is fully configured and your app is live 🎉🎉🎉

Digger does not require administrator-level access to your AWS account. It only asks for permissions necessary to provision and run applications managed by Digger.
You can see which permissions are required during the AWS account connection step:
Roles and policies
Permissions required
Copy link
On this page
Prerequisites
Deploying your first app
Appendix: permissions